Czar

Words from community managers are in this thread + others talking about it.

Why are you posting this on wishlist? They are planned already. "Planned Iraq North Features during Early Access: H2 and H3 airbases to support Operations Desert Storm and Iraqi Freedom Improved roads Haditha and Mosul dams Oil fields Continued refinement of 3D object placement to ground texture" At:

RCtrl + Pause

I was replying to exactly for the BVR claim. Read your comment that I replied to.

...and great visuals for a nitendo 64 esque throwback low poly sim for today. We... The SIM needs variety in models, especially updated visual wise. The current 135 is showing its age very quickly. I'd love to see something from CH to this regard. I'm a bit tired as well on sorting MPRS and non MPRS to figure it out where I can refuel my plane whereas in real life 135 MPRS would be enough but in DCS there is some sort of limitation at servicing boom and basket on 1 model.

To add a bit more. Where you get the info that's not proper behavior? Hornet's velocity vector will re center horizontally in certain scenarios of high horizontal drift from the plane, IIRC, for better reading by the pilot. Note that other 'games' out there executes the HUD elements in a complete disregard to what they are in real life. Some removes completely the velocity vector from the ladder in lateral drift scenarios, others don't. Some worse examples out there too. Check this footage from this doc from the A-7 HUD. 3:27 link starts from the timestamp. The center line of the plane is indicated by the vertical line bellow the heading tape, in this case low portion of the HUD. Notice how the velocity vector and the ladder together deviates from it due to the cross wind component.

Like this?: You just experienced a cross wind component shown by the velocity vector. Page 90 from the F-16 manual. It features a typo which it should read item 13 instead of 14. But read the item 14 on that list. Welcome to modern jets. Crosswinds can get MUCH worse than this. The flight path marker/velocity vector can actually get out of the HUD area indicated by an 'X' or cross over it, which means its horizontal deviation is higher than indicated. (yeah, I should of have de clutter the hud. Close to 'RIP' but it was alright.)

You don't need to fully install DCS anew or finish the download on a new drive to do that. Just start the download process -> cancel/exit the download -> copy the old DCS files from another driver over the new ones (overwrite everything) -> resume installation by booting up either the installation file you got from the DCS site or the new shortcuts it just created. DCS is properly 'installed' as soon as the download begins. I hope it helps.

You have a VA monitor. Some of the deepest blacks out there. Anything above 0-0-0 rgb value, even by 1, will pop out. I had similar issue on a old VA monitor, now I only have IPS ones. I can't really 'see' the problem now, but I know what you're saying, I believe. Tip: You need to reduce gamma or crush some blacks for the banding to disappear. I dislike those VA screens but they are awesome to watch movies in a dark room. In the end, the banding will still be there but you can mitigate some. It is a problem inherent to the VA screens. I'd say, enjoy their strengths. Likely an IPS monitor or anything else but VA.

We've already posted last year on this very thread extensive tests. Reducing terrain textures doesn't mitigate the issue. Thanks.

It is safe to say it won't be a redfor heli because of the current restrictions on selling their helis in Russia.

Not a solution at all. Anything but high textures blur out the cockpits for the Huey and similar aged modules to a major degree that you can't read words on it. Heavier maps are fine on a 12gb VRam. New cards are coming with less than 12gb. Omitted optimization not on par with the rest of the products available. Needing more than 12gb of VRAM to be able to use older modules on the map in the economy today is NONSENSE. Especially if the map visuals are not the current benchmark. No way I'm buying a new card just for the VRAM and because a dev doesn't optimize their work. The issue is intermittent. It is not a RULE to saturate the VRAM just because of the map at every sortie. It is more or less a 50% chance. The map doesn't offer any visual quality above the rest to warrant such a bump of memory needed. It IS a bug. Anyone can make an asset that can bring any system to a crawl intentionally. Optimization needs to be accounted or it ends up in the bug category. 12gb VRAM + 64gb RAM and I can't put the textures on high on a single map. My ass... The "Textures" setting has been found the one to be changed. It is the setting that wrecks cockpit readability on old modules if it is not on high. The "Terrain Texures" will blur a bit the terrain BUT still not enough to make room.....or something else is broken outside of Vram usage. This can cause a lot of confusion. It IS the map, but changing "Terrain Textures" won't do much. I have Iraq. It is in its own way heavy near cities and have a lot of satellite imagery, but this issue doesn't occur at all.

