chris.denovellis wrote:Attached is screen capture.
Running Chrome 30, Windows 8, on an AMD APU.
Firefox is a little better but similar performance.
You're right, bandwidth isn't the issue here, it's the decode time. You are decoding in ~27 ms, so that is limiting you to <40 fps. Typically each free physical CPU core on your system can handle about 720p30 via ORBX.js. What is the CPU config/speed/corecount of your system? Also make sure you don't have any extra tabs running in the background, as those can also eat up CPU cycles if they are running canvas/flash etc.
I am going to work on a simple substitute native launcher URL this week (that works with identical GUID, command line, etc.), and I'd like to have you retest using that in place of the JS client. This way we'll confirm if JS decode speed is what is dropping you below 60 FPS.
Thank you for the feedback. This is very helpful.