Whenever I use the time compression (8x or more) on the 747, I get CTD. Using P3v4. I do not turn off the AI, but I I never had CTD when I used FSX at 8 x or even 16x with AI. Anyone have any ideas??

 

TY

Being frank how can you expect any sort of realism with x8 acceleration especially with a complex 3rd party aircraft that is trying to keep its navigation data updated? You're asking for trouble.

It will probably work with a simple default aircraft with minimal instrumentation but that's it. Keep to a max of x4 or preferably x2 and you should be fine.

This is why I'm a short to medium haul simmer. I have the excellent QOTSII and T7 but don't use them but occasionally. Watching a flight on time compress seems unrealistic and pointless. Even so I have to occasionally cross the ponds. Time compress works best over water then land mass where you are picking up data that can over load your memory. That is my uneducated guess.

There is an alternative to time compression. Buy FSLabs Concorde-X.

Mach 2.0 instead of Mach 0.85. That's 2.5 times compression... except of course it isn't. No flight longer than 4 hours. It overtakes 747s at 750mph.

A version compatible with 64-bit P3D v4 should be available later this year or early next.

3 hours ago, Ray Proudfoot said:

There is an alternative to time compression. Buy FSLabs Concorde-X.

Mach 2.0 instead of Mach 0.85. That's 2.5 times compression... except of course it isn't. No flight longer than 4 hours. It overtakes 747s at 750mph.

A version compatible with 64-bit P3D v4 should be available later this year or early next.

Thanks for that info Ray. I'll keep a watch for this.

29 minutes ago, PATCO LCH said:

Thanks for that info Ray. I'll keep a watch for this.

As you pond-hop occasionally did you know that a real Concorde flew from JFK to LHR in 2h 59m? It caught a particularly strong jet stream. Fantastic. 😁

5 minutes ago, Ray Proudfoot said:

As you pond-hop occasionally did you know that a real Concorde flew from JFK to LHR in 2h 59m? It caught a particularly strong jet stream. Fantastic. 😁

Yea, scary thing is an enemy with sinister intent could do it faster. Small world for better or worse.

11 minutes ago, PATCO LCH said:

Yea, scary thing is an enemy with sinister intent could do it faster. Small world for better or worse.

But no champagne service. 

Thank you (I think) Mr. Proudfoot.

On 5/14/2018 at 10:33 PM, Contactdepture said:

Whenever I use the time compression (8x or more) on the 747, I get CTD. Using P3v4. I do not turn off the AI, but I I never had CTD when I used FSX at 8 x or even 16x with AI. Anyone have any ideas??

 

TY

According to page 149, PMDG 747 Introduction Manual, the PMDG 747 is limited to 16x's acceleration for proper autopilot functions to work.  I interpret this to mean it will not crash at 16x's if only the PMDG 747 is loaded and you are using default scenery, default settings, and there are no other addons.  I'm pretty sure this is how it was tested.  If you have resource intensive (eye-candy) scenery, AI, real weather programs like ASP4, then I could see the chances for having an anomaly like a CTD would increase dramatically.  Is this the fault of P3D?  P3DV4 time-compression was most likely tested with default settings, scenery, and aircraft.  

Did you get an Event that indicated the faulting module or an AppCrashView Report indicating the faulting module?

Are you using the P3D time compression from the menu or are you using the built in PMDG 'Auto Cruise'. The PMDG system is 'intelligent' and will slow down where necessary and is likely to reduce the chances of a CTD. Is it happening in the same place or randomly? If you aren't already, try using the buildin PMDG time compression and limit it to 4x and see how that goes. If that works then try 8x.

Thank you for your advice everyone.  I have determined I am having a hardware problem. Anyway, for what it is worth: I have used both the system and the PMDG time compression and it it will work at 8x. I agree 16x is too much for the autopilot to handle. No problem though, 8x is good enough to cross the Pacific etc.

 

Thanks everyone!!  Case closed.

Sometimes I get impatient and just use the system time compress at 8x sometimes even16x and monitor myself. When I approach a waypoint that involves the slightest heading change I slow to normal about 10 miles short, let the sim catch up, execute the turn then resume time compress. This seems to work as long as you stay with it. Also good for aircraft that don't have smart time compress like NGX.

Happy flying.