Bowman-011

Added two tracks to show the two aiming scenarios. IA-F-16CM-Canyon Run Attack CCIP on steerpoint diamond.trk IA-F-16CM-Canyon Run Attack CCIP on target.trk

Observed in OB 2.7.9 in the Syria map "Canyon Run Attack" mission. The mission is to bomb an early warning radar which I do every now and then to check out new DCS versions. This time I observed that my MK-82 Snakeyes always fell long and hit the ground behind the target when using high drag. At first I thought it was just lack of skill but after several repetitions I started to wonder. I noticed that the waypoint was always shown in front of the actual target rather than on top of it. If I drop the bombs with the pipper on the target they always impact way beyond the target. But if I drop using the indicated waypoint I hit right on the mark. Note that the bombs hit not just slightly off target. They hit the ground quite far from the expected impact point. As you can see, the waypoint is placed perfectly on top of the target in the mission editor. Approaching from different directions also moved the waypoint indication to a different side (notice the attack heading in the screenshots) . Using dive bombing CCIP I was always able to hit the target without any issue just by aiming straight on top of it. Is there something wrong with level flight bombing? I'm 100% sure that this was never an issue in previous versions. Am I missing something here?

So that's what the CNTL page is for I tried it again by just selecting SAM. This time with a more acceptable update rate. Thanks man!

On the weekend I've been playing with the cool new Viper features presented in last week's patch. Really great stuff! Thanks, ED! In a test mission I positioned some SAM sites and tried to engage it with the HTS. At the same time I wanted to try out setting markpoints with the TGP like demonstrated in some YouTube videos. After figuring out the logic and the limitations this worked quite well. However, after coming off my target SAM site in a left-hand turn and trying to re-acquire one of the SAMs they went green (inactive) and eventually disappeared from the HTS display. This wouldn't be that surprising to me if the emitters would have disappeared on the RWR, too. But on the RWR they were still present (and I could see their radar dishes rotating when switching to the external view). Only after getting some distance between me and the target and re-engaging after a couple of minutes I was able to get the SAMs back on the HTS. I know that some things are still wip and some others I encountered have already been reported as bugs (like the locked SPI issue). But I'm not sure if I'm missing something here: Why do emitters show up on the RWR and not on HTS? (sorry for this bad quality screenshot taken in VR, but I've also attached a track file if someone wants to try it out) hts_test_syria2.trk

Have you tried clearing the fxo and metashaders2 folders under <userprofile>\Saved Games\DCS ? I frequently get FLIR issues particularly in the A-10 after updates so I usualy delete the two folders regularly.

Then it would indeed be good to have it back!

Hmmm... in DCS 2.7.1.6709 the mask is still gone. I wonder if the mask is just cosmetics or if it really improves the frame rate by reducing the number of rendered pixels. Does anyone know?

I was trying SJ after some dogfights in the F-16 OBFM caucasus mission. When I left the dogfight mode I found that I was no longer able to jettison weapons. The SJ page is always empty. I tried to switch between A/G and A/A and back to NAV but I still wasn't able to recover SJ. Did I do something stupid? Here's a track file of the OBFM mission I stripped down in order to fit the 5mb limit: f-16_SJ-not-working-after-dogfight-4.trk

Good to know. At least the missing lasers are now fixed in 2.7.0.5118. Without them my aim was really messy

I was quite surprised to see that the performance is at least as good as 2.5 in VR even with the enhanced visual effects and clouds set to ultra. Great job ED. I really love the new Digital Cloud Simulator

I was about to post the same. Already played with the available options but I couldn't get it back working. Am I missing something here? The missing laser pointer is annoying but the fact that the thumb stick doesn't rotate buttons anymore makes it pretty unplayable.

Nice hint regarding alt+tab. I see that framerate drop every now and then. Regarding the SteamVR -203 issue I found an interesting video of a fellow DCS pilot on YouTube a few days ago. He proposes to set the pixel density in DCS to 0.5 and increase supersampling in SteamVR to whatever suits your FPS requirements. I've set mine to 250% for constant 45 FPS with my other settings. The visual quality feels just about the same as before at an equal frame rate (PD 1.0 in DCS, 50% in SteamVR) Since I made the change I wasen't able to reproduce the -203 error. It's a workaround. But if it does the trick, who cares . Good luck tryin' it out.

Looks like I'm in good company. This happens every once in a while on my system and I can reproduce it quite easily. Pretty annoying . As mentioned before, DCS is not crashing and there's no crash log to investigate on. DCS freezes, becomes unresponsive and after a minute or so I get the -203 in Steam VR. I made a couple of dump files of the hanging DCS.exe process using the Windows Task Manager. If some of the developers think this could help to pinpoint the issue I'd gladly share the files (~4 GB)