John Dowson

This is because it contains a comma not a full stop - MACH 0,78 not MACH 0.78 - or was that a typo? If it is a comma, you could try replacing that with a full stop first.... And as with your other post, try adding some logging statements to determine what is happening.... John

It is not necessary, as if string.find was true then the first test (string.find(spdstate, "---") and string.find(spdstate, "*")) would be have been true... Add some logging statements , e.g. If you test with the console window open, this should tell you what is happening.... I think the issue is that the * character has a special meaning (match 0 or more repetitions) and needs to be escaped - maybe string.find(spdstate, "%*")? John

Both of the FSUIPC6.ini and FSUIPC6.log files are in the FSUIPC6 installation folder. If you don't know where that is, use the Open Folder button in the Logging tab. If you cannot see the extensions (.log, .ini), then you have windows explorer set to hide the extensions of known file types, and you need to change this. This is described in the Installation and Registration guide if you have any difficulties. No point in me looking at those files as I do not know which one is being used. Please just attach one .log and one .ini, both from your FSUIPC6 installation folder.

You have multiple sections for various entries - Axes, JoyNames, AutoSave, ... Not sure why this happened but can cause issues as you do not know which section is being used. I have cleaned this up for you in the attached. Could you please download and use/check this (back-up/rename your current one first). For the AutoSave, you had two sections, one where active and one where disabled - I have kept the active one, so you may want to disable if not using this. I have also activated the JoyLetters facility to prevent issues if your joystick ids change. You have one profile that I am confused about: Is this for that specific variant only? If not, and you want to use this profile for all PMDG 777s then change this to: (I have not changed this!) You have a profile specific axes section for that profile, but your calibration is not profile-specific. Probably better to make this profile-specific if using the profile-specific axes. But the flap calibration does look ok on a first glance, so not sure what is going on. I will look further, but first can you try the attached ini, and make your calibration profile specific if using a profile for the 777. Then, activate logging for Axes Controls, and generate a short log file where you load the PMDG 777 and move the flaps lever through each of its detents, ending with full flaps. Then exit, show me/attach your FSUIPC7.ini and FSUIPC7.log files (the latter may need compressing/zipping) and tell me what you saw in the VC, i.e. if the flaps lever moved to the detent corresponding to your actual lever. Thanks. FSUIPC6.ini

These controls don't work! To change the view, you have to update the CAMERA STATE and CAMERA SUBSTATE variables. The only way to do this in the current release is via using presets. However, in the next version I will make the CAMERA STATE offset 0x026D writeable, and I will also add CAMARE SUBSTATE to offset 0x026E as 1 (unsigned) byte CAMERA VIEW TYPE AND INDEX:0 to offset 0x026F as 1 (unsigned) byte CAMERA VIEW TYPE AND INDEX:1 to offset 0x0270 as 1 (unsigned) byte GAMEPLAY CAMERA FOCUS to offset 0x0271 as 1 (unsigned) byte all as writeable. I have attached a beta version, 7.3.24a, which contains this update. Using this version, you can assign a button to the control Offset Byte Set using offset 026D with a parameter of 3 (external/chase). You can then overload this button assignment (via editing the FSUIPC7.ini file) to also send a parameter of 2 (cockpit), and add an offset condition so that the correct parameter is send depending on the current value of offset 0x026D. The resulting assignments should look like the following (the index number. joystick letter and button number may be different): 9=B026D=2 PS,2,Cx0100026D,x03 -{offset byte set, offset 026D}- 10=B026D!2 PS,2,Cx0100026D,x02 -{offset byte set, offset 026D}- The button will then toggle between external and cockpit view. You can add more assignments if you want to cycle between more views, e,g, to also cycle between showcase mode (9): 9=B026D=2 PS,2,Cx0100026D,x03 -{offset byte set, offset 026D}- 10=B026D=3 PS,2,Cx0100026D,x09 -{offset byte set, offset 026D}- 11=B026D=9 PS,2,Cx0100026D,x02 -{offset byte set, offset 026D}- You can also change views/cameras using offsets 0x026E (CAMARE SUBSTATE) and 0x026F/0x0270 (CAMERA VIEW TYPE AND INDEX) - please see the SDK documentation on these variables: https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Camera_Variables.htm Otherwise, check out the available MF presets, which use the CAMERA STATE and CAMARE SUBSTATE variables: CAMERA_ACTION_COCKPIT_VIEW_RESET CAMERA_ACTION_COCKPIT_VIEW_SAVE External_Quick_View_-_Quick_View_1 External_Quick_View_-_Quick_View_2 External_Quick_View_-_Quick_View_3 External_Quick_View_-_Quick_View_4 External_Quick_View_-_Quick_View_5 External_Quick_View_-_Quick_View_6 External_Quick_View_-_Quick_View_7 External_Quick_View_-_Quick_View_8 External_View_-_Default Fixed_Camera_ShowCase_-_Fin_View Fixed_Camera_ShowCase_-_Front_Cabin_Crew_Seat Fixed_Camera_ShowCase_-_Front_Left_Door_Enter Fixed_Camera_ShowCase_-_Front_Right_Middle_Seat Fixed_Camera_ShowCase_-_Left_Engine Fixed_Camera_ShowCase_-_Left_Wing_Window_ Fixed_Camera_ShowCase_-_Left_front_Window Fixed_Camera_ShowCase_-_Nose_gear Fixed_Camera_ShowCase_-_Passanger_Look_Aft Fixed_Camera_ShowCase_-_Passanger_look_Forward Fixed_Camera_ShowCase_-_Rear_Left_Middle_Seat Fixed_Camera_ShowCase_-_Rear_Top_View Fixed_Camera_ShowCase_-_Right_Engine Fixed_Camera_ShowCase_-_Right_Wing_Window Fixed_Camera_ShowCase_-_Right_front_Window Fixed_Camera_ShowCase_-_Underbelly_Close Fixed_Camera_ShowCase_-_Underbelly_Far Free_Camera_-_Camera_Drone Instrument_View_-_CB_WALL Instrument_View_-_Dual_MCDU_Cap___FO Instrument_View_-_EFB_CAPTAIN Instrument_View_-_EFB_FO Instrument_View_-_FCU_and_ECAM__Angled_ Instrument_View_-_MCDU_Captain Instrument_View_-_OVERHEAD__Angled_ Instrument_View_-_PEDESTAL__Angled_ Instrument_View_-_PFD_ND Instrument_View_-_UPPER_OVERHEAD Pilot_View_-_Close Pilot_View_-_Copilot Pilot_View_-_Landing Pilot_View_-_Normal Quick_View_-_Front__Zoom_in_ Quick_View_-_Left_120_Degree Quick_View_-_Left_45_Degree Quick_View_-_Left_90_Degree Quick_View_-_Rear_180_Degree Quick_View_-_Right_120_Degree Quick_View_-_Right_45_Degree Quick_View_-_Right_90_Degree John FSUIPC7.exe

