Hawkeye91

Same problem.

I’m having the same problem. Are you a FFB user? I am using the VPForce Rhino. No idea why FFB might cause a problem with the VVI but stranger things have happened.

Latest update, my VVI doesn't work and my Warning Lights are in Russian instead of English. null Mig29 Track.trk

@BIGNEWY Hey BN, any chance you put in a request for the Shrike B varient we could use for the F4? It’s basically a rocket motor and warhead upgrade and doubles the effective range of the Shrike. It would go a long way to making our F4E better at SEAD with minimal work. Thanks guys.

Also don’t lift the collective past the “ground detent” while trying to taxi. You can tell when you’ve gone too far lifting up the collective because the GND on the PFD screen will disappear. It seems like going past the ground detent kills any forward momentum you have.

@BIGNEWY I’m having this problem too. BN, can we get this topic moved to bug reports to be tracked? It’s definitely a bug.

Can confirm, this works

Seems setting the Cyclic trim switch from auto to manual makes a big difference in controlability. Try it out and let me know what you guys think.

Will this pass Integrity Check for playing online?

First problem I have is at times, when I load into a mission(even a cold and dark aircraft) sometimes the Buttkicker just gets a constant shake input signal that's maximum strength and giving me the clipping light on the amplifier with the aircraft still being cold and dark. This problem isn't constant, but happens often enough to be very troublesome. So far the only fix I've been able to find for it, is to completely restart my PC. Second Issue is with the Apache. Unless I turn off Gear Turbulence, I get a constant shake like above, but these are different problems as sometimes even when I turn off the gear turbulence in the Apache, it still shakes uncontrollably. Anyone have suggestions, because I'm really struggling with this software

When you have a rotary encoder set to change the pressure setting (CW/CCW keybinds) it jumps in 00.05" at a time. This is unusable. I have my rotary encoder set to the lowest press time possible in the software for it (10ms). These 00.05" jumps make it impossible to set local pressure settings with hardware. I could get around this if there was also an axis assignment to for the pressure setting by changing my rotary encoder to an axis, but there isn't an axis for the altimeter setting either.

Wonder if there could be some weird geometry on the carrier deck or if even just the arrester cables could be causing spikes in the calculated forces on the landing gear. In iracing, there would be weird invisible yet collidable anomalies in their laser scanned race tracks that could send your car to space or break your front end. Perhaps something similar is happening and was always present, but we just never noticed before because the landing gear wasn’t nearly as fragile.

Any chance the devs could go back and implement this? Seems like a pretty simple feature to implement.

I can get a stable 36 FPS per eye in large MP servers while playing the Apache until another Apache loads into the server, then my FPS tanks from a stable 36 to sub 20 FPS with terrible tearing making the experience unplayable. I'd upload a trackfile but large MP trackfiles are generally broken and too big to upload to the forum. I'm running medium-low settings My systems spec are: 3080Ti 12 Gigs VRAM 32 Gigs DDR 4 AMD Ryzen 5900x DCS installed on my NVME drive. Meta Quest 2 VR headset with 72hz with 1.3x Super Sample

Just for clarity he needs the TRACK FILE that DCS generates after you finish a mission, not a video.