Search results

It looks excellent! I'll soon be working with renewed energy on Multistage2026.

Initial UACS cargo support.

Hi everyone, I haven't had much time lately to test a new tutorial for running Orbiter on Linux using Winetricks. I'll make a new one soon, although I've had serious performance issues in my latest tests.

Where do you want to go today?

First textures and tests of the An225 cargo bay.

After struggling with an uninitialized memory error (I'm incredibly clumsy), I finally got the cargo bay opening working. Tomorrow I'll continue with the cargo bay's MESHVIS flags to give it a decent interior.

Vive la France! It's an excellent step forward; I always dreamed of an Orbiter in Spanish. When everything is ready, I offer to translate it into Spanish.

I hadn't thought of that, you're right! I need to review the code. There is undoubtedly an error in the formatting of the strings. I also forgot to mention that Multistage2026 is now, and will be for a while, case-sensitive. It also doesn't accept periods in filenames. I need to fix this as well.

Returning to a project I love...

Thanks for testing! Yes, the exhausts issue is still a bit mysterious; I don't understand why it sometimes works and sometimes doesn't. I have all the variables initialized. The boosters are working now, but the MFD still isn't. I recommend disabling it because it causes memory corruption.

Thank you so much for your report! I'm glad to hear that something is working! I'm going to take a short break from programming Multistage2026 while I read your reports and focus on what the next steps will be.

I have another test release. This time I fixed MS_Pad, which was not displaying due to memory corruption. What I did was port the code to Linux, and once there, using tools like Valgrind and GCC ASan, I was able to correct many pointers and out-of-index accesses. However, problems persist...

Thanks again! I'm currently modifying the MFD to use clbkGeneric as the method to communicate with the Multistage2026 rocket. Previously, a pointer to the class was used, but because the class wasn't loaded into memory, the MFD was failing when starting Orbiter and before starting Multistage2026.

After getting frustrated with not being able to make any progress with MS_Pad, I decided to focus on MFD. The result? MFD isn't displaying, but MS_Pad did appear, and it seems the other errors were mysteriously/magically/miraculously fixed. And since I used those three magic words to describe...

It's good to see you back! Hopefully, the problems with your previous account will be resolved soon. I believe it's one of the oldest on the forum, and from the previous version, M6.

Designing the VEx1b in Blender for testing at Multistage2026. The VEx1b is a prototype of the Tronador II rocket, whose current development status is unknown.

Multistage2026 source code for Linux uploaded! https://github.com/MatiasSaibene/Multistage2026_for_OpenOrbiter/tree/master/Multistage_for_Linux

I removed several arrays of 7500 elements each and replaced them with std::vector. I'm still having nightmares... So the question arises: how did MS2015 work perfectly in first place, and then, due to a few minor changes, it no longer works?* Or better yet, how did it work perfectly with so...

Testing Multistage2026 on Linux. I think Linux is stricter than Windows, and memory errors quickly become apparent. I was able to get the SLS exhaust texture to display. And I also got @Buck Rogers' N1 working (by the way, what a magnificent 3D model!).