I noticed this in the log (highlight added):
Code:
Devices accepted: 5
000000.000: [ ] RGB Emulation (SW)
000000.000: [x] Direct3D HAL (HW)
000000.000: [ ] Direct3D T&L HAL (HW)
000000.000:[COLOR="Red"] [x] Direct3D HAL (AMD Radeon(TM) R4 Graphics) (HW)[/COLOR]
000000.000: [ ] Direct3D T&L HAL (AMD Radeon(TM) R4 Graphics) (HW)
...
000000.000: Graphics: Viewport: Fullscreen 1024 x 768 x [COLOR="Red"]16[/COLOR]
000000.000: Graphics: Hardware T&L capability: [COLOR="red"]No[/COLOR]
000000.000: Graphics: Z-buffer depth: [COLOR="Red"]16 bit[/COLOR]
000000.000: Graphics: Active lights supported: [COLOR="Red"]-1[/COLOR]
...so Orbiter is trying to use a video mode that does not support Transform & Lighting, which can cause problems like you are seeing. What I suggest is to go into the video settings in the Orbiter launchpad and set the video mode to either
Direct3D T&L HAL or
Direct3D T&L HAL (AMD Radeon(TM) R4 Graphics) (HW). In addition, as a first test, I would try running Orbiter in windowed mode instead of full-screen. Once that works, you can try full-screen again.
Also, for best compatibility you want a color depth of 32 bits, not 16; e.g., you want it to look like this in the log:
Code:
000000.000: Graphics: Viewport: Fullscreen 1024 x 768 x [COLOR="Red"]32[/COLOR]
000000.000: Graphics: Hardware T&L capability: [COLOR="Red"]Yes[/COLOR]
000000.000: Graphics: Z-buffer depth: [COLOR="Red"]32 bit[/color]
000000.000: Graphics: Active lights supported: [COLOR="Red"]8[/color]
EDIT:
Another option is to install the
D3D9 video client and use that instead of the built-in DX7 video client: it has better performance as well as better compatibility.