Hi, my DigitialOcean server doesn't have the free disk space to host large texture files. However, I'll let @Xyon know about the issues on the other mirrors. It looks like the orbiter.us domain expired.
Hello all,
After extensive discussion among the forum staff, we have updated Clause 2 of Orbiter-Forum's Terms of Service to:
Explicitly clarify the rules around posting demonstrably misleading information that may harm others (now labeled "Clause 2a"), and
Rewrite the generic "leagalese"...
All the Orbiter SDK samples, including the DeltaGlider and its mesh and textures, were already released under the MIT license by Martin. i.e., I'm sure this was already sorted out before Martin released everything under the MIT license.
You can just copy it to any 8 GB USB thumbdrive you can grab near many store checkouts for a dollar and transfer it with that. :)
Or you can just use your laptop's WiFi to connect to your home network and copy the Orbiter files that way -- but you will need to mark your Windows drive on your...
The short answer is simply extract the add-on's .zip file into your Orbiter installation's top-level folder; e.g., C:\Orbiter. Beyond that, some add-ons require additional configuration steps, so you will need to check the add-on's readme file and/or instructions on its download page.
See https://github.com/orbitersim/orbiter/tree/main/Sound/XRSound for details about how to configure and build XRSound via its VS 2019 solution file. XRSound is also built along with the Orbiter core if you enable that and configure irrKlang paths in Orbiter's CMake settings.
And yes...
From what I can tell, these GenericVehicle vessels do not define any thrusters, and so XRSound by design ignores them since we don't want XRVessel sounds playing for UMMu astronaut "vessels", for example. (This is also why those vessels are not shown in the log file.) If you really want all the...
If XRSound is not creating log entries in the log file for your custom vessel, make sure that you enabled verbose logging by updating the XRSound.cfg file as per step 1 on pages 11-12 of the XRSound User Manual. If you do that, the log will show details for all vessels in the scenario. This code...
The 32-bit build of XRSound 3.0 should in theory work fine with Orbiter 2016, although I have not tested that. It will not be officially supported, however.
As for your question, what does "No issues with Orbiter Sound" mean? The configuration files for XRSound are entirely different from...
BTW as a matter of best practice / compatibility, it's best to always install Orbiter to a normal folder that has write permissions, such as C:\Orbiter. Installing Orbiter to something like C:\Program Files\Orbiter will cause permission headaches, as files under C:\Program Files are supposed to...
I respectfully disagree -- while I agree using 'const' can result in extra changes during development (e.g., the chain effect mentioned above), using const has helped me catch potential bugs as I develop, and it keeps me from accidentally modifying an object when I did not intend to. :) However...
I upgraded to the very latest VS 2019 build (Version 16.11.2), which is one patch newer than the one that broke CMake for me, and it looks like it's working again! Here is what I did:
Opened Orbiter folder in VS 2019.
After Ninja finished reading the makefiles (and this was where the previous...
As it turns out, I just committed an enhancement last night for the upcoming XRSound 3.0 that adds six new sound modification calls, including these two:
// Sets the playback speed of the sound with the specified ID.
// Note: the sound must have already started playing via PlayWav for this to...
Hi all! I am pleased to announce that the XR vessels, with the exception of the XR2's mesh and textures, are now open-source under the GNU General Public License 3.0. The XR vessel version numbers have all been bumped to 2.0-beta-1 to 1) differentiate them from the current public releases, 2)...
========== Rebuild All: 104 succeeded, 0 failed, 3 skipped ==========
Looks good (and it was failing consistently for me before). Thanks for the quick fix! Pull request merged. (y)
The first thing I would do is test in a clean Orbiter 2016 installation with just the XR vessels and XRSound. If you can duplicate the CTD in that configuration, please paste the scenario file. Otherwise, you can continue testing by installing one additional add-on a time, testing each time...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.