collective jumps and not smooth

[rocket302]

i have virpil collective control with throttle twist and when i move the collective up/down it jumps

my curves are smooth, so i'm not sure what is going on. calibration for the stick looks good too as it goes from 0-100%

where the jump is at around o-10%  from 10%-100% its smooth. 

thoughts?

 

 

 

 

[MAXsenna]

i have virpil collective control with throttle twist and when i move the collective up/down it jumps
my curves are smooth, so i'm not sure what is going on. calibration for the stick looks good too as it goes from 0-100%
where the jump is at around o-10%  from 10%-100% its smooth. 
thoughts?
 
 
 
 

Have you set the axis as a slider? (It should be). Most likely you have an axis conflict. What module is this?

Sent from my SM-A536B using Tapatalk

[LuseKofte]

4 hours ago, MAXsenna said:

Most likely you have an axis conflict.

This is very likely. After patches there is always put a axis function extra somewhere

[rocket302]

well i have changed my axis to slider and checked other bindings.  at this point i still have the issue.

what i notice is with the virpil app, both my throttle and collective move smooth from 0-100% so that seems fine.

however in DCS it jumps.  

 

- Notice in these picture (yes i know sliders is off for these images)

- this image the collective is at 0 or all the way down . Notice its shows -100

- next image shows the stick moved up maybe 1-2in but now the input is 0

this is where the jump is and like the stick is not really set to 0-100

if you want pictures with the slider enabled i can do that however it will look close to teh same but the values will be -50 etc

 

null

[trev5150]

Do you feel anything in the mechanism? Open up the base and check for any FOD.

 

Additionally, check to see if it follows to different modules or if it's on just one aircraft.

Edited December 5, 2024 by trev5150

[MAXsenna]

1 hour ago, rocket302 said:

what i notice is with the virpil app, both my throttle and collective move smooth from 0-100% so that seems fine.

however in DCS it jumps.  

The it should be fine in DCS. Only times I've had this issue is with axis conflicts/double bound axis.  

As you probably know, if you have many peripherals, they will get out of sight so to speak. So remember to drag the slider to the right to see them all. 

If suspect I have a conflict, I just highlight the suspecting row, collective in your case. And then I just drag the slider back and forth to make sure only one is bound. DCS do strange things and rebounds axis for no reason from time to time. Happened to me the past two updates.

10 minutes ago, trev5150 said:

Additionally, check to see if it follows to different modules or if it's on just one aircraft.

Good tip! 

[rocket302]

ok i did a couple tests.   the behavior seem to happen over multiple mods. Huey and Oh-58 tested.

if you look at the image provided you can see that the virpil axis shows 0% and 100%, therefore when i move the collective it registers from 0-100%

Same with throttle.   This seems to indicate that the issue is within DCS but i just can't see to find it.

 

null

[MAXsenna]

5 minutes ago, rocket302 said:

ok i did a couple tests.   the behavior seem to happen over multiple mods. Huey and Oh-58 tested.

if you look at the image provided you can see that the virpil axis shows 0% and 100%, therefore when i move the collective it registers from 0-100%

Same with throttle.   This seems to indicate that the issue is within DCS but i just can't see to find it.

 

null

Oh, I believe you! But like I wrote. Only happened to me when I had conflicts. I wonder if you have some sort of "ghost conflict"? Yeah, I know. Sounds silly. When the Hind was released, I had to manually clear out all axis settings for my TM Cougars, which even don't have axis, or I would drop out of the sky in air start missions.  

OT tip. To get rid of that "null" text when pasting pictures, click at the "paste as plain text" text below the post. Click the picture thumbnail to insert it where you want it. This was on my default before. Go figure. 

[rocket302]

ok, thanks. I'm reaching out to virpil and seeing if they know the issue.  I'm thinking it might be them instead because i just opened up their calibration center, then also opened up the windows game controller window.

i can see a jump on the game controller test window so something is up.  I'll let you guys know what i hear back

 

[MAXsenna]

ok, thanks. I'm reaching out to virpil and seeing if they know the issue.  I'm thinking it might be them instead because i just opened up their calibration center, then also opened up the windows game controller window.
i can see a jump on the game controller test window so something is up.  I'll let you guys know what i hear back
 

Ahhh! So that happens. Nice find. Maybe you only need to upgrade the firmware and re-calibrate. That's an easy fix, so we can hope for that.
I installed a newer version of the Virpil tool and that rendered my collective, (non-Virpil, while using Virpil electronics), completely dead. Had to update det firmware and re-calibrate, and all was back to normal. Well, except it changed name and GUID so I had to rename all the relevant diff files in DCS, easy enough, to get my control bindings back.

Sent from my SM-A536B using Tapatalk

[trev5150]

On 12/4/2024 at 8:43 PM, MAXsenna said:

 

I've been a pilot since the late 1900's, but only been a maintainer for the last 5, and I've learned a ton about fault isolation in that time. Isolating by swapping suspect components out for known good ones is one of those things.

Anyway, one of my preventative measures whenever there's an update -

and I don't care if others think this is unnecessary and they always say something (my post update quality of life is much higher compared to others who don't do this) -

Delete your fxo and metashaders2 folders entirely from your Saved Games folder, then run the repair *As Administrator* (right click on Start > Repair Run as Admin), with every option checked.

I'll die on that hill. It's worth the extra few minutes.

Edited December 6, 2024 by trev5150

[MAXsenna]

Delete your fxo and metashaders2 folders entirely from your Saved Games folder, then run the repair *As Administrator* (right click on Start > Repair Run as Admin), with every option checked.
I'll die on that hill. It's worth the extra few minutes.

Fair enough. But that won't ever solve peripheral issues.
Running as administrator won't either. Either you run repair or you don't. The Updater won't know the difference. It sets DCS back to vanilla, nothing else.
Repair won't ever touch Saved Games folders too, but one can rename the DCS Saved Games folders to completely get back to start.
Cheers!

Sent from my SM-A536B using Tapatalk

[rocket302]

ok, after talking with Virpil, they suggested a way to calibrate the stick. the key here is not to go into windows and re-calibrate

instead, just click the "reset" . Here was their response.

 

firstly, create new profile and calibrate axes in VPC Configuration Tool.

Then run VPC Joystick Tester and check if axes work correct.

 reset Windows calibration, Create New Profile-> Calibrate-> check in VPC Joystick Tester 

 

at this point it worked so i'm good for now.

thanks for all your help guys!!!

 

 

 

[trev5150]

On 12/6/2024 at 4:21 PM, MAXsenna said:

 

 

Fair enough. But that won't ever solve peripheral issues.
Running as administrator won't either. Either you run repair or you don't. The Updater won't know the difference. It sets DCS back to vanilla, nothing else.
Repair won't ever touch Saved Games folders too, but one can rename the DCS Saved Games folders to completely get back to start.
Cheers!

Sent from my SM-A536B using Tapatalk
 

All Run As Admin seems to do in my experience is ensure that it priotitizes CPU - been doing this long before I discovered process lasso - helps prevent applications from hanging because Windows thinks that printer driver updates a REALLY important RIGHT NOW....

... Goddamn I hate Windows.

 

All anecdotal, n=1, advice I internalized decades ago. I'm just throwing that out there as an aside for overall smoothness of life after DCS updates. I know it won't fix peripheral problems or the Saved Games folder.