ontheair

Thanks very much for taking the time to try. "To check the EXE, right click on it and select Properties - Version" I can confirm from my P3D version is 2.2.10438.0 as shown in the properties "Détails" TAB and I don't understand why FSUIPC.ini file is showing 2.2.10437 ?? Moreover, if the "AutoTuneADF" FSUIPC control does not work with the C172 Trainer A2A it works fine with the C337 Carenado (P3D v2.2 platform) : the ADF FREQ display set to 286 switches alternatively from 286 to 286.5 . It also does not work with P3D v1.4.4747 and the C172 Trainer It makes me think the issue seems to be related with the C172 Trainer that does not display ADF fractionnal FREQ. I did not try with FSX but some C172 Trainer users have reported it works OK Regards

Rather strange cause the "about" screen is showing 2.2.10438.0 ??? In other words the update seems to be properly installed... No, the issue is not that important to me. I was just wondering why the "AutoTuneADF" FSUIPC control that is said to be working fine is actually not working, at least for me ??

Thanks for the info but I'm currently using the 2.2.10438.0 update Just tried again this morning with FSUIPC 4.934 installed, taking off from LFPV : the issue is still there, the ADF needle does not move despite a correct freq setting 286. As for the rest, I'm afraid it looks like Chinese for me... Would you please check by yourself when you get enough time to do it Best regards

Salut Pete, From page 10 FSUIPC manual : AutoTuneADF : This controls an option to ‘auto-tune’ the ADF radio. If this is enabled, when FSUIPC detects no NDB signal being received it alternates the fractional part of the ADF frequency between .0 and .5 every seven seconds or so.This allows external cockpits built with only whole-number ADF radio facilities to be used in areas like the U.K. which have many NDB frequencies ending in .5 The AutoTuneADF=YES line was added to the General section of FSUIPC.ini file located in the P3Dv2.2 Modules folder but I can't make it working with FSUIPC v 4.931 (registered) : the ADF freq settings TA 286.5 5 or EM 295.5 (LFPV-LFOX) are not detected at all, the needle remains stationary even when overflying the NdB. Could you please check ? Should I try FSUIPC v4.934 instead ? Thanks for assistance. [General] UpdatedByVersion=4931 History=A7CFG4HR4PS9NAGGTC5Q2 InitDelayDevicesToo=No NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=Yes DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=3 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=Yes SuppressWindVariance=Yes WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=Yes MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=Yes WindSmoothness=-4 WindSmoothAirborneOnly=Yes PressureSmoothness=8 TemperatureSmoothness=25 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=Yes WhiteMessages=Yes ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=No SuppressSingleline=No SuppressMultilineFS=Yes AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=No OOMcheck=Yes WeatherReadFactor=1 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=No ThrottleSyncToggle=83,11 AllEngHotKey=69,11 DelayedMouseLookZoom=No AutoTuneADF=Yes FSVersionUsed="Lockheed Martin® Prepar3D® v2",2.2.10437.0 SimConnectUsed=2.2.0.0 [JoyNames] AutoAssignLetters=No 0=Thrustmaster HOTAS Cougar 0.GUID={CE3DFB20-0754-11DF-8001-444553540000} [buttons] ButtonRepeat=20,10 [AutoSave] Next=3 Interval=600 Files=3 SaveOnGround=Yes AutoSaveEnabled=Yes 1=Wed 195357 2=Thu 073411 3=Wed 190506 AlsoManage1=A300B4\Settings\*.dat AlsoManage2=C:\Users\Jean-Louis\Documents\Prepar3D v2 Files\*.P47 AlsoManage3=C:\Users\Jean-Louis\Documents\Prepar3D v2 Files\*.a2a [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [WideServer] WideFSenabled=Yes [sounds] Path=G:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Sound\ Device1=Périphérique audio principal Device2=Haut-parleurs (Sennheiser USB Headset) Device3=Haut-parleurs (Realtek High Definition Audio) Device4=Realtek Digital Output (Realtek High Definition Audio)

FSUIPC manual page 22 : "Non-scrolling FS messages to be white: This option merely allows application messages displayed in FS‘s own message bar (normally near the top of the outside view) to be coloured white on green, rather than the usual red on green. [Note that this only works after you have installed the SP1 update for FSX]" It's true this red text on the FSX green stripe is horrible and makes my eyes "crazy" !! I've the "Non-scrolling FS messages to be white" option selected (registered FSUIPC) without any success: the text msgs are still red despite the line "WhiteMessages=Yes" is well present in the FSUIPC4.ini file of the FSX Modules folder. What do I miss ? Do I need to select something else to make it working as expected. Woul you please re-direct me if my question has been already posted Merci PS currently running FSX Gold Edition

