Update XR Release Candidates (RC2) for Orbiter 2010

[dbeachy1]

That may be the case, but XRs are simply statically-linked DLLs built using Visual Studio 2005, and the release build runs fine for me under the debugger here (I just retested that to double-check). A more likely culprit is memory corruption by another add-on; XRs use a fair number of new/delete calls, and so memory corruption by another add-on will crash the system sooner with an XR vessel in the scenario. Just a theory, of course, but since it works for me here that's the best one I've got.

So here's what I recommend: as a test, make a clean installation of Orbiter/OrbiterSound/UMMu. Then run an XR2 scenario under the debugger. If that runs OK, then add in another add-on and re-test. If it crashes then, that would tend to indicate memory corruption of some sort by the other add-on. OTOH, if it crashes under the debugger in a clean installation, then something odd is going on...

EDIT:
I've been doing some testing here with OGLA and the XR2, and I am able to load and run the XR2 under the debugger using the OGLA client just fine. So perhaps it is some kind of debugger compatibility issue. One thing's for sure: it's frustrating to track odd stuff like this down... What I'll do for now is add a config option to disable the heating mesh feature.

 

[Artlav]

In any case, here is the method the XR framework uses to show or hide mesh groups.
...
What I'll do for now is add a config option to disable the heating mesh feature.

That won't be necessary, should now be fixed, thank you for info.
Here is an update: http://orbides.1gb.ru/orbf/ogla-100510-2.zip
(ADDED: Gear fix)

Now, what about the rolling gears animation?
What is unusual about it?
EDIT: Nvm, that's entirely my bug.

A more likely culprit is memory corruption by another add-on

Sounds plausible, it crashes on clean beta 100503, any debugger i have (VC2005, Delphi7, GDB).
EDIT: Please note, this is by no means a priority, as it does not affect other users much. I have other ways of debugging for such cases.
Here is the stack:

First-chance exception at 0x09928f68 in orbiter.exe: 0xC0000005: Access violation reading location 0xbaadf00d.
Unhandled exception at 0x09928f68 in orbiter.exe: 0xC0000005: Access violation reading location 0xbaadf00d.

 	XR2Ravenstar.dll!09928f68() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for XR2Ravenstar.dll]	
