John Dowson

First, you posted in the main FSUIPC support forum. As it says in the release note and in the README.txt provided with FSUIPC7-Beta, there is a dedicated sub-forum for FSUIPC7-beta/MSFS. I have moved your post for you. And if you had checked this sub-forum, you would have seen that this problem has been reported many times. It is an issue with SimConnect that is known and will be addressed in the next patch release of MSFS. Please see John

Both FSUIPC4 and WideFS7 require a new license, available from SimMarket. John

This may be helpful: https://myhomecockpit.de/index.php/en/?view=article&id=56

Not sure what you mean by 'FSUIPC offset', but if you want to assign a button to a PMDG 'custom control', then you need to select the '<custom Control> action from the 'Control sent when button pressed' drop-down menu (in the FSUIPC assignments dialog). You will then be presented with a dialog to enter the control number.

Download the latest version and run the installer. You can get it from www.fsuipc.com. No need to uninstall first. Note that 5.155 contained a fix for the offset mapping for the NGXu (and 5.156 and update for the PMDG 747), so you should update.

Please see the document entitled Offset Mapping for PMDG 737NGX and 737NGXu which is installed with FSUIPC. There are also many posts on using FSUIPC with PMDG aircraft. If you have any issues, try searching for previous posts first. Also, your FSUIPC version is out of date (5.152). Please update to the latest version, 5.157. John

But why have you installed FSUIPC if you only need MakeRunways? They are different programs. If you don't need FSUIPC, uninstall it and download MakeRunways instead. Also, the schiratti sight is no longer used. You should go directly to www.fsuipc.com to download MakeRunways.

I can only help you with FSUIPC, not PRO_ATC/X. Yes, that is how it is installed. What does this mean? What 'thing' can you not get to work? If you can be a little clearer on what you are actually trying to do and what your problems are. If this is related to PRO_ATC, you really need their support forums. The title of you post also mentions MakeRunways. Are you trying to use this? Have you downloaded and installed it? Have you checked the provided manual? John P.S. You posted in the sub-forum for the .net client dll. I have moved your post for you.

Simulator vartables are distinct from lvars (which are variables defined in/by an individual aircraft, not the simulator). They are part of the SimConnect API, as are the events. Please see the SimConnect API documentation for a list of the events and simulator variables provided by the sim. FSUIPC uses both events and simulator variables. It can also use lvars (but knowns nothing about them - they are aircraft dependent). If you look at the offset documentation provided by FSUIPC, it tells you whether and event or a simulator variable is used, but really you do not need to know this as an end user.

Sorry, but why would you want to run WideClient in a VM on the same machine as FSUIPC? You can just run it in the same OS as FSUIPC (by using the ClassInstance ini parameter - see the WideFS Technical guide for details). Anyway, have you tried setting the Protocol And ServerName (or ServerAddress) ini parameters? Btw, for future reference, attaching files is preferable to screenshots of their contents.

What sim & version of FSUIPC are you using?

Yes, its the time FSUIPC has been running in milliseconds. Yes, its defined in SimConnect and is the string name of an event. Not sure where the FSX SimConnect documentation is (maybe installed with FSX?), but the P3Dv3 documentation ids here and it should be pretty similar: http://www.prepar3d.com/SDKv3/LearningCenter/utilities/variables/event_ids.html Yes, they are the same. However, note that not all controls are from the FS. Some are added by FSUIPC and may operate using simulator variables rather than controls. Yes, that is the usual way to find out what a UI control uses which you can then assign to a button, switch or keypress. John

Sorry, forgot to update the last entry, which should be: 7=PA,19,C66704,0 -{APU_STARTER}-

