Unused g940 Rotaries, any ideas

[FifthColumnist]

Hi all,

 

Does anyone have any good idea what to do with trim wheels and rotaries on the g940, I can't think of a zone assignment or anything that would actually be useful, anyone using them?

 

Regards,

 

FifthColumnist

[ZQuickSilverZ]

Maybee you could use it to tune the radio, the Wingman and ID dials, or maybee use them for the rotaries on your Abris. Just a few ideas though I don't know if they would actually work for those applications or not. Hope that helps.

[FifthColumnist]

Having difficulty actually mapping cockpit rotaries with the logitech software, mapping a keystroke with repeat doesnt really work nicely, It would be good if I could make it so that a quarter turn to the right advanced a cockpit knob by say 10 clicks and of course the reverse, I guess that GlovePIE could do that but can't seem to work it out. Perhaps rubber nipples is the best option ;)

[EtherealN]

For rotaries on my X52 I've mapped them inside the simulator, but left the buttons mapped through the Saitek software. You could try something similar unless the Logitech software blocks everything that doesn't go through it's software suite.

[FifthColumnist]

After playing around with GlovePIE some more I devised this and post here in case it might be useful to someone, it allows one to control hud brightness with TRIM1 and the helmet brightness with TRIM2. It uses PPJoy and you will need to assign Buttons 1,2,3,4 of the ppjoy device to HUD brightness up/down and Helmet brightness up/down in the sim.

 

pie.framerate=40
var.hudstepsize = 2.0/8
var.hudcurrent = smooth(joystick1.rx,0,var.hudstepsize)
PPJoy1.digital1 = var.hudlast > var.hudcurrent
PPJoy1.digital0 = var.hudlast < var.hudcurrent
if var.hudlast > var.hudcurrent {
  var.hudlast -= var.hudstepsize
} elseif var.hudlast < var.hudcurrent {
 var.hudlast += var.hudstepsize
}

var.hmdstepsize = 2.0/64
var.hmdcurrent = smooth(joystick1.rz,0,var.hmdstepsize)
PPJoy1.digital3 = var.hmdlast > var.hmdcurrent
PPJoy1.digital2 = var.hmdlast < var.hmdcurrent
if var.hmdlast > var.hmdcurrent {
  var.hmdlast -= var.hmdstepsize
} elseif var.hmdlast < var.hmdcurrent {
 var.hmdlast += var.hmdstepsize
}

 

I might post a more refined version once I understand GlovePIE

 

S!

FifthColumnist

[FifthColumnist]

Thanks for the input. I tried delta originally and it wasn't very good as you say iterations are missed all the time.

I found issues with glove pie generating keystrokes with ctrl alt shift modifiers, I think its probably better if those keystrokes aren't generated at all.

 

The big problem with this script is keeping the glovepie frames in sync with the game frames, which I don't believe is possible, adjustment of pie.framerate is intended to fudge this a little, but its not perfect.

I don't really know how the game engine handles input, but heres my assumption: I believe if the game engine registers a button held down across two frames it will trigger whatever control is associated with the button twice, the other scenario is that glovepie can easily generate press->release->press->release cycle entirely within one game engine frame I assume only one cycle will be recognised.

 

I did think about storing pending button presses, but I think that dispatching the queued presses will suffer from the same problem.

Edited August 20, 2010 by FifthColumnist

[power5]

Is there a good g940 tutorial for BS? I have had the hardest time just trying to figure out what all the sliders and axis actually are when trying to assign functions to any of them.

 

Seems my throttle (collective) is not very sensitive either. I have to move the throttle pretty far to alter the collective it seems.

[FifthColumnist]

Is there a good g940 tutorial for BS? I have had the hardest time just trying to figure out what all the sliders and axis actually are when trying to assign functions to any of them.

 

Seems my throttle (collective) is not very sensitive either. I have to move the throttle pretty far to alter the collective it seems.

 

It takes quite some hours to get the joystick set-up in this game I found, and part of the learning curve while learning to fly the game is tweaking the controller to add inputs as you learn how to use the various functions of the aircraft, thats how I did it anyhow.

There is loads of useful information regarding the g940 and DCS... scattered across a myriad of posts. In addition there is just as much misleading or out of date information.

 

Personally I use the Logiitech Profiler to configure button inputs (although no reason you cant do that in game instead) and only map axis using the game, the advantage of doing it in the profiler is that you can pause the game, alt tab to the profiler and make changes mid mission.

You can configure axis sensitivity/range in the logitech software, but I think its probably better to this with "axis tune" in game, the reason being that I think that you are moving the joysticks physical position away from the ff 'dead spot' as generated by the game, I find that if you configure this in game then the natural off centre position generated by the trim system will be the same as the physical 'no force' position the joystick takes when you release it.

 

Its very much a matter of taste of how you like your joystick to feel and respond, personally I like it to be a little less sensitive to allow for very fine precision control (I imagine that using curves is a very bad idea though since the logical centre position is never at the joystick's physical centre position)

Edited August 20, 2010 by FifthColumnist

[power5]

Yeah, I have been mapping as I go, not using anyone's setups. I tried setting it up in the logitech software, but in game it was not taking. In fact, my logitech settings do not match the game and the game commands still work just fine. Is there something I need to do to make it take the profiler settings? I get no FF I dont think. Is there something I need to enable? When I go to FF tune in the game control settings, its all greyed out and will not let me adjust anything. I would definitely like to use the profiler though for the reasons you mentioned about switching during missions. Its also easier as a graphical interface and quick reference as to what the buttons do on the stick, instead of searching though the hundreds of items in the controls section in the game.

[FifthColumnist]

The logitech profiler works by generating key strokes for button presses, the "commands" you see in there are actualyl just little keystroke macros as you will see if you try and edit one, therefore to map buttons you need to take no action in the game and leave all the default keys as they, just map and configure your axis in game, as regards force feedback, stupid question, but do you have the power plugged in? and do the force work in the control panel?

[power5]

So, if I make any edits to the in game controls list, it will overwrite the logitech?

FF is powered Yeah, when I was calibrating it shook like crazy.

[FifthColumnist]

Not sure what happens if you map the button throught he game and also map the button as a keystroke in the profiler. Perhaps you might get the keystroke action as well as the action mapped to the button in game. better to not mix and match in my opinion.

Ah, you have to click on the one of the mapped cyclic inputs to press the ff tune button iirc

[power5]

I have different commands mapped in game and the profiler and only the game commands work.

 

I will try messing with the cyclic inputs when I get home. I was not sure if the FF was something that had to be enabled in a .lua file or something.