chrismk

Bloom was set to 0.05 - changing it doesn't make any difference. No shader mods being used!

That doesn't make any difference.

I have a recently purchased Acer Predator XB281HK running in 4K from a 1080ti When I change an internal camera view or even move within the current view, the brightness increases. If I select an outside camera and then back to interior, it reverts to normal. I established yesterday that this doesn't occur if HDR is unticked. I don't have this issue with my HP LP2475w monitor. Any thoughts? Additional edit: The problem doesn't occur in V5 which I've installed this morning so I'm guessing there might be some setting responsible?

Thought it probably was - will give it a go!

How is it attached Rob?

I've uninstalled FSX and gone over to the Steam Edition. I installed ChasePlane but I seem to have lost all my settings. There weren't many so it's not a big deal but should this have happened?

That's correct!

FSX will allow you to separate the two controllers so you can remove all the Xbox bindings but keep your joystick ones.

I'm assuming you are also using a joystick. When you go into the FSX control settings are you making sure you have the XBox 360 selected as the controller? Mine defaulted to the joystick which I hadn't noticed and all the Xbox settings were intact giving the same symptoms as you are describing.

Obviously a popular topic! The same happens with the 777 too. And the graphic doesn't even appear with the 747. This is after another complete re-install. I've opened a ticket.

Completed a reinstallation of FSX Acceleration on its own SSD. Installed FSGenesis Landclass & Mesh Installed ORBX Global, Vector and Southern California. Then installed the NGX. When I select the aircraft (doesn't matter which of the three), the graphic appears and rotates about one degree every few seconds and FSX can only be closed through the Task Manager. I realised when I first (re) installed it I still had some files in my Appdata/Roaming/ etc folder which I then subsequently removed after performing another re-install - along with the PMDG folder in FSX. I've run a registry checker and a manual search for PMDG and the only results are for the Operations Center and a licence reference. What is going on?

I uninstalled the product as per PMDG support instructions. The problem disappeared with the new installation.

With respect, if that was the case, I would have run into far more problems by now FSX is installed onto its own SSD, UAC was turned off many a moon ago, I am the sole user and have full administrative rights. In any case the panel states are being saved; they're just not loading with their related flights. A ticket was submitted this morning.

It seems your issue was with P3D - mine is with FSX - subtle difference! I am now encouraged :smile:

That's not very encouraging.

OK Dan, will do - tomorrow now though! Thanks.

Hi Andreas Yes I'm also using FSX but reasonably new to PMDG products so in the middle of a large learning curve. I can see that what you suggest will work - Dan's method of using slew mode to 'pause' the flight while the panel state is loading will presumably achieve the same effect. I think I need to test with some of my own flights using the default PMDG livery so I can properly check the loaded panel state. I might re-install the 737 first and take it from there. Thanks for your input though!

Hi Andreas That sounds the same as loading the panel state when in slew mode as Dan advised earlier? The issue I have then is that errors are introduced like autothrottle and autopilot warnings or in the case od another flight there is only 1 page under Legs. I could do with more of my own flights to test with rather than the Tutorials and Angle of Attack ones. It almost seem stht something has got corrupted. I'll see if Dan has any more suggestions otherwise I'll have to bite the bullet.

Hi Dan Just completed a KSAN-KLAX flight; got to the gate, went through a shutdown procedure and saved the flight. Quit and restarted FSX and loaded the previously saved flight and problem the same. Having uninstalled GSX and the Addon Manager before creating this flight there is nothing else running. Any more thoughts or am I looking at a re-install?

Hi Dan I've not gone anywhere near that part of the setup menu! The only thing I did do was to apply a Dark & Cold setup as the Default Startup State. I later realised this wasn't a good idea so after much searching deleted the entry from the 737NGX_Options.ini file which now looks like this: [iRS.0] LastPosValid=0 [iRS.1] LastPosValid=0 [iRS] IRS_QuickAlign=1 IRS_UseLastPos=1 [Pushback] PushbackUnitsFeet=1 PushbackCommsType=0 [AFS] ThrottleATOverride=0 AutotuneOBSinLOC=1 AP_EngageRealistic=1 [userOptions] FOCallouts=1 PauseAtTOD=0 SyncAltimeters=1 SyncStbyAltimeters=1 ShowThrustLeverPosition=0 ShowPilots=1 ServiceBasedFailures=0 TABforCDUinput=1 [PerformanceOptions] FPSlimit_PFD_EFIS_2D=15 FPSlimit_PFD_EFIS_VC=15 FPSlimit_ND_MAP_2D=15 FPSlimit_ND_MAP_VC=15 FPSlimit_Engine_2D=15 FPSlimit_Engine_VC=15 FPSlimit_HUD_2D=15 FPSlimit_HUD_VC=15 disableSide=2 [Aircraft Config] FixedConfig= [Panel State] StartupPanelState= [FMC] LastPosLatLon=N3604.9W11508.8 EZdok is still removed and will remain so until this is sorted and possibly for sometime after that! I haven't set a default aircraft in FSX. I think I may have misunderstood your instructions so will create a brand new one using a default PMDG livery and report back. Thanks for your patience!

Right, I've loaded a free flight using both the 700 and 800 with different PDMG liveries and made various changes to settings on the flightdeck. This was after completing a flight which I didn't finish but saved at TOC. This made no difference so I have also uninstalled EZdok and restored the default control settings. Whatever I seem to do, the default panel state loads! Very frustrating.

Sounds like a plan - thank you! I've established that the Ezdok problem disappears if I disable it before saving which may be documented for all I know.

Appreciate your reply. Well that prevented me from losing more altitude! However, it doesn't load the associated panel state - presumably it should? Is it good practice to save the panel state before saving the flight? I finally got it to load but there were all sorts of warnings and the a/p seems rather upset and despite all my efforts I am unable to get it to its original altitude. More intriguing than that is despite 'stabilizing' it the instruments are showing a small climb rate but I am in fact very slowly descending. And I'm very slowly losing airspeed! Otherwise all is well :smile: Interestingly I had to quit the flight because after I had saved it I lost my Ezdok keyboard shortcuts so there may be another issue here which could have corrupted the panel state? I'll repeat the (fortunately short) flight and see what happens. Edit: I see from Page 48 of the Introduction Manual that the correct panel state should be automatically loaded so it seems there is an issue here. None of my saved flights are loading with their correct panel. Nor any of the Angle of Attack ones which have never been loaded.

Rather new still to all this! Using the 737NGX I decided to save a flight at TOC and end the flight. When I loaded the flight from FSX all hell broke lose and I progressed into a rather swift dive! Shouldn't the panel state load with the associated flight? And if not how do you get round the problem? Many thanks!

Thanks Gents! Chris Curtis