Intermitent function

[Flyingwrench]

I have problems with guns and Vnecksafer working intermittently. There is no particular time or event where they start or stop functioning. Often it happens in the middle of a dogfight. I have the sights lined up, but when I press the trigger nothing happens. (The trigger on the VR control stick does not move) After a few seconds they start working again.

 

The Vnecksafer function, mapped to the hat on the gunfighter III grip, will often freeze with the view locked to port or starboard and I have to wait until it starts functioning again before I can view the instrument panel. Therefore it cannot be used except in straight and level flight, making it useless when it is most needed in a dogfight. The Vnecksafer auto function does not work at all and never has.    

 

Also the braking a has quit working. While the opening menu key mapping shows everything working, when I go into a mission the key mapping there shows the brake controls are frozen. It looks as though the two mapping menus function differently. I would chalk all this up to the infamous, shoddy communist manufacturing, but these were functioning fine until sometime during the last few IL2 upgrades. (In the Marines everything that malfunctioned was labeled "communist", as in, "this GD Communist PRC25 has quit working!" There was some irony in hearing a Marine, complaining to an armorer, curse his M16 saying, "this GD communist piece of crap jammed again!" Especially considering how the communist AK47 was a superior weapon.)     

 

I have a top of the line Cyberpower system with max memory, all solid state hard drives and a 3090 card. Controls are Honeycomb throttle, Gunfighter III grip and Thrustmaster pedestal mounted rudder pedals. All systems function properly outside the IL2 sim.   

[firdimigdi]

  

On 6/30/2022 at 2:23 AM, Flyingwrench said:

There is no particular time or event where they start or stop functioning. Often it happens in the middle of a dogfight. I have the sights lined up, but when I press the trigger nothing happens. (The trigger on the VR control stick does not move) After a few seconds they start working again.

 

Sounds like a controller issue to me. Check that the grip on your VKB is seated properly and doesn't display increased error levels in the VKB configuration utitlity (see instructions on the VKB site/forum*) when moving it around and that it is not losing USB connection (or if it's on a hub that the hub itself isn't losing connection, or if there are multiple devices on that hub make sure it is a powered hub with its own power supply).

 

*EDIT

Actually, here:

 

Select the device, press on "External Devices" and then the connected grip - a pop up window will come up showing the current error level for your device. Move the stick around in all directions and see if anything registers there - normally it should be 0%. If it does register some amount of error then remove the grip, clean the contacts and resit it firmly on the base.

 

Edited July 1, 2022 by Firdimigdi

[Flyingwrench]

Checked all the setting - no errors. The problem seems to be related to game settings. After entering a sim mission, the controls usually function and I can use the hat switch to look around with Vnecksafer. After departure the hat switch and other buttons quit working. Although the hat switch 0 degree hat button setting configured to operate the wing leveling function sometimes works en-route. Then just before an attack phase, the buttons  start working again and continue to work intermittently throughout the attack, but a lot of button pressing is required to hit a target as the buttons do not function with every activation. Then the buttons cease functioning on the way back to base. This includes the hat button, configured to run Vnecksafer, the gun firing trigger and the lower button on the KG12 stick configured to operate bombs and rockets. The control stick functions flawlessly throughout the mission.  

 

I don't get the nice external device images displayed in your screen shot.

[Hoss]

Well, does it not do that with Necksafer turned off?

Brakes looking frozen, try reversing the axis direction in keymapping, it's probably In instead of out..(Look down at the breaks, press them if they come up, they are backwards)  I would also put a dash mark in front of my IL2/data/Input/device.txt, (game won't see it) restart the game and let it regenerate itself. If things mess up, delete the unchecked one and uncheck the checked one..

device.txt ← New one generated at start

-device.txt ← Original one you put the dash mark in front of.

 

Mine looks like this, I run TARGET GUI in IL2 so it sees my TMWH HOTAS as a "Combined" controller the Stick and Throttle it does not have a conflict with. 

 

configId,guid,model|

0,%22d53184a0-c0fa-11e9-0000545345440580%22,Thrustmaster%20Combined| TMWH HOTAS running TARGET GUI

1,%220e2280d0-c0fa-11e9-0000545345440180%22,MFG%20Crosswind%20V2|  Rudder Pedals

2,%22bc302830-7e0d-11ec-0000545345440180%22,9%20axis%20112%20button%20device%20with%20hat%20switch| GVL R/P/Y Trim Box

3,%22797235a0-f385-11eb-0000545345440180%22,Joystick%20V2.04|  BlackHog Explorer

4,%220e22cef0-c0fa-11e9-0000545345440280%22,Joystick%20-%20HOTAS%20Warthog|

5,%220e22f600-c0fa-11e9-0000545345440380%22,Throttle%20-%20HOTAS%20Warthog

 

Make sure you do not have things in here you do not want. If you are running controller software, always start it before you start the game. Once you get things working correctly, make a copy of this in case you mess it up.... Like I do too often.. LOL

If you have a controller mixed in with the ones I have in red you may be getting conflicts you are not aware of.  Try to delete the unused controller and restart the game........ with your software running if you use it.

Edited July 14, 2022 by Hoss

[firdimigdi]

6 hours ago, Flyingwrench said:

I don't get the nice external device images displayed in your screen shot.

 

Oh right; for some reason they hide that very useful part of the utility unless you do this: there should be a zconfig.ini file present in the same directory as the VKBDevCfg-C.exe - edit that and under the [User] section add a line reading User=Developer - for reference this is what mine looks like:

 

[User]
PartialWrite=0
PartialCalibration=0
AutoRegFileMake=1
User=Developer

 

I'd done that a long time ago and had forgotten about it.