Hardware No MFD or HUD in Virtual Cockpit mode

[Pipcard]

^See title. The MFDs are all white...

 

[Woo482]

Try pressing Ctrl+H for the HUD, the MFDs could be due to either. A missing .dll or outdated Video Drivers.

 

[Quick_Nick]

Go to the Video tab of the Orbiter Launchpad and change it to 16bit if you have it on 32bit, or vice versa.

 

[Pipcard]

The HUD is on; it is set to 16-bit. It might be outdated video drivers.

 

[willy88]

Do you have an internal graphics card?

 

[Lucy]

See this: http://www.orbiter-forum.com/showthread.php?t=7435

I think it had to do with an Intel graphics chipset.

 

[Pipcard]

I have a Intel 945GM Express Chipset (on my laptop).

P.S. I'm planning to get a usb keypad.

 

[dbeachy1]

I have a Intel 945GM Express Chipset (on my laptop).

Unfortunately that is very likely the problem -- many onboard video adapters do not correctly support 3D applications due to limited texture memory and/or driver support.

 

[Pipcard]

I like the virtual cockpit, but I would have to live with the other two modes.

EDIT: My computer (display driver) just crashed when I tried to do it with 16-bit colors and full screen (and the computer with 32-bit). When I started it, I saw the VC having the HUD and MFDs, then it froze and crashed. Then it said the display driver "failed to respond". I had "killswitch" the power and reboot it. I think it is a hardware problem. I won't try that again.

 

[ex-orbinaut]

Hi, Pipcard,

Just in the evnt you have not solved this yet.

Try running Orbiter in 16bpp, fullscreen mode. Have "Try stencil buffer" and "Always enumerate devices" ticked, and select your laptop driver with Direct 3D HAL from the drop down list. Orbiter VC's work fine this way on my 1 GB RAM "notebook".

Hope it helped....

 

[Pipcard]

I won't try it, at the risk of crashing again.

 

[n72.75]

switch to 16 bit mode.