New Orbiter SVN commit (r.71, Oct 14 2017)

GZR_Ranger

New member
Joined
Feb 15, 2013
Messages
11
Reaction score
0
Points
0
Well, I did a clean install of Orbiter Beta, to include the textures. It works, EXCEPT when I go to the panel view on the XR-2. When going to the panel, it CTD's Is there some add-on that I need to have to get the panel to work? I've tried my config settings in XR2RavenstarPrefs.cfg... Any suggestions?

One thing I'm unsure of is this:

Code:
000000.000: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
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.
 

martins

Orbiter Founder
Orbiter Founder
Joined
Mar 31, 2008
Messages
2,448
Reaction score
462
Points
83
Website
orbit.medphys.ucl.ac.uk
One thing I'm unsure of is this:

Code:
000000.000: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
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.

No that shouldn't cause crashes. More of a problem might be this:
000000.000: WARNING: No texture data found for Mars (TileFormat = 2)
Did you not install the Mars textures? It's possible that the code requires planet textures at least to the root of the quadtree to be present (resolution level 4). Although I don't know if this would trigger a problem when Mars is not in view (I should test this). And there definitely shouldn't be any correlation with XR-2.

Do you get crashes only with the combination D3D9+XR2? Do each if these work individually in the latest beta?
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
As far as I rember, the inline graphics-client worked for me after installing only the eath-lowres-textures.
But the D3D9-client was crashing orbiter, until I have installed all the other available low-res-packs.
However, I have tried to use the modified XR2, too.
It worked, until I installed the KSC hires-texture-pack.
Now I am getting random CTD's on my Desktop.
I believe in my case, it's just some kind of out-of-memory-issue.
The same setup-works good on my laptop, which has more main-memory and video-memory compared to my old WinXP desktop, but I didn't test the XR2 on this box, yet.
 

Marg

Active member
Joined
Mar 20, 2008
Messages
482
Reaction score
66
Points
28
Sorry I still have not updated to r45. .. but I noticed something odd.
I orbited the moon with Apollo vessels (LM+SM). When I was in external camera view and close to vessels, a heavy flickering of lunar craters happened (45 degrees off the down looking point and more towards the horizon). Orbiter visualized crater "inside part" as it was the closest wall that flickered. But when I moved camera further away from vessels (100 m or more) it did not happen anymore. What can that be?
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
I found another issue with the new DG:

Whenver I load a scenario with the new DG docked to whatever vessel, Orbiter CTD's while loading the scenario, but no erros logged.
Happens with inline+external graphics-client.
Maybe related with the new "Oxygen-Pressure" feature in new DG ?

To solve this, I need to remove the docking-relevant entries in the SCN-file, and reload the scenario.
Then the scenario loads up without problems.
Right after loading-up , the DG docks again...as expected.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
I found another issue with the new DG:

Whenver I load a scenario with the new DG docked to whatever vessel, Orbiter CTD's while loading the scenario, but no erros logged.
Happens with inline+external graphics-client.
Maybe related with the new "Oxygen-Pressure" feature in new DG ?

To solve this, I need to remove the docking-relevant entries in the SCN-file, and reload the scenario.
Then the scenario loads up without problems.
Right after loading-up , the DG docks again...as expected.
This has nothing to the with the DG or any other vessel but everything to do with OrbiterSound. OS just isn't 100% compatible with Beta version(s).
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
Yes...you are right. Disabled Orbiter-Sound module and loading of the SCN worked fine.
Sorry, for not cross-checking.
 

jarmonik

Well-known member
Orbiter Contributor
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,651
Reaction score
785
Points
128
I made some tests with XR-2 Ravenstar and it is causing a CTD with D3D9 as well as with the inline engine. Debugger shows no leads, no D3D9 calls in a call stack or being executed.

Removed Mars and Moon textures from an installation to test texture dependency. No CTDs, rendered as black spheres.

---------- Post added at 23:29 ---------- Previous post was at 23:25 ----------

