General Simulation Command

[fabio.dangelo]

It would be very useful to have the simulation commands (Show Pilot Body, Show Controls Indicator, Kneeboard, Labels, View & Zoom and also the automatic START and STOP procedures). centralized in a general Memu like UI Controls.

so that you don't have to re-enter them each time for each individual module (also because I believe that like me many people use the same controls for these things precisely so that they don't get messed up between means).

At most you could leave them but empty even in the individual modules and in case they are set they would go into override on the general command.

I personally have a secondary throttle that I use to connect the pedal board and to set just the simulation controls.

[sirrah]

I do understand your wish and while at first it seems very logic, there's a serious downside to this:

Many simmers, have various hotas controllers. For instance, I use a collective, center stick, side stick and two different throttles, depending which module I fly. So, I always have one or two controllers spare, but it's always different ones. That means, that when for instance I fly the Viper (side stick + F-16 throttle) I use a spare button on my collective to quickly hide/unhide the pilot body. Whereas when I fly the Apache (collective+center stick), I use a button on my side stick to hide/unhide the pilot body.

Just an example, but you can imagine that the more UI centralized binds, the more often I'd have an issue.

[Gunfreak]

1 hour ago, sirrah said:

I do understand your wish and while at first it seems very logic, there's a serious downside to this:

Many simmers, have various hotas controllers. For instance, I use a collective, center stick, side stick and two different throttles, depending which module I fly. So, I always have one or two controllers spare, but it's always different ones. That means, that when for instance I fly the Viper (side stick + F-16 throttle) I use a spare button on my collective to quickly hide/unhide the pilot body. Whereas when I fly the Apache (collective+center stick), I use a button on my side stick to hide/unhide the pilot body.

Just an example, but you can imagine that the more UI centralized binds, the more often I'd have an issue.

Not really for the UI binds work like all other binds. So you can any number of peripherals to the same UI command.

The only general UI command I use is VR zoom. I use use 2 different throttles, and 2 different sticks and a collective.

On my Force feedback stick I have VR zoom on a spare button. But i also have VR zoom on a paddle switch on my F16 force sensing stick.

So no problem having the same UI command to several different throttles or sticks. 

[sirrah]

1 hour ago, Gunfreak said:

Not really for the UI binds work like all other binds. So you can any number of peripherals to the same UI command.

The only general UI command I use is VR zoom. I use use 2 different throttles, and 2 different sticks and a collective.

On my Force feedback stick I have VR zoom on a spare button. But i also have VR zoom on a paddle switch on my F16 force sensing stick.

So no problem having the same UI command to several different throttles or sticks. 

You missed my point (or maybe I just didn't make myself clear enough )

When I'm in my Viper, I have all my HOTAS buttons bound to the actual realistic throttle and stick buttons (no spares), so I have to use another controller (my collective) for e.g. pilot body hide.

When I'm flying my Apache, I have all my HOCAS buttons bound to the actual realistic collective and stick buttons (no spares), so I have to use another controller (my F-16 side stick) for e.g. pilot body hide.

So, I can't use the same button for pilot body hide/unhide in both the Viper and Apache. Hence, for me it would not be handy if that was added to the UI layer controls.

 

I hope that made sense  

[fabio.dangelo]

First of all, my proposal involves overriding the command if specified in the individual module, so your situation would still turn out to be expected.

But you still have to consider that a lot of people have only ONE Hotas so they probably have to remap the same support functions for all modules all the time and probably to not go crazy with the same buttons all the time.

As mentioned mine is a special situation in that I have a cyclic for the helicopters the Thrustmaster Viper throttle for the F-16 (and JF-17) and the Whartog for everything else, and I use the TWS (which I need to connect the pedal rudder) as a "service throttle" with all the generic simulation controls.

Having to put the same things back in with each new module I find it an unnecessary hassle.

Edited December 23, 2024 by fabio.dangelo

[sirrah]

23 minutes ago, fabio.dangelo said:

First of all, my proposal involves overriding the command if specified in the individual module, so your situation would still turn out to be expected.

 

Ah ok, I didn't understand that from your OP.

Well, as an additional "override" option, sure!