SonofEil

I'd always noticed the altitude errors as well since way back at A-10 beta. I can't for the life of me find it but someone wrote a similar thread, threw a bunch of math at the problem and determined that there is a slight, consistent error with how DCS itself calculates altitude. I don't know if that ever got fixed but I assume not since I've recently bumped radar altimeters against the baro (adjusting for the differential) and they can never seem to agree, or even disagree consistently. I'll post back if I can ever find that damn original thread.

I've experienced what you're describing also, but only at high wind speeds. In one mission I had Stennis maxed out at 26 knots plus a little headwind, maybe 8 knots, and my F-18 was being blow and dragged sideways across the deck. A thirty-forty knot wind shouldn't be enough to dislodge the bird. Enough to make taxiing more of a challenge, sure, but not to send her skittering. Is your problem similar or are you having these issues with negligible wind influence?

Regarding that specific statement, this is why I’m most excited about the Tomcat. I love the Hornet and ED is doing what they do best; making you feel like you’re flying! But the Hornet is a FBW aircraft that trims itself and has push-button spin recovery, etc. To me the Hornet isn’t aerodynamically interesting. It is a very interesting modern weapons platform. The Tomcat is going to satisfy my flying curiosity though.

Sorry man, you’re absolutely wrong. They add a thing called immersion. It’s a core component of any sim and I absolutely appreciate the amount of work and detail that have gone into the new maps. In fact one of the biggest disappointments of the last few months is the lack of upgraded buildings and urban areas in the new Caucuses map. To me it hurts the immersion having this beautiful new terrain texture full of trees and high mountains but still populated with towns from LOMAC. I wouldn’t delete a single street sign from PG or Nevada. But I agree with you they should be user scalable, and right now there are undoubtedly performance issues. PG is barely two weeks old for pete’s sake. Improvements are coming. And yeah, it’s often two steps forward, five back with ED, but we’ll get there. Just chill for a little bit, quit trying to unmake our new map, and enjoy your BETA access as best you can.

Hard freezes here too running todays patch. Mission is a simple PGM single player in the F-18. Cold start on Stennis way out at sea and waypointed to Abu Dhabi. I'll be cruising at ~20k, maybe twenty-thirty minutes into the mission when the sim freezes. It's serious enough that DCS won't even allow access to task manager even when alt-tabbing. I have to use my lock screen hotkey then a full computer shutdown from lock screen. Other assets on map are a bunch of coastal red and blue sams. No active triggers, airborne threats, or tasks of any kind. Simple A to B flight. Same as the other posters I have no crash logs or tracks to give. : (

Problem persists in today's update. :(

Ok, just figured it out myself, also after ~2 hours of messing around searching forums, YouTube, etc. Move your throttle to the cutoff detent on the appropriate "THROTTLE - OFF/IDLE". Set your left and right throttles to the left and right THRUST axis in the Axis Commands submenu What a frickin pain that was.

A profile, or at the very least, guidance, would be appreciated. There are 20+ ‘Throttle’ entries on the Control Options screen. None of them are binding to my Warthog throttles so I’m still stuck on the ground.

I haven't done any objective tests but yeah, I causually noticed I can see trees 'growing' out of the ground much closer than in previous updates. That's something that, while I'm not necessarily happy about it, I can live with for the time being. The static objects being invisible until you're practically right over them, on the other hand, breaks about half my missions.

With the latest update Static Object visibility distance has been set to <10nm. This would make some sense with small items like flags, tires, etc., but it's a serious problem with large objects such as compounds, factories and warehouses. Even when attempting to view static objects on a targeting pod they won't blink into existence until <10nm away. Tested in both Caucuses and PG. Is there a config value I can change until this is fixed? It's messed up a lot of my missions. Attached is a sample mission, Tech Combine placed in the center of the X runways. DELETE View Test.miz

1) Ok, the reason you're seeing all the comments is because people don't understand what SSAA is or how to use it, and ED hasn't provided a lick of guidance or explanation . A lot of us are basically getting what we can from wikipedia and anonymous 'forum experts', which of course is often contradictory or just plain wrong. Not everyone here is a software developer nor should they have to be to enjoy the sim. 2) After some testing I discovered that it wasn't working for me because I'd forgotten to turn MSAA off. 2xSSAA + 4xMSAA = No Workie. Mea culpa. 3) As expected, I still get noticeably better performance with MSAA. With SSAA on, flying over Dubai turns into a stuttery mess. The sea floor also doesn't render properly. Areas of the sea floor show up as weird geometric patters that seem to be tied to cockpit shadows, in other areas the sea floor isn't visible at all. I'll try to provide some screenshots in a little while. 4) If SSAA is only for lower res monitors, takes a huge amount of resources, negatively impacts performance, and provides negligible graphical improvement over the alternatives...what on earth is it for and why has it now been implemented in DCS?

