WARadioControl
New member
My son received the Basic version for Christmas. We got it running on his desktop machine without too many problems and it's been running great for days.
Then, this morning, it suddenly began acting weird. After a fresh restart, the first flight (any aircraft) would be normal. But second and subsequent flights would yield about 1-3 frames per second. That's not an exaggeration... it was really that slow. Restarting the software fixed it for the first flight every time.
I went through all the usual Windows XP configuration options trying to find anything that gave a clue. Task Manager showed RealFlight sitting at 100% CPU (true whether video was working properly or not) but the memory consumption was within acceptable limits and we weren't hitting the pagefile.
I finally found it by accident: Running Basic in full screen mode causes this behavior. Being in "resizable window" mode fixes it. Interestingly, this is true even if you manually expand the resizable window to occupy the entire screen! Something about clicking that center box in the upper right corner changes the way Basic operates and really, REALLY damages its video operation.
Apparently he had been running it in resizable mode for the first couple of days, and only this morning decided to put it in full screen mode.
Very weird. Thought I'd pass it along in case it helps anyone else. If you're having video problems, get out of full screen mode and see if things get better. They sure did for us.
Thanks!
Then, this morning, it suddenly began acting weird. After a fresh restart, the first flight (any aircraft) would be normal. But second and subsequent flights would yield about 1-3 frames per second. That's not an exaggeration... it was really that slow. Restarting the software fixed it for the first flight every time.
I went through all the usual Windows XP configuration options trying to find anything that gave a clue. Task Manager showed RealFlight sitting at 100% CPU (true whether video was working properly or not) but the memory consumption was within acceptable limits and we weren't hitting the pagefile.
I finally found it by accident: Running Basic in full screen mode causes this behavior. Being in "resizable window" mode fixes it. Interestingly, this is true even if you manually expand the resizable window to occupy the entire screen! Something about clicking that center box in the upper right corner changes the way Basic operates and really, REALLY damages its video operation.
Apparently he had been running it in resizable mode for the first couple of days, and only this morning decided to put it in full screen mode.
Very weird. Thought I'd pass it along in case it helps anyone else. If you're having video problems, get out of full screen mode and see if things get better. They sure did for us.
Thanks!
