davidk64

Thanks John. I checked the list of lvars and this one looks promising L:collective_grip I checked its value when grip fully twisted on and its 96. From here you list several steps: 1. "assign your axis to write its value to a free/spare FSUIPC offset" 2. "have a lua script that monitors the offset" 3. "calibrates the axis value" 4. "use this to set the lvar" I'm interested to try and follow these steps but I'm struggling to find how to do them in the documentation though I'm sure it's all there somewhere. Are you able to point me to the relevant sections or some tutorial online please?

How do I list the lvars please?

I've explained this all wrong! Let me start again please. The collective stick gets raised up and down and I have that assigned to the throttle axis in P3D which is working fine. The twist grip on the collective controls something else. This is what I'm trying to map to my joystick using FSUIPC. I tried mapping to the propellor axis within P3D and that didn't work. I've tried mapping to PROP_SET_PITCH in FSUIPC and also to Axis Propellor Set neither of which work. I don't feel there is anything else to try. I guess I hoped there was something I'd done wrong you might pick up. Please don't spend any more time on this - I'll just stick to using the mouse for the twist grip - I believe something in the vendor implementation is preventing the use of FSUIPC to map to the twist grip axis on the collective. Thanks for taking a look. P.S. I'll post on a helicopter forum and see if anybody succeeded in mapping to the twist axis back in the day. I can't be the first to try and do this 🙂

Hi John, my message has put you slightly wrong. I meant that mapping the joystick axis to throttle worked which demonstrated to me that the chosen axis wasn't the issue (I'm trying to use a slider for the stick twist). So at present I am unable to map the slider to the twist grip. I went back and logged what happens when I assign SET_PROP_PITCH to my joystick axis. Looking at the log first you'll see the result of interacting with the twist using the mouse then with my joystick axis. You'll notice with the mouse the zero parameter entries stop while the twist is engaged. In contrast they continue in addition to the entries generated by my using the joystick. So I wonder whether while I am using the joystick some vendor software is continuing to interact with P3D regarding the twist axis? I also tried Axis Propeller Set. I think you are going to say it's something weird about this vendor Heli that unfortunately FSUIPC can't help with alas 🙂 FSUIPC6.log

In P3D v5 with MILVIZ UH-1 helicopter. I enable logging of axis control and twist the collective grip. Looking at the log I think that corresponds to PROP_PITCH_SET. So I go into FSUIPC and assign an axis on my joystick to this variable but alas it doesn't work. If I instead assign the joystick axis to say throttle it works as expected raising and lowering the collective. Any thoughts on what I'm doing wrong please? FSUIPC6.log FSUIPC6.ini

Thanks John. I followed the instructions on creating mouse macros using the automated process and it worked a treat. FSUIPC6 is doing everything I need. I appreciate the support you provide for the product.

Thanks John, that may save a future user some time head scratching. Curiously while using the console window to get my switch panel working, I have had no repeat of this issue. I had the thought it was because I was just checking and unchecking the option to display logging in console and was not pressing the stop logging button. But when I tested this and tried to repeat the issue I couldn't! I am surrounded in mystery 🙂

I tried 0.5.1 first but no it didn't work either. I've managed to program all needed switch panel functionality for the Super Cub now so I think the use of the Lua scripts will do the job for me thanks. The nav lights switch was a funny one. When the plane loads the engine is off but the nav lights are on in the VC and external views. So, to get the switch panel in sync I ended up programming the switch press to turn the nav lights off and the release to turn them on! I wish I'd thought of doing so earlier as I spent an inordinate amount of time trying more fanciful combinations to get things in sync 🙂 If I was really keen, I guess I could try to install a VB6 development environment and debug the SPAD source code to see what is causing the error .... but since the Lua scripts are working, I'll get on with something else - like flying with Charlie Gulick!

Okay thanks for that. I have tried to implement the offset method. It might be working for the battery switch but I can't seem to get it out of sync to be sure! It's not working for nav light switch so not sure if I've coded it wrong? SuperCub.ini

Installing the Lua scripts seems to be working in so much as I can now press a button on the Saitek panel, and it registers in FSUIPC. One issue I'm having is that say I press the master battery switch to the on position, FSUIPC recognizes I have done so, and I can assign the simulation variable, say "Toggle Master Battery". But when I test it after closing FSUIPC I have to press the switch twice for every one toggle. For example, I press the panel switch on and the master battery switch is moved to on position in plane then to move the switch in plane to the off position I have to press the panel switch to the off position and then to the on position. If I go into FSUIPC with the panel switch in on position and press it down, then FSUIPC doesn't register the down position. Yet testing per the forum post for setting up these Lua scripts shows that FSUIPC does know about both positions.

Yes, by fluke I found that the download page works even though the home page doesn't! Download - Tools for Flight Simulator - Home of the SPAD (weebly.com)

I hope your break was good and thanks for taking a look. Attached log shows no mention of spad. I tried 3 methods, start P3D then start spad, start P3D open FSUIPC then start spad, start spad then start P3D. All give same error message. I fear it may be nothing to do with FSUIPC and something to do with my setup causing issues for spad. If you get it working that will confirm! FSUIPC6.ini FSUIPC6.log

After a lot of searching, I found the post!

I read in another post on the forum of a user having trouble seeing the console window and he found that there was an entry in the fsuipc6.ini file ConsoleWindow=0,0,0,0 Once deleted the problem went away. This post is to advise I have encountered the same issue. If I start logging, then stop logging and exit P3D then check the ini file the entry above gets added. A work around is to right click on the console entry in the taskbar and select "size" then use arrow keys to enlarge the window. The issue is repeatable for my setup but presumably 99.9% of users don't encounter it! I imagine trying to work out what in my environment is triggering the issue would be difficult and time consuming. It's hard to imagine the user wanting the console window to be 0 pixels square so maybe a check could be added to the code that creates this line alerting the user there is a problem with their environment?

In the P3D 3rd party Super Cub you can click on a screw head and it will toggle displaying a windscreen cover. I wondered whether I could map this action to a joystick button using FSUIPC. I started the log displaying non axis events but nothing shows up. Does this mean the display is done without there being a LVAR and I can't map it to a button?