Search results

You probably want to look at the vis-viva equation here: v = \sqrt{\mu \left(\frac{2}{r} - \frac{1}{a} \right) } From this you can calculate the orbital speed at apoapsis of your current orbit (v_{ap} = v(r_{ap})) Likewise, you can calculate the orbital speed at periapsis of the target orbit...

a) It's not gone yet. The inline and DX7 clients still build with the current sources (32-bit target only). When the 32-bit platform gets dropped, which will happen eventually, the DX7-based clients will be history. For now, they are still useful to me, because I am more familiar with them, so I...

I think I fixed the build script for the github runner. Can you please check if it works for you now?

I see. I suspect what's happening is that when building Orbiter on the github CI runner, cmake doesn't find the DXSDK installation and skips the D3D9Client build. I'll have a look to see if I can figure out what is going on here. Or maybe somebody more familiar with the build.yml script can spot...

I am not actually sure what this means. Are you saying your build doesn't produce a D3D9Client.dll in Modules/Plugin of your build directory when you build Orbiter? Do you get any error messages?

That is actually not quite what I meant. It is just that now that the d3d9client feature branch is merged into main, all commits to d3d9client are now commits to main. So for future modifications to the D3D9Client it would be cleaner to branch off main than to continue to commit to the merged...

Perfect - thanks for the quick response! All done now - enjoy the D3D9 client on the Orbiter main branch! Is it ok to delete the d3d9client branch? I tend to delete merged branches to keep the branch list clean.

Just checking in to say hello (it doesn't happen very often these days). I wanted to ask @jarmonik and the D3D9 developers about the d3d9client branch on github orbitersim/orbiter: is it ok with you guys if I merge the branch? I did upload a few commits to it (mainly minor stuff - rebasing to...

The AtmAttenuationAlt config entry is used only for visualisation. It has no effect on the atmosphere physics used in Orbiter. The physical behaviour is encoded in a DLL, and in fact you have a choice of three different atmosphere models: Orbiter 2006 legacy: do NOT use this. It is kept for...

High-Res texture packs for 2006

The earliest copy of Orbiter I have on record, from 2001.

Orbiter's 2002 release. Both files are needed for a working copy.

Orbiter's second release in 2002, which then included three subsequent revisions as patches to the base 021202 install. These are cumulative, which means if you want 030303 you need to unpack the 021202 base, then the 021206 patch, the 021217 patch, and then finally the 030303 patch, to get a...

The first revision of Orbiter from 2003. Not originally called 2003-P1 (as far as I know) but adjusted to fit the more recent format. You need _base and _tex for a working Orbiter install. _sdk is optional, for developing addons against.

The second revision of Orbiter from 2003. While this wasn't called 2003-P1 at the time as far as I can tell, that's what Orbiter later started using, so I've kept that format here as we go backwards in time. You need _base and _tex for a working Orbiter install. The _sdk is optional.

Orbiter 2005 - both the initial release and the later patch for a revision. The 050216 patch needs to be applied over the base 050116 install, it won't make a standalone Orbiter install by itself.

Orbiter 2006 base package.

Orbiter 2016-P1, base and separate SDK package. Only the base is needed for the core Orbiter application.

Orbiter 2010, in ZIP and MSI format - you only need one of these files.

Orbiter 2010-P1, both MSI and ZIP versions. You only need one of these files!