>	msvcr80d.dll!_unlock(int locknum=4)  Line 376	C
 	msvcr80d.dll!_heap_alloc_dbg(unsigned int nSize=72, int nBlockUse=1, const char * szFileName=0x00000000, int nLine=0)  Line 477 + 0x7 bytes	C++
 	msvcr80d.dll!_heap_alloc_dbg(unsigned int nSize=72, int nBlockUse=1, const char * szFileName=0x00000000, int nLine=0)  Line 474 + 0xc bytes	C++
 	msvcr80d.dll!_nh_malloc_dbg(unsigned int nSize=72, int nhFlag=0, int nBlockUse=1, const char * szFileName=0x00000000, int nLine=0)  Line 268 + 0x15 bytes	C++
 	msvcr80d.dll!malloc(unsigned int nSize=72)  Line 154 + 0x15 bytes	C++
 	msvcr80d.dll!operator new(unsigned int size=43296156)  Line 59 + 0x9 bytes	C++
 	00311d58()	
 	XR2Ravenstar.dll!09923d66() 	
 	OGLAClient.dll!_GetSystemTimeAsFileTime@4()  + 0xe18 bytes	C++
 	OGLAClient.dll!oapi::OGLAClient::clbkCreateReentryStream(PARTICLESTREAMSPEC * pss=0x738801f0, void * hVessel=0x009ff644)  Line 174 + 0x1b bytes	C++
 	msvcp80.dll!7382f69d() 	
 	msvcr80.dll!73894c58() 	
 	msvcp80.dll!7382cb59() 	
 	msvcp80.dll!7381f76d() 	
 	orbiter.exe!004a54e6() 	
 	winmm.dll!7374271c() 	
 	orbiter.exe!004a99aa() 	
 	orbiter.exe!004182c9() 	
 	ntdll.dll!7746fd6e() 	
 	ntdll.dll!77470d18() 	
 	ntdll.dll!77470cfc() 	
 	ntdll.dll!77470cfc() 	
 	ntdll.dll!7742a967() 	
 	ntdll.dll!773d36fa() 	
 	ntdll.dll!773bf992() 	
 	KernelBase.dll!76d0b75d() 	
 	kernel32.dll!74fc13f8() 	
 	msvcr80.dll!738aecdf() 	
 	ntdll.dll!773d36fa() 	
 	ntdll.dll!773d36fa() 	
 	ntdll.dll!773d32f2() 	
 	kernel32.dll!74fc14d1() 	
 	msvcr80.dll!73894c39() 	
 	msvcr80.dll!73894c58() 	
 	msvcp80.dll!7382f69d() 	
 	msvcr80.dll!73894c58() 	
 	msvcp80.dll!7382cb59() 	
 	msvcp80.dll!7381f71f() 	
 	orbiter.exe!0042038b() 	
 	ntdll.dll!773bfa8a() 	
 	kernel32.dll!7506870f() 	
 	orbiter.exe!004a5a86() 	
 	orbiter.exe!0041927c() 	
 	orbiter.exe!0049eb15() 	
 	user32.dll!75216238() 	
 	user32.dll!75216941() 	
 	user32.dll!75216901() 	
 	user32.dll!75216899() 	
 	user32.dll!75216941() 	
 	msctf.dll!75744505() 	
 	user32.dll!75216238() 	
 	user32.dll!752412a1() 	
 	user32.dll!75241259() 	
 	user32.dll!7521701b() 	
 	user32.dll!752410e2() 	
 	user32.dll!7522b160() 	
 	user32.dll!75216238() 	
 	user32.dll!752168ea() 	
 	user32.dll!75216899() 	
 	user32.dll!75216941() 	
 	user32.dll!7521cd1a() 	
 	user32.dll!7521cd81() 	
 	user32.dll!7524955f() 	
 	user32.dll!752370a9() 	
 	orbiter.exe!0041930a() 	
 	orbiter.exe!00419587() 	
 	orbiter.exe!004a8e3b() 	
 	kernel32.dll!74fc3677() 	
 	ntdll.dll!773d9d72() 	
 	ntdll.dll!773d9d45()

---------- Post added at 12:59 ---------- Previous post was at 12:29 ----------

And, here is the fix for gear animation bug:
http://orbides.1gb.ru/orbf/ogla-100510-2.zip

 

[dbeachy1]

Thanks for the fixes, Artlav! :thumbup: If you're up for it, let's continue troubleshooting the debugger crash in PM and see if we can pin it down.

 

[Artlav]

I'd certainly liked to get it fixed, PM answered.
Also, further bugfixes for OGLA wrt XR2 will be in the OGLA thread.

 

[dbeachy1]

Good news here! Thanks to Artlav's help in reproducing the bug, I was able to fix the debugger crash. Long-story-short, the problem only occurred when OrbiterSound was not installed and you were either running it under the debugger or running a debug XR2 DLL. The fix will be in the next XR2 release candidate (Artlav is testing the fixed DLL now). In the meantime, if you need to debug Orbiter with the XR2 loaded, just load the OrbiterSound module and it should run fine.

Many thanks to Artlav for helping me reproduce the problem!

 

[Bishop]

Hi Flyer! (NPI)

This is already done, check the small arrow on your thrust display, it shows the engine efficiency... about 75% at the Cape :thumbup:

- Bishop

I have also thought that some way of "de-rating" the engines for atmospheric flight could be a good idea when considering take off performance.

 

[flyer]

Thanks for the reply Bishop, yeah I've seen that and I was wondering if it is possible to provide some means of capping the thrust from within orbiter.

