Problem white bar above instrument panel in DGIV

[vonneuman]

In the DGIV while in full screen only I see a white bar above the instrument panel. Can someone tell me how to fix this?




Edit: Ok, not just the DGIV, I have that same problem in the DG

 

[TSPenguin]

What rendering device are you using? It fails to display transparency and instead draws white.
If unsure, please post your orbiter.log.

 

[n72.75]

Wow, that must be obnoxious to fly with.

...but yeah post your orbiter.log and we'll help you.

 

[vonneuman]

Ok here is the Orbiter log:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Radeon HD 3200 Graphics )
==> Direct3D T&L HAL (ATI Radeon HD 3200 Graphics )
Found 0 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module TrackIR.dll [API v.060425]
TrackIR module not found.
Module ScnEditor.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module OrbiterSound.dll [API v.060425]
Module Meshdebug.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module FlightData.dll [API v.050206]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module AutoSave.dll [API v.060425]
Module RendezvousMFD.dll [API v.050206]
Module AttitudeMFD.dll [API v.060425]
Module GPCMFD.dll [API v.060425]
Module AutoFCS.dll [API v.050206]
Module LolaMFD.dll [API v.050206]
Module Orulex-core.dll [API v.060425]
Module AeroBrakeMFD.dll [API v.060425]

 

[orb]

This tells nothing about selected rendering device. Is this whole Orbiter.log?

Wasn't there below what you posted anything like:

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: [color=blue][i]16/32[/i][/color] bit
Render device: Fullscreen [color=blue][i]width x height[/i][/color]
Device has [color=blue][i]some[/i][/color] capability

 

[TSPenguin]

We need the log that is present after you start a simulation. Not after starting the launchpad.

Sorry we didn't tell you earlier.

 

[orb]

There was already such a problem posted in this thread, but I can't say whether it was solved or not. Consider suggestions also posted by TSPenguin there.

 

[vonneuman]

Sorry I never had to deal with my Orbiter log before. I did not realize that the start menu is one of the things that cause it to be rewritten.
Here it is:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Radeon HD 3200 Graphics )
==> Direct3D T&L HAL (ATI Radeon HD 3200 Graphics )
Found 0 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module TrackIR.dll [API v.060425]
TrackIR module not found.
Module ScnEditor.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module OrbiterSound.dll [API v.060425]
Module Meshdebug.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module FlightData.dll [API v.050206]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module AutoSave.dll [API v.060425]
Module RendezvousMFD.dll [API v.050206]
Module AttitudeMFD.dll [API v.060425]
Module GPCMFD.dll [API v.060425]
Module AutoFCS.dll [API v.050206]
Module LolaMFD.dll [API v.050206]
Module Orulex-core.dll [API v.060425]
Module AeroBrakeMFD.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 16 bit
Render device: Fullscreen 800 x 600
Device has no hardware T&L capability
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
*** WARNING: Old-style texture contents file Earth_lmask.bin
Module Moon.dll [API v.041022]

As for what Orb said, no they did not solve it.

 

[orb]

Zbuffer: 16 bit
Render device: Fullscreen 800 x 600
Device has no hardware T&L capability

This is strange. Radeon HD 3200 should have T&L capability.

Have you selected at "3D device" on "Video" tab in Orbiter Launchpad the "Direct3D T&L HAL (ATI Radeon HD 3200 Graphics )" from the list?

Also, try to run simulation after changing "Colour depth [bpp]" to 32 on the same tab in the launchpad. And with "Try stencil buffer" checkbox also checked there.

 

[vonneuman]

Thank you. After I checked "Try stencil buffer" it works just fine.strange though, I have a copy of this one on another computer with out it checked and it works just fine.

 

[TSPenguin]

You really should change your rendering device to the one orb pointed out earlier. It will improve your performance several magnitudes.

 

[vonneuman]

I don't know if this is related but Orbiter has crashed on me since I fixed the problem. Here is the log:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Radeon HD 3200 Graphics )
==> Direct3D T&L HAL (ATI Radeon HD 3200 Graphics )
Found 0 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module TrackIR.dll [API v.060425]
TrackIR module not found.
Module ScnEditor.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module OrbiterSound.dll [API v.060425]
Module Meshdebug.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module FlightData.dll [API v.050206]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module AutoSave.dll [API v.060425]
Module RendezvousMFD.dll [API v.050206]
Module AttitudeMFD.dll [API v.060425]
Module GPCMFD.dll [API v.060425]
Module AutoFCS.dll [API v.050206]
Module LolaMFD.dll [API v.050206]
Module Orulex-core.dll [API v.060425]
Module AeroBrakeMFD.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Render device: Fullscreen 800 x 600
Device has no hardware T&L capability
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
*** WARNING: Old-style texture contents file Earth_lmask.bin
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.061227]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
Module DeltaGliderIV.dll [API v.060425]
>>> ERROR: Missing texture: U_mmu.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
>>> ERROR: Missing texture: U_mmu2.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
>>> ERROR: Missing texture: orulex\orangesoil.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
>>> ERROR: Missing texture: orulex\tree.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]

Something to do with missing textures.

 

[TSPenguin]

Do you have UMMU installed? The DGIV needs it.
Regarding the missing orulex textures, try disabling orulex and see if this fixes it.

 

[orb]

Missing textures from Orulex aren't that what causes crashes here, but lack of UMMU installed could be.

Also there is still no hardware Transform & Lighting support from graphics card, so CPU could be overheating, since it's used instead of GPU, and now there is selected 32 bit z-buffer and probably 32 bit color, so much more data to process. Is "RGB Emulation" your selected renderer for Orbiter or some of "Direct3D" ones listed at the beginning of the log?

 

[dbeachy1]

Also, I noticed this is still in the latest log:

Zbuffer: 32 bit
Render device: Fullscreen 800 x 600
Device has no hardware T&L capability

For best performance and stability you will want to be sure to select Direct3D T&L HAL (ATI Radeon HD 3200 Graphics ) as your video mode in the launchpad. Running without hardware T&L (Transform & Lighting) support will really kill your framerate.

 

[orb]

To be exact, it's Transform, clipping, and lighting. If it's turned off, all geometry calculations and transformations, lights lighting this geometry, and what from that will be displayed on screen is calculated in CPU, causing GPU to be mostly unused, and CPU overused, like I said in my previous post. And we don't know whether you disabled it deliberately, because it caused some problems in Orbiter, or is it graphics driver that doesn't want to turn it on, despite you selected the T&L renderer in Orbiter Launcher.

 

[vonneuman]

Ok I am using the Direct3D with hal and t&h now. Could that have been the problem? And yes I do have UMMU installed. It was my second add on after Orbiter sound.

 

[TSPenguin]

That could have been the problem indeed. But your current settings are good as they are.