John Dowson

The assignment index numbers in the ini have always started at 0 and have always been incremented by 1. Why would you want to increment by more than 1? Seems a strange thing to want to do. And if you are manually editing the ini, you can change the index numbers to any unique number within range.

Maybe also worth trying these lua scripts instead of SPAD: John

Well, as FSUIPC doesn't do anything with SPAD, it won't be an FSUIPC issue (although SPAD may talk to FSUIPC). But you should certainly be able to use the free SPAD version with FSUIPC, and I have done in the past (but over 5 years ago!). I have no recollection of how I set this up though... Do you have a link to download SPAD? Seems that it is no longer available at the link we provide(at http://fstools.weebly.com), and can't find it with google. Maybe also see https://www.prepar3d.com/forum/viewtopic.php?t=8356. John

That is 12 years old - way before my time! As I said, I will prevent FSUIPC from writing an entry with all 0's, but I do not know why this is being written occasionally, It should only write that entry if the console window is open, and the position/size is retrieved from windows. John

First, you posted in the wrong forum for FSUIPC support - you posted in the support forum for the .Net client dll. I have moved your post, but please take care post in the correct forum for support. What version of FSX are you using? i.e. what is 'Flight Simulator X-BR'? If that is the beta version (build 63003), please see: Although I would recommend not using that version.... Otherwise, please show me/attach your FSUIPC4 Install.log file.

License sent - sorry for the delay, I was on holiday. John

Also see:

I have not heard of this happening before, and this functionality has been around for many years. The ConsoleWindow entry should only ever be written if/when the console window is actually open, and not when any logging is activated. I don't know why it is adding that entry for you, but I guess I can not write the entry if the values are 0. John

Possibly - I will look into it. Maybe, I am not sure - FSUIPC just calls a windows API function to select/position the menu entry. I don't think its possible to force it to the top, but I will take a look when I can. Sorry, what do you mean by this - what 'increment' are you talking about here? You can use a simple lua script (using event.lvar, and just log the value in the handling function). I have been meaning to add specific support for lvar logging for quite a while, but have just not had time to do this yet. It will be added at some point, but I do not know when. John

The documentation is always a good place to start...from the README.txt: John

What do you mean? You do realize that I am on holiday: If this CTD is due to a bad weather file, then this is a known issue, has been known for 10+ years, and there is nothing that can be done about this in FSUIPC. It is the FSX API that FSUIPC uses to get the weather that is causing this issue. There are already hundreds of support requests in this issue, and the response from me (and Pete, before he retired) is always the same. Did you even try what I suggested: ? i.e. Did adding NoWeatherAtAll=Yes prevent the CTD? Your *.WX files will be in your Documents\Flight Simulator X Files folder (where your flights are stored), and the file "wxstationlist.bin" in your <user>\AppData\Roaming folder for FSX. You can always try searching for them, using something like Everything. John

I do not have this aircraft so cannot advise. You need to use the standard techniques for determining what control the aircraft is using - logging. First try logging for Axes Controls, open the logging console window (Log-> Open Console) and see if any axes control is logged when you move the throttle in the VC. If anything is logged, try using that. If nothing is logged, try logging Input Events. Again, with the logging console open, move the throttle in the VC and see if any Input Events are registered, and if so you can use those. But be aware that you cannot assign an axis to an Input Event directly, you have to assign to an FSUIPC offset and have a lua script that monitors the offset and sends the Input Event - I can help with this if needed. If no Input Events are logged, then the next step would be look into seeing if possible to control using lvars. John

Also see John

You should have tried the free license before purchasing, available at the top of this forum. Can you show me / attach your FSUIPC7.ini and FSUIPC7.log files. It is certainly not a good idea to randomly change things that you do not understand.... If your issue is with SkyDemon, have you tried contacting their support? I have been on holiday since last Thursday: As it states on the purchase page - NO REFUNDS. This is why I provide an extended trial license. John

I have not used the freeware SPAD version for many many years, and don't have this installed any more. I will download and take a look, but it will take me a few days before I can get around to this (just back off of holiday). I will update once I have investigated. In the mean-time, could you show me/attach your FSUIPC6.log and FSUIPC6.ini files. John

There may be an lvar - you need to log the lvars and check to see if one looks applicable - lvars are NOT logged with non-axis events. However, if it is a "click-spot", then you should look into using a mouse-macro - see the Mouse Macros section in the Advanced User guide. John

Then you are using FSUIPC7, and should have posted this in the FSUIPC7 sub-forum. II will move your post. Can you please show me/attach your FSUIPC7.ini and FSUIPC7.log files, the latter generated from a session where you experience the issue. John

It would, but there is no way to do this. Input Events are aircraft specific - I just call the sim to ask what Input Events are available, and get a list back, and there is no way to categorize the list returned. P.S. As Input Events are MSFS / FSUIPC7 only, I have moved your post to the FSUIPC7 / MSFS support sub-forum

Different aircraft use different controls/events. You can use the logging facilities in FSUIPC to see what an aircraft is using - for axes controls, just set logging for Axes Controls, open the logging console (Log -> Open Console) and see what is logged when you move the axis in the VC, then use that. Note also that for some aircraft there can be no controls/events that work, and you have to look into other methods of control, such as Input Events or Lvars. John

That is a SIOC error. Try SIOC support. You can post/attach your FSUIPC7.log file and I can take a look for any issues in FSUIPC7, but I cannot help with SIOC issues, sorry. John

Sorry. but I do not understand your question, and have no idea what SLC is. If you are having a problem installing the FSUIPC WASM module, then please show me your InstallFSUIPC7.log file, and also please show me your FSUIPC7.log file. Note also that if you just want to install the WASM for use with another product, you can download and install the WASM without installing FSUIPC7. The stand-alone WASM module is available here: FSUIPC WASM Module 1.0.4 John

As it states in the FSUIPC Lua Plug-ins document, lua filenames have a limit of 16 characters: Also, FSUIPC scans for valid lua files when oy is started and adds any found to a [LuaFiles] section of your FSUIPC6.ini file. There is no such section in your ini file and so no lua files have been detected. John

I can look into making these offsets writeable, but not sure when I will have time to look into this at the moment. For the time being, why not just use the provided FS controls: I can look into triggering those controls when the offset is written but it will be a week or two before I get time to look at this - I will update this thread once I have taken a look. John

As I said, everything needs to be ran at the same privilege level to connect, and always better to run as non admin - only run as admin if you have to, and of do run EVERYTHING as admin. Why don't you try the support forum for FSRealWX? P.S. I am on holiday now, back next Wednesday the 26th.

Don't think so - and I did ask the OP to check this in my first comment: Strange thing is it was all previously working, so not sure what, if anything, has changed...