JSpidey

Casmo's latest stream shows a hot start and the RDR ALT was on on the HDU but the actual setting was off in the FLT > SET page, he tried clicking it on and it remains off. I linked the exact timestamp of when this happened. Also from Raptor and other sources they have said that the RDR ALT should be on by default during a cold start, not sure if this has been acknowledged yet so just thought I would mention it as well. https://www.twitch.tv/videos/1442195694?t=0h16m25s

Yup, same thing is happening to me, when turning TADS on in the front seat or displaying TADS repeater on the VID page in the back. This performance hit is the same in the Hornet when using the Lightning/ATFLIR pods as well, the performance hit seems to be identical.

This would be a life saver in VR

You need to turn on your instrument lighting on the back left console....

Casmo should make a dedicated video on the topic. Or Brad or Raptor should chime in and give their opinions on the matter, they're both very smart when it comes to the Apache and its systems.

To each their own I guess, I'm in VR with no issues. Best we can do is wait until ED finishes investigating the issue and decides if there is something actually wrong with it, or it's just people's lack of understanding of it.

I think the main issue is just the manual not explaining things properly and giving people the wrong impression about how something works, then people believe there's a problem when there never was.

Sorry but objects should appear lower than what they actually are since the PNVS is lower than your head position and it doesn't take into account where your head is to counteract the offset. Maybe we can get an SME in here to shed some light on it but that's my take on it. I would try aligning it to where you want it (no PNVS parallax) and then have your CPG slave his TADS to your PHS and see how much of an offset there is. Since there's no technology in the Apache to counteract this parallax, when you don't see parallax, you're actually doing it wrong since now the PNVS thinks it's height is at your head's height. Also your aim will probably be much higher than it should be as a result and slaving too.

There is no problem with it though, you want your PNVS to be 100% aligned with your eyes and that's not how it should be. I have no problems whatsoever doing it the way it states in the manual. My gun is dead accurate and slaving to my PHS or my GHS is dead accurate so I'm happy with it.

Okay it does effect the PNVS but it's completely normal for there to be offset even when looking straight when aligning properly, you need to be more concerned with your accuracy with slaving and using your LOS reticle to employ weapons than the PNVS, there will be an offset. That's normal, just align it how it states in the manual and that's the proper way to align it.

Boresighting doesn't even effect the PNVS according to Casmo, and looking straight on, things will appear lower than they actually are, just like pointing left or right, things will seem farther left or right than they actually are. The only thing boresighting does is align your LOS reticle with where you're actually looking and has no effect on your view in the PNVS whatsoever. So I recommend instead of focusing on the PNVS go out and shoot the gun or have your CPG set his ACQ source to PHS and see how accurate the slave is to where your head is actually pointing.

Already been reported that the Cued LOS dot should always be visible in the FOR in the TADS and HDU regardless if SLAVE mode is activated or not.

https://www.twitch.tv/videos/1437224946 Go to 01:41:51 and listen to Casmo's explanation of boresighting.

Make sure you activate the laser in WPN > UTIL page when doing MP

I'm doing it the way it says to do it in the manual and it gives me good results. Don't forget in non-VR you can use "Right CTRL + Right Shift + Num 2 8 4 6 * -" and you can change your head position. You can also save whatever position you set it to but I forget what keybind that is.

Well, I know the proper way to do it and I have no issues. So I'm going to keep doing it the way it says in the manual and I'm happy with the results

Alright I understand what you're saying, it's just I never had an issue doing it my way, and the gun is always dead accurate.

Just tested it out while monitoring frames, frames are at a solid 45 FPS when the stuttering occurs while FLIR is on. So it's definitely not a framerate issue just a microstutter issue.

Interesting.. though according to Casmo the offset is normal and is like that in the real aircraft.

I was only referring to the PNVS/TADS video feed, I know it's supposed to be 100% aligned to your gun and other weapon systems.

Yeah I know. That's what's frustrating, I've already mentioned this problem a ways back, and no one seemed to be having the issue, now that the Apache is released, more people are experiencing what I've been experiencing for almost 2 years now with FLIR.

The issue I'm having has been going on since DCS 2.5, it's FLIR in general not just the TADS, like I said the F/A-18C Lightning and ATFLIR both have the same effect as turning the TADS on. I had everything low/off if possible and PD down to 0.5, still does it. It's not something I can fix on my end.

I remember in the past it never did this, maybe.. DCS 2.5? But after that I can't seem to stop it no matter what I do. It's virtually non existent without VR. What's your specs?

I'm getting micro stutters when I turn my TADS on, when I turn the TADS off, it becomes smooth. Same with the TADS in the VID page in the back seat. When I turn it on, the same type of stutters occur, when I turn the video feed off it smooths out. This same sort of stutter always occured in the Hornet as well when I turned the TGP on. And as a test in the Apache, I turned literally every single setting to low/off if it has the option and turned my PD down to .5, same micro stutters occured. The best way to see the stutters is by yawing your head left to right laterally and looking at the knobs on the TDU. Is anyone else in VR experiencing this? With my hardware I'm kinda shocked this is happening with settings that low. I also experiment with ASW using Right CTRL + numpad 1 2 3 and 4 and I can't seem to fix it. RTX 3080 10GB OC i9 9900K OC 5.1 GHZ 32GB RAM Oculus Rift CV1 Samsung 980 Pro 1TB SSD