For a bug to be recognised, we need a lot of information from you. We need to know what platform the program is running on, which means your processor type, speed, architecture, RAM amount, operating system, and graphics card make, model and specification.
You can get this information from your computer by going to the start menu in windows, choosing "Run..." and entering "dxdiag" in the box. Pressing enter will bring up DirectX's diagnostic tool which will show a little progress bar in the bottom left. Once this has filled completely, press the "Save all information", and it will create a text file which you can copy and paste into a post here between [code][/code] BB code tags.
We need to know
how you made the bug appear, from the very start, which means a step-by-step process of how one of us could reproduce it with our own systems.
We need to be sure that this was achieved on a clean Orbiter install, and about anything else which is relevant, for example game controllers you might have attached which could be miscalibrated.
Finally, we need to know what Orbiter had to say about this situtation. There's a file inside your Orbiter folder, just next to Orbiter.exe (the one you run to launch Orbiter) called Orbiter.log, and another called Orbiter.cfg. We need to see the contents of both of those files, preferably posted in here between [code][/code] tags, or put into
http://www.pastebin.com/ and linked in to a post here.
Without this data, it becomes all but impossible to assist you.