You can use 'if ( not( string.find...' - but you shouldn't need this o combine them: John

Yes, sorry, missed that... That surprises me though, for the reasons previously mentioned...

You can try assigning to the standard view controls: Next View, Prev View, View Mode, Next Sub View, Prev Sub View. There are also now quite a view presets available for setting specific views.:

That is the type of the value you are setting, and should probably be Percent not Number in this case, i.e. ipc.execCalcCode("50 (>A:LIGHT POTENTIOMETER:84, Percent)"), or you could use Percent over 100 and adjust the parameter, e.g. ipc.execCalcCode("0.5 (>A:LIGHT POTENTIOMETER:84, Percent over 100)"). See the following page for a list of simulator variable units: https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Simulation_Variable_Units.htm Note that it may not be possible to set this value directly for this particular variable, or it may be settable but setting this may not have the desired affect. You would normally use the control (or K-type variable)LIGHT_POTENTIOMETER_SET (with an appropriate index) to change this.. For example, this is the calculator code to increase the panel brightness in the Bonanza G36: (A:LIGHT POTENTIOMETER:3, Percent) 1 + 100 min 3 (>K:2:LIGHT_POTENTIOMETER_SET) You can refer to the SDK documentation to see if a variable is settable (as well as its type). However, some variables - including LIGHT POTENTIOMETER, don't seem to be documented.

Done.

I will send it to you via a PM when you ask for one. The email address associated to the license us the one you use for SimMarket. The email address isn't actually used, but you can/should update your email address in your SimMarket account to the new email address. Your FSUIPC4 license will not be affected. John

Then you can use the FSUIPC4.ini file from your old machine. It will probably need updating to handle the new controller ids and GUIDs. If you have your old ini, then attach that as well as the new one and I can take a look. And if it was working with the standard controls previously, then it should work on the new machine. As I asked before, does assigning to the standard flaps control move the flaps in the PMDG 777? I don't know how that can happen - the software (FSUIPC4) is identical and hasn't changed for a long time... If it worked this way before, it should again, so I would continue trying...just make sure you follow the instructions in the user guide... If you have your old ini, you could try copying across the flap calibration entries... John

Maybe better and easier to assign to the custom controls #define EVT_CONTROL_STAND_FLAPS_LEVER_0 (THIRD_PARTY_EVENT_ID_MIN + 5071) #define EVT_CONTROL_STAND_FLAPS_LEVER_1 (THIRD_PARTY_EVENT_ID_MIN + 5072) #define EVT_CONTROL_STAND_FLAPS_LEVER_5 (THIRD_PARTY_EVENT_ID_MIN + 5073) #define EVT_CONTROL_STAND_FLAPS_LEVER_15 (THIRD_PARTY_EVENT_ID_MIN + 5074) #define EVT_CONTROL_STAND_FLAPS_LEVER_20 (THIRD_PARTY_EVENT_ID_MIN + 5075) #define EVT_CONTROL_STAND_FLAPS_LEVER_25 (THIRD_PARTY_EVENT_ID_MIN + 5076) #define EVT_CONTROL_STAND_FLAPS_LEVER_30 (THIRD_PARTY_EVENT_ID_MIN + 5077) using the right-hand side of the axis assignment panel. i.e. set the detent position (custom) control when the axis lever range is around the detent position for both up and down. The control will then be sent to set the detent position when your axis lever enters the range set.

