Jayhawk1971

Yeah, I was determined to save the track file from mission 6 when I checked lead for holes and found two pristine bombs hanging from his wings, but after landing I just forgot (I clicked "end mission" out of habit). Next mission where I have to bomb something I'll pay attention, and save a track file!

On mission 7 now, no more collisions (that I was involved in ). I am hanging back a little, letting the AI do their thing from a safe distance. Pre-emptive combat spread, if you will. I also started to watch Wolfpack's videos, and they also taught me a lot about the ww2 AI. Really like the campaign so far, especially the reality of it all, just the missions as they happened in real life. Great concept! Also reading Len Deighton's "Goodbye Mickey Mouse" (again), to get me in the mood. (just skipping the more "melodramatic" chapters). I'm even getting the hang of landing the P-51 properly (slowly, but getting there). Three-point, that is. Wheel landings, not so much. [BTW, AI still doesn't seem to drop their bombs, post recent patch. Thankfully, I'm pretty accurate with my bombs, and make the whole group look good ]

I like the new visor very much (in VR, Vive Pro), and also the "wearing a helmet" feeling. I agree that he visor's edges could be more blurry. I do find it reasonable though to make it optional. The idea to link it to the pilot model is IMO good: if you have pilot model enabled, you get the peripheral helmet, if you have it disabled, you get just the visor tint if you "pull the visor down". Shouldn't we see a blurry oxygen mask?

Hi, this campaign is only my second foray into DSC WW2, first having been BNBoB. But there I was flight lead, so friendly AI was more predictable. The reason I ask is because it seems to me that Warbird-AI is even dumber than Jet-AI, and I would like to ask for some "best practices" dealing with it. The trigger for this post: I was blotted out of the sky by White 3 (I strongly assume) during mission 4, after striking the marshalling yard and while being in the process of forming up on White 1 and 2. I was not even close to them yet, over a mile at least behind and to the right, way outside of what would be 3's position in the formation. I didn't see 3, so I assumed he had been shot down by ground fire. Anyway, I was just flying along, when - bam - 3 crashes into me from behind. Just like that. I was flying straight and level, and not at all in "his spot".* [I double-checked that is was the correct flight by temporarily switching labels from dots to text] In the past I was occasionally rammed by jet ai as well, but at least I could see why (it was always in rather close formation, while refueling, and once during a battle damage check). But never out of the blue, in the middle of nowhere, not even close to being in formation with anyone. So, could anyone please give me some advice where to fly, or what "zones" to avoid? I could of course write to ED and ask them to fix their AI, but at this point that is like telling the rain to stop being wet; better to learn the quirks of the AI and work around them. * Obviously, I somehow must have been in the way of the AI's "rejoin flight path", but how am I supposed to know what that path is? Was it just a really unfortunate coincidence, because you probably couldn't do that deliberately, if you tried: guessing the exact same intersection of flight paths, both horizontally and vertically?

Alright, from my end, I'm good to go: ED, initiate transfer.

Yes, for me the game changer was the new kneeboard. Very immersive.

THX I'll try that.

IDK, when I compare the VR headset (Vive Pro) to flatscreen, my impression is that VR is more "contrasty", blacks seem more crushed. It is noticeable at night (in game) and with dark cockpits, like the F-4.

And for OLED VR lenses?

For all modules....

Very cool, thank you for posting it here. Also, very creative intro! (Did you film yourself on a treadmill? )

Had the same happen yesterday, of course I forgot to save a track, because by the time I made it back to base I had forgotten about it momentarily. Not that this nice, uneventful mission had anything to do with that.... Cobweb Blue 4 was taken out by Flak crossing the coast, so I was only with 1 and 3. I alt-tabbed out and managed to close the notification windows (by pressing "Enter"), and the mission resumed normally, DCS did not freeze. Whether or not 1 and 3 actually engaged the target with their bombs, I don't know. I *believe* I saw one of them on a strafing run (saw tracers going in). Other than in the previous two missions, the AI did climb significantly before attacking the ground targets, at least above the first cloud layer. IDK if that helps.

https://dalatpalacegolf.com/history/

I suppose that's because Heatblur actually thoroughly scanned the cockpits of the Viggen, Tomcat and Phantom. So those should be as close to reality as possible. I believe the older ED modules (A-10C, for example), that pre-date the widespread use of VR are the ones giving VR players some problems.

As far as I could find out (and take that with a massive grain of salt!!!!), there's IPD, used to adjust the physical separation of the lenses in the headset. And then there's the setting within DCS, which apparently is ICD, and which changes how you perceive the digital world in DCS. Parallax effect, I suppose. The upside of this setting is that you can adjust the perceived cockpit size (and objects within that cockpit) to your personal liking. The downside -at least in my case - is that, with smaller values, depth perception gets worse, as objects (such as, for example, the carrier, or airborne tanker; heck, the world itself) appear larger, or closer (?). Nice for enhanced visual clarity (lights, details), bad for judging height and distance. I experimented with this, and found out, to my chagrin, that in the Tomcat, a "force IPD" setting of 60 feels a bit better than the default, yet I found I lost depth perception somewhat, making AAR and trapping a little more challenging than usual (usual = a breeze). So I reverted back to default. It's a compromise. If anyone has better information about this, and/or a clear recommendation on what to do, feel free to both correct my post, and provide a solution for this annoying problem. The worst-documented feature in DCS! One thing I am still not clear about: is the "default" value just some "one size fits all" value ED came up with, or does the IPD value set for the headset (either physically, like with the Vive Pro, or via the headset's software) get "transmitted" into DCS, via the headset's driver? For example, if the IDP I've set for my headset is, say, 65, would the default setting (force IDP unchecked) also be 65, or would it revert to whatever ED thought to be a "middle of the road" setting (IIRC, unadjusted the value in the box said 63.5)?