IT-23 (Shkval Screen) Contrast + Brightness to X52 rotaries?

[JaBoG32_Prinzartus]

DCS does not seem to support a slider/rotary axis for the IT-23 brightness and/or contrast knobs from the targeting panel.

 

Unfortunately I neither have any idea how to get this features on to my x52 pro rotaries.

 

Do you?

[WynnTTr]

Here's what I did - map the actual keys to your rotaries using SST, then adjust the deadzone for the rotary so that it doesn't adjust brightness as soon as you move it in either direction.

[opformaster]

Since there is no axis for the rotaries you will have to make a macro that presses the key you want pressed when you rotate the knob. I have a N52 speedpad with a mouse wheel on it that I have programed to press buttons when the wheel is scrolled up or down. I use mine for the Abris Cursor rotary knob.

 

-op4

[Peyoteros]

Why would you need something like Shkval brightness on your stick? How many times do you use it during the flight? Somewhere in betvene 0 and 1?

[WynnTTr]

Flying combat missions with NVG's on. The whole point of HOTAS is to minimize kb use, and if you can put a function on the HOTAS, why not?

[Peyoteros]

Normaly you set all those things before you take off, but if you need it why not? The whole point of HOTAS is to have ESSENTIALS on the stick so you can fly and fight without letting the controls of your hands. Setting all things from start up procedure on HOTAS would be awesome, no need to touch KB at all, wicked. What I'm saying is that one must understand what is usefull to have on the HOTAS and what is useless, but it takes a time to understand.

[WynnTTr]

If your HOTAS can support it, why not?

 

Have you seen the programmability of a modern HOTAS?

[TX-Kingsnake]

Brightness is not the only potential application for slider/rotary axis. I've been meaning to map the wheel brake to my toe pedal on my rudder pedals.

[slug88]

Here's another great way to minimize keyboard use: use the clickable cockpit! It's far more immersive, and I don't know why anyone would still be the using the keyboard.

[Peyoteros]

If your HOTAS can support it, why not?

 

Have you seen the programmability of a modern HOTAS?

 

To be honest I have no idea... :noexpression:

Would you tell me about it please.

[Reticuli]

I prefer the top rotary as a 50% yaw trim and the bottom rotary for zoom.

[deviletk]

If your HOTAS can support it, why not?

 

Have you seen the programmability of a modern HOTAS?

 

:megalol:

 

Your preaching to the choir there im afraid. ;)

 

For me personally i wouldnt want to wear out my HOTAS because of mode changing just to change brightness or open the door. Instead using the immersive clickable cockpit as mentioned to do these things as they do it in real life. Letting go off the stick and adjust. And since you do it just once (normally) and most of the times you do it on the ground i personally dont see the point. But hey, OP asked for this so who am i to be a party pooper? ;)

[Boberro]

Why would you need something like Shkval brightness on your stick? How many times do you use it during the flight? Somewhere in betvene 0 and 1?

 

Hahahah :D

 

BUt it is true... rarely brightness, contrast is modified during missions ;]

[LennyLloyd]

I prefer the top rotary as a 50% yaw trim and the bottom rotary for zoom.

I used the bottom rotary on my x52 for zoom for a while, but it seemed to have a little play when left alone, making the view kinda jiggle in and out. Any ideas on how to neuter that?

[Peyoteros]

I used the bottom rotary on my x52 for zoom for a while, but it seemed to have a little play when left alone, making the view kinda jiggle in and out. Any ideas on how to neuter that?

 

 

I think this is one of the Saiteks weak points... as I have zoom on the little thumb slider on the throttle and the view jiggles too...

[JaBoG32_Prinzartus]

@Peyoteros:

I flew night missions with changing lighning condittions (illumination flares provided by someone else) . I had to permanently adjust the contrast / brightness.

+

I have those two rotaries available on my HOTAS.

 

That is the reason why I want it like that. I perfectly do understand what is useful to me !

Edited January 30, 2009 by JaBoG32_Prinzartus

[Peyoteros]

@Peyoteros:

I flew night missions with changing lighning condittions (illumination flares provided by someone else) . I had to permanently adjust the contrast / brightness.

+

I have those two rotaries available on my HOTAS.

 

That is the reason why I want it like that. I perfectly do understand what is useful to me !

 

Fine by me man, I'm not trying to insult you... If you want to have those on your HOTAS it's fine, take it easy.:joystick:

 

:pilotfly:

[JDski]

I'm having a hard time getting the parking brake to work after assigning it to a button on my hotas.

Another thing, I have the brake set up on my left toe brake, but you can't set the parking brake when your holding down the brake. So your forced to let off the brake for a second while you set the parking brake.

