I was assuming faulty memory chip based on my (possibly incorrect I now realize) perception that only one computer was generating this error and it was working fine on others.
This, especially if it's at the same address. Happening at different addresses would have suggested a bug in orbiter's allocation scheme, but if it always happens at the same address, you've probably got a stick going bad. Also, has anyone else been able to reproduce this bug?
Isn't torque just a force over time? Shouldn't GetTorque() then return GetForce() * simdt? I could be completely off my rocker there as well, but I think that's what I learned in physics class.
I have to a limited extent. I'm right now more working on the input stuff.
You and me both apparently.
Add-ons for Add-ons... I like it.
That's pretty much exactly what I did. It actually works pretty well.
Nice. I use Gentoo mostly myself, but as you say, Orbiter is strictly windoze which isn't so bad. I virtualize windows when I can in linux, and virtualize linux in windows when I can't.
The reason for the pulse concept is because it is something that is provided by every single Nasa space...
This project is going to have to go on hold for a bit as my computer monitor decided that it didn't like me and blew it's transformer. I've looked but been unable to find a good replacement transformer, so I have to wait until pay day to get a new monitor. I posted this from my wife's laptop...
A drop in solution which I'm very interested in using in my UFBW development. I asked in that thread, and I'll ask here as well if you'd be interested in collaborating on that project?
It has to go on a couple of week hiatus at the moment as my monitor managed to short itself out, but details...
If you clean memory right before running orbiter (several programs on the web to do this) does this still happen? And does it happen to anyone else? If yes to both of these, then it is probably some bug in the mesh load function. Meshes don't take that much ram though, so I'd be surprised if...
I wouldn't celebrate TOO quickly. They finalized that standard a year ago. It'll be at least one more before we have a compiler that meets most of it, and at least 3 more before we can use that compiler on Orbiter.
I don't know if you visited the trac yet? The first phase of the project was documentation and concept research. I finished that one last night when I managed to gimbal the engines of the xr2 and dgIV without issue. I've also demonstrated use of control surfaces, despite what the...
Love it so far. The ascent profile is pretty straight forward, but I love that the flight envelope is clearly pictured on the EICAS. That is a feature I've been wanting in the XR fleet for a while as I have to guess at the proper profile.
One thing I'd like to see is after switching the...
I've set up a project management page at http://ufbw.dyndns.biz. This page will evolve more frequently than the forum here. I'm working on setting it up so people will be able to get email updates from it as well.
It occurs to me my original reply was kinda harsh and not helpful. The suggestions about multiple inputs or any other kind of input mapping is outside the scope of this project. I plan on working closely with another author who is working on a project that'll do that stuff, the rest I'm...
Interesting. Mostly interesting in the fact that I had the exact same idea, with one tweak. The normal modes would not be based on a specific rate of rotation, but how quickly it'd be able to null that rate of rotation. "Hi" or something like that would be whatever rotation could be nulled...