Jump to content
The simFlight Network Forums

No HID device through LUA in Prepar 3D


Recommended Posts

Hi,

 

I have my own modules known as HID devices to the PC. One of them has rotary encoders attached to it and sends the information as a HID report. This report is caught by a LUA script within the modules folder, interpreted and passed on to FSUIPC offsets (NAV1, COM1, AP heading, etc.). This works fine with my FSX installed on my home PC.

 

However, on the same PC I have an incarnation of Prepar3D and also on my laptop. Both do not reckognize the HID device (the PC does)! It is not listed in the log files. Other LUA scripts (from the samples) folder are reckognized neither.

 

My Prepar3D is academic version 2.2.10438 and FSUIPC is registered version 4.934.

 

On my office PC I have a FSX also, here the HID is listed in the log file, but no reaction is visible (i.e. thru ipc.display(...)).

 

Any idea?

 

Many thanks for your replies,

 

Detlef

Link to post
Share on other sites

However, on the same PC I have an incarnation of Prepar3D and also on my laptop. Both do not reckognize the HID device (the PC does)! It is not listed in the log files. Other LUA scripts (from the samples) folder are reckognized neither.

 

HID devices aren't necessarily listed in the Log file. Why should they be?

 

So, is the problem not specifically anything to do with HID, but only that no Lua files placed in the P3D modules folder are recognised -- ie not listed in the [LuaFiles] section of the FSUIPC4.INI file?

 

On my office PC I have a FSX also, here the HID is listed in the log file

 

 

In what way "logged"? FSUIPC does not log all HID devices. My HidScanner program does. Can you explain what you mean there please?

 

Pete

Link to post
Share on other sites

 

 

In what way "logged"? FSUIPC does not log all HID devices. My HidScanner program does. Can you explain what you mean there please?

 

They were, I swear! However, during my efforts to get the script running, they disappeared and I forgot to document this ...

There were 3 HID devices listed with full information - sorry I can't show it any more.

 

 

 

... ie not listed in the [LuaFiles] section of the FSUIPC4.INI file?

 

They ARE listed in the INI file. And that's why I am so astonished that they do not show any action. As a test, I put DISPLAY VALS.LUA into the modules folder and expect to see some variables to show up in the FS window (which works on the one "good" FSX implementation), but there is nothing with Prepar3D and the other FSX.

 

Detlef

Link to post
Share on other sites

They were, I swear! However, during my efforts to get the script running, they disappeared and I forgot to document this ...

There were 3 HID devices listed with full information - sorry I can't show it any more.

 

Well, by default FSUIPC will, if GFDev.DLL is installed, load any GoFlight devices it sees, but not all HID devices -- else everyone's logs would show keyboards, mice and cameras as well as all joysticks as HID devices. Just run HidScanner to see what it would see.

 

Certain types of HID devices can be logged with a debugging option. You have to set

 

Debug=Please

LogExtras=512

 

into the [General] section of the INI file.

 

They ARE listed in the INI file. And that's why I am so astonished that they do not show any action. As a test, I put DISPLAY VALS.LUA into the modules folder and expect to see some variables to show up in the FS window (which works on the one "good" FSX implementation), but there is nothing with Prepar3D and the other FSX.

 

 
Just placing a Lua file in the Modules folder only lists it in the FSUIPC4.INI file, in the [LuaFiles] section. It won't run it. Only ipcInit.lua and ipcReady.lua are auto run unless you have appropriate entries in an [Auto] section, or assign a button or key to run them.

 

Without some more information, like an explanation of your actual steps and some logs and INI files to show, I really can't help. There is absolutely no difference in FSUIPC or Lua between FSX and P3D nor with different PCs. Try the HID logging I just mentioned (add those lines BEFORE running FS/P3D), and also enable button/key logging so I can see the Lua file being started.

 

Pete

Link to post
Share on other sites

Thanks Pete,

 

everything works fine now. The "Debug=Please" did the job: My HID device (and others) are visible in the log again.

I use an ipcReady.lua for starting my script now with success. I was misled by my one FSX implementation which starts my script even without an [Auto] entry nor an ipcInit/ipcReady script!

 

Detlef

Link to post
Share on other sites

everything works fine now. The "Debug=Please" did the job: My HID device (and others) are visible in the log again.

 

Well, that's all it would do -- Debug=Please simply enables more logging options, it doesn't change the FSUIPC behaviour.

 

I use an ipcReady.lua for starting my script now with success. I was misled by my one FSX implementation which starts my script even without an [Auto] entry nor an ipcInit/ipcReady script!

 

Without those entries the only other ways of auto-starting Lua plug-ins are:

 

1. Assigning a button or keypress to "Lua <name>" in the drop-downs, and having another Lua or initial button action sending the right button or keypress, or

2. Having a program running which starts the Lua via offsets provided to do this.

 

Maybe one of those was previously in use?

 

Glad it's sorted now.

 

Pete

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.