Jump to content

ABRIS Axis Controls


Go to solution Solved by MAXsenna,

Recommended Posts

  • Solution
Posted
Is there a reason we can't bind the ABRIS axis type controls (cursor position, brightness) to an actual axis control?


Because it's not axis in the real aircraft. And it would probably work very badly. What to do when you've reached the end of your physical axis, but you still need to "scroll" further?

Cheers!

Sent from my SM-A536B using Tapatalk


Posted (edited)

Same question for the IT-23

2 minutes ago, MAXsenna said:

Because it's not axis in the real aircraft.

Sent from my SM-A536B using Tapatalk
 

Interesting, but that doesn't prevent it from being implemented in DCS I assume.  Accommodating the widest variety of HOTAS/flight control equipment would seem to be a good thing for the sim.

 

I see your point on the cursor control binding however.

Edited by Bigity
  • Like 1
Posted
Same question for the IT-23
Interesting, but that doesn't prevent it from being implemented in DCS I assume.  Accommodating the widest variety of HOTAS/flight control equipment would seem to be a good thing for the sim.
I edited my answer.

Sent from my SM-A536B using Tapatalk

Posted
8 minutes ago, Bigity said:

I see your point on the cursor control binding however.

In my opinion, every axis in any module that is an axis in the real aircraft, should be available as a bindable as an axis in the game. While with encoders that scrolls from and to infinity, one can run into trouble if they are axis. 😉 

Cheers! 

Posted
10 minutes ago, MAXsenna said:

In my opinion, every axis in any module that is an axis in the real aircraft, should be available as a bindable as an axis in the game. While with encoders that scrolls from and to infinity, one can run into trouble if they are axis. 😉 

Cheers! 

Does that include axes that aren't functionally modelled in DCS?

7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat 

Posted
9 hours ago, MAXsenna said:

There are several modules that have axis that are not, yet, bindable on DCS yes?

Sent from my SM-A536B using Tapatalk
 

Yes, that is true, but the majority is. The other option is an encoder. Those are for all turn knobs that does not have a "stop", like the HSI knob in every aircraft or the ABRIS-controls in the Shark. 

My latest project, the Multi Function Button Box can be found at Kickstarter.

Posted
17 hours ago, Mr_sukebe said:

Does that include axes that aren't functionally modelled in DCS?

To be honest, I don't think I understood what you meant. Are you referring to like switched and knobs that we have in the cockpit but has no function? Like what was mentioned in the F-4E section, where a certain switch does not yet have keybinds, because it's function does not yet have any function in the module? 🤔 

2 hours ago, JackFlash said:

Yes, that is true, but the majority is. The other option is an encoder. Those are for all turn knobs that does not have a "stop", like the HSI knob in every aircraft or the ABRIS-controls in the Shark. 

Hence why I specifically mentioned encoders above, and how their behaviour is different compared to axis.

17 hours ago, Bigity said:

Hm wonder if I could bind a ministick to it somehow. 

Of course you can. Just use your favourite joystick to key mapper, or just use a hat. 

I personally use the bottom row on one of my TM MFDs for the ABRIS.

Cheers all! 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...