John Dowson

No, I don't need to see your MSFS.bat file. As I said, I need to see your FSUIPC7.log, with those logging features activated. Also, as Pete said, please check that you do not have assignments to your joystick axes in MSFS if using FSUIPC to assign.

I just checked your details and they are fine. Make sure you are using the correct email address you registered with, which is jorge@soldano-deheza.com.ar and NOT jorge@soldano-deheza.com

Can you activate FSUIPC logging for Axes Controls and Events, produce a short(-ish) log file showing your problem (i.e. load your aircraft and taxi showing your issues, then close MFS/FSUIPC) and then attach that, together with your FSUIPC7.ini file and I will take a look. Something must have changed if it was working and now doesn't. Do you have any idea what could have changed? Your FSUIPC7.ini file is the one I need to see your assignments, not screenshots. John

All three components - Name, Email/Address, Key - must be exactly as specified in your SimMarket purchase email - best to copy and paste. if your details previously worked, they still will, so please try again.

I was just testing with the autosave and previous flight files, loaded from the File -> Load Flight option. Haven't looked at he offsets for this yet, but they use the same SimConnect load/save facilities.

@eyemack👍😎 And sorry, missed you and @Renoi71 who also reported this...

Maybe @nandrews and @Gualdemar can try this again with the latest MSFS update and see if this is still an issue. Please download the latest FSUIPC7 release first, v7.0.5. John

Note that I have released FSUIPC7 v7.0.5, built against the latest MSFS SDK, v0.10.0.0. So please download and try with this version. I have done some tests. It seems to be working - but only sometimes, it causes a CTD on other occasions. The Previous Flight file seems to load ok, but I have had varying success with other autosave files. I will continue testing, but please try and report back anything you find - success or otherwise.

I am very busy at the moment and do not have time for basic/beginner lua questions. Please just try things out for yourself. We provide plenty of documentation and examples. There are many basic lua tutorials on-line. I have already given you plenty of information to get you started. And of course that is the correct way - if the bit of software that is writing to those offsets is writing it as a 32 bit signed integer. If not, it may be writing it as a 16bit signed integer (as Pete said earlier), in which case you need to change that to "SW" and change the read functions for those offsets from readSD to readSW. You have to make sure that you are reading offsets as the same type/length as you write them.

That line of code is correct. Are you sure that your axis values are being written to the offsets correctly? Why not log the values before the conditional to see what they are, i.e. add the following line ipc.log("0x66F5=" .. val1 .. ", 0x66E1=" .. val2.. ", groundSpeed =" .. groundSpeed ) Also check that you are calling event.offset for those two offsets.

But thats just the function I gave you. I have still no idea what you are talking about. What do you mean by 'the "And" between 66E1 and 66F5 don't work'? What does 'don't work' actually mean? what is 'between'? What 'And'? You aren't making any sense to me.

But I don't understand what you mean by this either. Show me the code and highlight the line you are talking about.

What does this mean? What is an 'And function'? If a lua script doesn't work, activate logging for lua plugins and try and determine what the problem is from the log output.

Yea, that should be possible. I can provide you with a time-limited license for you to try if you like. Let me know - and what FS version you are using.

Hopefully! Please try and let us know - I have slow download speeds and probably won't get the update installed until tomorrow... The release note also mentions a fix for a crash in bush trips with Little Navmap - hopefully this will also fix with CTDS in bush trips (and others) with FSUIPC as well.... John

I've just taken a look at your profile ini, and the section names are wrong. The Profiles in Separate Files document states: Looking at your MD-8X.ini file, your section names are: [Axes.Maddog] [JoystickCalibration.Maddog] etc. When they should be just [Axes] [JoystickCalibration] etc Did you create these manually? How come the profile name is also different than the actual profile being used (even if it shouldn't be there)? Try removing those extra strings/appendage from your profile section names. Also, you should revise your profile substrings used in your FSUIPC6.ini file, as I previously suggested.

Thats the ini files - where's the FSUIPC6.log file?

yes:

The substring oprion is set but you aren't using it! You need to change youe profile sections, e.g. can be just and to etc. i.e. just specify a substring that matches all the variants - and no others! For your issue, I also need to see the profile of the aircraft you have loaded so that I can see the assignments there and if they match the loaded aircraft, so for this example I would need to see your MD-*X profile for the Maddog X. Also, you are using Linda, I can't really diagnose FSUIPC issues when using Linda. Can you disable for the next test - just rename your linda.lua (or ipcReady.lua if thats all it starts) by renaming temporarily. Also, update you logging and, for the time being, disable axes event logging and enable logging for buttons & keys and events. Then load an aircraft, press a button with an assignment, and show me the files again (your .ini, .log and profile.ini for the loaded aircraft). The logs you posted show your devices were recognised and acquired ok.

Is this just a general question (ie. not related to FSUIPC6)? And what is EZCA? I have not noticed such issues - but I haven't flown much in P3Dv5.1 for a while now...

First, you posted in the FAQ sub-forum, where it explicitly states: So you see the FSIUPC7 splash screen? Once started, FSUIPC7 resides in your system tray and should be opened from there. If you don't see the splash screen and FSUIPC7 is not in the system tray, try double clicking the FSUIPC7.exe to see if it starts. If not, and you get an error, then you may need to re-install the VC++ redistributables (see the README.txt file provided). If it starts, there may be an issue with you EXE.xml. If that is the case, please see the following post: John

But that won't work correctly as you are not setting a value for val1 when the function is fired for a change in offset 0x66F5 (and you are overwriting the input value. To simplify, you could just read each offset directly and not use the input parameter if this is confusing you: And why change from 0x66E5 to 0x66F5? Ots a good idea to group the user offsets you use consecutively, but its not a functional issue.

Ok, then if its connecting to the PC running FSUIPC, you don't need WideFS. Sorry, but I don't know how you would use an arduino connected via ethernet to the main FS PC. You probably need to write an FSUIPC client (using the SDK) to read the data you need from FSUIPC and then send that to your Arduino yourself.

How does your arduino talk to FSUIPC? And what is it connected to? If it talks to FSUIPC when connected to the PC which FSUIPC (and PROSIM) is running on, then it can talk to FSUIPC via WideFS when connected to a client PC running WideClient. Thats is what WideFS does/is, i.e. it allows FSUIPC clients to run on a networked PC separate to that of FSUIPC and the FS.

The functionality in this area should be the same between the different versions as nothing has changed. Are you saying this worked in previous versions but not in FSUIPC7? Why? It is good to report anything you find, to help other users. Just because, in this instance, I am not going to take any action (at the moment), it doesn't mean that such things shouldn't be reported. John