But the D3D9-client was crashing orbiter, until I have installed all the other available low-res-packs.

I wasn't able to reproduce, if you experience something like that once more then, please, report in D3D9 thread.
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
>I wasn't able to reproduce, if you experience something like that once more then, please, report in D3D9 thread.

Will do so. I have nothing reported, because I thought the low-res packs were a (not just visual)requirement.
 

GZR_Ranger

New member
Joined
Feb 15, 2013
Messages
11
Reaction score
0
Points
0
No that shouldn't cause crashes. More of a problem might be this:

Did you not install the Mars textures? It's possible that the code requires planet textures at least to the root of the quadtree to be present (resolution level 4). Although I don't know if this would trigger a problem when Mars is not in view (I should test this). And there definitely shouldn't be any correlation with XR-2.

Do you get crashes only with the combination D3D9+XR2? Do each if these work individually in the latest beta?

Thanks for the reply, Martin & everyone else. I've been an Orbiter fan since I first downloaded back in 2006 on my computer before taking a trip to Afghanistan (where I fell in love with the simulator!)... It's obvious I'm still not an expert, tho!

After having issues with the latest beta, I specifically downloaded the latest textures, to include MarsLo.zip dated Nov 26 2015. Orbiter runs, but no matter how I try and "sneak" into the XR-2 (thru scenario editor, etc., and with or without D3D9) I still CTD whenever I load the XR-2.

Tomorrow I will try installing the Orbiter Beta and XR-2 on another computer to see if I get the same result.

Thanks again, everyone!
 

martins

Orbiter Founder
Orbiter Founder
Joined
Mar 31, 2008
Messages
2,448
Reaction score
462
Points
83
Website
orbit.medphys.ucl.ac.uk
I made some tests with XR-2 Ravenstar and it is causing a CTD with D3D9 as well as with the inline engine. Debugger shows no leads, no D3D9 calls in a call stack or being executed.

Removed Mars and Moon textures from an installation to test texture dependency. No CTDs, rendered as black spheres.


Ok, I found a problem that shows up if a Delta-glider is present in the scenario but doesn't have input focus. Essentially, the oapiRedrawArea and oapiPanelRedrawArea functions have a major flaw: they don't know which vessel made the call, so the redraw request can end up in the wrong cockpit.

I have now deprecated those functions and replaced them with VESSEL::RedrawArea and VESSEL::panelRedrawArea. This will come into effect with the next beta.

How this problem can be related to the Moon and Mars textures is a mystery.

Unfortunately I still get a CTD with the XR2, but now it might actually be a problem in the XR2 code:

I am receiving a call to GDIPad::GetOrigin(int *x, int *y)const from the XR2's clbkDrawHUD with invalid pointers for the x and y arguments. Not sure why this should show up only now, though. Doug, could you have a look?
 

GZR_Ranger

New member
Joined
Feb 15, 2013
Messages
11
Reaction score
0
Points
0
This might explain why the XR-2 will still load with a glass cockpit, but not the panel view.

In case it's helpful to have a double check, here are my logs:

Orbiter.log
Code:
**** Orbiter.log
000000.000: Build Jan 20 2016 [v.160120]
000000.000: Timer precision: 3.94739e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 150906, API 150906]
000000.000: Module AtmConfig.dll ......... [Build 150906, API 150906]
000000.000: Module DGConfigurator.dll .... [Build 150906, API 150906]
000000.000: Module D3D9Client.dll ........ [Build 160121, API 160120]
000000.000: Module ScnEditor.dll ......... [Build 150906, API 150906]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000: 
000000.000: **** Creating simulation session
000000.000: D3D9Client: [DirectX 9 Initialized]
000000.000: D3D9Client: Sytem has XNA math support
000000.000: D3D9Client: [3DDevice Initialized]
000000.000: D3D9Client: [Loading Stars]
000000.000: D3D9Client: [Loading Constellations]
000000.000: D3D9Client: [D3D9Client Initialized]
000000.000: Attempting to clear a texture 0x782A210 color=0x0
000000.000: Module Sun.dll ............... [Build 150906, API 150906]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 150906, API 150906]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 150906, API 150906]
000000.000: Module VenusAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 150906, API 150906]
000000.000: Module EarthAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 150906, API 150906]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 150906, API 150906]
000000.000: Module MarsAtm2006.dll ....... [Build 150906, API 150906]
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 150906, API 150906]
000000.000: Module Jupiter.dll ........... [Build 150906, API 150906]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 150906, API 150906]
000000.000: Module Europa.dll ............ [Build 150906, API 150906]
000000.000: Module Ganymede.dll .......... [Build 150906, API 150906]
000000.000: Module Callisto.dll .......... [Build 150906, API 150906]
000000.000: Module Satsat.dll ............ [Build 150906, API 150906]
000000.000: Module Saturn.dll ............ [Build 150906, API 150906]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 150906, API 150906]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 150906, API 150906]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 150906, API 150906]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 150906, API 150906]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 150906, API 150906]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 150906, API 150906]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 150906, API 150906]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 150906, API 150906]
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 150906, API 150906]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module ShuttlePB.dll ......... [Build 150906, API 150906]
000000.000: Module DeltaGlider.dll ....... [Build 160120, API 160120]
000000.000: Module LuaInline.dll ......... [Build 150906, API 150906]
000000.000: Module ShuttleA.dll .......... [Build 151205, API 151205]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9Client: [Scene Initialized]
000000.000: Finished initialising panels
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::GetHorizonAirspeedVector
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: ---------------------------------------------------------------
000088.283: D3D9Client: [Session Closed. Scene deleted.]
000088.283: **** Closing simulation session
000088.283: Invalid Window !! RenderWndProc() called after calling clbkDestroyRenderWindow() uMsg=0x49F370
000088.283: 
000088.283: **** Creating simulation session
000088.283: D3D9Client: [DirectX 9 Initialized]
000088.283: D3D9Client: Sytem has XNA math support
000088.283: D3D9Client: [3DDevice Initialized]
000088.283: D3D9Client: [Loading Stars]
000088.283: D3D9Client: [Loading Constellations]
000088.283: D3D9Client: [D3D9Client Initialized]
000000.000: Attempting to clear a texture 0x1A70A850 color=0x0
000000.000: Module Sun.dll ............... [Build 150906, API 150906]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 150906, API 150906]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 150906, API 150906]
000000.000: Module VenusAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 150906, API 150906]
000000.000: Module EarthAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 150906, API 150906]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 150906, API 150906]
000000.000: Module MarsAtm2006.dll ....... [Build 150906, API 150906]
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 150906, API 150906]
000000.000: Module Jupiter.dll ........... [Build 150906, API 150906]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 150906, API 150906]
000000.000: Module Europa.dll ............ [Build 150906, API 150906]
000000.000: Module Ganymede.dll .......... [Build 150906, API 150906]
000000.000: Module Callisto.dll .......... [Build 150906, API 150906]
000000.000: Module Satsat.dll ............ [Build 150906, API 150906]
000000.000: Module Saturn.dll ............ [Build 150906, API 150906]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 150906, API 150906]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 150906, API 150906]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 150906, API 150906]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 150906, API 150906]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 150906, API 150906]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 150906, API 150906]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 150906, API 150906]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 150906, API 150906]
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 150906, API 150906]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module ShuttlePB.dll ......... [Build 150906, API 150906]
000000.000: Module DeltaGlider.dll ....... [Build 160120, API 160120]
000000.000: Module ShuttleA.dll .......... [Build 151205, API 151205]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9Client: [Scene Initialized]
000000.000: Finished initialising panels
000043.180: ---------------------------------------------------------------
000043.180: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
000043.180: At least one active module is accessing an obsolete interface function.
000043.180: Addons which rely on obsolete functions may not be compatible with
000043.180: future versions of Orbiter.
000043.180: ---------------------------------------------------------------
000067.565: D3D9Client: [Session Closed. Scene deleted.]
000067.565: **** Closing simulation session
000067.565: Invalid Window !! RenderWndProc() called after calling clbkDestroyRenderWindow() uMsg=0x49F370
000067.565: 
000067.565: **** Creating simulation session
000067.565: D3D9Client: [DirectX 9 Initialized]
000067.565: D3D9Client: Sytem has XNA math support
000067.565: D3D9Client: [3DDevice Initialized]
000067.565: D3D9Client: [Loading Stars]
000067.565: D3D9Client: [Loading Constellations]
000067.565: D3D9Client: [D3D9Client Initialized]
000000.000: Attempting to clear a texture 0x16741008 color=0x0
000000.000: Module Sun.dll ............... [Build 150906, API 150906]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 150906, API 150906]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 150906, API 150906]
000000.000: Module VenusAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 150906, API 150906]
000000.000: Module EarthAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 150906, API 150906]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 150906, API 150906]
000000.000: Module MarsAtm2006.dll ....... [Build 150906, API 150906]
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 150906, API 150906]
000000.000: Module Jupiter.dll ........... [Build 150906, API 150906]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 150906, API 150906]
000000.000: Module Europa.dll ............ [Build 150906, API 150906]
000000.000: Module Ganymede.dll .......... [Build 150906, API 150906]
000000.000: Module Callisto.dll .......... [Build 150906, API 150906]
000000.000: Module Satsat.dll ............ [Build 150906, API 150906]
000000.000: Module Saturn.dll ............ [Build 150906, API 150906]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 150906, API 150906]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 150906, API 150906]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 150906, API 150906]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 150906, API 150906]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 150906, API 150906]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 150906, API 150906]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 150906, API 150906]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 150906, API 150906]
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 150906, API 150906]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module ShuttlePB.dll ......... [Build 150906, API 150906]
000000.000: Module DeltaGlider.dll ....... [Build 160120, API 160120]
000000.000: Module ShuttleA.dll .......... [Build 151205, API 151205]
000000.000: Module XR2Ravenstar.dll ...... [Build 130722, API 130101]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9Client: [Scene Initialized]
000000.000: Finished initialising panels
000052.965: ---------------------------------------------------------------
000052.965: >>> WARNING: Obsolete API function used: oapiBlt
000052.965: Colour key argument not supported by graphics client
000052.965: ---------------------------------------------------------------

