unltd

Just ran the F18 alert 5 mission. Just about all SAMs and radar AMs miss now, which is sort of interesting because you get to see ships hit, but seems to me a bug. Phalanx and RIMS seem to work fine. What gives?

First, check to be sure you are on the correct radio channel or have checked the simplified radio box in game options. Next, be sure the flight/wingmen have seen the enemy. You should receive a bandit contact call from them. After that, you can order them to engage or cover you and they will respond with an engaging call. If they can't see the enemy, they respond unable. Also, you can order different tactical splits that are helpful.

+1

+1 The issue is very apparent at night. It's like having dirty glasses but in 3d and is very disorienting. You can mitigate by decreasing gamma but then can't see other stuff.

Ocean wave energy remains long after the event/wind that created it dissipates. Many days I enjoy surfing waves in California created by storms many thousands of miles away in the southern hemisphere. Local conditions are mostly insignificant in comparison and usually only generate minor surface effects. If someone is actually considering recoding this in the ME then it should be decoupled.

Another note: quick mission with many units is totally playable again. Prior to patch it was a slide show. Ground units are moving normally etc...

Great patch! Vast improvement in VR FPS. Now getting a rock solid 40fps and hitting 80fps on occasion. Not seeing the decrease on Super Carrier mentioned above. This definitely has that 2.5.5 feeling again. I'm starting to think people with bad fps don't have their windows and/or their nvidia settings correct for VR.

Now with the closed beta group, isn't the so called stable release version sorta like a legacy version and the open beta really the release version especially since mp servers run it and all the new modules require it? Seems like we have a semantics issue now that may be compounding the communication issue. Perhaps all we need is a name change...

Thanks!

Request for sticky: Why the beta exists explained by ED's Nick Grey For those interested in why the beta exists and why we are testing it please watch this video by the Grim Reapers interviewing Nick Grey of Eagle Dynamics: particularly from 16:30 to about 31:00.

bump

Love the addition of the crew in the B17's. Although, when they bailed out, they were still there.

Negative ghostrider the pattern is full, go around. This patch is definitely worse for VR. Some issues: 1. Mipmap level of detail problems especially with damaged aircraft...you can now see enemy aircraft flying at certain distances with missing wings, large pieces of the fuselage etc. then they pop whole again when you get further or closer. 2. Shadow mipmaps twitching back and forth between different maps causing significant judder and stutter. This was fine in 2.5.5 and 2.5.6 prior to this patch. 3. Ground object details suddenly popping in and out causing judder. 4. There is a distinct level of detail bubble now very obvious around your view point that was not so visible before. 5. Also moving your head slightly in VR causes an abrupt change in shadows very similar to the way clouds used to change popping in and out of view depending on moving your head slightly. It seems like the graphics engine is missing certain level of detail texture maps. The smoothness is gone that existed in 2.5.6 from March 'til now. Way more ASW is observed. Way more stuttering from texture loads. I messed with visibility ranges and texture/shadow settings to see if I could compensate...no joy. On a positive note the P51 engine pop is gone!

Fixed in open beta, YES!

So what combo do you need to hit to win in the F-18? I scored 3x f-18s but no joy, wtf???? I thought the chairman in the radar picture was pretty good but this tops that by far. Definitely put my heart rate up when I realized the gear hadn't gone down lol. (PS did get the gear to go down with the emergency release). I love it that you guys still have a sense of humor during all that's going on, and definitely lifted my spirits today! Thanks ED, nice April fools! wait JACKPOT....ejection!

Brrrt! like a laser beam now! You actually have to aim at the target...lol...going to be a lot of griping about that. I like it!

My TH Warthog Trottle# 19823 main board failed and Robert in Canada did a quick repair. Just a shout out for his service. I highly recommend it. His service is listed here: https://www.ebay.com/itm/Repair-Serv...-/233195609114

In business terms this plan looks a lot like this: Gnomes collect underpants + ??? = Profit

Make sure you haven't alt tab'd focus to another app that may be running. If DCS is not the focused app, buttons won't work.

This thread brings back lots of old memories of similar arguments in various flightsims concerning the FW190...Air Warrior, Aces High, IL2...always the view or angles are wrong...always the developers crying we built it exactly like the real thing...always the developers not quite able to simulate all the factors: realistic cockpit geometry(solved early on), 6deg of freedom head movement(solved with trackIR), actual flying angle of attack (lots of debate here, seems solved in DCS), and now glass refraction (probably need to wait for ray tracing). I wonder if we can get the DCS A8 to do that snap roll trim on a slider trick from Air Warrior that would put you on the tail of a Spit every time...lol.

That's very interesting Strong05, I used to use the high preset and turn things down, and that seemed to do the trick of adding about 10fps...regardless, it appears there are some settings the presets adjust that have a significant effects on overall fps. I have long suspected such. So the question is, which preset works best?

+1 noticed this bug too. Employment range is much reduced.

Even with a 980ti and Oculus Rift CV1 the DCS experience in VR was far better than my track IR setup with 3 monitors. Now with the Rift S, I've disconnected the Track IR and two side monitors. It only gets better from here...VR baby. I'll probably ditch my last monitor with the next bump in VR res...I feel for all the builders with their cockpits and projectors...although a 3D motion rig would be a cool add...

Just re-iteration of some things that have been proven by others' testing: In VR: 1. MSAA has a serious negative effect on FPS. 2. Shadows on the ground and in the cockpit have a serious negative effect on FPS. 3. PD settings above 1.2 on Rift S or 1.5 on Rift CV1 have a serious negative effect on FPS (can't speak to all the others) On my system with MSAA and Shadows OFF I can stay pinned at 80fps mode in nearly all situations. As soon as I enable either, I drop into 40fps ASW mode. With both enabled I begin to see some stutters. While the various other graphics settings do affect FPS they seem to be in the 1-3fps each. Turning ASW off makes it a stutter fest unless FPS are pinned on 80. Setting PD above 1.2 on my rift s kills FPS without any noticeable visual clarity benefit. some other settings: vsync: off Civ traffic: off ground clutter: 150 trees: 70% Visibility range: High Anis. Filtering: 16x*keeps the lines on the runway from fading out Preload radius: 120000 Chimney smoke: 0 ***Also enabling Windows game mode gave me a significant FPS bump (windows 1809) Check your PD, shadows and MSAA settings.

Anyone here try placing a sound reflector near the headband holes sort of over the ears? I have noticed that if I hold my hands up there cupped, the sound quality improves tremendously. There's got to me a fabricator here that's done this already...love to see it/buy if it's been done. Meanwhile, I will tape on some card stock and see how it sounds and report back.