There is something wrong with your WideFS registration details. Make sure that you haven't included the '<' & '>' characters - there are there only to indicate the parameter that needs to be replaced. Check your details are correct, but if you cannot get this to work please PM me your FSUIPC7.key file and WideFS7 order details (date and order number) and I'll check them. Please DO NOT post them publicly. Make sure this is also a WideFS7 registration - you cannot use a WideFS6 registration with FSUIPC7. Well, you can add them but there are only 7 assignments, like I said. You also have no profiles yet created. To keep your assignments, add the following to your [Buttons] section: 1=RA,28,K113,8 -{Key press: F2}- 2=UA,28,K113,8 -{Key press: F2}- 3=RA,30,C1061,0 -{engine 1 autostart}- 4=UA,30,C1062,0 -{engine 2 autostart}- 5=RA,31,C1063,0 -{engine 3 autostart}- 6=UA,31,C1064,0 -{engine 4 autostart}- 7=P2,19,C66704,0 -{APU_STARTER}- I'm not sure why your previous log didn't like the engine autostart assignments (the comment for these assignments was empty). I've checked and those are still available (or should be) in FSUIPC7. Try them, and let me know if they are working still please, and if they are recognised in your ini (i.e. the correct comment is still there when the ini is re-written). Thanks, John

Hi Kenji, you say But also: So you assignments are still in the ini file but are not working? If so, could it be that new ids have been assigned to your joystick devices? Are you using the 'JoyLetters' facility (which will prevent assignments being lost if your joystick ids change for any reason, such as re-connecting a device to a different USB port). Maybe you can post you .ini and .log files and I'll take a look. Also make sure that you have power management turned off in your USB hubs, as otherwise windows may be putting your devices to sleep. John

Ok, good - glad it's now working. John

Yes, sorry - I shouldn't have removed that!

You only have 6 button assignments (4 of which look to be to controls that no longer exist) and no axis assignments, all to your 'C' device, which is your "Throttle - HOTAS Warthog" and is missing (i.e. not connected). Looks like this may be due to a GUID change. There is also an extra rudder device 'TPR T.Pendular Rudder' which is not connected. I think you would be better off removing your current assignments and starting again.To do this, replace your current [JoyNames] section with: [JoyNames] AutoAssignLetters=Yes and your [Buttons] section with: [Buttons] PollInterval=25 ButtonRepeat=20,10 Then start MSFS/FSUIPC7 and see if you can see all your devices. If you can't, then send me the new FSUIPC7.ini, FSUIPC7,log and FSUIPC7.JoyScan.csv files. If you would like to use your old settings from your FSUIPC4 installation, first do the above to check all your devices are recognised and assignable, and send me those files, but also send me your old FSUIPC4.ini file and I'll let you know what you can do to copy your assignments across. John

You can try this which should just register buttons 32-39. Don't forget to update the Vendor & Product variables. I've not tested this (no time, sorry!). John HidButtons32-39.lua

Can you attach your .ini, .log and .Joyscan.csv files and I'll take a look - they will be in your FSUIPC installation folder.

Sure. You can remove the axis processing stuff (and the logging if you don't need that), and only write the buttons you need here: ipc.writeUD(0x3340 + ((i-1) * 4), buttons) However, buttons are written 32 at a time (8 x 32 but words). You can ignore the first 32 buttons by not writing there when i=0, or just write buttons 32-64 when i=1. Try modifying yourself, but if you have any problems I can take a look tomorrow for you.

You should read the release note (or the README.txt that is in the FSUIPC7.zip) which contains this: John

I'm not sure yet, but its not such a big issue now FSUIPC is an exe rather than a dll. You can just run it either before or after you start MSFS. I'm still waiting for details on how to start a program automatically when the sim starts. Once that is clear, I'll look into providing an installer. For future reference, all questions/topics on FSUIPC7/MSFS should go to the dedicated sub-forum for FSUIPC7-beta/MSFS. I'll move this post there for you. John

It should be [Auto]1=Lua HidDemo That should auto-run the script. The virtual buttons should then be assignable in the UI. John

As I have already said, your version is not supported. Please update. John