FROM XR2Ravenstar.log... Note, the first load was with glass cockpit, then I exited... The second load I tried to go to panel view and CTD'ed.
Code:
01.26.2016 08:57:59.179 - [] Loading XR2Ravenstar: Version 1.7 BETA-1, Build Date: Jul 22 2013
01.26.2016 08:57:59.236 - [XR-2_01] Using configuration file(s): Config\XR2RavenstarPrefs.cfg (no override found [Config\XR-2_01.xrcfg])
01.26.2016 08:57:59.236 - [XR-2_01] Parsing config file 'Config\XR2RavenstarPrefs.cfg'
01.26.2016 08:57:59.247 - [XR-2_01] Successfully parsed configuration file 'Config\XR2RavenstarPrefs.cfg'
01.26.2016 08:58:01.418 - [XR-2_01] Using UMmu Version: 3.00
01.26.2016 08:58:01.467 - [XR-2_01] Using OrbiterSound Version: 4.00
01.26.2016 08:59:28.943 - [] Loading XR2Ravenstar: Version 1.7 BETA-1, Build Date: Jul 22 2013
01.26.2016 08:59:28.973 - [XR-2_01] Using configuration file(s): Config\XR2RavenstarPrefs.cfg (no override found [Config\XR-2_01.xrcfg])
01.26.2016 08:59:28.973 - [XR-2_01] Parsing config file 'Config\XR2RavenstarPrefs.cfg'
01.26.2016 08:59:28.974 - [XR-2_01] Successfully parsed configuration file 'Config\XR2RavenstarPrefs.cfg'
01.26.2016 08:59:30.655 - [XR-2_01] Using UMmu Version: 3.00
01.26.2016 08:59:30.882 - [XR-2_01] Using OrbiterSound Version: 4.00
01.26.2016 08:59:49.354 - [XR-2_01] Forcing 2D panel width of 1280 pixels per XR configuration file [Config\XR2RavenstarPrefs.cfg (no override found [Config\XR-2_01.xrcfg])].
01.26.2016 09:00:24.273 - [XR-2_01] Forcing 2D panel width of 1280 pixels per XR configuration file [Config\XR2RavenstarPrefs.cfg (no override found [Config\XR-2_01.xrcfg])].
 

