G940 v5.08 SW is available on Logitech Support Site

[blaster454]

Downloading ... have not yet tested.

[Lava]

Guh. Before I crash myself again, let me post a quick reply. The software's great except for a new bug that was (probably) introduced when they extended the shift functionality. If I shift on the joystick and press a throttle button, my system completely crashes. A hard core BSoD related to WXml (dot something), and a reboot. It happens any time, in game or not. I crashed my computer testing that out in my last attempt at posting, sigh. I'm sure they'll fix it in 5.09, we just need to (politely!) get Mark's attention.

 

I'm running Vista x64 bit.

 

(edit)

My other thoughts:

The profile is recognized automatically, and every single command is programmed in. I LIKE it. That saves us tons of effort, collectively. Thank you Mark! There's a 'default' configuration with the profile, but I switched it over to my own config in about 8 minutes. Not too bad. Hardest part is scrolling through all those commands! It's got a limited go-to capability, if you type a letter it jumps to that spot in the alphabetical list. Also, the mini-stick gets calibrated and was, from my limited use, usable for the Shkval. Make sure you delete the Logitech profile's command for it and configure it in-game through the Axis Assignment. The only in-game configuration I am using right now is the Axis Assignment, everything else is Logi's software.

Edited September 24, 2009 by Lava

[blaster454]

Well, I have not seen that crash yet. I am running in WinXP. When I program a shifted function on the throttle and set the stick's pinkie trigger as a shift key, it works both in the GUI controls window and in game. That is, when I press the throttle button either in the gui or in the 3d app, the correct function is shown or executed. Maybe it's something with Vista?

 

I agree that it is very nice to see the several profiles with (I think) complete Command lists. There profiles (more accurately, there are command definitions) for FSX, IL2, LOck-On, DCS BS, Falcon4:AF, Stalker, CFS3, and Crysis on my installation. Not sure if it recognized that those sims/games were installed on my machine or if it puts them in automatically. The actual mapping of commands to controls seems to have been done without much thought but that's not a problem as I would want to do my own mapping anyway. Some of the definitions for zone or POV or cycle commands seem to be a bit strange, but that is easy to change. The big thing is having all the base commands pre-defined. :thumbup:

 

Some thoughts and observations on the profiler software so far:

 

• When you click a device control and then assign a command, the list of commands seems to come up in two formats (one a long vertical list with scroll bars top and bottom and the other a multi-column table with no scroll bars. I assume this is dependent on the number of commands defined.
  

• The scrolling action in the vertical list is not consistent either in context or with Windows standards:
  
  

• The list will not scroll with the mouse wheel.
  
  

• If you jump to a beginning alpha character (by pressing "h" for example) when you are jumping down into the list, you can then scroll down by moving the mouse over the downward scroll arrow. The same does not work when scrolling up into the list (e.g., from "Z" to "F")
  
  

• If I had a preference, I'd rather see all the command lists displayed in multi-column format (with a scroll function if the list is too long). It's much easier to scroll through the larger table.
  
  

• It seems to me that sometimes when I am trying to define something other than a basic command or keystroke (e.g., a zone, or POV command), when I try to assign a command the list of available commands is less than the full list of commands defined.
  
  • For example, in the FSX profile, if I try to define a POV supercommand with the next and previous Category and View in Category assigned to N & S and W &E on the hat (S & SHIFT S, A & SHIFT A), the View Next Category and View Next in Category commands are available but the shifted commands are not. When I go back to the list of defined commands, they are all there.
    

   

 

• When in the device windows in control panel (either as part of setup or later to recalibrate), when I test certain controls, the FFB mechanism responds--sometimes with a fair amount of force :smilewink:.
  
  • For instance, moving the stick POV hat causes the stick to jump to the cardinal positions. Pressing the trigger causes the stick to start dancing and requires some other button press to stop it. Not too sure what this means
    

   

 

• I seem to have problems calibrating the Mini axis hat. I go through the first step moving the cross cursor to all four corners. If I do it more than once it seems to round off the corners a bit and my impression is that it continues to round the corners slightly more with further manipulation. When I go to the next step, the cross cursor is always positioned to the northeast diagonally from center. I move it back to center and while holding it there (not easy :smilewink:) press the NEXT button to define the center position. When I later go back into the device screen in control panel, the cursor is still displaced upward and right of center (Not a lot, but not centered either).
  

 

• I noticed some strange behavior in game with the mini-axis stick. I programmed this in game to control the absolute Schkval cursor movement horizontally and vertically). I must have something set up incorrectly because the vertical movement is reversed (mini stick up = cursor down). Also, when the mini stick is moved, the Schkval cursor continues to move after the mini stick is released ... it's almost like there is an acceleration function present. I have to fiddle with the mini-stick to get the cursor to stop movement.
  

