Search results

https://github.com/MatiasSaibene/Multistage2026_for_OpenOrbiter/blob/master/README.md

That's right, thanks. I need to create a short guide for compiling Multistage2026 on Linux and Windows using CMake. Give me a moment and I'll put together a short step-by-step guide on GitHub.

New Multistage2026 release for testing. Changes to booster mesh loading. Now detects booster groups. The error was introduced by me when I migrated the code and wrote new code to use the C++ STL.

@Gondos has been working quite a bit on an "experimental" Linux port. It works very well as far as I can tell; I use it daily and to develop some C++ add-ons. There's still a lot of work to be done, but @Gondos suggested first implementing and unifying everything on Windows and then bringing it...

I'm going to Windows right now to try it out. Thank you so much for your work!

Could you share some Ariane 5 meshes and .cfg files with me (privately if you prefer)? I may have made a mistake when changing the index of the BOOSTERS parser.

After a little investigation, I found the reason for the vessel name: it's using the mesh name. I'm almost certain the same thing was in Multistage2015; I don't recall adding that feature myself. In fact, I always just adapted the Multistage2015 source code because I'm sure Fred18 did a great...

Here is: https://download.blender.org/release/Blender5.0/

Have you tried the mirrors? https://www.blender.org/about/website/

I remember using this in Orbiter 2010: https://www.orbiter-forum.com/resources/videnie-orbit-drawing-1-0.2134/ I believe that functionality is built into Orbiter 2024 + D3D9 Client.

Well, I think the parser I tried to fix ended up doing black magic.

I'm pretty sure not, given that UCGO wasn't updated for Orbiter2024.

This is very valuable information because I see the problem with the numbering persists. I'm currently working on Linux to fix a bug in Multistage2026 that prevents the meshes from displaying correctly at launch. I have more diagnostic tools on Linux (Valgrind, for example). So, I'll sync the...

Welcome to the forum!

I'm actually working on fixing mesh indices right now! I think Fred was using 1->10 and I'm now using 0->9. That improves a lot of things in C++, but I need to maintain backward compatibility.

I believe the secret lies in using lowercase letters in the parameter names of the .ini file. I need to investigate why the component that processes .ini files (SimpleINI) is being too attached to case sensitivity. This would solve many problems, and make writing .ini files easier.

@jacquesmomo Here's a video of how Ariane 6 works on my Orbiter installation (on Windows 11): As you can see, some parameters, like the offset, are incorrect. I've attached the .dll files I used and the modified .ini file with some key variables in lowercase.

Well, first of all, thank you all very much for your contributions and reports. I'll be modifying the A64.cfg file shortly to properly test the boosters. I'll also be releasing another test build within the next few hours so you can try out the new fixes. @jacquesmomo Regarding your question...

I'll try to answer the questions: 1) As far as I can see, the commands are being truncated to a certain number. That might be why they aren't being applied correctly. I'll look into it in more detail later. 2) and 3) I have absolutely no idea where those parameters came from, but if they were...