John Dowson

There is also a few issues in your log file: And, more worrying: Those are usually caused by a simconnect failure or crash.

I was asking. not saying! And I was also asking if it works in the vanilla A320 (i.e. the original, without the mod). Either way, you should check the axis events logged when working and compare when not. That should give you a hint as to where to look. And if it is working in the vanilla A320, but not in the mod, then you need to talk to the mod providers FIRST, as I have said several times now. There are also many FSUIPC users using the FBW A320 mods. I don't know why they can't assist you in this.....if you created a proper title you may get more response (i.e. something like 'Help with throttle assignment in A320 FBW mod' rather than 'throttle axis assignment problem'). I'm sorry but I can't check this in more detail at the moment as I have had to uninstall the FBW mods (and all community add-ons) for the time being, as they can interfere while I'm developing an add-on myself. I may take a look in a couple of dats if you aren't getting anywhere - please report back. John P.S. And, as I also said, I need to see full logs, not continuation logs, and also your FSUIPC7.ini file to see your assignments. If you post again, please include both.

I am sorry but I am having difficulty understanding you. Some punctuation would help. Are you using google translate? What have 'newspapers' got to do with anything? I think you are saying the mod works with default MSFS assignments, but not when assigning in FSUIPC. Is this the case? Can you please re-read my previous posts as you don't seem to be taking any notice of them. I still do not know what mod you are using. You haver not shown me any log files (with Axis logging activated). And I have saif various times, if it works in the vanilla A320 and not in the mod, you should first talk to FBW support. Have you trued the vanilla A320? Have you compared the log output of the vanilla A320 to the mod A320? I cannot help you if you are not providing me with the information I need, or explaining yourself in a clear manner, sorry.

Screenshota don't help me. I need to see your logs. But what is your actual issue? If the throttle is not working in one of the FBW mods, but is working in the vanilla A320, then your first port of call should be the FBW mod support, as I said, Did you do that? Nothing has changed in this area in 7.0.4 or 7.0.5. What has changed is the FBW mod, so your problem must lie there. Which mod are you using? Try producing two log files, one using the MSFS assignments (no axis assignments in FSUIPC), and one using the FSUIPC assignments (no assignments in MSFS) and then comnpare them. Are they using the same controls or different ones?

Event file names are independent of the WASM - its only the names of the events in the file that depend on the WASM. His problem was that MSFs wasn't running, and event files are only loaded once FSUIPC is connected yo MSFS.

Note also that as FSUIPC's Steering Tiller axis actually uses the rudder axis (for historic reasons). The actual Tiller axis it is probably more effective. You could try assigning to 'Send to FS as normal axis' and use Steering Set, and then calibrate.

Do you have MSFS running? FSUIPC7 has to be connected before it loads *.evt files.

For the final time DO NOT edit or change that section. FSUIPC writes that automatically depending upon what it finds in your installation folder. If it isn't there, FSUIPC hasn't found it. You CAN NOT MANUALLY ADD THIS. Of course. No surprises there. It won't be there as long as the file isn't being recognised, and when it is it will be added to your ini file, automatically. Ok - that shows that you have the extensions for know file types hidden. How can you tell that your event file has the .evt extension and not a .txt extension? Please configure your windows explorer to show the extension types (instructions at the end of the Installation and Registration guide if needed), then check the file name is correct.

When attaching logs, I need to see the full log, not a continuation log. I think I'm going to remove the continuation feature.... If you have issues/questions on assignments, also please include your FSUIPC7.ini file. If something is working in the vanilla A320 and not in one of the FBW mods, then you should initially ask on the FBW forums to see what has changed and if this is an error on there side before I look into anything. Not usre what this means. What do you mean by 'the axes work on command by default'? Do you mean the default MSFS assignment? What is it assigned to? What do you see in the FSUIPC log when assigning in MSFS? How does this differ from the log when assigning in FSUIPC? Are you assigning to the same control that MSFS uses or a different one? Is the control that MSFS uses available?

