Deano87

Regardless of it being accurately described and corroborated its a difficult bug to replicate, I know because I've wasted a couple of hours TRYING to replicate this issue, in the very same mission where I had it happen to me a couple of times in the past. Unless the devs can replicate it, it can be difficult for them to track down exactly what is causing the problem. So if you have a track of it, it would be great if you could find some way of hosting it so the devs can download it. Yes I know the forum size limit is annoying.

Yes, as well as symbology showing wingmen location etc. But thats all in the future currently.

Did you edit that saved loadout in the mission editor in the past? That would result in that change. At least its pretty easy to just select what you want for each pylon.

The aircraft only flies using FBW... It's not like the Hornet where it has a manual reversion. If you "kill" the FBW you'd have no control of the aircraft. I think we might be flying different aircraft. With the airbrakes out, and the throttle at idle, and loaded up to 9G, my F-16 bleeds energy FAAAAAST. I don't really get what you mean by "overspeed" the jet, with the FCS in the Viper you are either in one of two states most of the time, you're either G-limited when you're going quick or AoA limited when you are going slow. If you're having issues hitting the ground while going 650 knots when you have 9G available to pull out then I don't really know what to tell you...

Yep its reported!

Delete the fxo and metashaders2 folders from the DCS saved games folder if you haven't already. Remove mods, do a DCS repair and then try again.

I had this issue in the previous version as well, my fix was to go LIST and then press 7 to show this: Dobber down until you highlight the "FDBK" then press a number to switch it off and back on again.

I get it in Caucasus. Can provide track if needed.

A big issue is with the tyres being too grippy laterally, as I noted here: https://forums.eagle.ru/showthread.php?t=262823 With my mod the aircraft is MUCH easier to steer on takeoff because the nosewheel is much less grippy so steering seems much more progressive. Unfortunately my mod doesn't work any more in 2.5.6, but I'm going to take a look at that later tonight.

Did my track help? Can we get this reported please?

Is this related to cold starting or spawning with the dogfight switch activated?

The mod was built for 2.5.5. I’m not surprised it doesn’t work in 2.5.6. I’ll take a look at it.

Yeah thats a new bug with 2.5.6 unfortunately.

The thick font is because the bloom effect is now much more prominent around bright objects, I find it largely goes away if the brightness is turned down enough.

Ok here is a track of it. I experience this on every cold start. The track shows the following, Horizon line, pitch ladder and FPM are offset a couple of degrees upwards, making them unreliable for precision use. Steerpoint HUD symbology and TPOD box also offset by the same amount. TPOD is looking at a tank, HUD shows that TPOD is looking at 2 degrees above said tank. I then do a CCIP dive attack on a small island with Mk84 bombs, usually very accurate (Note, no mission wind). Bombs fall short which shows that the CCIP pipper is also shifted upwards and unreliable. Finally come in for a strafe attack against the same target, rounds also fall short, showing the AG gun pipper is also shifted. Not shown in the track but In my testing I have tried Air to Air stuff and that does not seem to be effected. Hope its helpful D https://www.dropbox.com/s/j2n1h2tltx7behb/HUD%20Shift%20F-16.trk?dl=0

Yeah sounds like invalid INS alignment to me. Not seeing this issue in the current version when aligning Properly.

Brightness adjustment does work. Just need to click it quite a few times.

I will investigate in a little bit. Just trying to make a track for a couple of other bugs.

Yeah I’ve had this issue as well. Can’t reproduce it but it’s always in cold weather. Stuck/eronious airspeed readings and the sometimes it’ll depart and end up in a flat spin.

I have no issue adjust HUD brightness in VR with the latest patch. Make sure you clear out your fxo and metashaders 2 folder from your saved games DCS folder. Also then run a DCS repair. If you wish to adjust the hud brightness downwards simply roll down the top left rotary on the ICP next to the com1 button. If you’re flying at night then you may well need to turn it down to almost off to get it dim enough to use in dark conditions but it works fine for me in my Rift-S.

Not a bug? What?

I haven’t seen a lot of the issues you mention. Have you deleted your Fxo and metashaders2 folder from you DCS saved games folder? Then try a repair and remove any mods. I’m not saying this patch is bug free but I haven’t had any VR issues beyond frame rates and I haven’t had any hanging, crashes or long load times.

Glad to hear it BIGNEWY! :thumbsup:

Hey all. It seems the LODs are messed up for all objects such as static objects, ground vehicles and even other aircraft. In VR I can't see any of these until I'm a few hundred feet away, then they just pop into existence right in front of me. Guessing other people are seeing this as well? Doesn't seem to matter what ground unit I set, they all have the same issue (note, I haven't tested every single one, for obvious reasons.)

It seems something is messed up with the LOD bias, in VR objects etc aren't rendering until i'm right ontop of them.