I think this is because the PMDG aircraft do not use the standard P3D controls for flaps. What have you assigned to, and does this assignment actual work, i,e, can you see the flaps lever move with this assignment? PMDG provide their own custom controls for many actions, including flaps: See the following FAQ entry on how to use custom controls for PMDG aircraft: However, you can only assign custom controls to buttons and keys, not axes. If you want to use a custom control for an axis, you would have to write the axis value to an FSUIPC offset, and use a lua script to monitor/read that offset and send the appropriate custom control with the value read. John

Yes - you will automatically get a discount of 5euros on check-out if you have previously purchased another version of FSUIPC. The current trial license is valid until 1st October. This will be updated to 1st November when there is less than 7 days available on the current trial license. I generated a new trial license when there is < 7 days (approx) left on the current one. John

There are two ways to set a simvar (or A-type variable0 that is not already held in an FSUIPC offset: 1. Use calculator code, e.g ipc.execCalcCode("50 (>A:LIGHT POTENTIOMETER:84, Number)") 2. Add the simvar to a free/spare FSUIPC offset, and use the provided lua offset functions to read/write to the offset. How to add a simvar to a spare FSUIPC offset is described in the Advanced User guide. John

string.match will return a string, not a number, so you need to convert the results to a number (using tonumber). Also, the match will stop after the first non-digit character is found (after a digit), so "Mach 0,78" will return 0 (due to the comma). If you want to extract decimals, see https://stackoverflow.com/questions/38140434/lua-how-to-retrieve-a-decimal-number-from-string. Otherwise, maybe take a look here: https://stackoverflow.com/questions/46794989/extracting-number-from-string-using-lua But it would be better to just read the offsets holding the values you want to extract. For example, if its the mach speed, that will be in offset 0x11C6 (or 0x35A0 or maybe 0x07E8 for AP mach value).

Please see the example TripleUse.lua script, which will be in the Example Lua plugins.zip file in your FSUIPC7 documents folder. This shows how to use a button for single press, long press and double press. There is also a user contribution that expands on this, available here: John

License sent via PM. John

Just to let you know, I have raise this on the P3D developer support forums but have yet to receive a response - I will update again if/when I hear anything,,,

What is your issue? Have you read and followed the network configuration section in the WideFS User Guide? All the information you need is documented there, so please follow that. If you still have problems with connections, try disabling your firewalls (server, client and router) and see if it connects then. If so, then enable the firewalls one-by-one to see which is causing the issue, and then configure that firewall to allow the connection. Also try adding the ServerName (or ServerIPAddr) ini parameter to your WideClient.ini - again, see the documentation. Note that you can also use FSUIPC7 on a client PC instead of WideFS / WideClient. This does not provide the same functionality as WideFS/WideClient (it will not communicate with the FSUIPC7 version running in the FS PC) so this depends on what you want to achieve on the client PC. Instructions on how to set this up are in an appendix in the Advanced User guide. John

You need to use presets. First, please update your FSUIPC7 version to the latest version, 7.3.23, if you have not done so already. This version contains a new feature that makes finding presets a lot easier. In the assignments panel, check Select for Preset and then click the Find Preset... button. you should then see presets for both of these buttons, e.g, Note that you can also use the MobiFlight hub-hop site (https://hubhop.mobiflight.com/presets/) to search for presets. John

Neither of these are showing where? Did you check 'Send Preset to FS'? Your log file shows 11085 presets have been loaded, so you should see at least that that many entries in the drop-down when you select 'Send Preset to FS'. Can you first update to v 7.3.23, which was released a few days ago. In this version, there will be far fewer entries in the axis assignment drop-downs when 'Send Preset to FS' is selected as only those accepting a parameter will be displayed. How many presets do you see loaded (check your FSUIPC7.log file, near the top)? You should see 11090 +the number in your myevents.txt file.

There is no problem having the script ran on a button press. However, this means that a new thread is created & started and the script is compiled (before being ran) an each button press, which introduces a small overhead/delay on each button press. Having the script auto-ran and activating on events is generally more efficient as the the thread generation and script compilation is only done once (and at start-up) rather than on each button press. John

Note also that if you do want to call a preset (available in FSUIPC) from an FSUIPC client app, you can do this by writing the preset name (preceded by 'P:') to offset 0x7C50. John