Search results

For all that Versions of Orbiter: No, there isn't a Lua function. And there never will be, as old Versions are ....old ;) For C++ this API Function has been available for ages (I even believe it is ABI compatible all the way) For Lua this might be different: Orbiter 2010: No, not at all Orbiter...

You are asking me? I have not the slightest idea :D ... Actually I have a slight idea: I think it' a subproject, as git keeps nagging about 'subprojects' in .\Extern from time to time... "a target"? What exactly do you mean by that? And to be honest, I can't make any sense out of that sentence...

No luck :( These error appear as soon as "the cache" or whatever that is is configured... 1> CMake generation started for configuration: 'windows-x86-release'. ... 1> [CMake] CMake Error at Src/Vessel/DeltaGlider/Help/CMakeLists.txt:20 (add_custom_command): 1> [CMake] Error evaluating...

32 bit ... you mean when building OpenOrbiter, right? As I don't know how to build vspkg as 32 bit. Let me try that...

Hmmm no change :( (except for another useless 97,5 MB of "tooling")

Aha! Thanks for the info. So "just" clone & build vspkg (as noted here I guess...) and re-try to generate docs in OpenOrbiter... I will try...

A general documenting question: Has anyone been able to build the documentation? I am still struggeling to get it working :( The README.md says: I think I need that vspkg thing (and do something with that?), as all the other requirements I do fullfill (I believe :D ) Can anyone possibly help?

PR for the "predictable precision" has been requested https://github.com/orbitersim/orbiter/pull/411 After that is merged, the ScriptMFD changes can be merged.

Hi @Thunder Chicken , thanks for the testing (y) The issue with truncating of floating-point values (C++ double types to be precise) is something that has been present in Orbiter since ages :eek: That's why most of the add-ons that needed a specific precision internally build a string and use...

Better that I've feared.

"vessel script scenario"? If you mean .\Scenarios\Tests\VesselApiTest.scn, that's intended to do so. Automatic CI Tests need to be run that way - this has nothing to do with the changes (see Tests\README.md). That's why I said it is another challenge to write those CI "headless tests"...

Here you are. Notes: Backup your original LuaInterpreter.dll - it is overwritten ;) The Scenario is based on my unit-test approach, so nothing really usefull here. Note however how the key-value pairs are represented in the BEGIN_MFD Right block. The ScriptMFD itself...

I could try to pack the changed binaries (I think only a couple of DLLs, as documentation can not be generated yet ;) ...) Do you run a 32-bit version or a 64-bit version?

Hey, after lots of trouble getting the current OpenOrbiter to build (mainly CMake oddities) i have been able to implement some of the missing Orbiter-API. This is just the pain 1 to 1 "translation" of C++ API to Lua, so not exactly what you've requested, but as I said: One step after the other...

Ah, I see. Yes that is absolutely right! You mean Doc\Orbiter.odt , right? Yes, a history.txt ore similar would also help when updating Doc\Orbiter.odt. Yes as Martin explained here the CI currently does not do this.

You mean the DirectX 9 runtimes? I couldn't install those, as it was not my machine ;) and I don't want to mess up that system. If we are lucky I can get my hands on another machine on wednesday where I can do everything because it will get wiped (complete OS reinstall) anyway ;) Prop a note if...

Hi Jarmo, I've tried your binaries (although I did not expect 32bit build) The System I had at Hand was a Windows 11 Machine with there GPUs: On the launchpad Video-Tab when I first selected "D3D9on12Client" under "Graphics engine", the "3D device" Combo-Box was empty... Only after switching...

I am not sure I understand that correctly. Accepted (merged) Pull Requests do update a document somewhere? Or do you mean: It is possible to find that information by looking at (closed) PRs.

Looking into CMakeLists.txt (The main one in root directory): Is this valid syntax? I mean line 103 ... Lines 86 & 87 have similar entries, but not an extra double-colon ("::"). And by the way, where is LUA_DIR defined?

How exactly? Might be nice to know for others.