I really like the way the FFB stick is working in BS, especially with the trim. I see very little play in the x- and y- axes after the stick is trimmed and the stick does hold it's position. And the sensitivity is pretty high ... so much so that I'm going to try to tune it down a bit (either the axis sensitivities or by putting in a small dead zone--not sure of the impact to trim yet so it's all experimental). The reason for this is that I find, after going into a hover, that when I try to use stick buttons or the Schkval cursor hat that it's pretty hard not to move the stick and cause some perturbation from the hover. This is probably as much my technique (or lack of :)) as it is stick sensitivity. I do know that it is very easy to control the Shark (as long as I can keep from getting ham-handed and going into oscillations :doh:!)

 

I'm hoping that we can get a G940 "Tips & Techniques" thread going where we can share experiences and learnings. There also seems to be a lot of room for some unique programming with zone-, cycle-, axis-, and POV-commands ... it would be nice to share here, too.

 

I too have everything set up in Logitech SW except axis assignments. I still need to tweak and understand some things (like when repeatable key presses are good or bad--and what degree of repeatability is best). It seems that it's possible to pretty closely set up the stick and throttle one-to-one with the KA-50 setup -- or at least pretty close.

 

Nice job so far, Logitech! There is a lot of room for making the profiler more powerful but I'm not too sure Logitech will be interested because this is multi-use SW. It still bothers me to see it referred to as the "Wingman Profiler" :(

[Lava]

(edited completely) At first I couldn't replicate the crash bug. It doesn't occur while staring at the Logitech software itself. Then I crashed myself out of Firefox and Black Shark and managed to write down the error data. This happens when in another program and you press the shift (s5 on my joystick) and any throttle base button (haven't tested other throttle buttons). I'm running Vista x64.

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL

crash in wxmlcore.sys (although google tells me it might be wmxlcore.sys ? Reluctant to crash my comp again to find out)

 

I'm tempted to try reinstalling the xml packs, but I think this is a Logi software bug.

Edited September 24, 2009 by Lava

[Lava]

I like your ideas, Blaster.

 

It seems the FFB mechanism is tested along with the buttons in the Game Controller screen. Each button performs a distinct (but very energetic) action.

 

The Mini calibration shows the same rounding phenomenon for me as well. I'd like to think it's because the sensor actually IS round, it sure feels that way. Mine is currently calibrated well with no drift, but I haven't tested it in BS. Try re-calibrating yours, and when it asks it to center, actually leave it alone and don't actively center it?

 

I too noticed that pressing a button or manipulating the Shkval will cause you to move the joystick just a tiny bit. The stick's sensitive enough to pick that up! That's amazing. Never seen the need for a deadzone before, but hey, it's hard to complain that the stick is 'too' sensitive. "Wahhh it reads every single movement we make!" :)

 

The POV/Hat commands seem useful, I'm not sure why I read someone complain about them elsewhere. The ones that Mark defined are actually great, except he has his set up precisely opposite how mine were set up, so I had to rearrange them. Nonetheless ;-) On the throttle, the top HAT controls shkval zoom and tv frame size. The bottom HAT/fake-mini controls weapons stations.

[schkorpio]

did you guys ever get the mini stick and shkval to work properly ? :)

 

having the same drifting issue in BS (but not in windows control panel)