FSUIPC4 Autosave enabled + the whole FSX folder excluded from MSE scanning (Andy's recommendation found on NGX forum) the micro-freezes seem to have vanished !! (to be confirmed on the long term) + FSUIPC Autosave feature seems to be working fine at last ! (to be also confirmed)

"To let PMDG determine how loading their own saved files does not restore the aircraft to its state at the time of saving you will have to send them some samples" already done, 3 samples were sent as attached files. My feeling is they all were just ignored. "No one from PMDG has contacted me in years. That is most certainly a falsehood" OK, I'm not so surprised. I'll let Paul know asap

Merci Pete, My recent ticket to the PMDG 737NGX forum : "Are you planning to make this FSUIPC Autosave feature NGX compatible ?" Quoting Pete Dowson answering a similar question I posted some time ago on FSUIPC forum "FSUIPC's Autosave simply calls the FS routines to save the flights -- exactly the same as you doing it from the FS menu or using the ; shortcut. The only difference is the automatic naming. Answer from Paul Gollnick/Manager Customer Support Precision Manuals Development Group : "We needs Pete's assistance to correct the issue and unfortunately he has not responded to our requests for assistance so until we are able to work with him on the issue, it will not be resolved" C'est ce qui s'appelle se renvoyer la balle.... (sorry but I don't know the corresponding english expression)

I'm currently using the FSUIPC4 autosave utility but when loading an already autosaved 737 NGX flight, sometimes it works (rare) but most of the times it does not due to a panel state that is cold & dark (the FMC/CDU is inop in such a case which means there is no way to load a previous panel state) The FSUIPC4 autosave feature works fine with all of my other addons. I know this issue is not from FSUIPC side but rather from PMDG's but I'm just wondering why it doesn't work all the times with the NGX. Any idea ? Regards

Thanks Pete. Sounds much clear now. "you certainly would not have needed to re-register unless you deleted the KEY file in the FSX Modules folder" This key file was not deleted and I was not asked to re-register, but at the end of the FSUIPC4 re-install process the registration window pops up prompting me to do so. I might have skipped/ignored it. " ...... you cannot deal with by just reassigning or recalibrating controls. Deleting all of your existing settings seems rather over-drastic unless you are really stuck..." As I'm using the Thrusmater HOTAS Cougar I don't feel concerned about reasignement or calibration controls. Jean-Louis

From the PMDG 737 NGX intro manual : "During testing we have found that in extremely rare circumstances, users with FSUIPC installed would need to delete their FSUIPC.CFG file after installing the PMDG 737NGX in order to get everything playing well together. We recommend that you try this if it seems the NGX is not behaving normally after installation" I must admit I had to re-install and re-register FSUIPC just after installing the PMDG 737 NGX : once it was installed I discovered the FSX Add-ons menu was empty !! What is this FSUIPC.cfg file they are talking about ? I cannot find it on my PC. Would it not rather be the FSUIPC4.ini file ? I'd like to understand Merci

"and of course those lines won't be read until you next re-load FSX.So, start off by deleting all your unwanted files, then run FSX" my mistake ! Everything is now perfect : only 3 files (3.FLT.sav) and (3.dat) are kept as per my setting Merci

"A special section on this is provided in the Advanced User’s document. Please check its contents list" Thanks, I found the special section (AUTOSAVE: INI-file only options) page 10 of FSUIPC4 Advanced Users and made the following change in FSUIPC4.ini file located in FSX/modules : [AutoSave] AutoSaveEnabled=Yes Interval=600 Files=3 SaveOnGround=Yes Next=1 1=Wed 132826 2=Wed 134802 3=Wed 135802 AlsoManage1=FSLabs\Concorde\PanelState\*.FLT.sav AlsoManage2=A300B4\Settings\*.dat Both indicated paths are within the main FSX path I'm afraid the (.FLT.sav) and (.dat) files are still accumulating in their resp. locations... What did I do wrong ? does it matter if FSX is not installed in the default (C:) drive but in a different one (E: in my case) Regards

I'm currently using a registered version of FSUIPC. The Autosave feature is enabled with the following settings : - save interval 600 secs - how many to keep 3 - save whilst on ground checked The FSUIPC Autosave files automatically generated (3.FLT + 3.WX, located in My documents/Flight Simulator X Files) are accessible from within FSX with the load option. Fine ! When flying Concorde X/FSLabs, and despite the number of file (3) to be kept, the number of previously saved Concorde-X panel states (.FLT.sav type) located in MSFSX/FSLabs/Concorde/PanelState, are accumulating to such a point that I need to purge the oldest ones from time to time ? Is there a way to limit this number of (.FLT.sav) files to only 3 as per my setting ? Merci Best regards