John Dowson
-
Posts
11,999 -
Joined
-
Last visited
-
Days Won
241
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
2 minutes ago, mrb13676 said:
[Macros]
1=MBAutoT
1.1=68836,x20000000
1.2=69837,x20000000
2=FSUIPC. //this is just copied from the manual to check the macro is available in FSUIPC
2.1=K68,12; Tab D
2.2=K70,8; F
The problem is that the MBT7:MBAutoT does not appear in the dropdown list. MBT7:FSUIPC Does appear.
Any ideas what I'm missing here? I've had a look at the manual but I'm clearly missing an important bit.
Control numbers must be preceded by C, so its:
[Macros] 1=MBAutoT 1.1=C68836,x20000000 1.2=C69837,x20000000 2=FSUIPC. //this is just copied from the manual to check the macro is available in FSUIPC 2.1=K68,12; Tab D 2.2=K70,8; FJohn
-
4 hours ago, antpl81 said:
Requesting Trial License Please
Sent
-
@VENOMous Still waiting to see your FSUIPC7.JoyScan.csv file so that I can correct your assignments...please also attach your latest FSUIPC7.ini and FSUIPC7.log files.
-
15 hours ago, Flávio Oliveira said:
This file, when executed, will turn on the aircraft light, for example.
You can use the FSUIPC SDK to create such a file. Using the SDK, you can write to FSUIPC offsets to trigger events/controls, presets, etc. There are also quite a few wrappers to the SDK for various languages, the most popular and advanced being Paul Henty's .Net client dll. There is a sub-forum for this here:
https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/Otherwise, take a look in the SDK folder of your FSUIPC installation.
John
-
11 hours ago, Reco said:
looking for engine trim rpm increase and engine rpm decrease .
Can't seem to find it in the menu is it under a different title ?
I do not know of any such control - as far as I understand, there is only the throttle...
Do you have an aircraft where it is possible to control this (in the virtual cockpit)? If so, then it may be possible in that aircraft, but there is no generic FS control/event for this.
-
37 minutes ago, hermann2441 said:
Is there an offset that i can use to recognice that the plane is a 777?
You can read the name of the current aircraft in offset 0x3D00.
-
1
-
-
3 hours ago, maxam said:
I installed the FSUIPC WASM Module and Mobiflight events.txt, but the preset remains blank.
You have NOT installed the MF events.txt file - from you installation log:
QuoteMF events.txt file not installed.
and from you FSUIPC7.log file:
Quote62 Preset file 'C:\FSUIPC7\events.txt' not found [info only]
62 Preset file 'C:\FSUIPC7\myevents.txt' not found [info only]Please re-run the installer and select to install the MF events.txt file, or download it from the MF HubHop site (https://hubhop.mobiflight.com/presets/) and copy it to your FSUIPC7 installation folder.
-
11 hours ago, maxam said:
In an attempt to program the Bravo Throttle I choose "Select Preset" in FSUIPC7, but the window is blank. I have the PMDG 737-700 installed. What am I doing wrong?
I don't know as you do not provide enough information. Did you install the FSUIPC WASM module? Did you install the MobiFlight events.txt file (which holds the MF presets)?
Please show me/attach your FSUIPC7.log file and also your InstallFSUIPC7.log file and I will take a look.
-
11 hours ago, MD80PROJECT said:
in any of these free spaces that I show you below:
0x66C0 - 0x66FF: 64 bytes
0x0D70 - 0x0DFF: 144 bytes
0x0FA0 - 0x0FFF: 96 bytes
0x3C00 - 0x3FFF: 1024 bytes
0x5200 - 0x53FF: 512 bytes
0x5400 - 0x55FF: 512 bytes
0x5600 - 0x56FF: 256 bytes
0x5700 - 0x57FF: 256 bytes
0x5C00 - 0x5FFF: 1024 bytes
0x7000 - 0x7FFF: 4096 bytes
0x8000 - 0x83FF: 1024 bytes
0x8400 - 0x87FF: 1024 bytes
0x8800 - 0x88FF: 256 bytesit's right ?
No! Why do you think that? For example, 0x0D70 is the area for Macro and Lua requests, as it states in the FSUIPC6 Offset Status document:
Quote0D70 128 Macros and Lua requests
Write here the complete identity string of a Macro control or Lua program control in order to have FSUIPC execute it.
For a Macro, the string should begin with up to 16 characters giving the .MCRO file name (just the name part, not the type), and then, separated by a ‘:’ character, the macro name within that file—again, up to 16 characters. Spaces either side of the ‘:’ are optional.
...Please see that document, and you can use offsets in areas designated as Free for general use.
11 hours ago, MD80PROJECT said:In that case, my intention is to use the following code, to save the value of CM1_egpws_on_adv1 in a free offset, for example using the offset 0x8804.
function egpws_on_adv1 (var_name, value)
ipc.writeUD( 0x8804 , value)
end
event.Lvar("L:CM1_egpws_on_adv1", 100, "egpws_on_adv1")Thats fine and will store the value of the lvar in the offset (for reading ONLY), except that offset 0x8804 is NOT free for general use. Please DO NOT use offsets that are not documented as free for use as this may cause issues.
11 hours ago, MD80PROJECT said:want to save a .lua file called egpws_on_adv1.lua, in the FSUIPC6 raid folder
What is a 'raid folder'? All lua scripts should go in your FSUIPC6 installation folder, or the folder specified by LuaPath if using that.
11 hours ago, MD80PROJECT said:in the [Auto] section, remaining as follows:
[Auto]
1=PitotHeat
2=Lua MADDOG_X
3=Lua CM1_mastercaut_adv1
4=Lua CM1_masterwarn_adv1
5=Lua ovhd_apu_bus
6=Lua eoap_a_adv1
7=Lua ovhd_emerg_pwr_adv1
8=Lua CM1_alt_adv1
9=Lua eoap_door
10=Lua eoap_ice
11=apu_L_bus
12=ext_pwr_L_bus
13=ovhd_pa
14=egpws_on_adv1Entries with indices 1m11,12,13 & 14 are ALL incorrect. Lua scripts in this section MUST be preceded by Lua, as are the entries with indices 2,3,4,5,6,7,8,9.
11 hours ago, MD80PROJECT said:I am trying to interrogate the offset 0x8804 to turn on the LED.
You can interrogate (i.e. read) the offset to get the status of the LED, but you cannot control it as the offset will be read-only, as you have not added any lua code to handle a write/update.
Please do not attach images, especially of MobiFlight which I do not support. I will remove that.
-
9 hours ago, Edoradar said:
Hi John, did you have any chance to look into that?
No yet - I am rather busy in support issues at the moment, and my time is rather limited at the moment due to health issues.
Don't worry, I haven't forgotten, and will hopefully find time to look into this next week.
-
Looks good now!
3 hours ago, PEPIN said:I notice that my fps have increased. Do you think that it is in relation with these wrong repeat settings ?
No, I don't think a repeat assignment would effect fps that much....but you could add it back to see if the fps decreases if you want to check this.
John
-
Many of the camera controls in MSFS are not working when assigned externally, including the zoom controls.
There are also some MF presets for zoom, but these also don't seem to work.Therefore to control zoom, you can either assign in MSFS, or assign in FSUIPC7 to the default key assignments. So, for example, to assign to cockpit zoom-in, assign your button to send the equals key ('='), and for zoom-out, assign to the hyphen/dash key ('-').
-
You still have not changed the preset assignments on repeat in your [Buttons.PMDG 777] section - change these as well, as I said in my last comment::
15=RF,4,CPPMDG_B737_FD_Switch_Capt_On,0 -{Preset Control}-
17=RF,31,CPPMDG_B737_FD_Switch_FO_On,0 -{Preset Control}-
21=RE,4,CPPMDG_B737-7_GEAR_DOWN,0 -{Preset Control}-
-
That log file you attached ends after 94 seconds before you even had the 777 loaded and ready to fly, and so is useless.
You also have other presets sent on repeat - please also change these:
15=RF,4,CPPMDG_B737_FD_Switch_Capt_On,0 -{Preset Control}-
17=RF,31,CPPMDG_B737_FD_Switch_FO_On,0 -{Preset Control}-
21=RE,4,CPPMDG_B737-7_GEAR_DOWN,0 -{Preset Control}-
-
23 minutes ago, noahharget said:
The only issue I'm having now is FSUIPC isn't starting with MSFS. I have to manually open it.
For all auto-start issues, see
23 minutes ago, noahharget said:I switched to SPAD for controls.
Sorry to hear that. No idea wht your issue was as I never saw your files. There does seem to be an occasional issue with the WASM when using the 777 which I am investigating.
-
This issue is usually caused by flaps calibration. If flaps assigned in FSUIPC, make sure it is assigned with 'Direct to FSUIPC calibration'. If not assigned in FSUIPC, check that you are not post calibrating. You can attach your FSUIPC7.log and FSUIPC7.ini files and I can take a look.
-
II need to see your FSUIPC7.log file as well please. I always need that.
I have now experienced a WASM crash switching between the PMDG 737 and 777, so there is definitely an issue there. But your WASM log shows that it ran ok for you, so it must be something else.
I am investigating the WASM crash and will get back to you once I have found anything.
-
58 minutes ago, MD80PROJECT said:
I use FSUIPC6.
You mean to use a script.lua to read if the value of Lvar: CM1_egpws_on_adv1 changes state, and store the value in a free/spare FSUIPC offset, is that correct?For example:
function egpws_on_adv1 (varname, value)
ipc.writeUD(0x0000, value)
end
event.Lvar("L:CM1_egpws_on_adv1", 100, "egpws_on_adv1")but I need to know what the free/spare FSUIPC offset list is to be able to use, and replace (0x ? ? ? ? ) with a free/spare offset, can you tell me where I can get this list?
Yes, that looks correct. Check the FSUIPC Offset status document for a free offset, e.g. there are 512 bytes free starting at 0xA000
1 hour ago, MD80PROJECT said:Once stored in a free/spare FSUIPC offset value, configure it with mobiflight to turn the LED on or off according to the value of the new free/spare FSUIPC offset, is that correct?
No. Your lua script is only for reading at the moment. If you want to update the lvar when you update the offset, you have to have that as well. So you need to add an event.offset call (on the offset you use) and in the handling function you can set the lvar value. Before you set the value, check it was not the value received and written to the offset, e.g. store the lvar value in a local script variable when received and check its different from the offset value when that changes before you use it to set the lvar value.
-
First, what version of FSUIPC and what simulator are you using?
1 hour ago, MD80PROJECT said:I want to identify the offset where this Lvar is saved so I can program it with mobiflight
For information on offsets, please see the FSUIPC Offset status document for your version of FSUIPC.
However, there will be no offset holding that lvar value. FSUIPC does not hold any lvar values in offsets by default. If you want to add an lvar to an FSUIPC offset, you can do that but it doesn't happen by default.
In FSUIPC7, you can use an [LvarOffsets] section of the FSUIPC ini file - see the Advanced user guide for details.
For other versions of FSUIPC you would have to use a lua script. The script should wait for the lvar value to change (event.lvar) and in the handling function, write the value to a free/spare FSUIPC offset.
But if using MobiFlight, doesn't that have access to lvars without using FSUIPC?
John
-
35 minutes ago, dutchkip said:
Had to assign throttle 2 as it wasn't reacting
I noticed this was missing in the ini file you attached, which I thought was strange...
36 minutes ago, dutchkip said:and found throttle 2 moving about when on auto pilot and VNAV activated causing AT to switch off
Not sure what could cause this.
Anyway, please keep an eye on things and send me the files again if you get a problem, as there may be an issue somewhere as others are having similar problems.
-
First, get you stop all these errors:
Quote128079 [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '2 (>L:S_OH_EXT_LT_LANDING_L) 2 (>L:S_OH_EXT_LT_LANDING_R) 2 (>L:S_OH_EXT_LT_LANDING_BOTH)'
These are from preset FNX320_LIGHT_LANDING_BOTH_ON which you have assigned on repeat, so this is getting sent 20 times a second, causing those errors. Please change the assignment line in your [Buttons.Fenix A320] section:
14=RE,17,CPFNX320_LIGHT_LANDING_BOTH_ON,0 -{Preset Control}-
Change that R to a P:
14=PE,17,CPFNX320_LIGHT_LANDING_BOTH_ON,0 -{Preset Control}-
You are also using the same assignment in your TBM 930 profile - change there, or maybe just remove those assignment to Fenix presets.
Other than that, it looks like WASM connection wasn't working, which is why the presets weren't working.
Can you make that correction please and test again and show me the new FSUIPC7.log file and the FSUIPC_WASM.log file. The location of the latter is:
QuoteFor Steam installs, in the following folder under your user account:
AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\workFor MS Store installs, in the following folder under your user account:
AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\fsuipc-lvarmodule\work -
Also, please add
TestOptions=x800
to the [General] section of your FSUIPC7.ini file. This will add extra logging on when/why FSUIPC7 is starting, or not.. -
Sorry, but your log file again shows that you were trying to use presets before FSUIPC was ready.
Did you actually load an aircraft and get ready-to-fly? Looks like you got to the main MSFS menu after 76 seconds, then exited MSFS 5 minutes later, and FSUIPC7 did not detect you having an aircraft loaded and ready-to-fly. Can you please explain what you did.Also, please try another aircraft. Maybe this is an issue with the Fenix.
-
On 7/6/2024 at 8:41 PM, noahharget said:
I have not tested this in other addons, however I do recall needing to previously set which profile for each livery.
This is because you are not using substrings for your aircraft names in the [Profile.xxx] section of your FSUIPC7.ini. You need to edit the names there to be a substring of the aircraft name that matches the aircraft regardless of livery. Otherwise, you can switch to using UseAirLocForProfiles instead (see Advanced User guide on this parameter), but if you do this you will have to add each aircraft to your profiles again, and remove the current entries under your [Profile.xxx] sections as these will no longer be relevant.
(MADDOG X) search offset, indication light.
in FSUIPC Support Pete Dowson Modules
Posted
Sorry, but I do not understand this. If I search for free offsets in the offset document, I find these:
This is for FSUIPC6 v6.1.5 and later. The official release is now 6.2.0. If you are using an older version, please update.
Is that not enough space to use? If not, then you van use offsets assigned to other things (i.e. 3rd party software such as the PMDG offsets).
But please at least first use the offsets available. If then you run out of space, I van let you know which other offsets to use (documented in FSUIPC7, but not yet in FSUIPC6).
John