I'm purely thinking again from a 'real life' perspective here, as doing this in real life has the benefit of reduced engine wear etc etc

Of course it is possible to manually do this by just positioning the thottles/thrust levers myself but I guess I'm thinking of a rudimentary engine management system/FADEC which can provide a "switch" between spaceflight and atmospheric flight.

Also, the amount of thrust used for acceleration along the runway affects the maximum speed at which you can reject the takeoff and still be able to stop in the remaining runway length (a basic V1 calculation). I've tried looking at some numbers and I personally find it interesting to make these calculations and bring them in to the orbiter world.

I realise I may be alone in my quest to bring some aviation like operating standards into, what is at the end of the day, a fictional world, but I can't help thinking "what regulations/restrictions would be placed on a spaceplane by the various agencies" and trying to implement them! Things such as test programs, which I see as progressing much like a new airliner test flight schedule, before blasting off into some sort of sub-orbital trajectory and ending up with the orbital proving flight and from there it's how far your fuel/lox/patience/imagination can take you!

I think it's an interesting discussion point...although I might be alone on that!

All the best
(Another long post...sorry!)

 

[dbeachy1]

Please remember that you can already tune your XR's engines (and a bunch of other things) however you want by editing the 'CHEATCODES' section in your vessel's config file; e.g., C:\Orbiter\Config\XR2RavenstarPrefs.cfg:

#--------------------------------------------------------------------------
# Maximum main engine thrust in newtons, PER ENGINE (x2 for total)
#--------------------------------------------------------------------------
#MaxMainThrust=3.023e5

(Remember to uncomment that line first.)

 

[flyer]

Thanks Doug, yeah I had seen that in the cfg file.

I guess there isn't much call for this stuff from people - looks like I'm on my own with it!

Thanks for the replies though and keep up the good work!

 

[Wafel]

Hi Orbinauts. I’m new to the Orbiter Forum.

I’m testing XR2 on orbiter 100509 and 100520.

I have a problem with scenarios with XR2 docked to another vessel/space station module like DG-IV, Mir2 or Cassiopee. When I’m loading these scenarios I have CTD after few seconds of simulation. No matter if any modules are installed/activated/deactivated.

There is no problem if XR2 is docked to the ProjectAlpha ISS, Atlantis or Delta Glider.


