simfan1983

There is a Windows registry tweak that stops Windows 11 feature updates. I have been running like that since prior to the horrid 25H2 mess. You still get all the other security and driver updates but avoid problems like ChasePlane and Aerosoft aircraft being borked. Once you have everything working take a system image backup so you can always go back. This also applies to GSX as every update breaks something.

In my opinion 5.3 HF2. I don't find 5.4 as stable and it doesn't really add any features that I would use. I don't use volumetric clouds as I think legacy clouds, especially with ASCA, look better. v6 is a no go for me as FSLabs and various other addons are not compatible and it's a pain to get stuff working. I would recommend Orbx FTX Global and the other global products as a big step forward in textures. ChasePlane, GSX v2, ActiveSky and Navigraph Charts / AIRAC are pretty essential for an immersive experience. You can fly with default airport scenery but the good payware airports do transform the visuals.

Make that 632.

I'm not absolutely sure whether the deregister issue is related to the P3D version - I assume it's from v5 onwards? If you don't deregister, when you restore your PC, P3D thinks you have installed on a new computer and if you have run out of allowed installations you will obviously need to email LM to get the counter reset. They can take a few days to get back to you, as I learned through experience! I think you actually do end up uninstalling the client when you deregister P3D, so when you restore you will have a clean p3d.cfg so take a backup if you make tweaks. It's also worth taking a backup of your keyboard / controller settings and graphics settings in P3D and then you can get back up and running quickly. If you use FSUIPC, when you restore you may need to tell FSUIPC which aircraft type you are using the first time you fly each livery, which is a bit of a nuisance but better than having to start from the beginning. I use Windows backup and restore to make the system image on an external drive - it's not the most user friendly way to do it but it works, is free, and provides a lot of peace of mind. Having the system image meant I was able to avoid Windows 24H2 which is a horrendous mess, I have then turned off major Windows updates to new versions using a registry tweak so can continue to use P3D without issues.

Agreed, take a system image when it's all working but be aware that to restore from a system image you need to deregister PMDG aircraft and P3D (don't need to uninstall). Also never install a GSX update without waiting for the errors to be fixed as the P3D updates invariably have problems.

The line fms_flightplan_path=<your flight plan folder> goes in the [OPTIONS] section of super80pro.ini. I wouldn't expect you to be able to load the flightplan into anything other than the super80pro as the others don't have the FMC. If you go to the Coolsky support forum and search on fms_flightplan_path with the date set to any you should find some threads from 2009. Unfortunately I don't currently have the line in my ini file as I reinstalled and never set things up again but I have had it working in the past. I think you are correct that it should be a standard pln format file. Do you have access to the forum? There is no longer support from Espen but I can still access all the old threads.

There is a thread in the forum here that tells you where you find the path for flightplans. I think as default it uses p3dv4 not v5 but you can change that. Super 80/DC-9 Web Forums - Search Results - S80 pro fms_flightplan_path In the Super80Pro.ini file, there should be a section that looks like this... fms_flightplan_path=<your flight plan folder> IIRC you will need to set it for each of the DC9, Super 80 and Super 80 pro ini files. You can also use the Navigraph FMS upater to update the AIRAC for the Coolsky products - the path my FMS updater uses is C:\Program Files\Lockheed Martin\Prepar3D v5\Navigraph and the product being updated is described as Flight 1 Fokker/Super 80 Professional/C182T, DA Piper Cheyenne.

I agree it sounds like a controller issue. Go into P3D controller settings in the slew section and make sure that axis for joysticks aren't mapped. I use the keyboard only for slew to avoid the warp speed problem. Using the keys, if you press a direction key repeatedly the slew speeds up, to slow down press the key for the reverse direction.

I also recommend v5.3HF2 and set an appropriate Affinity Mask if you are using an Intel CPU. I use this website: Prepar3D 5.3+ Affinity Calculator

No, not in my experience.

Last major update it was a couple of months before Umberto fixed it for P3D.

Unfortunately it isn't possible to roll back GSX if you have updated it as far as I am aware. I understand that a GSX beta upgrade option may be available in future, but the last big update has indeed broken GSX for P3D and FSX according to the FSDreamteam P3D support forum. Umberto is aware of the issues and is working on a fix according to his recent responses. It's never a good idea to update GSX if you have it working, every update always seems to introduce problems. The approach I take is to take a system image before doing any updates in order that I can roll back, but doing so requires de-registering all PMDG products and P3D so that when you restore from the system image you can reregister everything. One other possible approach is to take a backup of your C:\Program Files (x86)\Addon Manager folder before updating, and then overwrite the folder after any update to attempt to go back, but I have not tried this.

Yes it works with H224.

Fair enough but I was only passing on a potential fix from a friend that said it worked for them, and others have also said it helped. I'm sorry if it doesn't work for you. As you say, not having a second monitor might be the issue. The reason I don't have H224 is that it doesn't improve Windows functionality or performance, and introduces a raft of issues that Microsoft are hardly going to address. Some older P3D aircraft don't function properly on H224. The original reason I rolled back was that after H224 installed P3D would periodically open across both screens and I couldn't get it to stop doing that, which was super annoying. So it's not just ChasePlane that is affected by H224. I can still install security and other updates and simply avoid H224 for now. Others can't avoid it or can't roll back as it is too late. At some stage support will end for Windows 11 that is not on at least the H224 build, but I will cross that bridge when I come to it. I generally avoid all updates to all my apps such as GSX, OBS, Nvidia Broadcast, Navigraph Simlink, Nvidia drivers, SODE etc. because I have everything working with no CTDs and can reliably do a long haul flight without and performance issues. Every week or two I take a system image backup so if anything gets installed I can roll back to where I was. This approach has saved me on several occasions from a lot of hassles. I continue to buy scenery and aircraft for P3D and am more than happy avoiding MSFS and enjoying what I think is currently the best sim available with a fully functioning ChasePlane.

Yes, I believe the fix reduces the issue to where it is not a deal-breaker. One thing to try to alleviate the slight pause when clicking on another window would be to force ChasePlane to stay 'always on top' on the second monitor. I don't have any CP issues myself, so am merely reporting what others who did that reportedly works for them. It's certainly a better option than ditching CP altogether IMO.