rocket302

Glad they are working for you . Clearly they are not for me as shown in my image. I will try night flying for comparison. They should show up in both day and night. I’d like to see a one to one comparison on what you see for day flying?

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!!!

yes i tried these with both binding them and using my mouse. still nothing. i'm wondering if this is a issue using DLSS just like the mfd graphics

i'm going to say this is not an issue like i thought. the issue is that you need to cock the gun, then put the gun back into the center switch or it will not work. make sure you bind the "cock gun" to return back to center

thanks, since this is not just me...I'm going to summit a ticket. if we all submit tickets maybe they will start making it a priority. thanks

currently the PDU does not work and show any reticle so i have to use the grease mark. It would be very helpful to allow us to bind the grease mark to my hotas or other control

I am selecting gun or rockets to fire. I do this from my hotas . In the mfd you can see the change and when I pull the trigger I either get rockets or guns. But no reticle

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

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

hi, while flying the MFD i get these weird gray lines and the graphic is not clear. the gray lines shift etc anyone else seeing these? Note its hard to see unless you look close at the mfd image i uploaded. its pretty bad in game however. null null

ok here is a picture. No reticle, all mods turned off. Latest DEC 4 2024 build still nothing not sure how to get this to work then?

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

this is unbelievable that people have been asking for this since June and still you guys are not fixing this issue. still no fix in DCS 2.9.10.3948 This is total BS and before you cry babies get on here and make excuses for them not fixing this...i am a software engineer so i know what i'm talking about. it should not take this long to fix this issue. period! its very apparent they don't care about it and instead want to just push out stuff to try and incite people to buy more half/ass modules with their own bugs. Hey here is a novel idea, fix what you have so people like me can continue to play. If we can't play what we have we sure is hell not going to put more money into this. Dont think it matters, listen to your customers this is just from the first search page of the forum... there are many redit post and more.

Mostly playing hot start missions. To get the PDU to show you have to “show” it using a keyboard or mapped command. Once it shows there is no retical inside. you say no such problem so what version are you playing with? Are you on steam or normal download. I am on steam with last update. I will try dec 4 update when I get home to see if it’s fixed. I can also check for mod issues. How do I do that? you say upload some screen or track.. not sure what you are asking a screenshot of a empty PDU is all you will see. Is there something else you want me to upload?

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?

if i select master arm switch then re-cock the gun, the gun will not work. i have to play around with switching the two switchs untill the gun finialy works. it seems that if i re-cock the gun first, then hit the master arms switch things kind of work. it just feels very buggy am i doing something wrong?

not sure if i'm just not doing things right or if there is a bug? i turned on the pilot display, turnned on master arm and can fire rounds. however inside the display nothing shows up. i mapped the brightness and contract and can change thouse but again nothing shows up in the display. if i switch to missile still nothing shows up. any idea of what i'm doing wrong?

Tried the above recommendation but it does not fix the issue. Issue still present in latest build. also you cannot roll Steam version back. I installed pc version as test, roll back to June and it worked. However all mods not available since I bought them on steam. Tried updating with recommendations of dlls but they would not fix issue. glad it works for some of you but for the rest we are hosed till they fix it

Unfortunately steam does not have a way to roll back the game. Anyone know a work around to fix this? also I noted above that the issue was still in 2.9.9.2280 so rolling back to that version will do nothing. Anyway to get back to a earlier version?

There is a bug that affects hands in vr right now. From searches it seems people have been asking about this since July. I hope they fix these issues soon.

hi, i want to edit a mission that already has the weapons ready to use and powered up with the TPG aligned verse having to wait 3-5 minutes after power on. this will give me a faster learning curve if i don't have to sit there and wait. it also lets me preconfig a mission and aircraft where a newbie can just fly it and shoot verse learn all the bells and whistles. i read maybe you can do this with triggers????? not sure any help would be appreciated.

Did you not read my response??? I don’t know the key binding or what its description is? If you’re saying there is already a binding then please let me know what that is? All I know now is how to turn it on/ off in options menu

I looked for that mapping in the f16 but did not find it. Do you know what it’s called?

is there a way to only show the pilots legs, maybe a Mod or something i can edit. the pilot looks awesome except the upper body gets in the way of the control so i can't toggle or switch them.

I'm not sure if this is normal or if I'm doing something wrong? First, i have aligned the Maverick and TPG and then set the WPN mode to Visual. The TPG is set to Auto. When i lock and fire a missile, i can watch the missile through the TGP until it hits the target. Also, note in the HUD i see the TGP square and then the Maverick lock circle. however after the missile hits its target the TPG goes somewhere i can't determine. also the symbols on the HUD go away. to get back to Fire another missile i have to switch WPN in to Bore, then back to Visual which i'm then able to re-target. What i am wanting to know, is this normal having to go back to Bore then Visual to get back to a new target lock, or is there a different way i can do this?