Originally posted by secondeye
Installed the new version, tried it with and without 10 FPS.. 10 FPS is just the same thing much slower.. KOS is now an endless loop.. (Well, I gave up after 5 replays) and punts are sometimes 3-4 replays before it finishes.
If you have the version that detects the frame rate, players should never move slower at 10 than at 20. Their movement should be rougher since there are fewer frames, but never slower.
Originally posted by
This was a known issue with the previous versions, happening on any long play, but now it's much worse. without wading through the 240 pages is there any other explanation or fix?
I saw this before in earlier versions, and I always knew the framerate fluctuated slightly, but I never thought this was the cause.
At 20 frames per second, Bort has basically doubled the amount of array accesses required to generate a frame, and added an addition, division, and some associated logic. The extra work involved is adding more time to the frame calculations and taking up time the browser could probably use to finish drawing. So, the only explanation I have is this: "your browser is getting inundated with drawing requests and just isn't servicing them fast enough".
If the thread that actually draws the elements (which I have no control over) takes too long to do it's job, the thread that keeps the play timing actually passes it up. What's happening is that on longer plays, the graphics are so far behind that they're still drawing once the postDelay kicks in and changes the play. The postDelay starts up after the timing thread completes so as far as the script is concerned, the play is over.
Several people are recommending to increase the postDelay to watch the whole play. But, increasing the postDelay does not fix the script. When you increase the time the script has to draw the frames, you're not watching the replay at 20 frames per second any longer. Instead of watching 200 frames in 10 seconds, you're watching 200 frames in 15. Your frame rate has gone down and players are actually moving slower.
While working on adding the fields and shadows and what not, I said that the graphics don't scale well at all. This looks like a perfect example of that. If 20 frames per second don't work for you, then try replacing the field with the original ugly as sin football field (it's the only gif that occurs in the field list). If it still doesn't work, put it back at 10 and leave it alone. If it still doesn't work after that, then honestly, I really don't know what to tell you right now.