Yes, but I accidentally left out that I'm on a ten year old 1080p monitor. According to the above logic SSAA should be perfect for me, but it's not. It literally makes DCS unplayable. I've never seen a bigger more consistent performance hit from any other settings option. Edit: I mean, it's nbd. I just turn it back off, msaa back on, and I'm back in business. If ED decides to force SSAA then we're going to have a problem.

Thank. God. And if we could expand upon that to scale-appropriate icons for all user-placable objects in ME then mission building time could be cut by half. Long overdue.

Nope. I clearly have a rig that can run DCS in higher resolutions and I'm normally between 40-60% card utilization. If I turn on SSAA at all it's constant jitters, <20fps, and no noticeable improvement of image quality.

I haven't found if this is already posted/announced, but BIG SMOKE IS NOW TRIGGERABLE. It's not the most intuitive approach, but it works. Here's the method I've been using: Create a static object, warehouse, whatever. Create a trigger zone directly over the static object, warehouse, whatever. Create a trigger. Under "Conditions" select Unit Dead (your static object, etc.), then under "Actions" there's a new option called Effect-Smoke. Viola, big smoke is triggered on destruction of the unit. Caveats: There's still no late activation option in the static objects list, so 'activate static object' is not used. Don't use the 'Group' conditions on static objects, the smoke will trigger immediately. 'Group' conditions appear to function properly with non-static objects. Smoke only forms in the center of the trigger zone assigned to it. As such, you can destroy a building and have the smoke triggered on the other side of the map if that's where you placed the zone. The size of the trigger zone might have an effect on whether the smoke is triggered and/or visible. I've had succes with a 500 foot trigger zone and large smoke and fire. HUGE smoke and fire doesn't seem to be working, I get a small smoke only. This might have to do with zone size, but haven't tested that far yet. And that's it. Sorry if this is old news, but it's new to me.:thumbup:

Wags has said these maps are built with expansion in mind, I expect at some point they’ll increase the details outwards. Hell, you can actually see Edwards AFB on the current map, and even San Bernardino. They are a very-very-very low res mesh only of course, but they’re there. It’d be fantastic if we could have a Nellis-level detailed Edwards at some point in the future, though I expect if it ever happens, it’s years away.

Thanks for the reply’s. My drives are all solid state, Windows on a M.2 and DCS on SATA. I built my machine specifically for DCS 2.X and it was running great up until 2.5.1. Prior to the .1 update my graphics card would utilize 75-100% of the available memory, depending on scenario, with lower power consumption and GPU clock. Since the latest update my GC memory is capped at 4.5gb and the power and clock are maxed out trying to make that work. And this is with zero assets on the map, just me in a F-5 flying around the trees in daytime. Oh, and I’m only using an old 1080p monitor, no 2 or 3 or 4K glass.

That’s the problem though. I used to run stutter free, now in 2.5.1 low level flight is nearly impossible. Not to mention the fact that my graphics card, which was purchased specifically to handle DCS, has been effectively crippled by two-thirds, something I don’t appreciate. I’d like to hear from someone in-the-know about what’s going on here.

My video card memory has been capped. I've had a noticeable performance loss since moving from 2.5 to 2.5.1. While flying in the trees I get stutters and lags that I never had with the previous versions. I also have microstutters while taxiing. I ended up tracking it down to capped memory usage on my 1080 ti. There are 11GB available from the card but since updating to 2.5.1 my card maxes out at 4.5GB memory usage. My drivers are up to date. Attached are screenshots of my settings and card performance while flying low level in the mountains behind Batumi. I've performed tests in other graphics-intensive games/apps and usage is normal and not capped at 4.5GB, only in DCS is this new issue apparent. Though it shouldn't be, could this issue be related to the new memory management system? Anyone have any ideas or suggestions about what's going on, how to test it, whether this is a know issue? I haven't found anything in a forum/reddit/google search.

Ah. I'm under the impression their intention is to make the Harrier as complete as possible. Standard omissions such as IFF apply, of course.

I’ve had the “engaging bandits” message get stuck on a loop once or twice, but when I give my wingman the RTB command maybe 75% of the time he’ll get stuck on a “2, RTB” loop until he lands or (more often than not) crashes. The only way I’ve found to shut him up is to retask him. I’ll usually tell him to “orbit here” until I land and end the mission. Edit: Ha, didn’t realize this was a P-51 thread. I’ve encountered this issue with both the F-5 and Harrier. That probably means the bug is module agnostic.

Is that a question or a statement?

I’ll agree with the consensus so far. There are a lot of buttons and switches that aren’t yet implemented or are half functional, but most of those fall into the “full study sim” column. As a flyable aircraft, as in takeoff-navigate-land, it feels quite mature. I’m a big fan of DCS primarily for the excellent simulation of flight physics and Harrier is one of the most aerodynamically interesting modules on the platform, nearly equal to the Black Shark imo. (This is also a reason I’m super hyped about the Tomcat and not so much the Hornet.) The Harrier is a pure joy to learn to fly and I think RAZBAM is on the right track to completing a must-have module.

Nah, tracks haven’t been fixed, twelve+ years and counting. You just got lucky on that one.