- Joined
- Jan 13, 2008
- Messages
- 2,302
- Reaction score
- 6
- Points
- 38
- Location
- Atlanta, GA, USA, North America
So I decided to pick up Orbiter again and actually fly it after years stuck in a development cycle. I thought that the first thing that might be interesting, would be to fly to the moon, using the DG until I got my bearings again. This time however, I decided to use the D3D9 client which gives massively higher framerates on my system (higher fps == higher accuracy of course). The first time I flew, I barely had to make any midcourse corrections. Thinking that was odd, I checked my parameters after the flight and sure enough, accidentally left nonspherical, radiation pressure, and gravity-gradient torque off. The next flight I flew, I made sure those were on...and only had to make a couple of real small corrections, and even then my lunar periapsis was only off by about 5km. So I downloaded D3D9 3R tonight, and flew a slightly different mission, but still, I only had to tap the thrusters once or twice throughout the entire mission before making my orbital insertion.
Now, I have done only two things differently between this, and other flights where I had made three or more MCCs at various stages. I set IMFD's map program to use the RK7 integrator, and I used D3D9. The only obvious differences aside from the lack of having to make MCCs, has been the massively increased framerates. Using the inline graphics, I got 50s-70s, but under D3D9, while IMFD was running, framerate remained in the mid-200s the entire trip. Have the higher framerates really had that much effect on the accuracy of executing IMFD's burn solutions? Or is there something possibly with settings in Orbiter itself that I'm just missing?
Now, I have done only two things differently between this, and other flights where I had made three or more MCCs at various stages. I set IMFD's map program to use the RK7 integrator, and I used D3D9. The only obvious differences aside from the lack of having to make MCCs, has been the massively increased framerates. Using the inline graphics, I got 50s-70s, but under D3D9, while IMFD was running, framerate remained in the mid-200s the entire trip. Have the higher framerates really had that much effect on the accuracy of executing IMFD's burn solutions? Or is there something possibly with settings in Orbiter itself that I'm just missing?