Search results

Hi there, after a long period I found some time to look again at my fork of orbitersim/orbiter at github. There are Pull Requests from dependabot (in my fork), what is the recommended way to handle these? Thanks in advance, Kuddel

I've noticed in your video that you've started orbiter.exe, not orbiter_ng.exe. I don't even know if orbiter.exe still works in the 2024 Versions. So make sure you test with orbiter_ng.exe This confusion is very unfortunate. So try Xyon's steps, they should get you goin' I would also recommend...

Maybe just "[CTRL]+[H] Toggle HUD display on/off" was done?

I would have thought that commenting out (double-slashes) the two not wanted lines in \Config\MicroTex.cfg would solve that... Something like: // BODY [<string> BodyName] // NORMALS [<bool> 0-1] // LEVEL [<int> 0-2] [<string> texture name] [<float> resolution pixels/meter] BODY Moon NORMALS 1...

A picture is worth a thousand words! (y)

Since "Herr Lehmann" (The movie) I have my favorite melancolic version: ...english, yes - but still amazing.

(Current) Open Orbiter / Orbiter 2024 does not have any version Number set (yet) - so 0.0.0.0 is O.K.

From XRSound.h: So looping over Sound IDs 10000 to 11999 might work, although it's a bit much I think. In the same file: enum DefaultSoundID { AirConditioning = 10000, // 10000 LandedWind, // 10001 AudioGreeting, // 10002...

Maybe the BurnTime is too long (1.3 hours)...?

I have the same issue with a stock Orbiter and DG setup (my Graphics is a Intel(R) Iris(TM) Graphics 550 however). This behavior appeared quite a long time ago (October 2022! See this post) on my machine and I could not find out what exactly is the issue. I had to completely re-install my OS...

...that went slightly off-topic very soon - and well :p

Addendum: As you are using Orbiter 2016, there were two symbolic links: {Orbiter_root}\Modules\Server\Config => {Orbiter_root}\Config {Orbiter_root}\Modules\Server\Sound => {Orbiter_root}\Sound (only if OrbiterSound (4.0) Module detected)

I don't think so as the symbolic links that the D3D9Client creates are only from \Modules\Server\ (link) to \Config\ (real). The D3D9Client configuration is located in Orbiters "root" folder \D3D9Client.cfg. ...unless I did not understand the issue correctly. In case you would like to remove...

...another 4 hours well spent! NASA's Mariner Missions Thanks again to Homemade Documentaries, in case your're here in the forum as well (y)

just heard of this... https://www.nasa.gov/news-release/acting-nasa-administrator-reflects-on-legacy-of-astronaut-jim-lovell/

AI, in my experience, is very good at some things like generating lots of words that describe things I don't like to write by hand. For late ISO certification for example I used it to create a procedures (a.k.a. Processes) for upgrading "IT Assets" and many other processes.... Nothing new it...

Yeah, that paint with a bit of concrete- and steel-structure beneath might be needed:p

Those two lines were just to check if the vessel-class is acually the one we expect - not every vessel does react to "P" the same way. So these line are more of a debug output to indicate when something is not as expected. In "production code" that kind of error has to be handles differently of...

I do not have any experience with Orbiter running on Windows 11, but it should work in general. For Orbiter D3D9Client to work (Orbiter_ng.exe) it is essential that you've installed the DirectX 9 runtimes. Having any other Direct X capabilities does not help, Direct X 11, 12 do not include that...

Thanks again for the countless efforts you put into this Xylon!