Biggus

I'd love to grab these skins, @Strut! They look awesome! Where can I download them?

My understanding is that they had short shelf lives and that might have impacted upon their general effectiveness. The Super 530s were entirely new missiles and were roughly on par with the AIM-7F and -M. Maybe 10nm head on at high closure for the R530. It's very hard to separate out the poor performance of the weapon from the performance of the early radars that were guiding the semi active variant. The IR variant was rear aspect only and might be usable out to 3nm. Like a really big AIM-9B. I find it hard to make predictions about how it will stack up in the game against the Flogger's Fox-1s. Kinematically I'd expect to see the R-23/-24 to perform a bit better than the R.530. There are other factors that come into play though. Most Floggers IRL had poor look-down capability, much like the early Cyrano IV. If that's true in DCS (and this is a massive if, as I believe that most AI have unrealistically high LD stats), then a range disadvantage may not be too hard to offset with some situational awareness and good tactical sense. However if in this case our Flogger AI has the ability to track and launch on things 20,000ft below and 20nm in front of him, life's going to be harder than it should be.

Can't say I'm a fan of this new layout. I much preferred being able to access everything from the main index.

I assumed it might be a pretty difficult task. In the meantime, I might include one of the HAD-friendly radars on the sites just to give players a signal to slew the TGP onto.

Just wondering whether the SA-12/20/23 should be appearing on the HAD in the Viper? I've played a couple of missions lately where they aren't showing up. I assume that is just a DCS limitation, but just wanted to confirm the behavior.

Yesterday you offered a pretty reasonable suggestion on a thread I posted in the VR bugs subforum regarding a large black artifact across the front of my cockpit. I was able to narrow that down to an OpenXR issue that only occurs when MR is on automatic. MR auto is definitely doing something. It might be unintended, but auto is not equal to disabled. Prior to discovering this issue, I ran the same ~5 minute scenario for hours, testing each state. I wish that I'd thought to put the OXRDT overlay up while I was testing it to provide you with some solid evidence. I've since made some substantial changes to my setup so I'm not sure if I'll be able to replicate it again, but it was glorious prior to the shader issue.

Last night I posted a bug in the VR bugs forum, however I'm no longer sure it's purely a DCS bug because it only seems to occur when running OXR. This didn't happen with SVR. I've seen one other user report this issue earlier in the thread. Some water textures disappear as per pic below. I also get a black box at the front of the cockpit as below, where I can look to the sides of the aircraft with no issues but this black box covers the cockpit front panel and windscreen. It sometimes disappears for a little while. In addition, the picture on the TGP is often obscured even when the black box is not present, and only zooming in to maximum zoom on the pod seems to clear it. It's almost like the TGP has it's own version of that big black box blocking my forward view. Reverting to SVR fixed this issue, and then cleaning, repairing and reinstalling OXR brought them back. I'm very much hoping that this is just a user error of some kind, but I'm not sure what else I could be doing wrong. Any suggestions or advice would be very welcome.

Quick update. Reverting to SVR from OpenXR fixed this issue. It also fixed a disappearing water texture issue. I'll report it in the large thread in the main forum too. Hopefully it'll be an easy fix. Edit: With further testing, it appears that this issue only occurred when using automatic motion reprojection. So long as OpenXR is set to disabled or always on, everything appears to work as expected.

Yes, I should have mentioned. I do it after every update. I'll do it again though.

Just wondering if anybody has been experiencing this. A black box roughly the size of the map on the F10 view covers up everything on the dashboard. I can look out the sides fine, but that black box covers everything to my front. So far I've only noticed it in the A-10C2. It sometimes disappears (and then sometimes comes back). I think it's related to the FLIR as that seems to precipitate the occurrence. I'm also getting some strange corruption on the TGP in every mode, and it only disappears when I make the pod zoom in. Only been happening in the current OB patch. I've tried a repair and a clean, to no avail. It's like there's a corruption in the shaders.