Here is my Orbiter.log

    **** Orbiter.log
  Build May 20 2010 [v.100520]
  Timer precision: 2.79365e-007 sec
  Found 0 joystick(s)
  Devices enumerated: 3
  Devices accepted: 3
  ==> RGB Emulation
  ==> Direct3D HAL
  ==> Direct3D T&L HAL
  Module AtlantisConfig.dll .... [Build 100520, API 100520]
  Module AtmConfig.dll ......... [Build 100520, API 100520]
  Module DGConfigurator.dll .... [Build 100520, API 100520]
  Module EnergyConfigurator.dll  [Build ******, API 060425]
  Module OrbiterSound.dll ...... [Build ******, API 060425]
  ---------------------------------------------------------------
  >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
  At least one active module is accessing an obsolete interface function.
  Addons which rely on obsolete functions may not be compatible with
  future versions of Orbiter.
  ---------------------------------------------------------------
  Module transx.dll ............ [Build 100503, API 100503]
  Module TrackIR.dll ........... [Build 091120, API 091120]
  TrackIR module not found.
  Module ScriptMFD.dll ......... [Build 100520, API 100520]
  Module ScnEditor.dll ......... [Build 100520, API 100520]
  Module Rcontrol.dll .......... [Build 100520, API 100520]
  Module Meshdebug.dll ......... [Build 100520, API 100520]
  Module LuaMFD.dll ............ [Build 100520, API 100520]
  Module LuaConsole.dll ........ [Build 100520, API 100520]
  Module Framerate.dll ......... [Build 100520, API 100520]
  Module FlightData.dll ........ [Build 100520, API 100520]
  Module ExtMFD.dll ............ [Build 100520, API 100520]
  Module CustomMFD.dll ......... [Build 100520, API 100520]
  Module NAVSET.dll ............ [Build ******, API 060425]
  Module LaunchMFD.dll ......... [Build ******, API 060425]
  Module InterMFD53.dll ........ [Build 090521, API 060425]
  Module BaseSyncMFD.dll ....... [Build ******, API 060425]
  Module AttitudeMFD.dll ....... [Build ******, API 060425]
  Module AeroBrakeMFD.dll ...... [Build ******, API 060425]
   
  **** Creating simulation session
  DirectDraw interface OK
  Direct3D interface OK
  Graphics: Viewport: Fullscreen 1280 x 1024 x 32
  Graphics: Hardware T&L capability: Yes
  Graphics: Z-buffer depth: 32 bit
  Graphics: Stencil buffer depth: 8 bit
  Loading 8816 records from star database
  Module Sun.dll ............... [Build 100215, API 100212]
  VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
  Module Mercury.dll ........... [Build 100215, API 100212]
  VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
  Module Venus.dll ............. [Build 100215, API 100212]
  Module VenusAtm2006.dll ...... [Build 100520, API 100520]
  VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
  Module Earth.dll ............. [Build 100215, API 100212]
  Module EarthAtmJ71G.dll ...... [Build 100520, API 100520]
  VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
  Module Moon.dll .............. [Build 100217, API 100215]
  ELP82: Precision 1e-005, Terms 116/829
  Module Mars.dll .............. [Build 100215, API 100212]
  Module MarsAtm2006.dll ....... [Build 100520, API 100520]
  VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
  Module Phobos.dll ............ [Build ******, API 060425]
  Module Deimos.dll ............ [Build ******, API 060425]
  Module Galsat.dll ............ [Build 100217, API 100215]
  Module Jupiter.dll ........... [Build 100215, API 100212]
  VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
  Module Io.dll ................ [Build 100217, API 100215]
  Module Europa.dll ............ [Build 100217, API 100215]
  Module Ganymede.dll .......... [Build 100217, API 100215]
  Module Callisto.dll .......... [Build 100217, API 100215]
  Module Satsat.dll ............ [Build 100215, API 100212]
  Module Saturn.dll ............ [Build 100215, API 100212]
  VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
  Module Mimas.dll ............. [Build 100215, API 100212]
  SATSAT Mimas: Terms 113
  Module Enceladus.dll ......... [Build 100215, API 100212]
  SATSAT Enceladus: Terms 33
  Module Tethys.dll ............ [Build 100215, API 100212]
  SATSAT Tethys: Terms 101
  Module Dione.dll ............. [Build 100215, API 100212]
  SATSAT Dione: Terms 59
  Module Rhea.dll .............. [Build 100215, API 100212]
  SATSAT Rhea: Terms 68
  Module Titan.dll ............. [Build 100215, API 100212]
  SATSAT Titan: Terms 100
  Module Iapetus.dll ........... [Build 100215, API 100212]
  SATSAT Iapetus: Terms 605
  Module Uranus.dll ............ [Build 100215, API 100212]
  VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
  Module Miranda.dll ........... [Build ******, API 060425]
  Module Ariel.dll ............. [Build ******, API 060425]
  Module Umbriel.dll ........... [Build ******, API 060425]
  Module Titania.dll ........... [Build ******, API 060425]
  Module Oberon.dll ............ [Build ******, API 060425]
  Module Neptune.dll ........... [Build 100215, API 100212]
  VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
  Finished initialising world
  Module Spacecraft3.dll ....... [Build ******, API 060425]
  ---------------------------------------------------------------
  >>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
  At least one active module is accessing an obsolete interface function.
  Addons which rely on obsolete functions may not be compatible with
  future versions of Orbiter.
  ---------------------------------------------------------------
  Module XR2Ravenstar.dll ...... [Build 100507, API 100503]
  Finished initialising status
  Finished initialising camera
  Finished initialising panels
  Finished setting up render state
  **** WARNING: Mesh not found: .\Meshes\.msh

 

