Search results

This is not entirely accurate. Orbiter_NG uses no graphics client by default, which is why it has the suffix "_NG" which is short for "No Graphics". It can make use of any graphics client, it's just that D3D9Client is the only one available.

Not really. There have been a couple of attempts at Virtual Space Agencies (VSAs) through out the years but they all eventually folded. It's because Orbiter isn't really geared at multi-crew member operations. There is a couple of multi-player add-ons however but these are more geared at...

No. UMMU needs to be recompiled to work with Open Orbiter AKA Orbiter 2024.

The moon isn't visible in front of the sun during an eclipse (this is of tomorrow's eclipse as seen from San Antonio, Texas):

@jarmonik Could you include a section on *.flt files in the OpenOrbiter D3D9Client manual?

Circled areas in the attached photo shows the SSRMS Elbow cameras on their Pan/Tilt Units (PTUs) AKA "swivel mounts". Also, don't be too literal on PR CG materials, those can be wildly incorrect (see how long SLS sported it's "Saturn V" appearance despite never having it the first place also...

Shouldn't all of the OS specific code be replaced with their XRSound equivalents given the closed source nature of OS and the fact that there's no need for it anymore as XRSound now comes included with the base install of OpenOrbiter?

Is there a way to tweak the distance haze in OpenOrbiter D3D9Client? I tried playing with the various sliders in the Atmospheric Controls dialog, but none of them had any effect on the distance haze. Is this something that needs to be from the cfg file?

Isn't more a case of that Windows 11 can't run it? Also, what about the Terrain Toolkit guide?

Where in the development phase is this: https://github.com/orbitersim/orbiter/issues/381 Also, could a tutorial be written on how to use the Terrain Toolkit?

Here's improved ISS Radar Test scenario which has the orbiter properly on the R-BAR at 600 ft rather than the weird offset that the original has.

Not what I am seeing:

Would it be possible to incorporate a damper for "nervousness" of the A2 LINE OF SIGHT RATES display? Also, it seems like the RR half of the Ku band system doesn't save/load a tracked target, forcing you to redo the initial two steps of the KU OPS cue card of the RNDZ FDF to reacquire the target...

Where do we stand on getting this issue from 2020 properly addressed: https://www.orbiter-forum.com/threads/d3d9client-development.16787/post-263061

No issues with that version here. Could you try deleting your D3D9Client.cfg and Orbiter_NG.cfg files? I had a problem with the planetary textures being MIA with the same error message and that was due to an overwritten Orbiter_NG.cfg file from jarmonik's BakedVC_testing.zip.

Do you need the actual *.elv files for the Terrain Toolkit to function or while the *.tree files suffice?

Orbiter log after the CTD: **** Orbiter.log 000000.000: Build Feb 1 2024 [v.602931718] 000000.009: Timer precision: 1e-07 sec 000000.150: Found 0 joystick(s) 000000.402: --------------------------------------------------------------- 000000.408: BaseDir : E:\OpenOrbiter\ 000000.413...

The screenshot was with the Baked_VC dev package jarmonik posted earlier. Now, it is build 240201, the x86 version.

Tried that and it still CTDs. This is with a clean install of OO.

So how do I access the built it one?