Search results

You can edit the corresponding XR vessel configuration file (e.g., XR2RavenstarPrefs.cfg) right near the top: #-------------------------------------------------------------------------- # Define the 2D panel resolution that the XR2 should use. # # 0 = Autodetect (default) # 1 = Use...

Setting the Panel Scale per this post works fine for me on Windows. If Panel Scale does not work under Linux, that points to a Wine issue, not an XR vessel or Orbiter core issue.

Welcome to Orbiter-Forum! To answer your question, the permissions page shown literally says how to do that: You are now at one approved post (the post you made above), so just making a second, non-spam post will grant your account full forum membership, including the ability to download...

This is expected behavior until if and when a replacement for UMMu is available. Then I can re-enable crew support in the XR vessels.

So @Xyon and I looked into this, and it looks like the permission for moving add-ons ("Resources", as the Xenforo Resource Manager calls them) is hardcoded for moderators and admins only. So if anyone wants to have their add-on(s) moved to a different category, please DM any staff member and...

Hmm, I'll look into that. Thanks for letting us know!

BTW I saw some add-ons that were deleted and then recreated in a different category. As a heads-up to everyone, you don't need to delete and recreate your add-on just to change its category -- it's easy to move it: A "Move addon" modal pops up: ..and then click on the "Destination...

One that @garyw found:

The XR5 Vanguard, DeltaGlider-XR1, and XR2 Ravenstar are cutting-edge, high-performance spacecraft for the Orbiter Space Flight Simulator. All XR vessels are built on a common framework and share similar internal systems. Highlights include three (XR1), four (XR2), or five (XR5) 2D instrument...

The XR5 Vanguard, DeltaGlider-XR1, and XR2 Ravenstar are cutting-edge, high-performance spacecraft for Orbiter 2024. All XR vessels are built on a common framework and share similar internal systems. Highlights include three (XR1), four (XR2), or five (XR5) 2D instrument panels that natively...

The XR5 Vanguard, DeltaGlider-XR1, and XR2 Ravenstar are cutting-edge, high-performance spacecraft for the Orbiter Space Flight Simulator. All XR vessels are built on a common framework and share similar internal systems. Highlights include three (XR1), four (XR2), or five (XR5) 2D instrument...

XRSound for Orbiter 2016 automatically adds sounds and voice callouts to all Orbiter vessels (not just XR vessels!). Version 2.0 adds support for Orbiter modules, such as MFDs or other plugins, in addition to Orbiter vessels, and version 2.0 is fully backwards-compatible with all XRSound...

The D3D9 (DX9) client was built for Orbiter 2016, not Orbiter 2006, so it's not compatible with Orbiter 2006. Orbiter 2006 is 16 years old now.

Just launched yesterday on Steam, PS4, and PS5. User reviews so far: EDIT: https://www.theverge.com/23271212/stray-game-cats-watching-twitter-annapurna-interactive

There was some discussion about possibly including Face's SoundBridge in the OpenOrbiter distribution and installing it alongside XRSound by default, but I don't know what the status of that is.

Grats on tracking down that bug! (y)BTW, it's actually a three-byte difference between bools (one byte) and ints (four bytes). :) So doing a sscanf of an int (via "%i") into a bool variable (which only reserves one byte of memory) will overwrite 3 bytes beyond the end of the bool, which will...

You should be able to set a breakpoint in the debugger before even starting Oribter.exe -- check out https://docs.microsoft.com/en-us/visualstudio/debugger/using-breakpoints?view=vs-2022. Try putting a breakpoint at the start of clbkSetClassCaps, for example. Then once you start Orbiter.exe in...

You will need to set up properties for a Debug build and set the build target to Debug. There are separate project properties for Debug and Release builds, and the two do not conflict. Generally speaking, you will always want to run Debug builds during development and only switch to Release...

If you run your add-on under the Visual Studio debugger (as a Debug build, of course), the debugger will pop up on the line where that exception occurred. You can check out this thread for details about how to run your add-on in the debugger, enable Visual Studio's runtime memory heap checks to...

Since you can reproduce the problem consistently, I suggest a standard debugging approach here: Set a breakpoint at the start of the callback where you know the memory overwrite occurs (clbkLoadStateEx, in this case). When you hit the breakpoint, add the variable the you know gets corrupted to...