MR always on leaves me with bubbly artifacts and drops my frame rate into the teens on the F-14 Forrestal case 1 recovery instant action even if I set everything to low. Disabled is also quite unpleasant. Auto is the only way that I get a good result (and it's a great result even with my settings cranked up to high with 4xMSAA, far better than SVR ever achieved). My system isn't a bad one, either. A 5800X with a 3070 and 32gb of some pretty well tuned RAM. Just an observation, but I wouldn't completely write it off as not worth experimenting with.

I also saw little to no change with either the OpenXR WMR Toolkit nor directly entering values manually in the ini file. I have not attempted a number greater than 1.0 though. Also noticed that I'm definitely seeing some changes between all of the Motion Reprojection settings. Disabled leaves me with a stuttery mess, Always On is unusable to me because I get lots of weird artifacts that I can only describe as feeling like I'm looking through a block of jelly, and Automatic is nigh on perfect in terms of smoothness and clarity.

I've owned my G2 since September last year and have toyed with it a little here and there, never quite completely happy with the performance and the graphical fidelity. Thanks to this thread, I've been flying in VR all week and it's glorious! Thanks guys, I'm very happy with the performance now!

Interesting. Maybe try a similar setup on a map where you can try the same scenario over open water?

Also experiencing this in the tutorial, with Wingwing Orion throttle. Binding it to a keyboard key also has no effect.

Thanks @Flappie.

That's a great find. He has one other F-4 video which is arguably better.

If it's not literally a difference in resolution between the two modes, then it's something that presents itself as such. It could be a problem with building trackfiles. It could be something else entirely.

I'm happy to provide a track if necessary, but the steps to reproduce this are likely easier than to run a track, given that you click on the training option and then click on the landing tutorial, followed by proceeding to fly the mission. I've attached a screenshot from the landing tutorial, taken at 200ft AGL. I don't entirely believe that this level of visibility is intended in a training mission, unless the intention is to haze new Huey pilots.

Just tried a few tests and couldn't replicate, albeit I was banking left instead of right. Single inbound Su-24M at FL350 a little over M0.9, me at FL300, banking left immediately after the initial track appears in TWS (which was usually around the 74nm mark). Bank angles of 10, 20 and 30 degrees. Didn't lose the track at any stage while the contact was within the scan volume. @captain_dalan, where are you noticing this phenomenon? Are you over land? Could you be getting spurious returns from ground clutter that distracts the radar just long enough to move the scan volume but not long enough to build a track? I'll test it a bit more when I get some time.

I agree with your suggestion about the dropping of tracks, @DoorMouse, but I'm finding TWS shots with Mk60s at least to generally have a higher PK than ever before with this current patch. This sort of scenario (nose-hot striker AI group flying trail or six feet from each other) is the only one I've yet found where TWS isn't going to be my default engagement mode. That would not be the case if the fighter AI were to adopt similar formations. Those AI don't care much if you launch a PDSTT shot at them, they fly straight and level and die.

Thoroughly enjoyable missions coming out of this generator. Well done. Been having a blast all week.

Okay, I just quickly knocked up a similar mission. Much the same result as yours, @EnDSchultz. Spot four Su-24Ms at around 100nm. Single track in TWS down til under 30nm. That trail formation is super effective. A few variations with changing altitude and pushing wide to change geometry didn't net much of an improvement. Setting the Su-24s to AFAC changed their formation and definitely made it easier to pick them up individually a little earlier, but I had nothing like the success rate I normally enjoy against Su-27s. I'm not sure whether RWS is a bit too good, or TWS is a bit too poor. @IronMike, I've included a track from this mission. It's not my finest work, but you can clearly see how easily the radar picks out individuals in trail at a long distance and seems to be unable to pick the trails out until quite late. Hope this is helpful. TWS test.trk

I've had this mod installed and briefly played with it for about a year now, but since this latest patch I've given it a really good look and I am utterly blown away with how impressive it is. It's an incredible little plane and I would really like to thank the devs for all their hard work. Last night, I was tasked with clearing out a convoy that my friend in his Hind was unable to engage safely. I laid a stick of Mk81s along it with the wonderful computer designation mode and it was glorious! Well done, guys!

Could you share your mission file? I'm trying to think of things that you are doing differently to me and there isn't very much to list. I generally don't touch the target aspect switch. It's probably best practice to do so, but it's one big difference. I also tend to set my TID range to 50 as the contacts approach that range. Again, I wouldn't expect that to make much difference in this scenario where there are no other potential aircraft to get caught in my scan volume. Have you tried changing the Su24s out for another aircraft? Su27s, maybe? I'm just wondering whether there might be some weirdness with the RCS of old AI assets.