John Dowson

Your logs show that FSUIPC7 is waiting for the WASM. Can you: 1. Check to see if the WASM is running. You need to enable the developer tools in MSFS to do this. Once you have enabled the MSFS developer tools, go to Debug -> Display WASM Debug menu, and then select the FSUIPC WASM module from the menu, and go to the Module Section tab. What do you see? Can you take a screenshot. It should look like this: Maybe also a screenshot of the Wasm Section tab. 2. Show me / attach your FSUIPC_WASM.log file. If you don't know where this is, take a look at the WASM section in the Advanced User guide. It may also be a good idea to set Debug level logging in the WASM (via the FSUIPC_WASM.ini file LogLevel entry), also explained in that section. John

This is not possible....or shouldn't be! Every device on a network needs its own unique IP address - if the IP addresses are not unique, how can anything connect?!!! And as I said, there was an error in your ini - did you correct this? Did you try with ServerName instead of ServerIPAddr?

They will be in your FSUIPC7 installation folder, on your client PC. They must be there - check also that you have not set Explorer to hide the extensions of known file types. Your ini file has a mistake: That should be ServerIPAddr. Also usually better to use ServerName unless you have allocated static IP addresses. As it says in the WideClient.log: John John

Do you know where I can download the FSX version? Found a version here: https://milviz.sharepoint.com/sites/GeneralProductSupport/Shared Documents/Forms/AllItems.aspx?id=%2Fsites%2FGeneralProductSupport%2FShared Documents%2FGeneral%2Finstallers%2Fv5%2FMV_UH1H_v2.210719.zip&parent=%2Fsites%2FGeneralProductSupport%2FShared Documents%2FGeneral%2Finstallers%2Fv5&p=true&ga=1 but that seems to only be for P3Dv4 and P3Dv5. This question was also recently asked here: https://www.avsim.com/forums/topic/682013-uh1-huey-redux-for-fsx/ John

Listing the lvars does just that - it lists all the local panel variables available. You then have to determine if any are relevant to the switch you are trying to control. You list the lvars two or three times, with the switch in different positions and see if any of the values change. Ok - and what switch are you looking at? As its freeware, I can install it and take a look, but it will take me a couple of days before I will have time to do this. I am just back after a couple of days away and need to catch-up on a few things first. John

There don't seem to be any issues with the latest update as far as I can see here. Can you please show me / attach your FSUIPC7.log file. John

So it doesn't work with only the MSFS assignment? That is very strange. The Nose Wheel Steering control is not available for external assignments - there is no such event in the SDK. Did you try Steering Set? Also try this without calibration first (i.e. remove any steering calibration). As I don't have this aircraft, I don't know. Try the Steering Set control. If that doesn't work, list/log input events to see if there are any that control the steering tiller. Also list the lvars and show me a log file.

Did you try either the Steering Set or Axis Steering Set axes (using 'Send to FS as normal axis')? FSUIPCs SteeringTiller axis is a special axis that should only be used in conjunction with the rudder and provides blending between the rudder and tiller (see the User guide). If you are using a separate Steering Tiller axis, you should try assigning to one of the MSFS-provided steering controls. If those don't work in the fenix, then you will need to look to see if any input events or lvars are available to control this axis. I don't have the fenix so cannot look into his for you, but if you log/list the available lvars and input events and anything looks applicable I can show you how to use theses. John

Glad you solved it. I think you got confused with the joyletter being 'C' and also with a C being used to indicate a Compound assignment, so you initial assignment 'PC...' needed to be changed to 'CP(-j2,b2)C...'... John

Your log file looks very strange... What state is MSFS2024 in when FSUIPC7 is started? Usually it is started while MSFS is still loading, but your log seems to indicate that an aircraft was already loaded and ready-to -fly. What happens if you exit FSUIPC7 and then restart it? Could you also please set WAPI Debug logging (Log->WAPI->Debug), and add offset logging (Log->Offsetts...) for offset 026D as U8. Then show me another log with that logging, and also exit an restart FSUIPC7 and show me a log file from that. John

There are issues with your registry and some entries need removing. Can you please do the following: 1. Run regedit and take a back-up of your registry 2. Unplug the following devices: VPC MongoosT-50CM3 VPC Control Panel 3 VPC Panel #2 VPC Rudder Pedal Joystick (Razer Huntsman V2 Analog) 3. Download and run (i.e. double-click) the attached .teg file: removeDevices.reg 4. Reboot. 5. Reconnect your devices. 7. Start FSUIPC7 (no need to run MSFS), check to see what devices are recognised and then exit. 8. If you still have issues, show me those files again (except the InstallFSUIPC7.log - that is not needed). John

It just scans the installation folder for .mcro files. You should never manually edit the [MacroFiles] section - unless you know what you are doing. If you deleted this section and is was automatically rebuild, the macro files will have been assigned new index numbers. And as you assignments are to the index numbers of the macro files, and not the files themselves, your current assignments to the macro files will be triggering the wrong macro in the macro files. You will therefore need to review your current assignments to macros and update them. John

