It happens on the inline client as well, so it is not related to D3D9Client. I suspect something is performing really intensive computations that it shouldn't at that time which leads to Orbiter being overloaded and freezes.Sometimes I have, but didn't notice if it happens also on inline client. I can confirm on DX9.
Freezing confirmed.Updated the HAC Test scenario to just before HAC intercept. Vehicle is Columbia in the STS-107 configuration. Also fixed the retracted position of the Orbiter Access Arm of the SLC-6 Access Tower.
---------- Post added at 11:28 PM ---------- Previous post was at 10:24 PM ----------
Just checking here: Is anybody else besides me getting freezes when using 100x time acceleration? Doesn't matter if the vehicle is in launch or orbiter only config.
Anyone up to adding the Centaur pane to the VC? I have checked in a test version with just the basic panel, without any switches.
I was thinking it could be enabled/disabled through a mission file parameter that would also add the Centaur umbilicals in the midbody.
Can you just add it for now so I can verify that the panel size and orientation is good before I add any switches?Should be possible by using the same code that currently handles the ODS panel, which is also optional.
Can you just add it for now so I can verify that the panel size and orientation is good before I add any switches?
Latest.Which build ?
Tried it on my new machine which gets better fps, and I don't have this problem anymore.I'll take a look at the RMS issue. DaveS, can you post the RMS position when you're encountering this issue? It might be occurring because the RMS is almost completely extended.
The fps is the same for me in the aft flightdesk and forward cockpit views (this is with Orbiter 2010 P1 - are you using a different version?). RMS readouts are also working fine for me.Tried it on my new machine which gets better fps, and I don't have this problem anymore.
Another thing is that something is seriously draining the fps when you're in one of the aft flightdeck views. Also the RMS digital readouts on A8 always show negative(-) even when the numbers should be positive.
Weird. I'm using 2010-P1 as well but with D3D9Client as it gives better performance on Win 7. Could this be the reason?The fps is the same for me in the aft flightdesk and forward cockpit views (this is with Orbiter 2010 P1 - are you using a different version?). RMS readouts are also working fine for me.
Just ran a the same scenario on the default inline client and got the same. The performance is just so bad on a Win 7 machine running the outdated D3D7 inline client that the poor performance masks the FPS drain.The fps is the same for me in the aft flightdesk and forward cockpit views (this is with Orbiter 2010 P1 - are you using a different version?). RMS readouts are also working fine for me.
I have a problem when using the RMS in SSU. When I start a scenario that has a payload grappled, the RMS is in the correct position, but the payload is attached to the RMS's stowed position. If I move the RMS, it snaps into the stowed position, with the payload attached. Anyone confirm this ?
PS. It works correctly in 2010 P1
As I wrote above: The poor performance of the inline client masks the FPS difference.I can reproduce both these issues with the D3D9 client. For some reason, the framerate is much lower in the aft view for the D3D9 client than with the default client.