Thanks for the info folks - you have answered a lot of questions- many I didn't even ask. The issues of frame rate manipulation (though I'm not using MVP, it won't load to my hybrid CPU motherboard), is of course in the basic VIRTU and is probable cause for something I've had problems with in Flight Simulator. The basics of crashing to the desktop on exiting from one aircraft to load another sometime, and one that has really been causing me headaches (worse if it was for real), ....improper vectoring from air traffic control on instrument flight rule approaches to some airports.
At times, ATC will vector me to the course to intercept the ILS radial as much as 60 miles from the airport. That is an absolute no-no not gonna work situation. The ILS localiser can not be received more than 25 - 26 miles from the airport. Ideally you are vectored to intercept the localiser at around 10 to 15 miles from the runway threshold and you will then establish on the localizer and intercept the glidescope signal at around 5 miles from the runway threshold. This is uber important because instrument flight rules are used when and because you can't see anything with the naked eye. You see where you are and where you are going through your instruments. A vector for localizer intercept at 60 miles out will never bring you anywhere near the airport, and in mountainous (or high hilly) areas can bring you smack up against terra firma because ATC tells you what altitude you should be flying as you near the airport and the lowest altitude you need to be at to acquire the glidescope signal.
The core operating parameters for Flight Simulator to know where you are in space (gamewise) and how far from an airport, is calculating aircraft image frame rates and the stationary airport frame rates. I don't pretend to know the math for this but it is the only logical way for a ones and zeros computer manipulation to place things in time and space. I'm using deductive reasoning for this conclusion - I don't know for sure. But - BUT - if Virtu is selectively deciding when and if it will send or use a frame, by the time you complete a 5 - 6 hour flight. Your aircraft image (or frame history) is not where Flight Simulator has calculated it to be in relation to the airports stationary image over time - ergo vectoring directions from air traffic control (ATC) that thinks you are 30 miles away when you are 60 miles away. At night, in heavy clouds or nasty weather, that can really spoil your day and more so when it's an airbus 340, or 747 and close to 300 or more people sitting behind you waiting to get home to their loved ones.
And if VIRTU is over calculating frames by doubling them or something, that could explain why my video card is getting so hot. Virtu is drivng it to the hilt dealing with the Flight Simulator frame rate calculations.
Well who asked for all that - ignore my pilot talk. But as soon as this response posts, the MSI card comes out - the Nvidia drivers are deleted, and as i'm using i-mode, I'll see just how good the 4000 series Ivy bridge IGP is.
P.S. Goodbye VIRTU
Thanks all for your great support.
Facebook
Twitter