It looks as though the parking brake is just a catch on the brake lever to hold it in place when you apply brakes. But it doesn't funtion that way in the sim.

[Reticuli]

I think this is one of the Saiteks weak points... as I have zoom on the little thumb slider on the throttle and the view jiggles too...

 

Hmm...I thought I heard this is because a lot of sims don't use the analog axiis at their highest resolution, so you end up getting it flipping back and forth between increments. I have the same issue, but I just realized it can be easily fixed by just using a smoothing function in GlovePIE for that axis. Since I'm already running a script, I might as well fix it using that.

[Quirkitized]

If your having problems with the zoom on your X52 set to a Rotary, you need to program it in the SST software profile, not the game. I had the same issue in LockOn and BS...here is how to do it:

 

Set rotary to Bands

Make 3 bands

Split the two bands with a small %

 

 

This will give you a smooth zooms, no more jitterz once you stopped your zoom in/out.

Edited January 31, 2009 by Quirkitized

[Peyoteros]

There is nothing wrong with transition itself, it's smooth, the view starts jiggle when you stop zooming in or out. After view starts jiggle all I do is shift slider forward or back tiny bit and the jiggling stops.

[Quirkitized]

That's what I ment, sorry didn't word it correctly. In BS & Lock-On, I would have same problem....view in/out just fine, soon as I stopped, it would jitter. Mapping it to my profile via software and un-mapping it in-game fixed it...maybe work for others. Edited my original post.

Edited January 31, 2009 by Quirkitized

[JaBoG32_Prinzartus]

Fine by me man, I'm not trying to insult you... If you want to have those on your HOTAS it's fine, take it easy.:joystick:

 

:pilotfly:

 

hehe, no worries ! :)

 

 

btw.: I also have zoom on the x52-pro slider; But i normally use is fopr zooming in to the max, and zooming out to the min, that's why I have tuned so that it is very sensitiv in the (unused) center, but rather insensitive towards the ends of the band. That seems to mnimize jiggering for max and min zoom view levels.

 

However, I still notice the behavior. But its a saitek issue.

[Reticuli]

Notice how Smooth is set. That fixes this problem integrated into my scripts. Then you just have to use the slider and xrot axis from the PPJoy instead of directly from the x52.

 

var.0 = PPJoy1.Analog0

var.1 = PPJoy1.Analog1

var.2 = PPJoy1.Analog2

var.3 = PPJoy1.Analog3

var.4 = PPJoy1.Analog4

var.5 = PPJoy1.Analog5

var.6 = PPJoy1.Analog6

PPJoy1.Analog2 = Joystick1.z

PPJoy1.Analog3 = Smooth(Joystick1.xrot, 2, .03)

PPJoy1.Analog4 = Joystick1.yrot

PPJoy1.Analog5 = Joystick1.zrot + (Joystick1.yrot * .5)

PPJoy1.Analog6 = Smooth(Joystick1.slider, 2, .03)

if doubleclicked(joystick1.button6) then begin {

var.m = var.m + 1

if var.m = 1 then begin {

say("Standard Dynamic Trim")

press(leftctrl)

press(t)

release(t)

release(leftctrl)

} end

if var.m = 2 then begin {

say("Flight Director Dynamic Trim")

press(leftctrl)

press(t)

release(t)

release(leftctrl)

} end

if var.m > 2 then var.m = 0

if var.m = 0 then begin {

say("Manual Trim")

} end

} end

if var.m = 0 then begin {

t = joystick1.button6

PPJoy1.Analog0 = Joystick1.x

PPJoy1.Analog1 = Joystick1.y

var.y = 0

var.x = 0

var.c = 0

var.l = 0

var.r = 0

var.p = 0

var.s = 0

} end

if var.m = 1 then begin {

var.c = 45

var.l = -0.575

var.r = 0.275

var.p = -0.900

var.s = 0.0

var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s)

PPJoy1.Analog1 = var.y + Joystick1.y

var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r)

PPJoy1.Analog0 = var.x + Joystick1.x

} end

if var.m = 2 then begin {

var.c = 70

var.l = -0.5

var.r = 0.0

var.p = -0.775

var.s = 0.0

var.y = EnsureRange(Joystick1.y / var.c + var.y, var.p, var.s)

PPJoy1.Analog1 = var.y + Joystick1.y

var.x = EnsureRange(Joystick1.x / var.c + var.x, var.l, var.r)

PPJoy1.Analog0 = var.x + Joystick1.x

} end

Edited February 1, 2009 by Reticuli