Bert Pieke Posted October 8, 2011 Report Posted October 8, 2011 I'm looking for some trouble-shooting help... I've developed some lua code to intercept a change in LVARs in an add-on airplane, and issue key-presses when the change is detected. This works nicely and a number of users have adopted my code and reported success. One user, however, is reporting that the lua programs fail to execute on his system and after some joint trouble-shooting and comparison of ini and log files, we've come to the surprising conclusion that a simple [Auto] statement in the ini file works, but a specified list of specific airplanes [Auto.xxxxx] does not. Example [Auto.VansRV7A Tip-Up 03] 1=Lua 530_knobs 2=Lua 530_buttons 3=Lua 327_buttons does not work on his system, and yet his log file shows that the airplane was loaded: 77564 Aircraft="VansRV7A Tip-Up 03" 86487 Starting everything now ... I should add, that with LUA program logging enabled, there are no luaxxx.log files created either - leading me to believe that FSUIPC does not start them up.. Again, this all works nicely on my system, and at least half a dozen users'.. and, as we found out, it works on his system with a simple [Auto] statement! Is there anyone who might have a theory on where this could fail? This is with a fresh install of the latest registered FSUIPC release. Windows 7 vs XP, 64 bit vs 32 bit.. or is the Airplane name with several spaces possibly a source of problems.. any ideas?? Bert
Pete Dowson Posted October 8, 2011 Report Posted October 8, 2011 or is the Airplane name with several spaces possibly a source of problems.. any ideas?? No, sorry. Spaces are not relevant. I'd need to be able to reproduce this to see why it was occurring, but there's nothing special about any naming methods. If you can narrow it down to something you can reproduce yourself, get back to me. if i can think of anything extra that can be logged, I'll let you know. The mechanism is the same one which selects the aircraft-specific Buttons, Axes, JoystickCalibration and Keys sections too. Maybe it is something related to those (or their absence?), so a sight of his INI file might help. Oh, and, please, rather than say "latest" for the FSUIPC version, please ALWAYS give the version number. That is what it is for. "Latest" is really quite meaningless -- anything from 3.99 to 3.998e and 4.70 or 4.742 is "latest" and that covers over 6 months of development and many releases for two distinct platforms. You haven't even said which FS version you are talking about! Regards Pete
Bert Pieke Posted October 9, 2011 Author Report Posted October 9, 2011 No, sorry. Spaces are not relevant. I'd need to be able to reproduce this to see why it was occurring, but there's nothing special about any naming methods. If you can narrow it down to something you can reproduce yourself, get back to me. if i can think of anything extra that can be logged, I'll let you know. The mechanism is the same one which selects the aircraft-specific Buttons, Axes, JoystickCalibration and Keys sections too. Maybe it is something related to those (or their absence?), so a sight of his INI file might help. Oh, and, please, rather than say "latest" for the FSUIPC version, please ALWAYS give the version number. That is what it is for. "Latest" is really quite meaningless -- anything from 3.99 to 3.998e and 4.70 or 4.742 is "latest" and that covers over 6 months of development and many releases for two distinct platforms. You haven't even said which FS version you are talking about! Regards Pete Hi Pete, we tried shortening the name but that did not help. Here is the ini file: [General] UpdatedByVersion=4728b History=GG6SZ9K6GSKTBAUG6KCXX TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 Console=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No 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=No UseProfiles=Yes EnableMouseLook=No GetNearestAirports=No LuaRerunDelay=66 [JoyNames] AutoAssignLetters=No 0=Saitek X52 Pro Flight Controller 0.GUID={E5294180-12BD-11E0-8001-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={66B73A20-FD71-11DF-800B-444553540000} [WideServer] WideFSenabled=Yes [buttons] ButtonRepeat=20,10 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [sounds] Path=F:\FSX\Sound\ Device1=Primary Sound Driver Device2=Speakers (2- High Definition Audio Device) Device3=Digital Audio (HDMI) (2- High Definition Audio Device) Device4=Headphones (2- High Definition Audio Device) Device5=Digital Audio (S/PDIF) (2- High Definition Audio Device) [LuaFiles] 1=327_knobs 2=530_buttons 3=530_knobs 4=log lvars [Auto.VansRV7A Tip-Up 01] 1=Lua 530_knobs 2=Lua 530_buttons 3=Lua 327_knobs [Auto.VansRV7A Tip-Up 02] 1=Lua 530_knobs 2=Lua 530_buttons 3=Lua 327_knobs [Auto.VansRV7A Tip-Up 03] 1=Lua 530_knobs 2=Lua 530_buttons 3=Lua 327_knobs [Keys] 2=114,8,L4:R,0 4=115,8,1084,0 [Window.LUA display] Docked=7440, 3241, 3516, 3786 And the log: ********* FSUIPC4, Version 4.728b by Pete Dowson ********* Reading options from "F:\FSX\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name="xxxxxx" User Addr="xxxxxxxxxxxx" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 577 System time = 07/10/2011 14:56:00 577 FLT path = "C:\Users\i7-920\Documents\Flight Simulator X Files\" 577 FS path = "F:\FSX\" 998 LogOptions=00000000 00000001 998 SimConnect_Open succeeded: waiting to check version okay 8143 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 8143 Initialising SimConnect data requests now 8143 FSUIPC Menu entry added 8190 C:\Users\i7-920\Documents\Flight Simulator X Files\RV7 @ YRED.FLT 8190 F:\FSX\SimObjects\Airplanes\Vans_RV7\vansRV7.air 77564 System time = 07/10/2011 14:57:17, Simulator time = 14:56:07 (04:56Z) 77564 Aircraft="VansRV7A Tip-Up 03" 86487 Starting everything now ... 87688 Advanced Weather Interface Enabled 171492 Sim stopped: average frame rate for last 86 secs = 19.5 fps 196187 LogOptions changed, now C0000000 00000001 323905 Sim stopped: average frame rate for last 127 secs = 19.9 fps 334310 LogOptions changed, now 00000000 00000001 347664 System time = 07/10/2011 15:01:47, Simulator time = 14:59:34 (04:59Z) 347664 *** FSUIPC log file being closed Average frame rate for running time of 221 secs = 19.7 fps Memory managed: 101 Allocs, 101 Freed ********* FSUIPC Log file closed ***********
Pete Dowson Posted October 9, 2011 Report Posted October 9, 2011 Hi Pete, we tried shortening the name but that did not help. Here is the ini file: ... UpdatedByVersion=4728b Okay. The problem is due to a small error in that version of FSUIPC -- fixed in 4.742, the current interim version. It happens when the [Auto ...] sections are the only ones which are aircraft-specific -- i.e. there are no assignments or calibrations which are also aircraft specific. Due to a little bug, as described in the changes list, this stops FSUIPC generating the needed [Profile] section which tells it to use the [Auto] sections. Just make sure folks keep up to date with interim changes and it'll be fine -- see the Download Links subforum. I will be building a replacement installer in a few days. Just got some testing to do on more recent additions. Regards Pete
Bert Pieke Posted October 9, 2011 Author Report Posted October 9, 2011 Okay. The problem is due to a small error in that version of FSUIPC -- fixed in 4.742, the current interim version. It happens when the [Auto ...] sections are the only ones which are aircraft-specific -- i.e. there are no assignments or calibrations which are also aircraft specific. Due to a little bug, as described in the changes list, this stops FSUIPC generating the needed [Profile] section which tells it to use the [Auto] sections. Just make sure folks keep up to date with interim changes and it'll be fine -- see the Download Links subforum. I will be building a replacement installer in a few days. Just got some testing to do on more recent additions. Regards Pete Super - thanks for the clarification! Bert
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now