Search results

Okay, that's pretty cool.

Could you paste that into some code tags. it's kinda hard to tell. If the problem only happens sometimes, it's almost certianly due to uninitialized memory.

Are you running Orbiter through Orbiter.exe or Orbiter_NG.exe?

@kryptoid256 -----> https://www.orbiter-forum.com/resources/d3d9-for-orbiter-beta.5495/

It figures that I assumed this was going to be a thread about data-structures...

Not really. To be honest there aren't really a huge amount of Orbiter vessels with complicated virtual cockpits. Generally, keeping things organized is probably best. Perhaps you could make a class for each of the "panels", and then have a std::vector of your switch class to keep track of them...

Set your mesh resolution back to 32. And see if that fixes it. I don't know if I can confidently say what the problem is, just by looking at a screenshot. (and we can't really debug Orbiter 2016) but it looks like you might be running out of memory for terrain.

Yeah, each time we make a major update to the systems, the only 100% reliable method we have for updating those is to refly the full mission each time. So those tend to bo increasingly less updated the further into the mission they are. Your safest bet is to use the T-4 hour scenerios. If you...

enabling "absolute animations" in the D3D9 client settings may also be of use here.

When you say trim tabs, I presume you're referring to the Deltaglider? That's very weird, I didn't even think you could set elevator trim independently. Do you have any joystick or controller plugged in that might be interfering?

I was in fact wrong about how easy this would be haha. I'm still doing it though. Here's a first pass attempt at a change-log. It will need some cleanup and some distinction between major/minor/bugfix/etc. Also, there are some major changes to Lua and to D3D9 Client. I still need to add those...

I would be happy to.

A change-log could easily be created from the 2017 beta rev notes, and the merged pull requests since 2020.

GLS had proposed this solution, although I'll admit I don't know enough about cmake to help much. If we can't figure out how to do this automatically in the next week or so, I would recommend the following alternative solution. When we're ready to release, make a new branch called...

I'd that one ready for review?

yes

I think your video is private vs unlisted

Cautionary tale about mascons and low polar orbits

It's probably advisable to wait until OpenOrbiter actually releases, or people will very likely get confused. Hopefully with the work going on at the moment, we will have a release soon.