John Dowson

If writing to offset 0BC0 doesn't change the trim, then this implies that the aircraft does not respond to the Elevator Trim Set control/event. You could try with offset 0x2EA0 (Elevator Trim Position) instead. First monitor the offset and see if the values change when you adjust the trim, and if so you can try writing to that offset instead.. Otherwise, you could check if there are any lvars associated to the trim position.

We can download it correctly, just can't unzip it. However, I just tried with 7zip and it worked with that, just not with the windows default extraction program. John

Yes - I just tried and it tells me the (compressed) folder is empty. I think Pete must have made a mistake zipping it - can you check @Pete Dowson?

Offset 0x0BC0 will use the standard ELEVATOR TRIM SET control. What are the ' normal trim commands' that work for this aircraft? You should just ise the controls that work for that aircraft. Create a profile for the JF Bae 146 (check the 'profile specific?' check-box and assign your buttons to the controls that work for that aircraft. Try changing the trim and see what controls are logged - activate logging for Events and keep the console window open and see what is logged when you adjust the trim in the cockpit UI, and then assign to those (again, in a profile). You could also try logging the contents of offset 0x0BC0 (using FSUIPC's offset logging facilities) to see if this value changes (or not) when you do this, and what the values are for the various trim positions. John

FSUIPC's SteeringTiller control blends rudder and tiller operation, with the amount of blending defined by the MaxSteerSpeed ini parameter (and also the RudderBlendLowest ini parameter) - see the Advanced User guide P11 for details. You could try adjusting this MaxSteerSpeed parameter. However, if you do not want any rudder/tiller blending at all, change your assignment to 'Send to FS as normal axis' and use P3Ds steering tiller control, rather than the one provided by FSUIPC that does this blending. John

Ah, sorry - please ignore my post then...

I'm sorry but I cannot support MSFS, only FSUIPC7 with MSFS. I also use the steam version and don't really know the details of an MS store purchased version. I suggest you try the Asobo support forums. John

Are you sure that the event file is in your FSUIPC7 installation folder? Check that - if it is, it should also appear in the [EventFiles] section of your FSUIPC7.ini. Check that (but do not manually add it there -this section is managed by FSUIPC). If you don't know where your installation folder is, use the Open Installation Folder menu option from FSUIPC7's File menu. The events should appear at the top of the control menu drop-downs, preceded by a colon ':'. Note also that there is no need to use event files any more, as all these events can now be handled by presets. Check the MF HubHob resource (https://hubhop.mobiflight.com/) for the AP disconnect for the aircraft you are using. For the FBW A320, it is probably Autopilot_Disconnect_Push which you can assign to as Preset: Autopilot Disconnect Push without the need to use event files. John

Can you attach your FSUIPC4 install.log please. Looks like you are running a steam version - have you installed the latest updates (not the latest beta)? The latest (non-beta) should be: fsx.exe version = 10.0.62615.0 whereas you are using: fsx.exe version = 10.0.62607.0 However, I think you should be ok if your version includes SP1, but you may as well update to the latest (non-beta) version of FSX, if possible. John

Is this the WideClient.exe in the WideFS6 release? If so, that message is strange... There should be a WideClient that is compatible with windows XP (we think!). Pete will take a look and possibly post you a version to try - we cannot verify this here as neither of us have a win XP system anymore. John Later: Pete has amended his previous post with a version for you to try...

Is this a question about FSUIPC? If so, you have posted in the wrong forum (Feel There Airplanes) - please post in the FSUIPC (or FSUIPC7 forum) for FSUIPC support. You also don't say which Honeycomb product - the Alpha yoke or Bravo throttle? For the latter, I have already posted some basic assignements for this controller in this post: John

Click on the order number and that should show you the order details, including your registration details. You should also have received an email with these details to the email address used. John

Please use the attached license file - this contains both an FSUIPC7 and a WIDEFS7 license valid until 30th May. John FSUIPC7.key

No problem. Thanks, John

You can assign an axis to up to 4 separate controls - that is why there are four controls drop-down menus with check-coxes to activate them. Just activate the second control menu and select RightBrake there. John

I do not know what you mean by FSUIPC6a. The latest installer can always be downloaded from http://www.fsuipc.com and from the Download links -> Updated Modules section in this forum: John

Is this your MSFS Community folder: C:\Users\andre\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\ ? If so, can you check the FSUIPC WASM manifest file: C:\Users\andre\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsuipc-lvar-module\modules\manifest.json It should look like this: { "dependencies": [], "content_type": "MISC", "title": "FSUIPC7 WASM Event Module", "manufacturer": "John L. Dowson", "creator": "John L. Dowson", "package_version": "0.5.8", "minimum_game_version": "12.13.0", "release_notes": { "neutral": { "LastUpdate": "11/04/2022", "OlderHistory": "" } } } If it doesn't look like that, try downloading 7.3.3 again and re-installing. Maybe I updated this after the initial release - was a while ago now and can't remember... John

This was added in v7.3.0 and is included in the latest offset documentation: John

This issue is caused by bulk writing to an offset area when some of the offsets are not in the offset table. ProSim is bulk writing the payload data including the position data, which don't exist in the (internal) offset table for P3D. This error was introduced in 6.1.8. This should be fixed in the attached version, v6.1.9a, if you would like to try: FSUIPC6.dll John

Try moving the throttle in the UI to see what throttle controls it is using - activate logging for axis controls (in FSUIPC) and open the logging console, and see what, if anything, is logged when you move the throttle. Also, check to see if there is any type of throttle configuration necessary for the aircraft (in the aircraft documentation) - some MSFS aircraft require this (e.g. the FBW A320). Otherwise, try asking on Just Flight support or check their forums. John

Only the latest version of FSUIPC is supported. v6.0.11 is quite old now - please update to the latest version before requesting support, which is v6.1.8. Be aware that you also need to run P3D at least once after installation, before you install FSUIPC6. John

Your ini looks ok - there are no assignments to any axes. Have you checked your assignments in P3D? Its a good idea to disable controllers in P3D completely as it can re-assign your controllers if you don't do this. John

Yes, sorry - didn't re-read the whole thread... If your old PC is 32-bit, you will need to run the WideFS6 version of WideClient, and a license for WideFS7 on the server PC. I'll see if I can generate you a time-limited license for WideFS7, but this will be tomorrow at the earliest. John

If the loaded aircraft is using a profile specific Axis section, then it ONLY uses the aircraft specific axis section and you cannot create/modify/delete general axis settings with such an aircraft loaded. Either load an aircraft that is not using a profile, or remove the aircraft from the profile by editing the ini. I am not sure what you mean by ' I will/may loose my Go-Flight modules as well.;', but you can remove aircraft from a profile and still leave the profile settings intact. However, as you are using completely new hardware on your new PC, I don't think it is worth keeping any of your existing settings to any device - except maybe key assignments. It is always better to re-do your assignments for new controllers.

What do you need WideFS7 for? As FSUIPC7 can now be ran on a client PC, this could possibly be used instead, so I would suggest you try this first. Details on how to use FSUIPC7 on a client PC are in the Advanced User guide, Appendix 4 on page 64. John