PMDG 777 Switches not working

[noahharget]

Hi!

I just updated and made a profile for the PMDG 777. It works for a few minutes after sim launch but then is unusable. I flew one flight where it worked the whole time.

Is there a way to fix this? I presume I did something wrong. I did try the reload presets, and restarting FSUIPC.

I have not tested this in other addons, however I do recall needing to previously set which profile for each livery.

Edited July 6 by noahharget

[noahharget]

Also - not sure if this is FSUIPC related but it has been present since the update of FSUIPC and the 777.

Last night, I made two attempts to fly KMIA->KORD on the 77W. I flew KORD->KMIA with no issues, but on the return leg I received a CTD between 12000-16000ft approaching Chicago. I have never had a CTD in MSFS before this update of the 777. I use DX11. I was using DX12 but started to run into low frame issues with some addons. Made another attempt today resulting in a CTD, all is well until between VEECK and BOONE on the VEECK5 arrival.

System -
i9-9900K CPU @ 3.60GHz 3.60 GHz
64.0 GB RAM
Nvidia GeForce RTX 2080Ti

Addons used -
Amsim KMIA
FSDT KORD
PSXT (AIG Models)
DD Chicago City
PMDG 777-300
MSFS Map Enhancement
Active Sky FS

[John Dowson]

On 7/6/2024 at 8:41 PM, noahharget said:

I just updated and made a profile for the PMDG 777. It works for a few minutes after sim launch but then is unusable. I flew one flight where it worked the whole time.

When it becomes unusual, can you please exit FSUIPC7 and then show me / attach your FSUIPC7.log and FSUIPC7.ini files please.

On 7/6/2024 at 11:12 PM, noahharget said:

Also - not sure if this is FSUIPC related but it has been present since the update of FSUIPC and the 777.

Last night, I made two attempts to fly KMIA->KORD on the 77W. I flew KORD->KMIA with no issues, but on the return leg I received a CTD between 12000-16000ft approaching Chicago. I have never had a CTD in MSFS before this update of the 777. I use DX11. I was using DX12 but started to run into low frame issues with some addons. Made another attempt today resulting in a CTD, all is well until between VEECK and BOONE on the VEECK5 arrival.

If you get a CTD, please check the windows Event viewer for further information, and show me that and also the FSUIPC7.log file at the time of the CTD.

[John Dowson]

On 7/6/2024 at 8:41 PM, noahharget said:

I have not tested this in other addons, however I do recall needing to previously set which profile for each livery.

This is because you are not using substrings for your aircraft names in the [Profile.xxx] section of your FSUIPC7.ini. You need to edit the names there to be a substring of the aircraft name that matches the aircraft regardless of livery. Otherwise, you can switch to using UseAirLocForProfiles instead (see Advanced User guide on this parameter), but if you do this you will have to add each aircraft to your profiles again, and remove the current entries under your [Profile.xxx] sections as these will no longer be relevant.

[noahharget]

On 7/8/2024 at 5:28 AM, John Dowson said:

When it becomes unusual, can you please exit FSUIPC7 and then show me / attach your FSUIPC7.log and FSUIPC7.ini files please.

If you get a CTD, please check the windows Event viewer for further information, and show me that and also the FSUIPC7.log file at the time of the CTD.

I ended up doing a repair install, and reinstalling the 777 which fixed the CTD issue.

I switched to SPAD for controls.

 

The only issue I'm having now is FSUIPC isn't starting with MSFS. I have to manually open it.

[John Dowson]

23 minutes ago, noahharget said:

The only issue I'm having now is FSUIPC isn't starting with MSFS. I have to manually open it.

For all auto-start issues, see 

 

23 minutes ago, noahharget said:

I switched to SPAD for controls.

Sorry to hear that. No idea wht your issue was as I never saw your files. There does seem to be an occasional issue with the WASM when using the 777 which I am investigating.