I would think that very few people have such slow machines and while
they are out there do they really form part of your target audience?
What exactly are you doing to exercise the machines heavily?
Last year I worked on a project that involved animating 150+ avatars on
screen together (with depth queues and collision detection) and
naturally while the clients machines ran fine, I knew that for many
people the experience would be poor - their machine would be unable to
sustain the frame rate.
I decided what the lowest acceptable frame rate was and built in a
counter to measure the actual frame rate on the users machine. If the
frame rate dipped below the acceptable level I reduced the number of
avatars until the frame rate recovered. This worked very well. It could
also be used to increase the avatars if the user had a very fast machine.
So depending on your particular usage, you may be able to adapt to the
users machine capabilities.
Paul
On 10/04/2011 01:43, Anthony Pace wrote:
How do you do your testing?
Do you still have slow machines to test everything on? do you
virtualize it and assign a slow processor speed and fewer resources?
or do you have another method?
I used to test apps on an old Compaq p3 633 mhz (if it ran well there
than I could trust it would run almost anywhere); however, I don't
have access to it anymore, and I totally need some accurate benchmarks.
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
