General Question A couple of graphics issues.

[Traynor]

Hey all, ive just come back recently to orbiter after not using it for a long time and really enjoying 2016. Ive got a couple of questions about graphics if that's ok. (im using D3D9)

1) Earth and the moon (I haven't got as far as anywhere else yet!) look elliptical, like they've been squashed a bit, more so when there towards the side of the screen. is there a way to change this?

2) I was getting really low frame rate this evening when attempting a re entry to earth which hasn't happened before, although its the first time I have tried to have a go at re entry. So i downloaded and un zipped the latest version of D3D9 to my orbiter folder, but now there's a big grey rectangle that pops out on either side of my screen when I put the mouse pointer there? any ideas on what this could be?

3) When im using the DGS for some reason the main fuel in the read out in the top left of the screen just stays on maximum and doesn't go down? It does go down on the instrument panel though?

many thanks.

 

[Traynor]

Here's a screenshot showing the grey rectangle issue and my fuel still being on full despite using a load getting into orbit.

 

[n72.75]

Hi,

Do you think you could post some screenshots. That would make it a little w
Easier to diagnose, and we can get you up and flying.

 

[Traynor]

There is a screen shot in the above comment, it took a while to show as it was waiting to be approved, thank you.

 

[asbjos]

Hey all, ive just come back recently to orbiter after not using it for a long time and really enjoying 2016. Ive got a couple of questions about graphics if that's ok. (im using D3D9)

1) Earth and the moon (I haven't got as far as anywhere else yet!) look elliptical, like they've been squashed a bit, more so when there towards the side of the screen. is there a way to change this?

2) I was getting really low frame rate this evening when attempting a re entry to earth which hasn't happened before, although its the first time I have tried to have a go at re entry. So i downloaded and un zipped the latest version of D3D9 to my orbiter folder, but now there's a big grey rectangle that pops out on either side of my screen when I put the mouse pointer there? any ideas on what this could be?

3) When im using the DGS for some reason the main fuel in the read out in the top left of the screen just stays on maximum and doesn't go down? It does go down on the instrument panel though?

many thanks.

1. The field of view (FoV) of the viewfinder has this effect. For high FoV (~90 deg), more of the view is squashed into the screen, and thus the things on the side of the screen will look distorted. Press Ctrl+X and Ctrl+Z in simulation to change the FoV. I'm usually around 40 degrees, and don't see much optical distortion there.

2. See this https://www.orbiter-forum.com/showthread.php?p=605217&postcount=5160
and also the following comments. It may be related to your problem.

3. In the Orbiter Launchpad (the scenario browser when you launch Orbiter[_ng].exe), click "Parameters", and ensure that "Limited fuel" (under Realism) is checked. If it's unchecked, the propellant level will remain constant.

 

[kuddel]

Here's a screenshot showing the grey rectangle issue [...]

It's not a bug, it's a feature
See https://www.orbiter-forum.com/showthread.php?p=605217&postcount=5160 and following posts in case you like to disable that.

 

[Traynor]

That's great thanks all, ive manged to get rid of the grey rectangles now and thank you for the tip with field of view.

It turns out that the main propellant read out in the top left hand corner of the screenshot is telling me how much scram jet fuel I have and goes down if i use the scram jet engines. Is there a way to change it to tell me how much main fuel I have instead? many thanks.

 

[asbjos]

It turns out that the main propellant read out in the top left hand corner of the screenshot is telling me how much scram jet fuel I have and goes down if i use the scram jet engines. Is there a way to change it to tell me how much main fuel I have instead? many thanks.

Strange, that should not happen. :huh:

But no, there's no way to change it*. The vessel developer can set which propellant to display when programming the vessel, so if using the default DeltaGlider, the main propellant should be selected.

Can you post the contents of the Orbiter.log after running such a scenario? Maybe you have some old/incompatible addons that change things?

*) It is probably possible to edit which propellant source is listed, if you know programming, using the SetDefaultPropellantResource API command.

 

[Traynor]

