kraze

Yeah I liked how he drives the point home that not winning AND not losing the fight is OK as long as you get out alive.

Oh I actually mean making it more like a human WSO. I don't mean giving him a radar eyes, I mean that, say, with the radar we have in F4E - a human crew member in DCS will spot contacts visually first before they even get into a "usable" radar range (which seems to be ~18 nm and less). So what I mean is biasing Jester scans towards the direction of "spots in the sky" because that's literally what I'm doing right now with the 'center' command (which seems to be forcing Jester to keep scanning that spot regardless of where the nose is pointing (naturally within limits of radar), which is sweet, so as I dive - Jester keeps scanning that area above - keep it as is, I assigned that order to a button - much help with Sparrows now). So it's not a comparison with AI, more like giving more "human-like" autonomy to Jester, because a human WSO would totally prioritize that area if a pilot spots some dark dots in there. It's just not as easy communicating "scan 11 o'clock, about 20 degrees up" to Jester. The fact that a 'smarter', more "autonomous" Jester will counter AI's advantage - is what I mean.

Good to know. Is it possible to make Jester behave at least somewhat on par with the general AI? What I mean is - not literally copying it, but simply considering that a human WSO will have a lot less trouble selecting an appropriate "doppler mode" and a scan area, so basically maybe auto-biasing Jester towards where enemies are and their aspect, while still not making it cheat-like.

OK I think I found a way to somewhat improve this situation. If you tell Jester to scan 'center' elevation - he will actually scan the boresight area with a narrowed range - detecting enemies at 15-18 nm and even maintaining a decent STT lock. Unfortunately Sparrows still fail to track for whatever reason and radar cues are all over the place, but at least Jester is working. He is still worse at it than AI F-4s though. I realize it's a dated pulse radar, but I hope it's very WIP and it's the reason the Sparrow tutorial is missing

Eh Marianas work for me because it's all flat sea Jester doesn't see / no contacts appear on radar on land maps with a lot of ground clutter even if you are below the guy and facing upwards so ground clutter isn't at play and your radar cone looks into space basically.

Eh turning off interlock is not a big problem, the bigger problem I notice is that F4E AI planes in my formation easily detect enemy planes and launch sparrows from 15 nm effortlessly, but Jester doesn't detect anything, even if I directly face an enemy in the sky, as apparently AI planes work by the different rules and their radars aren't simulated on par.

I watched a number of tutorial videos on this topic by a number of DCS players and everything seems to work so well for them, but for me Jester never seems to detect anyone on his radar. I tried flying very low with Migs being at 21k feet, so ground clutter wouldn't be at play, and ordering Jester to scan +3500 to +7500 feet up, 10-20k feet, 25 nm narrow, pointing the reticle straight at the enemy planes and pushing context button - no luck. No contacts show up on the radar screen. At best (and this happens VERY rarely) he would detect and report enemies when they are about 8 nm away, but at that point the closure rate is so high - I'd just use heaters. I also tried CAGE mode and pushing the context button while pointing the reticle straight at the enemy - and about 5 seconds down the road Jester would lock something. But whatever he locks up there in the sky - it's not an enemy plane, the circle will take random sizes and RMax will jump all over the place - and Sparrow will never launch. The only time I ever got an enemy with a Sparrow thus far is when I selected a CAGE mode, hit nose-wheel steering for auto-acquisition and then actually got to launch a missile hitting the MiG. So I take it I'm doing something really wrong, because it looks really effortless in videos.

and here I was really thinking I'm that bad of a pilot after 2.8 supposedly made AI planes behave less UFO. Although admittedly YoYos work wonders after the initial merge and I can put that heater reticle almost immediately on the enemy plane after going back from that maneuver - but if I somehow mess that up - an AI MiG will then run very tight circles around me until one of us runs out of fuel.

Yeah I agree, it's pretty bad. However did you try setting the resolution of an actual window on the desktop when you are in VR? E.g. if you desktop resolution is, say 1920x1080 - and there is DCS running in a window which takes, say, 1280x720 pixels - did you input the window resolution as HB UI override resolution?

I'm on Quest Pro and the key is basically to set UI size override to whatever window size is shown on your desktop However I do have another issue. Not only the wheel isn't centered horizontally (which may be fixed by trial and error with an offset), but it also is not centered vertically, so it appears above my center of view, making it unusable with head movement, but at least my HOTAS has enough hats to help with that.

Resolved. Needed to turn motion blur off. Looks like it messes up rendering in VR.

Hi, using recommended force VR force XR flags and running MT DCS exe. When entering the menu in VR everything is fine. I can see it floating right there and 3D hangar is visible with no issues. However upon launching any kind of a mission, even as simple as free flight - I get really hard glitches like having whole 3D world rendered in the top left 1/6th of the screen, but with no cockpit, the rest of the screen is black, however plane's green HUD is visible and leaves traces all over when moving my head around. What can be causing this issue as it happens only during missions? Specs: Win10, i7 10700k, 32 GBs RAM, RTX3090, HP Reverb G2 v2

Hmmm, it appears that after installing different memory - OC settings for the CPU were reset and it had a ceiling of 1.21v versus 1.31v I've had set before for 4.8 GHz. Maybe that's the case. Lemme test.

Overclocking only the CPU, not GPU. 1080Ti is running at a purely stock settings. Had an older driver when I've noticed crashes, updated to the new one - they are still there. As for OC'ing CPU - it was at those settings before and DCS was running stable - the only things that have changed is me not playing DCS for about 4 months and also replacing 8x2 GSkill Ripjaws V 3000 MHz with 16x2 Ripjaws V 3600 MHz

CrashLogs.7z Crashlogs plus event viewer app error report plus mis1.miz - basically I take off from the carrier, fly for about 5 minutes, return to the carrier group and just a few minutes into the CASE I recovery it crashes - every single time i5 9600k @ 4.8 GHz / G.Skill 32 GBs RAM 3600 MHz (stock XMP) / GTX 1080Ti with latest drivers / Win10 x64 on 850 EVO / Game on 860 EVO / no mods whatsoever / did 'clean' and 'repair' - didn't help