John Dowson

Hi, all your assignments and controls are stored in your FSUIPC5.ini file (in your modules folder). Take a look at that file. The format of the entries is described in the FSUIPC5 manuals. Comments are added automatically so that you can see what your assignments are. If you are using the 'profiles in separate files' feature, then you will also have an ini file for each profile. If you are going to edit it, make sure you take a copy/backup first. Cheers, John

Yes it is a limitation, only 1-9, as indicated by the document: RunReady1=, RunReady2=, ... RunReady9=: These are identical to the RUN options above, except they are not actioned until WideClient is actually connected to WideServer. John

So you re-enabled controllers in FSX for this? Make sure controllers are disabled in FSX if you are assigning your axis in FSUIPC. To use the full functionality of these, you should look into using the SPAD (freeware - http://fstools.weebly.com/) or SPAD.next (payware - https://www.spadnext.com/home.html) drivers. I use the latter (with FSUIPC) and it works very well. Cheers, John

Hi Matthias, It will rescan your devices. Does it also start working when you click the switch in the VC after opening/closing FSUIPC? It does sound like an issue with your add-on LJ35. You could try logging non-axis events and button presses (from the FSUIPC logging tab). This may show if something different is being sent after the spoiler retract. Cheers, John

The controls are events provided by P3D, so you need to look into the P3D documentation (e.g. see 'SimConnect Name' column in https://www.prepar3d.com/SDKv4/sdk/references/variables/event_ids.html). The specific controls added by FSUIPC are documented in FSUIPC' documentation. For your magneto problem, can you try activating non-axis event logging as well as buttons and switches (from FSUIPC's logging tab), generate a log file going through the magneto positions up and down and show us the results. John

Hi Urs, your WideClient.ini file is not correct. There is no [Programs] section - thats for FSUIPC (or WideServer)! As Pete said, you want to be using RunReady, which takes the form RunReady1=.... and is located in the [User] section of your WideClient.ini (or the [WideServer] section in FSX). Please see the WideFS Technical guide. John

As Thomas says, please show.attach your ini file. Can you also activate button logging, as well as non-axis events, and attach your log file. Thanks, John

Hi CrazzMC, Are you sure its not just the Airline? If the state of the AI aircraft is 'Initialising' (128) or 'Sleeping' (129), then you will get just the 'Airline'. Note that you can also change the ATC id used using the TCASid parameter, which can be changed from FSUIPC's Miscellaneous tab - see the Advanced User Guide (p5). You can also try the attached lua script which will log all 96 ground/air slots for you - drop it into your modules folder and assign it to a key or button press. This gives output such as the following: John logAI.lua

PM means 'Private Message', you posted on a PUBLIC forum!

That key works here - you must be entering it incorrectly. I've send you an email with a key file to try (and instructions).

Hi Buzz, No, its not - or shouldn't be! Can you PM me you SimMarket purchase email (with your provided key) and I'll check it. John

You could also try ignoring that button by adding IgnoreThese=1.7 to your [Buttons] sections of your ini file.

The instructions to follow are in the FAQ section:

If you have a new issue, could you please start a new thread - your problem does not seem to be related to this threads title! More information is also needed - what version of FSUIPC are you using? What sim? How did you install on another computer - if you just copied across your ini file, this most likely won't work as your joystick ids (and GUIDs) will have changed. Please start a new thread with the above information, and also attached your ini, log and joyscan.csv files (all from your Modules folder). John

Thats very strange...I don't think its possible to have two copies of FSUIPC running... Maybe check (or post) your DLL.XML file (in your AppData\Roaming\Lockheed Martin\Prepar 3D vd folder) to make sure there is only one entry for FSUIPC5. Thats strange - it should be 5.152. I'll check and update - thanks for pointing this out. You can always get the latest versions from our download page over here on simflight: This all sounds very strange, especially if you have new issues and nothing has changed... Try removing FSUIPC completely and check P3D is working ok. To do this, rename your 'Modules' folder and remove the FSUIPC entry in the aformentioned DLL.XML file - this section: Save the file and restart P3D. If all is ok, download FSUIPC 5.152 (from the link above) and re-install. You don't have to register again - copy your key file from your old (renamed) Modules folder to the new one. You can also copy across your ini file if you have anything there you want to keep. Cheers, John

Hi Detlef, no problem. Looks like a nice piece of kit - lots to program to get that all connected - good luck! Cheers, John

Again, I have no idea what this means, sorry.... Does it matter? Make a backup of your registry and you can always revert back to it later if it causes issues. I'm sorry, but I don't understand what support you require. Please follow the instructions. If that doesn't work, then post the results here and we'll try to help. John P.S. You are hijacking a FAQ thread. If you have any issues, can you please start a new thread in the support forum (not the FAQ). If the support request requires a different solution to that posted in this FAQ entry, then I will update accordingly. I'll leave these comments in the FAQ entry for a while, but they will be deleted as they are really not appropriate to a FAQ entry. Thanks.

Hi Detlef, the second lua script does not end as you have an infinite loop, so the timer is never called. Try this instead: ipc.display("Timer event test") gCount = 10 ----------------------------------------------------- function MyTimer() gCount = gCount-1 ipc.display(gCount) end ------------------------- init ------------------------ event.timer(100, "MyTimer") Ok, then you don't need to auto-start. So, after starting a script with the 'L' key, you then wait for an 'L' key event? Sounds a strange thing to do, but ok if thats what you want.... The script needs to end/finish (not exit! That will kill the lua), then it will react on the events. It won't react to events if the script is still running (i.e. you are in an internal loop). There are various ways to achieve this, although the recommended way using FSUIPC is to use the provided ipc.get and ipc.set functions - see the lua library documentation. Cheers, John

So you haven't tried the fix mentioned? Sorry, I don't know what this means... John

If you choose to continue, does FSX crash? If so, does the fix mentioned in this FAQ post not work?

And do what with it? Why do you need FSUIPC for this? FSUIPC stores all data in memory at specific offsets - see the Offset Status document for a list of data available. John

Hi Detlef, how are you activating this lua? As you are using events, it should be activated from the [Auto] section of your ini file. However, this line ipc.exit() will cause your lua program to exit and no longer respond to events. You also have: event.key(TIC_MS, 86, 0, "KeyReceived") -- Key v (normally make screenshot) event.cancel("KeyReceived") where you are asking a function to be called on a keycode (of TIC_MS, which is not a valid keycode) with shifts of CTRL-ALT-TAB-APPS (=86...really?), and are then cancelling this event straight away, so it will never be called. Probably quite a few other mistakes - I haven't checked it all. I think you need to review the examples again, especially on events. Basically when you add an event (and don't cancel it or stop the lua!), the lua sits in the background waiting for the event, and then calls the appropriate function. Also, lua logging is your friend - try activating this to find errors and see what your lua is doing. Cheers, John P.S. You posted in the FAQ - I moved your post to the support forum - please post in this forum for all support requests,

Your macro file is not valid - you are missing the first line: [Macros] John

Hi Scott, you can use just the shift key only by modifying the key definition 6=N220,8,1005,2560,1005,2560 -{\|key: Press=BUTTON FLAG Toggle: Joy 10 Button 0, Release=BUTTON FLAG Toggle: Joy 10 Button 0 }- to 6=N16,9,1005,2560,1005,2560 -{\|key: Press=BUTTON FLAG Toggle: Joy 10 Button 0, Release=BUTTON FLAG Toggle: Joy 10 Button 0 }- It seems that 16 is the keycode for null, not 0 as specified in the documentation (which I will update). Cheers, John

Yes, that will be your problem! If you left-click the filename and hold for a second or so before releasing, you can change the filename and extension (or right-click and 'Rename'). You will have to confirm the change. Notepad++ is a good free source editor that a lot of people, including myself, use for this type of thing. Btw, your FSUIPC version is quite old now - the latest (and only supported) version is 5.152. please update at some point. Cheers, John P.S. Its a good idea to set the AutoAssignLetters ini parameter to Yes (or manually assign them - see the "Joy Letters" section of the User Guide, p24 in latest version). This will prevent possible problems if your USB device numbers change for some reason.