Thank you very much for your help asbjos, here is the contents of my log file after running a scenario with the DGS;

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 1e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module XRSound.dll ........... [Build 180309, API 160828]
000000.000: ---------------------------------------------------------------
BaseDir : C:\Users\Owner\Documents\Orbiter\
ConfigDir : C:\Users\Owner\Documents\Orbiter\Config\
MeshDir : C:\Users\Owner\Documents\Orbiter\Meshes\
TextureDir : C:\Users\Owner\Documents\Orbiter\Textures\
HightexDir : C:\Users\Owner\Documents\Orbiter\Textures2\
ScenarioDir: C:\Users\Owner\Documents\Orbiter\Scenarios\
000000.000: ---------------------------------------------------------------
D3D9 DLLs : C:\Windows\SYSTEM32\d3d9.dll [v 10.0.18362.387]
: C:\Windows\SYSTEM32\d3dx9_43.dll [v 9.29.952.3111]
000000.000: ---------------------------------------------------------------
000000.000: Module D3D9Client.dll ........ [Build 200418, API 160828]
000000.000: Module BaseSyncMFD.dll ....... [Build 180408, API 160828]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module Glideslope.dll ........ [Build 180401, API 160828]
000000.000: Glideslope module init: version v2.7, date Apr 1 2018
000000.000: Module ModuleMessagingExtMFD.dll [Build 180624, API 160828]
000000.000: >>> MMExtMFD module initialized: version 2.1, compile date Jun 24 2018
000000.000: Module LoadMFD2.dll .......... [Build 161223, API 161124]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
D3D9: 3D-Adapter.............. : Intel(R) HD Graphics 520
D3D9: MaxTextureWidth......... : 8192
D3D9: MaxTextureHeight........ : 8192
D3D9: MaxTextureRepeat........ : 8192
D3D9: VolTexAddressCaps....... : 0x3F
D3D9: NumSimultaneousRTs...... : 4
D3D9: VertexDeclCaps.......... : 0x37F
D3D9: MiscCaps................ : 0x2FCCF2
D3D9: XNA Math Support........ : Yes
D3D9: Vertex Texture.......... : Yes
D3D9: Separate AlphaBlend..... : Yes
D3D9: Shadow Mapping.......... : Yes
D3D9: D3DFMT_A16B16G16R16F.... : Yes
D3D9: D3DFMT_A32B32G32R32F.... : Yes
D3D9: D3DFMT_D32F_LOCKABLE.... : No
D3D9: D3DFMT_A2R10G10B10...... : Yes
D3D9: D3DFMT_L8............... : Yes
D3D9: D3DDTCAPS_DEC3N......... : No
D3D9: D3DDTCAPS_FLOAT16_2..... : Yes
D3D9: D3DDTCAPS_FLOAT16_4..... : Yes
D3D9: Runs under WINE......... : No
D3D9: D3D9Build Date.......... : 200418
D3D9: Available Texture Memory : 4056 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module DeltaGlider.dll ....... [Build 160828, API 160828]
000000.000: Module LuaInline.dll ......... [Build 160828, API 160828]
000000.000: Module ShuttleA.dll .......... [Build 160828, API 160828]
000000.000: Module ShuttlePB.dll ......... [Build 160828, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: Glideslope module sim start
000000.000: >>> MMExtMFD module sim start
000000.000: Finished initialising panels
000000.000: XRSound 1.10 (Build Date: Mar 9 2018) initialized using sound driver DirectSound8; irrKlang version = 1.6.0. XRSound UpdateInterval = 0.050 (20.0 updates per second)
D3D9: ERROR: SurfHandle=0x78B89C0, Never use Sketchpad::GetDC() hDC not available
000067.762: D3D9: [Session Closed. Scene deleted.]
000067.762: D3D9: [Destroy Render Window Called]
D3D9: ERROR: [Failed to Reset DirectX Device] (Likely blocked by undeleted resources)
000067.762: XRSound 1.10 (Build Date: Mar 9 2018) terminating.
000067.762: Glideslope module sim end
000067.762: >>> MMExtMFD module sim end
000067.762: **** Closing simulation session
000067.762: Glideslope module exit
000067.762: >>> MMExtMFD module exited

 

[asbjos]

Strange, I can see nothing out of the ordinary ...
Sorry, doesn't seem like I can help you.

If it's a comfort, the DeltaGlider has fuel dials for both main and scram propellant in the 2D/3D cockpits. Optionally, you can use something like BurnTime MFD or ReFuel MFD to monitor your fuel state.

 

[Nicholas Kang]

Hi. Welcome back. I can help out for this question.

3) When im using the DGS for some reason the main fuel in the read out in the top left of the screen just stays on maximum and doesn't go down? It does go down on the instrument panel though?

many thanks.

https://www.orbiter-forum.com/showthread.php?p=541427&postcount=135

Refer to the link above, the fuel gauge is coded to refer to the scram fuel, not the main tank fuel. I have the same question as yours in the past.

You can consider using the DG (without scam) version if you need to read off the fuel load off the screen directly. The fuel gauge in the original DG will show the fuel depletion over time on the top left corner of the screen. Not sure if you can change the code to refer to the main fuel for DG-S though.