John Dowson

You can download all versions of FSUIPC from https://fsuipc.com/. Your license details will be available from your SimMarket account - there is no need to re-purchase.

Of course you can move your Community folder anywhere, The FS Installation location in MSFS2020 (and MSFS2024) held in offset 0x3E00 is the InstalledPackagesPath value from the usercfg.opt file. Why don't you just take a look at it?

Well, that thread is this thread, and that post is for setting the trim on keys, not buttons. But you can assign your buttons to those controls - that is basically the same assignments you are using for the trim wheel (virtual) buttons).

It is not confusing FSUIPC7. it is confusing MSFS. Offset 0x3C00 is populated from the path received in the 'AircraftLoaded' system event, If it is wrong for variants, then it should be reported to MSFS. I can take a look next week to see if I see the same issue and if so will report this, but I don't think there is much else I can do. Cheers, John

The Community folder should be under 'Flight Simulator installation' folder held in offset 0x3E00,

But I just don't understand why you are posting at all... There ini file is there - you attached it, and it is the one with the type 'Configuration Settings'. The log file is there, and with the type 'Text Document'. You cannot see the extension because you have Explorer set to 'Hide extensions of known file types', If you want to see the extensions, then uncheck this option. This is all documented. This topic of this post is 'Shouldn't I have an .ini file?'. The answer is yes - and you do. It is first created when you run FSUIPC7. I really have nothing more to say on this topic so I am closing/locking it now. Please consult both the documentation and these user forums for any issues before posting,

You have controllers set to on in P3D: If assigning in P3D, you should disable controllers in P3D. Your log file only shows FLAPS_SET and AXIS_FLAPS_SET controls (and custom control 85637) - it does not show any of the PMDG flaps custom controls. And the parameters to these controls look to be setting different positions.... So, please disable controllers in P3D (or at least remove any assignments to your flaps lever/axis) and try again, and attach the new log as well as your latest FSUIPC5.ini file. The one you posted before doesn't look quite right - most of the JoystickCalibration ini parameters are missing for some reason.... Can you also please set logging for Buttons & Keys - maybe be necessary to see the range controls being sent...

Does FSUIPC7 run ok? Can you add assignments, and when you run FSUIPC7 the next time are they still available (i.e. have been preserved/saved)? If so, you have no issues and there must be a FSUIPC7.ini and FSUIPC7.log file. If you have any issues, please report them and show me / attach your InstallFSUIPC7.log. If the log and ini files are generated, you can also attach them (if you have issues). If they are not generated, then try running as admin. If they are then generated, it will be a permissions issue on the folder that you installed into.

Did you read the documentation? I am sorry but I provide documentation so that I don't have to answer such questions - I even told you where to look... From the documentation: Your image shows that this is still checked. Before you post here, please: - check the documentation, - search these forums to see if your question has already been answered

See https://devsupport.flightsimulator.com/t/simconnect-requestsystemstate-aircraftloaded-returns-partial-path-of-aircraft-cfg/9041/6 John