jarmonik

Well-known member
Orbiter Contributor
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,651
Reaction score
785
Points
128
How this problem can be related to the Moon and Mars textures is a mystery.
Those are not related. Sorry about not being accurate enough, I was merely testing if a lack of planetary textures could cause a CTD in the client. So, the reported CTD with the XR2 was not due to lack of textures.

---------- Post added at 17:41 ---------- Previous post was at 16:46 ----------

I am receiving a call to GDIPad::GetOrigin(int *x, int *y)const from the XR2's clbkDrawHUD with invalid pointers for the x and y arguments. Not sure why this should show up only now, though. Doug, could you have a look?

Looks like we have forgotten to implement GetOrigin() entirely in D3D9. (Fixed) Yes, I am seeing the same problem of invalid pointers passed to GetOrigin(). Although, by-passing that one results a CTD in somewhere else. Removed all other vessels from a scenario but still it won't run.
 

dbeachy1

O-F Administrator
Administrator
Orbiter Contributor
Addon Developer
Donator
Beta Tester
Joined
Jan 14, 2008
Messages
9,214
Reaction score
1,560
Points
203
Location
VA
Website
alteaaerospace.com
Preferred Pronouns
he/him
Unfortunately I still get a CTD with the XR2, but now it might actually be a problem in the XR2 code:

I am receiving a call to GDIPad::GetOrigin(int *x, int *y)const from the XR2's clbkDrawHUD with invalid pointers for the x and y arguments. Not sure why this should show up only now, though. Doug, could you have a look?

Sure, I'll look into it.
 

dbeachy1

O-F Administrator
Administrator
Orbiter Contributor
Addon Developer
Donator
Beta Tester
Joined
Jan 14, 2008
Messages
9,214
Reaction score
1,560
Points
203
Location
VA
Website
alteaaerospace.com
Preferred Pronouns
he/him
OK I took a quick look here and the CTD only occurs for me if I load a DeltaGlider in the same scenario -- Martin, can you please confirm? Here is what I did:

1. Updated to the latest Orbiter Beta code using SVN.
2. Copied the XR2 1.7 Beta-1 DLL to $ORBITER_HOME\Modules.
3. Ran orbiter.exe and loaded the XR2 Ravenstar\1 - Ready for Takeoff to ISS scenario and got a CTD on load.
4. Cloned the above scenario file and removed this section from it:
Code:
GL-02:DeltaGlider
  STATUS Landed Mars
  BASE Olympus:3
  POS -135.4300000 12.7366196
  HEADING 0.00
  PRPLEVEL 0:1.000 1:1.000
  NAVFREQ 0 0 0 0
  XPDR 0
  GEAR 1 1.0000
END
5. Re-ran orbiter.exe and loaded the above scenario; Orbiter started successfully this time.

Oddly, if I run orbiter.exe in step 3 under the VS 2013 debugger it does not CTD. So then I ran orbiter.exe directly and attached a debugger remotely after the CTD occurred in step 3, and it showed this in the call stack:

Code:
>	orbiter.exe!0046526b()	Unknown
 	[Frames below may be incorrect and/or missing, no symbols loaded for orbiter.exe]	
 	orbiter.exe!004653af()	Unknown
 	orbiter.exe!0046224a()	Unknown
 	orbiter.exe!00464599()	Unknown
 	orbiter.exe!004b794e()	Unknown
 	DeltaGlider.dll!29a989cc()	Unknown
 	DeltaGlider.dll!29a98ae5()	Unknown
 	DeltaGlider.dll!29a8f495()	Unknown
 	DeltaGlider.dll!29a984db()	Unknown
 	DeltaGlider.dll!29a90175()	Unknown
 	DeltaGlider.dll!29a88132()	Unknown
 	orbiter.exe!00486179()	Unknown
 	orbiter.exe!0041c8fb()	Unknown
 	orbiter.exe!0041f760()	Unknown
 	orbiter.exe!004225e4()	Unknown
 	orbiter.exe!004228bb()	Unknown
 	orbiter.exe!005094fd()	Unknown
 	kernel32.dll!774738f4()	Unknown
 	ntdll.dll!775f56c3()	Unknown
 	ntdll.dll!775f568e()	Unknown

So I'm not seeing any XR2 code involved when the crash occurs for me, and everything works fine if I remove the DeltaGlider from the scenario. [I also recompiled the XR2 DLL against the latest Orbiter libraries but it didn't change anything.] Martin -- do you have any ideas??
 

JMW

Aspiring Addon Developer
Joined
Aug 5, 2008
Messages
611
Reaction score
52
Points
43
Location
Happy Wherever
Scuse my ignorance, but where should the Matlab runtimes be installed for use with tileedit.... Program files, or somewhere else.......?
 

GZR_Ranger

New member
Joined
Feb 15, 2013
Messages
11
Reaction score
0
Points
0
OK I took a quick look here and the CTD only occurs for me if I load a DeltaGlider in the same scenario -- Martin, can you please confirm?

I've replicated this result; by deleting the Delta Gliders from a scenario, the XR-2 works fine.
 

jarmonik

Well-known member
Orbiter Contributor
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,651
Reaction score
785
Points
128
After re-installing XR-2 and removing the Delta Glider I got the XR-2 to run but there is still a CTD when switching to a virtual cockpit. I get the same results with D3D9 and inline engine. Although, everything is working just fine with Orbiter 2010-P1. I have no idea what's going on there.
 

Attachments

  • CTD.png
    CTD.png
    60.7 KB · Views: 30

dbeachy1

O-F Administrator
Administrator
Orbiter Contributor
Addon Developer
Donator
Beta Tester
Joined
Jan 14, 2008
Messages
9,214
Reaction score
1,560
Points
203
Location
VA
Website
alteaaerospace.com
Preferred Pronouns
he/him
After re-installing XR-2 and removing the Delta Glider I got the XR-2 to run but there is still a CTD when switching to a virtual cockpit. I get the same results with D3D9 and inline engine. Although, everything is working just fine with Orbiter 2010-P1. I have no idea what's going on there.

I just tried that here with both the inline engine and the latest D3D9 client and both work fine for me. Can you dupe the CTD you are seeing in a clean Orbiter beta install?
 

martins

Orbiter Founder
Orbiter Founder
Joined
Mar 31, 2008
Messages
2,448
Reaction score
462
Points
83
Website
orbit.medphys.ucl.ac.uk
Hi Doug, here are my findings:

- Installed fresh Orbiter beta from SVN
- Installed OrbiterSound 4.0 and UCGO3.0
- Installed XR2Ravenstar-1.6a
- Run Scenarios | XR2 Ravenstar | 1 - Ready for takeoff to ISS (after removing all vessels except XR2-01, XR2-01_Bay, XR2PayloadCHM-01-1

Result: CTD at start.

Running an Orbiter debug build on this scenario, I get a crash in GDIPad::GetOrigin, called from the Ravenstar's clbkDrawHUD method, as mentioned above.

If I bypass the GetOrigin code, the crash seems to happen directly in clbkDrawHUD.

The crash happens at the same location when starting in panel, VC, or glass cockpit mode.
 
Top