John Dowson
-
Posts
13,298 -
Joined
-
Last visited
-
Days Won
271
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
As Pete says, your lua script is using a LINDA lua library function that isn't present when you run your script outside of the LINDA environment.
To use this outside of LINDA, you would need to include that script, and all its dependencies. -
Can you also check that you have 'Power Management' disabled' on all your usb devices and hubs.
-
Maybe you could also try with this added to the [General] section of your FSUIPC7.ini:
UseAIClient=NoThis will instruct FSUIPC to NOT use a separate SimConnect connection for AI, and will use the main connection instead (i.e. no change in functionality). This would help me to determine if the issue is related to multiple SimConnect connections interfering somehow.
-
@MartyReynolds If you are unplugging and re-connecting USB devices, you should really use the 'JoyLetters' facility (see User guide if you don't know what this is), which will prevent problems if/when Windows assigns a different id to your device(s).
-
Looks like you have registry issues, but could you please also show me your FSUIPC6.log file.
Also, you aren't using the 'JoyLetters' facility. You should really activate this to prevent problems when windows re-assigns your ids. Please see the FSUIPC User guide for details, or simply change
AutoAssignLetters=No
to
AutoAssignLetters=Yes
in the [JoyNames] section of your FSUIPC6.ini file and run P3D. -
1 hour ago, PSantos said:
(GPS buttons and Altitude Pre-Select) also can´t programa the Reset-Start-Freeze-Map-Con-Instr buttons.
There are many buttons/switches that can't be programmed at the moment either due to lack of controls or controls not working, especially for AP systems (G1000 etc).
Also. it seems that, depending on the aircraft and the AP system used, you may have to switch authority from the FCU to enable, and this may also apply to the MCP. I am referring to this post:
QuoteI have found this possibly interesting post on MSFS forums :
"There are no commands that are visible in control settings GUI. But you can control the FCU authority with these Sim Connect sim events; HEADING_SLOT_INDEX_SET SPEED_SLOT_INDEX_SET ALTITUDE_SLOT_INDEX_SET VS_SLOT_INDEX_SET Sending these with parameter 2 gives the authority to FCU, and sending with parameter 1 activates selected mode for each knob. You’ll need to use a 3rd party controller interface software that use sim connect; ....."
Maybe that these "SLOT_INDEX" variables or controls set to 1 allow normal operations for the knobs of MCP ?
I cannot send them directly to simconnect... never even tried to do this directly, only used FSUIPC.
See this topic for further details:
-
59 minutes ago, Masterius said:
I've no idea why it runs in LINDA but not FSUIPC.
Nor have I - assignments look good. Try activating logging for Buttons & Switched and Lua plugins to see if that tells you anything. You can post your log file here. Try without LINDA running as well to see if that's interfering.
-
I'm not sure about the Saitek X56, but its possible with the mode switch on the saitek yoke.
When you change the mode switch, does FSUIPC see this in the buttons and switches assignment dialog? If so, it should be straightforward to use in FSUIPC.If not, some folks had to remove/rename a file called SaiD0BAC.PRO (in C:\Windows\System32) to get the mode switch of the yoke recognised. Maybe there is something similar for the X56?
Also, note that FSUIPC only sees the first 32 buttons (0-31), so if the button number of the mode switch is higher than that it won't be recognisd in the assignments panel and you would have to resort to lua to program the button. You can check in the windows game controllers utility to see if your mode switch is recognised there (and what number it has).
Finally, make sure that you have not installed the saitek software or drivers and just use the standard windows drivers.
-
@Thomas Richter Those assignments are fine. He's just overloading the previous button press (adding '10' to the entry number, and using offset conditions.
These are the ones that should be removed as they are assigned to controls that no longer exist:
Quote50=RL,12,C1010,0 -{}-
51=RL,7,C1011,0 -{}-For the actual problem, I'm still not sure if the TrransmitClientEvent failures are due to MSFS or FSUIPC7. However, when this occurs FSUIPC7 should be able to disconnect and reconnect successfully without crashing. This looks to be a threading issue which I'll look into.
Btw, could you also activate 'Extras' logging. This will add a but more information (namely the thread id of the thread logging the message) which may be helpful.
Thanks,
-
14 hours ago, bahnzo said:
There's so many buttons that don't have mappings it seems.
Yes, but its pretty much the same in FSX/P3D, although not quite so bad. However, previous versions of FSUIPC had the mouse macro functionality that enabled you to assign to UI components that weren't controllable via standard SimConnect events or variables. I think we have to wait for something similar to be implemented in MSFS, rather than expecting ASOBO to implement SimConnect events to control all buttons/switches for all aircraft.
-
14 hours ago, Masterius said:
It appears that buttons can be programmed for keypresses, controls, and macros, but not a .lua.
Starting/stopping luas are controls added by FSUIPC, as Thomas has shown you.
-
18 hours ago, erjdriver said:
What if the lua file has no window?
As Pete said earlier, just run it again and it will kill the previous incarnation. Or to just kill it, you can also use the provided control.
-
15 minutes ago, erjdriver said:
ok now i need wideFS you say - i installed it, ran wideclient and then when p3d runs - it says another p3d program is already running.
You run WideFS on a client PC. If you want to run it on the same PC as FSUIPC/P3D, you have to change the class name - see the provided documentation for details.
But, do you really need WideFS? This is really only needed to run FSUIPC clients on a different machine to P3D o/FSUIPC. You should not use that just to use the lua display library. You can use ipc.display instead for luas running in FSUIPC. For example, try the attached lua:
-
Hi Stephan,
first, I have moved your post to the dedicated FSUIPC7/MSFS sub-forum. Please use this sub-forum for question on FSUIPC7/MSFS.
18 minutes ago, SloMo said:Can i assign them via FSUIPC as second inputs for the aileron and rudder ?
Yes, you can - but only if your device is recognised as a standard windows HID device.
19 minutes ago, SloMo said:And what about sensitivity ? The elevator-trimmwheel seems to be over-sensitive, and the sensitivity-adjustments of MSFS seem to be not usable for a trimm-input.
Is it correct, that i can handle this via FSUIPC too ? Making a curve with less sensitivity during the middle 2 turns ?
In FSUIPC, you can add 'curves' to adjust the sensitivity.
I suggest that you just download and try FSUIPC7-beta. It currently comes with a time-limited license so you can try the assignments. See
John
-
-
There is now an installer ready that includes the WebSocket server + integration into FSUIPC7 (via an Add-ons menu entry). You can download from here:
http://fsuipc.simflight.com/beta/Install_FSUIPC7.zip
http://www.fsuipc.com/download/Install_FSUIPC7.zipThere is an issue if the WebServer is already running when FSUIPC7 is started as it currently doesn't check for this. I may add this at a later date.Also, there is currently no indication if the WebSocket server is running or not (apart from entries in the log). I think I'll update the FSUIPC7 title bar to include this information at some point.Let me know if you have any issues or suggestions.John -
Hi Joshua,
as described in the Announcement and in the provided README.txt file:
QuoteMissing Functionality
The following functionality is not currently available in FSUIPC7. We may look at re-instating some of these
items at a later date, if and when such facilities are provided by the MSFS SDK:1. Mouse Macros (and other mouse functionality, e.g “mouse look”, etc): pending facilities to be provided
2. lVar access: pending facilities to be provided (if lVars still exist!)
...John
-
How are you running the lua? On a button press or from the [Auto] section?
Maybe you can attach your FSUIPC6.ini file and I'll take a look. Otherwise, you could try activating debugging of Lua plugins to see what that tells you.
-
7 minutes ago, erjdriver said:
Do I need the paid version of fsuipc?
Yes. Lua functionality is only available in the registered version of FSUIPC.
-
Sorry, but it is still not clear what you issue is. Is it the loss of controls, or with Pilot2ATC?
For loss of controls, check that you have power management disabled on your usb devices/hubs.
You can also try activating logging for Axes Control in FSUIPC7. Monitor the console log (i.e. Log -> Open Console) and see what is logged, if anything, when you experience the loss of control.However, as you say that you lose control of your mouse, it sounds more like an MSFS issue as FSUIPC7 does nothing with the mouse. You could also check to see if any keyboard shorcuts have any affect when this occurs.
For issues with Pilot2ATC, you really need their support forum.
-
6 hours ago, erjdriver said:
It says add .lua files to the Modules folder - where is this folder?
Where the documentation uses the term 'Modules folder', it refers to your FSUIPC installation folder. Previous to FSUIPC version 6, FSUIPC was, by default, installed in a folder called Modules, located under the main P3D folder. So its the folder that you select to install FSUIPC6 into. if you don't know where this is, there is also an 'Open Folder' button in the FSUIPC6 logging tab that will open Windows Explorer on this folder.
6 hours ago, erjdriver said:Can you suggest a test lua file from the examples folder that will display something on the sim screen - for me to know it's working
Would mydisplay.lua work??
Sure.
6 hours ago, erjdriver said:Do I need to restart P3D on each edit or will it be automatically be re-loaded on edit/save.
No, you need to restart the lua. i.e. kill it (if its running) and start it again. The file will be re-compiled each time it is ran.
6 hours ago, erjdriver said:i.e. is this Modules folder being monitored by fsuipc for auto reload.
No, it isn't But as I said, you just need to stop the lua running and then restart it.
-
23 hours ago, PandaPlayerz said:
, but I'm not sure if the G1000 PFD and MFD buttons are able to be configured yet. Is this possible yet, or are we still waiting on that support?
Still waiting. This has already been asked many times, e.g.
-
30 minutes ago, wiganlad said:
I'm having an problem installing FSUIPC6 into prepar3d v5, It appears to be going through the install procedure ok, ( log file attached) it doesn't appear in the Add-ons in Prepar3D v5 menu., however it shows in the Options - Add-ons drop down menu but is unticked,
After you have installed FSUIPC6 and you start P3Dv5, you should have seen a pop-up dialog asking if ok to enable the add-on:
didn't you see this and give permission?
30 minutes ago, wiganlad said:ticking the option also does not fix the problem, have done restarts of P3D and reboots but to no avail.
So when you tick the option, select 'Ok', then close and restart P3Dv5, you still don't see the Add-ons menu option with FSUIPC... menu option?
Your installation log looks fine, so I'm not sure what is going on. I suggest that you uninstall the FSUIPC6 installation in P3Dv5 by running the uninstaller (located in your installation folder: C:\Users\onebo\Documents\Prepar3D v5 Add-ons\FSUIPC6\uninstallFSUIPC6.exe). Then re-run the installer and try again. I would also suggest that you choose a folder outside of your Documents folder for the installation. This is just a default and is where the add-on.xml will be created, but it is better to actually install FSUIPC6 in a different folder (e.g. C:\FSUIPC6).
-
There is no change with this functionality in the latest build, and I just tested in the Lomgitude and its working as expected.
23 minutes ago, ankh21 said:Anything i can do to help investigate this behaviour?
You can try logging Events and Axis Controls. Before you activate the toggle, you should see the THROTTLEn_SET controls with a positive Param:
Quote...
714156 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 194 (0x000000c2) THROTTLE1_SET
714156 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 226 (0x000000e2) THROTTLE2_SET
714156 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 454 (0x000001c6) THROTTLE1_SET
714156 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 484 (0x000001e4) THROTTLE2_SET
714234 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 649 (0x00000289) THROTTLE1_SET
714234 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 679 (0x000002a7) THROTTLE2_SET
714234 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 876 (0x0000036c) THROTTLE1_SET
714250 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 905 (0x00000389) THROTTLE2_SET
714250 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 1103 (0x0000044f) THROTTLE1_SET
714250 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 1131 (0x0000046b) THROTTLE2_SET
714250 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 1315 (0x00000523) THROTTLE1_SET
714250 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 1342 (0x0000053e) THROTTLE2_SET
714250 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 1591 (0x00000637) THROTTLE1_SET
714250 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 1617 (0x00000651) THROTTLE2_SET
714281 *** EVENT: Cntrl= 66093 (0x0001022d), Param= 0 (0x00000000) AP_AIRSPEED_ON
714312 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 1883 (0x0000075b) THROTTLE1_SET
714312 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 1908 (0x00000774) THROTTLE2_SET
714312 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 2126 (0x0000084e) THROTTLE1_SET
714328 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 2150 (0x00000866) THROTTLE2_SET
...When the assigned button is pressed, you should see the toggle control:
Quote722484 *** EVENT: Cntrl= 68069 (0x000109e5), Param= 0 (0x00000000) THROTTLE_REVERSE_THRUST_TOGGLE
and after this, the Param for the THROTTLEn_SET controls should be negative:
Quote...
723500 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -24 (0xffffffe8) THROTTLE1_SET
723500 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -32 (0xffffffe0) THROTTLE2_SET
723625 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -68 (0xffffffbc) THROTTLE1_SET
723625 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -76 (0xffffffb4) THROTTLE2_SET
723703 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -101 (0xffffff9b) THROTTLE1_SET
723703 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -108 (0xffffff94) THROTTLE2_SET
723703 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -137 (0xffffff77) THROTTLE1_SET
723703 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -145 (0xffffff6f) THROTTLE2_SET
723765 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -186 (0xffffff46) THROTTLE1_SET
723765 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -193 (0xffffff3f) THROTTLE2_SET
723765 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -218 (0xffffff26) THROTTLE1_SET
723765 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -226 (0xffffff1e) THROTTLE2_SET
723781 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -255 (0xffffff01) THROTTLE1_SET
723781 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -262 (0xfffffefa) THROTTLE2_SET
723828 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -292 (0xfffffedc) THROTTLE1_SET
723844 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -298 (0xfffffed6) THROTTLE2_SET
723844 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -365 (0xfffffe93) THROTTLE1_SET
723844 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -371 (0xfffffe8d) THROTTLE2_SET
723875 *** EVENT: Cntrl= 66093 (0x0001022d), Param= 0 (0x00000000) AP_AIRSPEED_ON
723890 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
723890 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
723906 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -413 (0xfffffe63) THROTTLE1_SET
723906 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -420 (0xfffffe5c) THROTTLE2_SET
723906 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -446 (0xfffffe42) THROTTLE1_SET
723906 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -452 (0xfffffe3c) THROTTLE2_SET
723906 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -482 (0xfffffe1e) THROTTLE1_SET
723922 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -488 (0xfffffe18) THROTTLE2_SET
723922 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -527 (0xfffffdf1) THROTTLE1_SET
723922 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -533 (0xfffffdeb) THROTTLE2_SET
723937 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -568 (0xfffffdc8) THROTTLE1_SET
723969 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -573 (0xfffffdc3) THROTTLE2_SET
723969 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -604 (0xfffffda4) THROTTLE1_SET
723969 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -610 (0xfffffd9e) THROTTLE2_SET
723984 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -661 (0xfffffd6b) THROTTLE1_SET
723984 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -666 (0xfffffd66) THROTTLE2_SET
723984 *** AXIS: Cntrl= 65820 (0x0001011c), Param= -701 (0xfffffd43) THROTTLE1_SET
724000 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -707 (0xfffffd3d) THROTTLE2_SET
...Are you using the same FSUIPC7.ini file? You could attach that and I'll check it for you.
Best way to make browser interface with FSUIPC?
in FSUIPC Support Pete Dowson Modules
Posted
Ok, thanks Paul. I'll update the installer for this version for the next release. I would appreciate some feedback on the current release though first, in case I need to make some other updates. Thanks,
John