I've had the 747 since release day but I have a strange problem I can't solve. The problem is something is causing the 747 to run awful 2 - 3 days after it's installed. The first few days I get a constant 30FPS. Then on day 3 or 4 I will boot my PC, load P3Dv3, ( I always load the default cub then change to the 747 etc.. ) and I will only get 5 fps.  It only happens with the 747. The 737 and 777 run normally.

First I used a system image to restore my PC back to a point a few weeks before the 747 was released. But again 2-3 days after I install the 747 it runs awful.

Then I did a clean install of Win10 and then clean installed P3Dv3, Ezdok v2, Orbx, FSUIPC, Rex Soft Clouds, Rex4 textures, Rex HD Airports, PMDG 737,777 & 747, FSL A320 and TFDI717.  Everything runs fine and so does the PMDG 747. But all of a sudden after 2-3 days the 747 will revert to the 5 fps issue. I am totally dumbfounded as to why this happens. 

 

 

Hi,

The first question is:

_ What changes on you PC during this 2-3 days? Any update of Windows, or drivers?

If you have an Nvidia GPU for exemple, do you have a driver update? Some users of an addon from another developper have reported that with some drivers they had worst performances than before and rolling back to older driver version was solving the problem.

It seems that different addons react differently to some system changes.

On ‎3‎/‎3‎/‎2017 at 8:55 PM, petkez said:

Then on day 3 or 4 I will boot my PC, load P3Dv3, ( I always load the default cub then change to the 747 etc.. ) and I will only get 5 fps.

Changing your sound devices at all during this time?

yes. Sometimes my computer sets my TV as the default sound playback and i have to change it back to the creative sound.

 

 

 

 

3 minutes ago, petkez said:

yes. Sometimes my computer sets my TV as the default sound playback and i have to change it back to the creative sound

This is kind of a bug (in that our code is not handling the sound device change properly), but also something I'd look into on your own comp, too (randomly changing default devices could mean some other sort of issue, unless you're plugging and unplugging things yourself).

The bug on our side is resolved in the next update (whenever we release it to the public). For now, you can simply open your <sim root folder>\PMDG\PMDG 747 QOTS II\747QOTSII_Options.ini file and delete the "SoundDevice=" line from the file. It'll re-assign it on the next sim session.

thanks i will take a look after work

3 hours ago, scandinavian13 said:

This is kind of a bug (in that our code is not handling the sound device change properly), but also something I'd look into on your own comp, too (randomly changing default devices could mean some other sort of issue, unless you're plugging and unplugging things yourself).

The bug on our side is resolved in the next update (whenever we release it to the public). For now, you can simply open your <sim root folder>\PMDG\PMDG 747 QOTS II\747QOTSII_Options.ini file and delete the "SoundDevice=" line from the file. It'll re-assign it on the next sim session.

I don't have a "SoundDevice=" line in my 747QOTSII_Options.ini just as follows.

 

[IRU.0]
LastPosValid=0
[IRU.1]
LastPosValid=0
[IRU.2]
LastPosValid=0

 

 

1 hour ago, petkez said:

I don't have a "SoundDevice=" line in my 747QOTSII_Options.ini just as follows.

[IRU.0]
LastPosValid=0
[IRU.1]
LastPosValid=0
[IRU.2]
LastPosValid=0

Were you having any issues while the options.ini was in this state, or was it like this because you reinstalled it?

1 hour ago, scandinavian13 said:

Were you having any issues while the options.ini was in this state, or was it like this because you reinstalled it?

It seems ok atm. running fine.

 

11 hours ago, petkez said:

It seems ok atm. running fine.

That would make sense then.

If you run into issues, remove the lines from the .ini file.

will do and thanks