John Dowson
-
Posts
13,264 -
Joined
-
Last visited
-
Days Won
271
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
12 hours ago, shorthauler said:
I had the Lua scrip running continuously due to a faulty Auto entry in FSUIPC.INI
No problem.
Note it would be more efficient if you changed the script to something like:
Quotefunction modeKnob(param)
ipc.writeLvar("VC_GSLD_CP_EFIS_ND_Mode_Knob", param)
endevent.param("modeKnob")
have the script auto-started, and assign your rotary buttons to the LueValue <script> control to set the parameter. Doing this, the lua script is only compiled once and you should get better performance.
John
-
4 minutes ago, shorthauler said:
I have an 8-position-switch (A320 EFIS mode selector), so this corresponds to 8 seperate buttons. I have set up these buttons to call a Lua script ("Control sent when button pressed"). Every button calls the same Lus script but sends different parameters (0, 10, 20, 30, 40). The parameters are supposed to set an Lvar state that will select the respective mode (LSm VOR, NAV, ARC, PLAN). This is for FSUIPC4.
Ths Lua script consist of one single line:
ipc.writeLvar("VC_GSLD_CP_EFIS_ND_Mode_Knob", ipcPARAM)
That sounds reasonable...
5 minutes ago, shorthauler said:Any input will be much appreciated.
Please activate debugging for Debug/Trace Lua plugins (NOT Log Lua plugins separately) as well as Button and Key operations and generate a log file showing your issue. Please also list the lvars before you move your 8 position rotary so that I can check the lvar exists (you can assign a spare button or key press to do this, either using the List local panel variables control, or the provided Log Lvars.lua), as well as after you have turned your rotary to check if the value has changed or not. Then show me / attach your FSUIPC4.log and FSUIPC4.ini files together with your lua script.
John
-
2 hours ago, Mustang 1-1 said:
You are saying I need to name it .mcro.txt?
No! Quite the opposite...
2 hours ago, Mustang 1-1 said:t’s called TAKEOFF-TRIM-MACRO.mcro
From the Advanced User guide:
QuoteIt is important that the file name (xxxx.mcro) is limited to 16 characters maximum, (plus the ".mcro"). This will be used as part of the name of the added controls in the drop-downs. Best to keep the names short and to the point—probably the name of the program or program function for which the controls are being added.
Your filename contains 18 characters, so please rename to something shorter and more sensible. And don't forget that the filename and macro name will appear for assignment (i.e. as filename: macroName), so name both the file and the macros in it accordingly.
-
4 minutes ago, Mustang 1-1 said:
The correct macro extension is .mcro right?
Yes. Some users have found that their macros weren't recognised as a .txt extension had been added after the .mcro, so worth checking.
-
@salsero_at Could you please attach your MakeRwys_Scenery.cfg file - it may need compressing/zipping before attaching. Can you also check the Windows Event viewer to see if there are any events relating to MakeRunwys, especially crash/error events, and also post the details of those.
Thanks,
John
-
Check the [MacroFiles] section of your FSUIPC6.ini file - do you see your macro file there? If not, then the macro file is either not in the correct location or it has the wrong extension type.
If it is there, then it should be in the menu...
You can also check that you have installed in the correct location by using the 'Open Folder' button in the Logging tab - do you see your macro file (and with the correct extension)?
-
Do you have a steam and and an MS Store version installed on the same PC, or are they on different machines?
If they are on different machines, please show me/attach your InstallFSUIPC7.log file for the MS Store version. Also please see the following FAQ entry:If they are installed on the same PC (which I didn't know was possible), then the Installer will first detect the steam installation and install for that. To also use with the MS Store version, you will have to manually update the EXE.xml file for the MS Store version to start FSUIPC7, and if the two versions have different Community folders, then you will also need to copy across the WASM from the Steam Community folder to the MS Store one.
Also, please give your posts a relevant and appropriate tile - 'FSUIPC7' applies to every post in this forum and is therefore useless...I will update it.
John
-
-
12 hours ago, mrjohn said:
May I have a trial key please?
License sent.
12 hours ago, mrjohn said:I especially want to know if I can derive aircraft attitude (pitch, bank, heading) and latitude/longitude using FSUIPC7.
Those values will be held in FSUIPC offsets. Note that you don't need a license if you are writing your own program using the FSUIPC SDK (or WAPI API).
-
-
Ah, sorry...you are using the PMDG 737. You can use the custom controls (parameter probably not necessary). The following controls are available:
Quote#define EVT_CONTROL_STAND_FLAPS_LEVER (THIRD_PARTY_EVENT_ID_MIN + 714)
#define EVT_CONTROL_STAND_FLAPS_LEVER_0 (THIRD_PARTY_EVENT_ID_MIN + 7141)
#define EVT_CONTROL_STAND_FLAPS_LEVER_1 (THIRD_PARTY_EVENT_ID_MIN + 7142)
#define EVT_CONTROL_STAND_FLAPS_LEVER_2 (THIRD_PARTY_EVENT_ID_MIN + 7143)
#define EVT_CONTROL_STAND_FLAPS_LEVER_5 (THIRD_PARTY_EVENT_ID_MIN + 7144)
#define EVT_CONTROL_STAND_FLAPS_LEVER_10 (THIRD_PARTY_EVENT_ID_MIN + 7145)
#define EVT_CONTROL_STAND_FLAPS_LEVER_15 (THIRD_PARTY_EVENT_ID_MIN + 7146)
#define EVT_CONTROL_STAND_FLAPS_LEVER_25 (THIRD_PARTY_EVENT_ID_MIN + 7147)
#define EVT_CONTROL_STAND_FLAPS_LEVER_30 (THIRD_PARTY_EVENT_ID_MIN + 7148)
#define EVT_CONTROL_STAND_FLAPS_LEVER_40 (THIRD_PARTY_EVENT_ID_MIN + 7149)To use PMDG custom controls, please see the following FAQ entry:
John
-
1 hour ago, qxadrian said:
Hi, John, Please, Could you send me a trial key?
Sent.
John
-
24 minutes ago, simnutzer1962 said:
What do you mean "see the discription for offset 0x0BDC"? The Usermanual of FSUIPC? Or a thread here in the community?
In the FSUIPC Offset status document.
25 minutes ago, simnutzer1962 said:And a question to the alternatively: Where can I read/log the offset?
Use the FSUIPC offset logging facilities.
27 minutes ago, simnutzer1962 said:I would be pleased, if you could help in further ways, like an example, where to find and how to do.
First, enable logging for offset 0BDC as U32. You do this on the right-hand side of FSUIPC's Logging tab. Make sure you check FS Title Bar, and the offset will be logged in the P3D title bar. Then, move the flaps lever to the position that you want for an assignment, and take note of the value displayed in the title bar - this is the parameter that you need to use for the assignment. Then move to the next flap position and repeat.
John
-
Sorry, I understood that it is not working when you run it as non-admin but is working correctly when you run it as admin.
Since Pete has retired, MakeRwys is no longer supported - from fsuipc.com:
QuoteNote that MakeRunways is now closed for further development, as Peter Dowson, the original author of this product, has now retired. However, you can download the source and update for your own needs. The source code for this utility is available on GitHub at the following location: https://github.com/jldowson/MakeRunways/. If you would like to take over development and support of this product, please PM me via the support forum (SimMarket)(John Dowson).
However, Pete does still pick-up and respond to issues with MakeRwys. Unfortunately he is currently on holiday, back at the end of the month. I can ask him to take a look when he returns.
John
-
Just run it as administrator - from the MakeRwys readme document:
QuoteNOTE that you should run MakeRunways “as administrator”. This is especially true on Win10. The best way is to mark it needing admin privileges in its (or its shortcut) “Properties – Compatibility” settings (right click on the EXE or the shortcut)
John
-
You can use the Flaps Set control. To calculate the parameter, see the description for offset 0x0BDC:
QuoteThe “notches” for different aircraft are spaced equally across this range: calculate the increment by 16383/(number of positions-1), ignoring fractions.
Alternatively you can read/log offset 0x3BFA which will give you the flaps detent increment (i.e. the value between each flaps detent/position) and then use this to calculate the parameter needed for each position.
John
-
11 hours ago, Hazzer111 said:
Unfortunately the axis does not show up, nor can I see it when I request the LVARs to be listed.
What axis? You are defining a preset, not an axis or an lvar. You can see presets in the axis assignment panel once you have selected 'Send Preset to FS'. You should then see the presets you have defined in the axis assignment drop-down. When you list the lvars, you can see the lvars that the presets you have defined are using: INPUT_AILERON & INPUT_RUDDER_S.
Note I have just released a new version which, amongst other things, reduces the presets in the axis assignment dialog drop-down menu to contain only those presets which accept a parameter, which drastically reduces the number of presets available and makes them far easier to find and assign. So please update at your earliest opportunity.
John
-
Which version of FSUIPC and what FS are you using? If its FSUIPC7 / MSFS, please use the specific sub-forum for this product.
No A-type variables (also known as simvars) can be read via lua. The only A-type variables can be read are those that are held in FSUIPC offsets.
7 hours ago, Raysot said:I've tried several variations, like ipc.readLVar("A:CIRCUIT SWITCH ON:73") and ipc.readLVar("A:CIRCUIT SWITCH ON,73")
...and a few other variants, all returning NIL.Of course, as these facilities are for L-type variables, or lvars, only. You cannot use them for any other variable type.
So, A-type variables (simvars) can only be accessed (read/write) via FSUIPC offsets. Facilities are provided to add any simvar to a free/spare FSUIPC offset (see the Advanced User guide) using a file called myOffsets.txt. So you can add them to a spare/free FSUIPC offset, and then use the appropriate lua offset function to read the value.
-
Yes. just delete it.
John
-
3 minutes ago, thepairoto said:
May I have a trial license?
License sent.
3 minutes ago, thepairoto said:I am trying to test if I can bind the engine run/stop key on the citation longitude, seeing if I can make this work.
You can assign to the presets Longitude Eng R Fuel Run Stop Button Press and Longitude Eng L Fuel Run Stop Button Press. There are also presets available for the engine left/right starter - see https://hubhop.mobiflight.com/presets/.
Note that tomorrow I will be releasing a new version that contains a UI update that makes finding presets a lot easier, so I suggest you update to this version once released.
John
-
On 9/7/2023 at 10:02 AM, John Dowson said:
- Add a Find Preset... button to the key assignments dialog. This should be straightforward.
This has now been implemented in the attached version. 7.3.23. This completes the implementation of this item for the time being.
The attached version will also be the next release, and also contains a version check at start-up and will notify (display a message) if a newer version of FSUIPC7 is available.
John
EDIT: the attached file/version has been removed as this version has now been released
-
On 9/8/2023 at 3:16 AM, vanislepilot said:
Looks like this was an issue with LVars not loading currently. Working fine now.
What do you mean by this? Lvars are independent from the PMDG offsets. Even if you uninstalled the FSUIPC WASM module (to disable access to lvars) the PMDG offsets would still be available and populated (once activated)..
-
On 9/8/2023 at 2:52 PM, aurel42 said:
because the tree view doesn't remember which branches were visible/"unfolded". Is that something the toolkit can do?
Please try the attached version: FSUIPC7.exe
This should automatically select and show any current preset that is assigned, and also select the parent of the previous selection made if no current selection/assignment available. Note however that it does not remember the previous state if no selection is/was made.
John
-
On 9/7/2023 at 10:02 AM, John Dowson said:
Automatically select the preset in the preset tree if a preset is already assigned when the Find Preset... button is pressed. I am having some difficulties with this but will continue to look unto this.
This has been implemented in the attached version. Also, if there is no currently assigned preset, the parent node of the previous node selected will be selected.
John
C# app integration for hardware and WASM module
in FSUIPC Client DLL for .NET
Posted
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