Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ontheair

  • Rank
    Advanced Member
  1. 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
  2. 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 ??
  3. 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
  4. 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= [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)
  5. Dear Nikola, "I am most certain that the nature of your problem comes from your Windows being in French language" this is 100% right and I can proove it : 1) on my laptop, I went to config panel/regional settings and change the decimal symbol from comma "," to point "." 2) I ran the TOPER tool providing the key when required, entered all the data including the TOW 56.4 and I did no get any error message for the 1st time 3) after hiiting the Calculate button the tool returned the calculated assumed temp of 50°C i.e the highest possible value It seems now to be OK except whatever the data entered, the tool returns the same value 50°C ???? something might be still wrong "I am assuming you are using Windows7" yes have a look on my signature below W7-64 "The activation is valid on "one key-one system" basis" : I better understand now "If the problem persist, please be so kind to ask simmarket for a refund" I won't ask for a 3 euros refund, let me buy you some beers instead ! Just let me know what you think about the assumed temp issue that is constant (= 50°C) whatever the data and units (metric or imperial) Cordialement P.S. a workaround to avoid any decimal symbol issue would have been to use TOW full value i.e 56400 kg instead of 56.4 x1000 kg
  6. "I am very pleased to hear you have solved your issue" where did you read that ?? you're wrong it is NOT fixed yet and I'm still waiting you to investigate what could be wrong ! Would you please answer all my questions (see above my post dated yesterday, 04:47 PM) and give me some more assistance. "I have unlocked your serial number so next time you register it, no error message will appear" yes but only for 1 time and that is not enough for sure !!!. I tried to install TOPER on my laptop instead of my desktop and again I got the message "Already registered using these credentials". Can you believe one second I will try to give someone else a tool that does not work at least for me ? regards
  7. Bonjour Nikola, I just tried again to reinstall the TOPER tool with the TOPERv1.0_Setup.exe installer. At the end of installation I just ignored and cancelled the automatic .NET Framework process (with the repair or delete otions) that is, I guess, the source of my issue. You should check this and make your customers aware about this automatic unnecessary process, or delete it (if you can) from your installer. When trying to register again I provided the Reg/Serial/Voucher Key/Number I got with my order 917232 date 19/09/2012 at Simmarket. An activation error message was returned "Already registered using these credentials" What can I do ? Could you please provide a new Key/Number or make mine available again ? Merci
  8. Many thanks Nikola for investigating the issue I have each time I'm trying to use your product "Do you have trouble calculating only those specific parameters, or does the application fail to produce results at all? " it fails to produce any result at all, whatever the data, yours, or different ones. I'm experiencing the bug anytime on my PC (W7-64 french version- see specs below ) : no way to get any result cause I get the error message as described above. BTW were you able to read the content of this error message ? I know he beginning is in french but the rest is in english. Does the message "Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)" talk to you ? it seems to be linked to the conversion of the weight string "la conversion de la chaîne "54.6" en type "Double" n'est pas valide" where 54.6 is the weight (54600 kg) "Did this happen before or after the update?" before and after. A the very first run I did not know about v.1.1 I found on the forum. The framework does not have to be "repaired", you can just click "cancel". would have been fair to inform your customers about that... Any way the .NEt Framework 4 repair process went OK. (in the window that popped-up the choice was to 1) repair or 2) to delete) "It is crucial to use "." as a separator-the program does not accept commas. fine ! I did use "." but the bug is still there I know the product price is low (3€) but it should work on any system. Thanks for considering again Best regards
  9. Bonjour Nikola, Just bought and installed TOPER v1. It's now registered. I just downloaded and installed new version v1.1 as recommended with imperial weights (IMHO, it would have been better not to convert the rwy lenght in feet but to keep it in meters instead) Is that normal to perform the Microsoft.NET Framework 4 "reparation" during installation ?? Unfortunately it does not work with the data provided with you PDF manual : RWY ELEV: 'SL-1000' RWY LEN: 2800 WET: unchecked OAT: 15 WIND COMPONENT: 0 TOW: 56.4 ENGINE BLEED: ON ANTI ICE: OFF it seems to be linked with the weight format 56.4 or 56,4 and maybe the decimal symbol ?? I tried both but the problem is still there if it can be of any help, please find below the error log : System.InvalidCastException: La conversion de la chaîne "56.4" en type 'Double' n'est pas valide. ---> System.FormatException: Le format de la chaîne d'entrée est incorrect. à Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat) à Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat) --- Fin de la trace de la pile d'exception interne --- à Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat) à Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value) à _737NG_perfcalc.Form1.Button1_Click(Object sender, EventArgs e) à System.Windows.Forms.Control.OnClick(EventArgs e) à System.Windows.Forms.Button.OnClick(EventArgs e) à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) à System.Windows.Forms.Control.WndProc(Message& m) à System.Windows.Forms.ButtonBase.WndProc(Message& m) à System.Windows.Forms.Button.WndProc(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Assemblys chargés ************** mscorlib Version de l'assembly : Version Win32 : 4.0.30319.269 (RTMGDR.030319-2600) CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- 737NG-perfcalc Version de l'assembly : Version Win32 : CodeBase : file:///E:/Program%20Files%20(x86)/TOPER%20Calculator%20Tool/737NG-perfcalc.exe ---------------------------------------- Microsoft.VisualBasic Version de l'assembly : Version Win32 : 10.0.30319.1 built by: RTMRel CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Version de l'assembly : Version Win32 : 4.0.30319.269 built by: RTMGDR CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Version de l'assembly : Version Win32 : 4.0.30319.233 built by: RTMGDR CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Windows.Forms Version de l'assembly : Version Win32 : 4.0.30319.278 built by: RTMGDR CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Version de l'assembly : Version Win32 : 4.0.30319.282 built by: RTMGDR CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Version de l'assembly : Version Win32 : 4.0.30319.1 (RTMRel.030319-0100) CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- System.Configuration Version de l'assembly : Version Win32 : 4.0.30319.1 (RTMRel.030319-0100) CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Version de l'assembly : Version Win32 : 4.0.30319.233 built by: RTMGDR CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Windows.Forms.resources Version de l'assembly : Version Win32 : 4.0.30319.1 built by: RTMRel CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll ---------------------------------------- mscorlib.resources Version de l'assembly : Version Win32 : 4.0.30319.235 (RTMGDR.030319-2300) CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll ---------------------------------------- Microsoft.VisualBasic.resources Version de l'assembly : Version Win32 : 10.0.30319.1 built by: RTMRel CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/v4.0_10.0.0.0_fr_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll ---------------------------------------- Thanks for your assistance Merci d'avance
  10. 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
  11. 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)
  12. "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
  13. 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)
  14. 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
  15. 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
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.