John Dowson

You can't add this manually - it is an automatically generated section. If its in the correct folder, I can't see how it can't be found. Can you attach your FSUIPC7.log, FSUIPC7.ini and also the G1000Events.evt event file you are using.

'Also' - Who else has this problem? Did you add the file when FSUIPC7 was already running? If so, you need to restart FSUIPC7 for the file to be picked-up. Can you also check your FSUIPC7.ini file - the event files found in your installation folder are listed under [EventFiles]. Check to see if they are listed there.

The DontLogThese ini parameter didn't seem to work. Did you add this to the ini after you had started FSUIPC7? Maybe move it to the first line after the section name (although this shouldn't make a difference). Can you also calibrate your steering tiller in the profile please - you currently don't have a calibration profile. Click the profile checkbox in the calibration tab and calibrate your steering axis there. Then, show me both files again. Check to see if you still have those LIGHT_POTENTIOMETER_SET and FUELSYSTEM_PUMP_SET events logged first - they shouldn't be there when using those DontLogThese options... Also, did you check that you didn't have any axis assignments in MSFS? The parameters to your rudder. Although not related to your issue, you should also change to the following settings in your [General] section: InitialStallTime=100 NormalStallTime=-2 The first setting will increase the time allowed for the initial connection and prevent retries (MSFS is quite slow to start!) and the second will instruct FSUIPC7 to only log a stalled connection and not re-connect. You can change this later if you get issues and need to re-connect, but when this is a positive value (and especially 1) this can cause many reconnects if/when your system is overloaded and can cause an MSFS CTD when simconnect runs out of connections.

Why? If assigning direct to FSUIPC calibration, you have to calibrate. Please re-calibrate your axis, also taking into account my previous comments (e.g. did you remove that strange delta setting)? So, please check your assignments and calibration and try again. If you still have your issue, then show me your log file (with the appropriate logging activated) as well as your FSUIPC7.ini file - always attach this when you attach a log file please, I need to see them together. You also have lots of superfluous events logged. Please add DontLogThese=67227,67192 to your FSUIPC7.ini profile section (i.e. under [Profile.Custom B787] if that is still what you are using). This should reduce the size of your log files.

There is no change in the new version w.r.t your issue, so it won't. However, check those assignemnts that I mentioned, especially the delta - correct that and try again. Probably a good idea to re-calibrate your steering tiller axis once you've changed the delta. Your calibration for this axis in your profile looks way different than the general calibration for this axis: SteeringTiller=-12873,2560,6144,11903 vs SteeringTiller=-32384,-512,7534,32648 Note the differences in the max/min. Your B787 calibration is only using a third of your axis range....maybe that, together with the delta, is your problem?

Yes, you did. But thats from v7.0.4, not v7.0.5, and you haven't activated the logging requested to show me your issue. Please re-read my posts and follow the instructions before posting again.

In your installation folder, the same place as your FSUIPC7.ini. Also, you seem to have two axes assigned to the steering tiller for your B787 profile, and one with a huge delta (as mentioned by Pete): 0=AR,5632,D,36,0,0,0 -{ DIRECT: SteeringTiller }- 1=AS,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }- Did you change that manually to 5632? Why? Try changing it back to 256, the default delta. And why assign two axes to the same control? Maybe remove one, if you don't need both.

Also, your FSUIPC7 version is out of date. Please update to v7.0.5 (released yesterday). Only the latest version is supported.

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?