John Dowson

You posted your key!!!!!!!!!! I said, DO NOT POST YOUR KEY!!! If you do that again. your key will be blocked as posting a key publicly is a violation of the license conditions. I have deleted your message. I've sent you a PM showing that your registration is valid. I really don't understand what your problem is as you are providing no information except that 'my key is not valid', which it obviously is.

Did you do as I said? What happens after you click the 'Register' button? You should get a pop-up either saying that your registration is valid or not - what did it say? If it said it was invalid, then you entered your details incorrectly. I have validated them here and they are fine.

Your registration details work just fine here. Please double check that you are entering them correctly - as I said, best to copy/paste, and make sure you click the 'Register' button.

Sorry, what does this mean - v4 or v5? what is '14'? An FSUIPC6 key is valid for FSUIPC6, not FSUIPC5. You must use the details EXACTLY as specified in your SimMarket account/purchase email. Try copying and pasting the details from there. If you still have issues, let me know your order number and purchase date and I will check it here. DO NOT POST YOUR key!!! John

It seems that the events MSFS uses to control the avionics individually have not been exposed through SimConnect. Activating them via the UI (or via an assignment in MSFS) shows no associated event/control. I can ask if its possible to add these to the SDK. For now, you would have to use the Avionics Master Set.

Hi Rod, the individual controls are no longer present in MSFS - well, in the SDK documentation. I'll activate them here locally to see if they work, and if so I'll report back and add them back in for the next release. I've just taken a look at the C172 and it looks like the Toggle Avionics Master has no affect. However, the Avionics Master Set control works. You can use this with a parameter of 1 to turn both avionic systems on, and 0 to turn them off. John

If you want to assign an action to a button, you would use the drop-down 'control' menu to assign the action there. Whether this action is then implemented via an event/control or via updating a simvar is not particularly important. Usually there are various methods of implementing a function. If you had the choice of using an offset or sending a control, then the control method would be preferred - the offset method may use the same control/event in the background, so using the control directly would be (slightly) more efficient. Note I will be removing those 'Ok-SimC', etc status from the document at some point as I think they are confusing and unnecessary for most users. It would be better to just say if read/write wee working or not (or unknown).

The distinction is technical and is related to the SimConnect API - and not really relevant to users of FSUIPC, so I wouldn't worry about this too much. SimConnect provides both simulator variables that you can read and sometimes write to (not all variables are writable), as well as 'events' (or controls) that perform specific actions. FSUIPC uses both methods.

PMDG usually implement their own controls for these type of things. Are you sure this was working for your PMDG aircraft in FSX? For many PMDG controls, you have to use their custom controls. This is explained somewhere in their SDK. This also may be helpful: https://myhomecockpit.de/index.php/en/?view=article&id=56 John

What aircraft are you using? Just tried it in the Maule and it seems to work ok there. If its an add-on aircraft, standard controls may not work. You could try try AP_MASTER to see if that works, but that will toggle on/off. However, if that works, you can probably add an offset-check condition to only turn it off via the button (if you do not want the toggle functionality). Otherwise, turn on FSUIPC event logging, switch the autopilot on and then off in the UI and see what events are logged. Cheers, John

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