John Dowson

You shouldn't need to run FSUIPC as admin, unless maybe you are also running MSFS as admin.... Check that you haven't installed FSUIPC in a windows protected folder (such as Program Files). You should install it in its own folder, outside of the MSFS folders and not under a windows protected folder.

Did you install the MobiFlight WASM module into your MSFS Community folder?

Yes, there is the announcements sub-forum: https://forum.simflight.com/forum/140-announcements/ I'll post there when the beta is ready to be released, and also create a topic in this forum for feedback.

Check to see if your FSUIPC7.ini file is being updated - that is where your assignments are held. It should be located in your FSUIPC7 installation folder, along with your FSUIPC7.log file. Do you see it there? If not, it could be that you installed in a windows protected folder. Try re-installing in a different location of that is the case. However, if you are using a registered version, it should be ok as the FSUIPC7.key file has been created, so I don't know why it wouldn't be able to create or update your FSUIPC7.ini file.

Do you have a steam or MS Store install of MSFS? All the desktop link does is display a splash screen and then start MSFS. You can skip this and start MSFS how you used to before you installed MSFS. Try that and see if MSFS starts and also FSUIPC7.

It is the free version that supports the reading/writing of values to the offset area, accessible by the provided SDKs. The major functionality that a license adds is device/controller assignments and access to the Lua library and interpreter functionality. Best to just download and try the free/unregistered version firt to see if that suits your needs. John

I don't know X-Sim, so not 100% sure what you are asking, but FSUIPC4 is the FSUIPC version for both FSX and FSX-SE.

The logs look ok now. They show a few full -ve tiller deflections and some positive (but only up tp 2/3rds). There are a few rudder axis controls so they must be either from an MSFS assignment or auto-rudder. How was the handling - do you get the same problem? If so, I'm not sure there's much that can be done. Is the handling better using Steering Set or better using FSUIPC's Steering Tiller control? You can switch back to the other control to compare. You could also assign your tiller axis to both the rudder and the steering tiller axis (and turn off auto-rudder) to see if that helps. When did you notice the change in the steering handling? Was this after (or before) the last MSFS update? I'll have a look at the B787 later today to see what works best for me and report back.

As well as what Pete says, you can also activate logging for Buttons & Keys and Events (non-axes controls) and check to see whats happening when you activate the button assigned to your Parking Brakes. You can see this in real-time if you open the log console window, and also attach your FSUIPC6.log file if/when you attach your FSUIPC6.ini.

You loaded a different model of the 787-10 that is not covered by your profile. Please change your '[Profile.Custom B787]' section to the following so that it will match ALL of you B787 variants: Can you also change to use the following parameters in the [General] section: InitialStallTime=125 NormalStallTime=-2 And, as I said, you have to be moving for the steering tiller to take affect (and be logged), so you need to apply some thrust and get moving before you move the tiller through its full axis. Try opening FSUIPC's console window and you can see what is being logged in real time. No, that shouldn't be necessary. Not sure what you mean by this. The tiller won't work if the aircraft speed is below the RudderBlendLowest parameter, which defaults to 1 (knot). Please check your logs before posting them again. We are after a log that shows the rudder axis controls with the parameters, to see if you are getting the full range. There is no point posting the log otherwise. And, as I also said, maybe also try assigning to the FS Steering Set control (and still calibrate in FSUIPC) to use the actual tiller axis rather than the rudder. Yes.

FSUIPC4 is for FSX, not MSFS. For MSFS (2020), you need FSUIPC7. If its FSX (or FSX-SE) that you are using, then your registration details are still valid. Make sure all three parts - name, email/address, key - are exactly as written in your SimMarket purchase email/account. John

Yes, if/when you upgrade and your license fails. It will still validate in the installer, but when you run FSUIPC you will find your assignments have gone as you will be unregistered. When that happens (and if i haven't PM'ed you a new license by then), just comment on this topic again to remind me. John

WifeFS7 is to allow FSUIPC clients to run on a separate PC to that of the FS, but not on a tablet. It runs on the client PC, not on the PC where your Flight Sim is running. It duplicates FSUIPC's class name, so that programs can talk to it as they do FSUIPC. You can run it on the same PC as the FS if you like (only useful to have button-screen functionality on the FS machine), but to do that you have to change the class name it uses via the ini.

Thee control numbers for events in event files are determined as follows: control number = 32768 + (event file index)*256 + event index number where event file index is the index number of the event file (in your FSUIPC7.ini, under [EventFiles]) and event index number is the idex number if the event in the event file. So, the first event in the first event file will have a control number of 32768, the second event 32769, first event in the second file as 33024. etc

Yes - its loaded but won't be added to the add-on menu (and init page displayed) until an aircraft is loaded and you are 'ready-to-fly'. John

That will be needed for the following and subsequent releases.

The mod creates that? Weird.... Why? And if thats automatic, why does that affect your assignments? Surely the mod isn't telling you how to assign or/and configure? Do you have any references for this? Does it help you configure your throttle in FSUIPC, and if so, how?

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.