Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi, with FSUIPC6 and P3D, there was a way to speed up the travel of the trim associated with the buttons.

With this parameter, as in the figure, it was possible to vary the speed at which the trim was activated.

Is there the same parameter for FSUIPC 7 and MSFS?

Thank you.

FSUIPC.jpg

Posted
9 minutes ago, Freccia said:

Is there the same parameter for FSUIPC 7 and MSFS?

Generally yes, although this can depend on the aircraft in question. Some aircraft (especially add-ons) may not use the standard control/event that this offset uses.

John

Posted
Just now, Freccia said:

Hope it works on other addons too, especially MD82 (beta on MSFS).

It should work with most aircraft, but maybe not with complex add-ins such as the FBW A320. May even work there though, but I haven't checked. Just needed to add a disclaimer as I haven't, and can't possibly, try each offset with each aircraft, default (i.e. included) or otherwise.

John

Posted
7 minutes ago, Freccia said:

Controlled now with Leonardo's MD82 for MSFS (Fly The Maddog X).

Unfortunately it doesn't work ... 😔

Try activating logging options (for events initially, and also maybe axis controls) and trim in the UI to see what events that aircraft is using. Or maybe check for custom events or lvars. If you can figure out what is controlling the trim, it should be possible to set it up (via a custom profile) specifically for that aircraft.

Unfortunately I don't have that one, so can't really assist with this - just give you general guidance on what to try.

John

Posted
1 hour ago, Freccia said:

Hello John, I have activated the following options from the Log menu: Buttons & Keys, Events and Axes Controls. Attached is the log file.

I am not sure what you expect me to do with that...

I suggest that you keep the logging console window open. Then, activate whatever function that you want to program in the UI (i.e. the trim) , and take a note of what event, if any, is logged. Then, try assigning to that event.

I cannot tell from your log file when you are activating the trim in the aircraft UI - only you can do that...

John

Posted

I'm sorry John but, obviously, I didn't quite understand what to do.

Below I am sending you a text file where I have summarized in a few lines the data recorded by the Console by selecting "Buttons & Keys" from the log list and moving the elevator trim (up and then down)

I will also send you a link where there will be a video that will show you what happens to the registration of the Console when I try to record "Events" or "Axes control". Of course without moving any command.

https://drive.google.com/file/d/1rpWvbCfAn1mKEdLVp5foaGyyN_i_r5zd/view?usp=sharing

elevator_UP_DOWN.txt

Posted
2 hours ago, Freccia said:

Below I am sending you a text file where I have summarized in a few lines the data recorded by the Console by selecting "Buttons & Keys" from the log list and moving the elevator trim (up and then down)

But you have already said that the standard controls don't work for that aircraft, so there is no point logging your button presses - which your log just confirms are working and sending the assigned controls. You need to find out what, if any, controls work for the aircraft. For this, you activate the trim in the aircraft UI, and see what, if any, events are logged. If there are any, try assigning to those. Otherwise, see if the aircraft comes with its own SDK and/or custom controls. Otherwise, try asking the developers of the aircraft - surely they have a support forum?

John

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.