I have no idea - please check the WideFS documentation on connection issue trouble shooting. If you still have issues after reading and trying the suggestions there, I would need to see your WideClient.ini and WideClient.log files, your WideServer.log and FSUIPC7.log files, and your FSUIPC7.ini file. you should attach these files. Most WideClient connection issues are due to firewall issues or using different workgroups, so at least check the workgroup and disable all firewalls (client, servewr and router) to test. Also try specifying the server name and protocol in your WideClient.ini - see the documentation. John

Can you please attach your FSUIPC6.ini file. John

What FS are you using, which aircraft and what switch?

i am currently travelling and will take a look tomorrow. John

You have a min value set as -7503, so any number less than this will give an out value of -16383. You need to calibrate correctly. I also don't understanbd why you have calibrated a max value of 3212. Basically you are only using a sma;; range of your throttle. I have no idea why your in value is so high in MSFS2024.

This sounds very strange, and I can't see hoe FSUIPC could affect any other non-fsuipc clients. You can start by showing me / attaching your FSUIPC7.log and FSUIPC7.ini files to see what they reveal. Which MSFS update provovked this? I am currently travelling but will review the latest update when I am back, which will bew tomorrow. John

I presume your question is regarding FSUIPC7 / MSFS - can you please post in the FSUIPC7 sub-forum. You keep posting in the main forum for some reason. I will again move your post. How you assign reversers depends on if using an axis or a button. Most reversers are controlled either by a reverser lever, which triggers a button, or using a throttle with a reverse zone that also triggers a button when pushed down into the reverse zone. To assign reversers on a reverse (lever) button, there are generally two methods: 1. Assign the reverse button press to the Throttle Decr control on repeat, and the release to Throttle Cut. If using multiple axis for different engines, then use the Throttle1/2/3/4 versions of these controls for individual engines. Then, when your throttle is at idle and you activate the reversers, throttle decrement controls will be sent to advance to full reverse thrust, and when you disengage reversers, the Throttle Cut will move back to idle. 2. If you want control of the amount of reverse thrust, then you can assign your reverser to the Throttle Reverse Thrust Toggle control, on both press and release and with no repeats. When you do this, activating the reverser (when throttle is in idle) will trigger/toggle reverse thrust mode, and you can then use/advance the throttle to increase reverse thrust. To switch back to normal thrust, you then reduce the throttle to idle reverse, and then turn of the reversers which will then toggle back to forward thrust mode. Note that is not possible to use this method for individual engines in the current release of FSUIPC7. This will be available in the next release, and is currently available in the latest beta release, which you can find in the following post: John

Yes, I know - but it does not work in the super version. I know that the lua + offset assignments work in the basic version of the 727. So I would like you to try to get that working (you can switch back to the _EX1 events afterwards). Once you have it working in the standard version, THEN you can see if it also works in the 'super' variant. I suspect so, but honestly have no idea as I still have not seen what input events this aircraft is using. Can you please show me your log and ini for this? As I said, it would be good if you can confirm it works in the standard version, as I know it does here, and then try the super variant. One step at a time.... Well, I think that you can get this to work in one way or another. But if you do not want to try, I will consider this closed. John

In the first log, you were using the aircraft 'Boeing B727-200 Condor | Retro | D-ABMI' - is that the 'super'? I suspect so, as this is listed under your 'Boeing 727 Super' profile. But that log shows nothing - no lvars or input events. The second log was for the aircraft 'Boeing 727-200RE Passenger - Cougar' - is this a 'super'? If so, it is not using your 'Boeing 727 Super' profile. That log shows lvars but no input events. I would like to see the input events available in the 'super' version, as well as the lvars. I understand - but it is better to ask if you don't understand something rather than ignore it. It is difficult to get to the bottom of an issue when my questions are ignored, and I am getting no feedback from the solutions I am providing. In what version? What was the issue? I know this works in the standard 727, so you should at least try to get it working there. Once that is working, you can then try in the 'super' version. If you have issues getting this to work in the standard version, please let me know, and attach your ini and log files. Your latest ini shows that the lua script I provided has not even been installed into your FSUIPC7 installation folder. John

I could possibly get the Super to look into the throttle, but before I do this I would like you to at least check and try what I have already said. i.e. check the input events for the 727 super and if the throttle ones exist, try the lua I provided. Also, it would be useful if you could attach another log generated when using the 727 super, and showing the input events (i.e. activate logging for Input Events) and the lvars (i.e. list the lvars). John

That is not what I asked... I asked if the Super has the same input events (or any input events for the throttle). If so, you should try that lua I provided - maybe modified if the input events have different names. I keep asking if you have tried this but you are not answering this question. If you want me to help you to set this up with FSUIPC, you need to try what i suggest and provide feedback. John

What is the '727-200 Super'? I only have the 727-200F, and that works with the lua script I provided - I did not check with normal assignments. If the Super variant has the input events ENGINE_Throttle_1/2/3, then you should be able to use that lua script. Have you tried this? John

Did you try the lua script I provided? That will move the throttles using the input events. I have updated to the latest version of this aircraft, and the script looks to be working to control the throttles and I can now move the aircraft. Seems to work just using the input events, so I have removed the code to also send the throttle set events in the attached lua, so please try this one. John FSS-727Throttle.lua