Do you mean in offset 0x3C00? What is the value in that offset, and which aircraft are you using? Could you add logging for that offset and show me the FSUIPC7.log file. Note that this should be the full path name but sometimes its a relative path (reported to Asobo several years ago, but I haven't checked this for a while). This also may not ne available/correct for encrypted aircraft, Yes, as the documentation says for this offset: ICAO Designator: Read from aircraft.cfg file (only available when 0x3C00 contains the full path to this file) So it looks like MSFS is just not returning the full path of the aircraft,cfg file for the aircraft you are using. Its even worder in MSFS2024 now aircraft are streamed... Cheers, John

No - is there a simvar (or anything else) that holds this information?

No - it is the same application for both versions. This is created the first time you run FSUIPC7. You have no FSUIPC7.log file either, so it looks like it hasn't been ran yet. But you also need to change your Explorer settings to see the extensions of these files - please see the Addendum on the last page of the Installation and Registration guide.

You shouldn't need an email with https://filetransfer.io/ - select the 'share as link' option and post the link.

Then its not off at all. There are various versions of this script available, for different devices The one included in the Example Lua Plugins.zip is the original that is provided as an example and will need to be edited - it is for a GoFlight RP48 by default and handles 4 rotaries. The one on the post I referenced is specifically for the two rotaries in the Honeycomb Bravo.

Ok, so that is why that is controlling the trim. Delete that assignment. You are using the wrong Rotaries.lua script. You need to use the one in that post I mentioned, which has been adapted for Bravo. Please check files before using them! The first lines of the file you were using would have told toy something wasn't right: Here is the correct file (the same one as in that post I referenced):Rotaries.lua John

Please show me / attach your FSUIPC7.ini file as well as the Rotaries.lua fille you are using. The furthest left is the speed brake, no? And as that is an axis, it is very perplexing that this is triggering button assignments...I suspect it is assigned as an axis in MSFS... What do you see in both the FSUIPC' Axes and Button assignment panels when you move both the trim wheel and that axis? Are the virtual buttons recognized on the axes and not the trim wheel? I would like to know if you see those button offset assignments in FSUIPC when turning the trim wheel or using the left axis, or in neither. And please double-check your assignments in MSFS2024. You need to check both in the general and aircraft-specific sections - this is causing a lot of issues for people....

Its DontLogThese. i.e. under [General] section: DontLogThese=66485,69000-70999,66503,66504,66587 If it didn't work, you did do something wrong - did you check the Advanced User guide on this parameter? It shouldn't be that large. Turn off all logging in FSUIPC and restart P3D so FSUIPC starts with no specific logging. Select and load your aircraft on the runway and ready-to-fly. Then, open FSUIPC and set the logging for Axes Controls and Events. Then move your flaps leaver through the ranges and back again, then exit P3D/FSUIPC and attach the log (compress if still too big). If its too large to attach compressed (oy shouldn't be!), you can transfer using one of the free file transfer services (e.g. https://filetransfer.io/ or https://wetransfer.com/)

I mean exactly what i said - do NOT start/request a new/continuation log file - take a look at the log file you attached: John

The ini file you attached is a continuation log file and contains no useful information relating to your issue. Please attach a full log file - do NOT start a new log file. The Rotor Brake control is what the PMDG aircraft use for many custom controls (internally) - the ones in your log have a parameter of 67803 and 67903 which are a 'mouse move' (03) over the control stand trim wheel and speed brake lever: #define EVT_CONTROL_STAND_TRIM_WHEEL (THIRD_PARTY_EVENT_ID_MIN + 678) #define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER (THIRD_PARTY_EVENT_ID_MIN + 679) You can ignore such events by using the DontLogThese ini parameter - see the Advanced User guide for details.

Those assignments look ok, except that the ranges for flaps 0 and 40 look rather small, try increasing them, and the lower range should be Down only, and the upper range Up only (although not strictly necessary). So try: [Axes] PollInterval=10 RangeRepeatRate=10 0=1R,256 1=1R,U,16383,14580,76773,0 -{ Entering=Custom control: <76773> }- 2=1R,B,11663,13316,76774,0 -{ Entering=Custom control: <76774> }- 3=1R,B,5702,8593,76775,0 -{ Entering=Custom control: <76775> }- 4=1R,B,2386,4604,76776,0 -{ Entering=Custom control: <76776> }- 5=1R,B,-247,1601,76777,0 -{ Entering=Custom control: <76777> }- 6=1R,B,-3306,-1068,76778,0 -{ Entering=Custom control: <76778> }- 7=1R,B,-7128,-4410,76779,0 -{ Entering=Custom control: <76779> }- 8=1R,B,-13081,-9721,76780,0 -{ Entering=Custom control: <76780> }- 9=1R,D,-16384,-14748,76781,0 -{ Entering=Custom control: <76781> }- If you get the same issue with that, activate logging for Axes Controls and Events and see what he log says. Best to do this with the logging console window open so you can see the log in real-time. You can also post/attach it here along with your ini if you can't see the issue and I will take a look. John

Pete retired over 5 years ago...

Please also see the following thread which is the same (or similar) issue (but for a different controller):

👍

If there are Linda scripts available for your device and aircraft, you should certainly try that, although beware the Linda is no longer supported. However, I would have thought it would be quite stable for P3D with PMDG as both have been around for a while. Linda is lua interface that sits on top of FSUIPC's lua facilities. Check these forums and also the Linda support forums for any issues - there should be a lot of information there if you need further assistance.