Search results

That's what happens when you're away from Orbiter for so long. Thanks, Face!

So after a long hiatus, I'm getting back into Orbiter, picking up with my truss system. I'm trying to get everything recompiled with VS2013, and I got it to work with a surprisingly small number of issues, however, I'm stuck on getting the scenario editor pages to appear. Here's the relevant...

Is nonspherical gravity enabled? What's your altitude? You are likely seeing small perturbations caused by some kind of external force. Nonspherical gravity and the atmosphere are the two most likely sources.

Wrong answer. There are plenty of reasons for consumer-level users to have overnight-running stuff without needing all the pro version has.

And if I have stuff that needs to run over night, then what? Sorry, but the concept of "active hours" is a bad one since it forcibly removes user control.

I'm with you Andy, including the bitter old man part. The unfortunate thing is I'm not actually an old man :(

It's got shiny graphics, but that's about it. There were numerous problems with the simulator going back half a dozen versions that still aren't fixed in the newest one (called Train Sim World).

Sounds like par for the course for DTG.

Just leaked footage of the launch attempt: http://www.gifbin.com/bin/042012/1334602684_footage_from_the_north_korean_missile_test_from_conan.gif

SQUEEEEEEEEE!!!!

Wow! That one really gets me :salute:

What I meant by that is high voltage + high current potential = scary. I'll happily walk up and touch a bus bar with 1 volt potential otherwise carrying a million amps. That 1 volts isn't enough to drive enough current through me to kill me. On the flip side, I have no problem touch a million...

Copper that big, looks scary when it's that exposed. I mean I guess it could be carrying like a million amps at one volt...but I doubt it.

:facepalm: I should have seen this coming. Ok, so, I'm making progress. I added independent roll thrusters. It seems to have pretty much solved it. The only sticking point is sometimes depending on how the vehicle rolls during ascent, it may end up way off heading. My target heading during...

Since you did realize what was being talked about booster-wise, I'll leave that out. But in terms of the sentence about multiple instances. What I mean is, that's why I'm so performance-conscious. No, they don't share state, but I still want to improve the efficiency of anything that's called...

No, there shouldn't be any sharing of state. The only things I would share is anything that would only be read and not written to (such as constants for defining mesh, thruster, fairing offsets).

For clarity sake I eliminated that line and replaced it with: return engineGuidance(time); But I still have the same results. PIDData is something for testing, I was using it to help determine how fast my PID Loop settled and how much it overshot so I could dial in the gain values. It's only...

The first RollGuidance method is used when the vehicle is vertical. So it rolls to a point where the top of the vehicle (+Y Axis) points to the desired heading. Then when the pitch program engages, it pitches "up" which puts the vehicle in a heads-down orientation.

No, it's not on github, I'll post the relevant methods here: //This method is just called from clbkPreStep bool Prometheus::updateGuidance(const double &time) { //mode 0 is engines only if(guidanceRunning) { //throttle engine user group if(guidanceMode == 0) { return...

When I wrote that, it was simply not working. As in there was no roll control at all. Now, somehow, and I don't know how, it only works from external view. If I go into the glass cockpit (it's a launcher, no real cockpit), it goes out of control when it gets to that phase of the launch. If I...