This really shouldn't happen and I don't know what could be causing this. Could you reboot, re-install the latest version and try again please. Ok, the second statement maybe slightly confusing. You CAN calibrate axis assigned in MSFS, although this is not recommended. I was going to remove this in MSFS as this may interfere if you calibrate in MSFS as well. The first part of the second statement is true - FSUIPC does not interfere by default. However, the second part should probably read 'you have to assign in the Axes Assignment first, or Calibrate in the Calibration page of assigning in MSFS. That's the way we recommend. You should also create empty profiles for your controllers in MSFS (except for mouse and keyboard).

Sorry, can you also activate Extras logging when you produce your log files. This will then log the in/ou after the slope adjustment on the tiller. Also apply some thrust so that you are moving as the tiller axis won't take effect when stationary.

Thanks for the info @Jetdriver50. @GBOULANGER Did you do this?

No, that wouldn't work as its now clear the the installer is determining the correct installation type. Ok, so it is working. The problem is that the installer can't create the EXE.xml file. Now you have manually created it, can you re-install to see if it now works. If not, you will have to manually create the file again (or save a copy somewhere before you re-install - don't move or delete it). I can only think that this is one of two things - a permissions issue or something strange in your registry and the LOCALAPPDATA environment setting is not being read properly, which is more likely. Either way, there's not much I can do about it, but I'd like to know if a re-install works now that the file has been created.

This has now been reported several times. I am not going to explain yet again what to do - find one of the other posts where this has been reported and follow the instructions. Also, please check for existing posts on an issue before creating a new topic. Are you saying that FSUIPC doesn't run when you double-click the exe? That sounds very strange indeed... Try downloading again and re-installing. If the issue persists, try uninstalling and re-installing the VC++ redistributables. Check the provided README.txt for instructions. John

I see you have changed to using signed words now. Did you verify that this is correct, using FSUIPCs offset monitoring, as suggested by Pete? If you have confirmed that it is indeed a signed word, then good - some progress... But you are making the same mistake again. A Signed word is two bytes, so if you have one at offset 0x66F5, it will cover 0x66F5-0x66F6 (2 bytes) inclusive, and the next should be at 0x66F7, and not 0x66F6. So your values are overwriting each other, which is most probably why you are seeing strange values. Please don't post should large (and useless) log extracts. You have gone way overboard with the logging. A single log line, or maybe two, would help you see things a lot clearer (and shorten the log considerably). Remove ALL your current log lines, and use something more like what I previously advised, something like (two dots is the string concatenation operator in lua, FYI) Why have you gone back to using event.timer instead of event.offset? Up to you of course, either will work.

Ok, thanks - I'll take a look at those in detail a bit later. The log looks a lot better - the DontLogThese took affect, so we also know your profile is being used. Could you provide me with one more log. Just load your aircraft, and move the steering tiller axis through its full range, forward and backwards. Then close down MSFS and attach that log. This will then show the full steering tiller range without too much logging from other activity. Sorry, I should have mentioned this previously. Thanks.

@Solito You posted your registration details, including your key!!!!!!! They have been visible now for over 7 hours. It states in MANY places to NOT make your key available publicly and violates the license agreement. I know what your registration details are from your purchase order number. You must see that posting such details allows them to be used by anybody? I can't stop that key now being used in the current released version, but I will add it to the banned list and it will no longer be valid in future releases. I will PM you a new key at some point (when I have time) - this time ONLY. Remind me if I forget...(i.e. post again in this topic) As for you issue, as I say your details are correct and work without an issue. I have had 2 other cases where this was resolved by uninstalling and re-installing the VC++ redistributables, so you could try that (instructions and link in the README.txt). Otherwise (or first), try manually creating an FSUIPC7.key file on your FSUIPC7 installation folder with the following content: replacing your key with the registration key from the email.

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.