[Woo482]

Spacecraft3.dll could be causing the crash, I'm pretty sure it's not compatible with the new betas, and to Orbiter-Forum !

 

[Xyon]

Indeed it isn't, we shall need a new version for the new API when it's finished I suspect.

Beta testing addons always works better if those addons are the only addons you're testing . Just FYI. And also, welcome to OF.

 

[dbeachy1]

OK guys, the XR Release Candidate 2 builds are ready for public testing. The most significant change is the implementation of the XRVesselCtrl 2.0 APIs, which now allow other Orbiter modules to set or clear XR vessel damage while Orbiter is running. Here is the list of changes since the RC1 builds:

* Updated the gear indicators on the HUD to use thicker lines to better match the look of the new HUD in Orbiter 2010: lines are either three, four, or five pixels wide now depending on the resolution of the Orbiter window. [Suggestion from tl8.]

* Fixed bug where "UMMu Required" error message box was hidden underneath the main Orbiter window if UMMu was not installed and Orbiter was running in full-screen mode. [Reported by Xyon.]

* Fixed bug where the airbrake (speedbrake) still functioned when the ailerons were offline. [Reported by supersonic.]

* Fixed bug where damaged ailerons functioned again after the scenario was saved and reloaded. [Reported by woo482.]

* Fixed bug where vessel pitch still worked when the ailerons (elevons) were offline.

* Added comma separators to the altitude indicator on the HUD to make it easier to read.

* Fixed memory leak in the tertiary HUD code.

* XRVesselCtrl.h (for the XRVesselCtrl API) is no longer included with each XR vessel: it is now shipped with the new XRVesselCtrlDemo module, which is downloaded separately.

* Fixed XR2 CTD when running the release-mode (optimized) binary under the debugger when OrbiterSound was not installed. [Many thanks to Artlav for helping me reproduce the problem.]

* XRVesselCtrl API: fixed bug where ShiftCenterOfGravity did not work.

* XRVesselCtrl API: fixed bug where GetCenterOfGravity direction was reversed.

* XRVesselCtrl API: fixed CTD with 'GetStatusScreenText': changed method call signature to 'int GetStatusScreenText(char *pLinesOut)' in order to work with XR vessels' static linking.

* XRVesselCtrl API: fixed bug where the XR2 incorrectly reported "N/A" when querying its payload bay door status.

* XRVesselCtrl API: refactored several 'Get<foo>' methods to be 'const' wherever possible. [Refer to XRVesselCtrl.h for more information.]

* XRVesselCtrl API: fixed bug where 'SetElevatorEVAPortActive' call on the XR5 did not work.

* Switched main engine gimbal up/down keys: Nose-Up=ALT-;, Nose-Down=ALT-P.

* As a quick fix to the XR vessel sometimes being damaged or destroyed during a playback (due to damage fuzzy logic), XR vessels can no longer incur damage during playbacks except for hard landings and vessel crashes.

* Increased the XR5's gear compression distance by 0.7 meter so it now sits 0.7 meter lower than before.

* Added new 'EnableDamageWhileDocked' config parameter to the XR configuration files to allow the user to prevent damage from occurring to the XR vessel when it is docked inside a larger vessel. The default value is '1', which means that damage is enabled while docked. [Feature requested by Cairan.]

* The XR Flight Operations Manual had some minor updates (now version 2.1a) and was converted to PDF at a higher quality setting.

There is also a new XRVesselCtrl test/demo application that I developed to test the XRVesselCtrl 2.0 APIs. It is downloaded separately from XR vessels and is designed for use by other add-on developers. Here are some excerpts from the readme file:

-------
SUMMARY
-------

I originally developed this module so I could properly test the XRVesselCtrl 2.0 APIs. However, I decided to release it so that other add-on developers could use it to view sample code for each XRVesselCtrl API call as well as play around with the XRVesselCtrl APIs in order to see exactly what effect a given API call has. Please note that unlike other XR software this product is not designed for use by end users (XR pilots): it is designed to provide sample code to demonstrate and test the XRVesselCtrl 2.0 APIs for other add-on developers who want to develop their own code that interfaces to XR vessels. Full source code and Visual Studio 2010 C++ project files are included.

...

----------
WHAT'S NEW
----------

Beyond the new XRVesselCtrlDemo test/demo application, the significant changes to the XRVesselCtrl 2.0 APIs over version 1.0 are:

1) A new static XRVesselCtrl::IsXRVesselCtrl(const VESSEL *pVessel) method that allows you to easily and safely check whether a given vessel supports the XRVesselCtrl APIs.

2) A new SetXRSystemStatus(const XRSystemStatusWrite &status) method that allows you to set or clear damage dynamically at runtime. This will allow developers to write custom damage modules that perform things like "random damage", and you can now repair damage to XR vessels at runtime. [In the demo application the command to repair all damage is 'Reset Damage'.] Note, however, that the Reset Damage call will not "uncrash" a crashed ship.

3) Several bugfixes made to the XRVesselCtrl APIs.

Since you can now set and/or clear (reset) XR vessel damage at runtime using the APIs (e.g., from the demo app), to all you guys who have been asking for a 'random damage' module for the XRs, now you can write one using the XRVesselCtrl APIs. For more information, take a look at the readme file in the XRVesselCtrlDemo app.

KNOWN ISSUES:

* oapiIncHUDIntensity and oapiDecHUDIntensity do not work in the latest Orbiter beta, so the HUD brightness rocker switch only affects HUD data rendered by the XR vessels themselves. Selecting HUD color, however, works fine.

* Payload bay camera view does not work under Orbiter_NG: the ship's mesh is not rendered. This is due to an Orbiter external graphics client issue.

* Transparent "blitting" is not supported by external graphics clients (such as D3D7Client) with Orbiter_NG.exe, and so various indicators on the 2D instrument panels will not look right. This also affects the artificial horizon indicator, so it will not render under Orbiter_NG. A future build of the XRs will address this problem by refactoring the affected panel components to render using a transparent mesh rather than transparent blitting. However, this is not a trivial change and so it will be deferred until a future release. In the meantime, you can run Orbiter.exe instead of Orbiter_NG.

As a reminder, these are release candidate builds and so no non-trivial new features will be added at this time. If you find a bug, please be sure to test it in a clean Orbiter 2010 beta installation first. Here are the installation instructions:

1. Install Orbiter 2010 Beta 100524 or later.
2. Install UMMu 2.0.
3. Install OrbiterSound 3.5 (optional, but highly recommended).
4. Install the XR1 and/or XR2 and/or XR5 release candidates.
5. (Optional; for developers) Install the XRVesselCtrlDemo module.

Several files are necessarily duplicated in each XR package, such as the flight manual and the invisible payload bay vessel .cfg file; you may safely overwrite your existing version (or not) as you choose -- the files are identical in each release.

The zip download links are below:

DeltaGliderXR1-1.6_RC2
XR2Ravenstar-1.1_RC2
XR5Vanguard-1.3_RC2
XRVesselCtrlDemo-1.0_RC1

As with RC1, there are no RAR versions available for these release candidates; RAR versions will be available when Orbiter 2010 goes gold. Thanks again for your help testing these release candidates!

 

[dbeachy1]

NOTE:
The new XR versions have gone gold along with Orbiter 2010; more information here.

As such, the XR Release Candidates have been superseded and have been pulled from my site. Thread locked. :tiphat: