The two views definitely render differently so cannot be representative are a true benchmark. Both need to render exactly the same. I wouldn't say a fixed view is ideal but would prefer the camera to travel around the scene on a fixed path to show performance with high poly counts and low.
A longer term graph of FPS may also be more useful as a comparison rather than a fluctuating counter + average fps. I certainly think benchmarks are very useful in the decision of which engine to choose but there are so many other factors including the open source aspect and the support give from the team behind the product. I can't speak for Flare3D but Away3D certainly has that team and support. As you can see from the reaction of people so far, providing a benchmarking example is going to be open to a lot of criticism as people try to defend their favored product - which is only natural, but also try to highlight problems/inconsistency, etc to prove/disprove the validity of the benchmark. You may also want (if you plan to evolve this) do a feature comparison - Away3Dlite or other engines, could then be included in the comparison. To sum it up, I think a benchmark is useful tool to have, but in this case it doesn't - yet - hit the mark and still requires work. Greg