In addition, you can move the active window between screens on a multi monitor setup with Win + LShift + Arrow keys . It is often handy.

I agree with this thread. It will only get worse from here if ED doesn't intervene in things like this. I doubt the RWR is even finished also. I can be wrong...

There is also an object list through one of the left hand side buttons menu that you can filter units for selection without having to click the icons on the map. Yeah, the thing of controllable aircraft on top of each other on the carrier is a pain. If you get used to using the list, the issue might get less noticeable while the ME doesn't get an overhaul.

This is beyond amazing!!! I came across your video on youtube and followed the link here. I'll add this to my DCS asap!!! terrific work.

I personally don't think photogrametry or laser scanning is directly correlated to bad performance. The meshes don't necessarily have more polygons, it is just the polygons are much closer to where they should be in with a different workflow. If that makes sense. It is perfectly understandable to be wary of new software releases performances with the current global prices in hardware. I too relate to that.

I'm having the same issues as of late. I did post on this thread (I think) extensive tests and videos showing the problem. GPU load goes bananas bellow a hard AGL altitude which is around 900ft. Late posts pointed at VRAM load although I have a 12gb VRAM card. I've let this problem go then... It got better after the VRAM usage dcs core update or it was a placebo effect as the problem is intermittent. Lately the issue came back and wasted me a 40 minute mission on the F-4E. It is like pushing on the brakes on DCS enjoyment even though I have other maps to enjoy, this one is a recent purchase. I don't really see as a hardware limitation issue as 12gb of VRAM should be very well enough to handle this map, as it handles all others well... New cards are coming with less than 12gb VRAM and a lot of more reports are going to come about this if the developer doesn't do something. For me, it is a bug, being otimization or not. Absolutely it should be given of the highest priority to fix because it wrecks frame times inducing a giant amount of lag on commands especially head tracking. Reducing textures settings is a NO GO. Other maps are fine and reducing textures will result in unusable cockpit on modules such as the Huey and similar aged. I don't plan to be changing settings every time prior to launch a mission either. Dissapointed about this, as the map is glorious on its own strenghts.... I'm experiencing similar results here too.

Best news since DCS Iraq, for me. I'll sure grab it when I can. Hardware upgrades recently made things a bit difficult for software side purchases on my end. I find this a valuable milestone for ED as it is a REDfor fighter jet, and I cheering for its success for much more RED planes to come after. The player base is surely in need, regardless of their favorite side/country of origin for aircraft. Done right, it will enrich everyones experience, imo. Great news that it is coming out of the oven finally.

They were selling DCS modules there. It was also the main hub to get the manuals.

It is not only VR. It is global....2D as well... Known for ages. There is a improper scaling at distance on the shadowmaps resolution for performance optimization. It is too abrupt. Shadows at maximum settings, btw. Bellow, compare shadows on the F-4, which is near the pov to the tomcats, which are farther away.

Good news. Anyone of those is the right one as long as it is updated to the latest version. DCS 2.9.15.9599.1 https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.15.9599.1/ You probably updated from old builds before the Open Beta & Stable merge. You can wipe those old shortcuts and make new ones to the executable in the 'bin' folder. There is no Open Beta anymore.

Where did that come from?! F-18: Finland, Canada, Switzerland, Kuwait... F-16: Greece, Italy, Poland, Turkey, Israel... etc... These have dynamic numbers besides USA.

@virgo47 Orbx didn't make the map, nor any of their dev teams. The map was published under Orbx but whoever actually fixes bugs are the developer that did South Atlantic map as well. Perhaps trying to message/mention the developer is a better path than trying to contact Orbx itself. Imo, this kind of publishing makes things harder and is a bit misleading overall, but it was what the developer could do to make those maps into DCS.