derodo

Increase drag to help the aircraft slowing down maybe?

Hey! Just wanted to chip in and just say I’m having a great time playing this campaign. Flew the first 4 missions and they really are my cup of coffee :P Not uber complicated, clear and concise and, overall, FUN to play. Keep up the good work!

I noticed this too. I think it needs to be pressed for a little longer. Short clicks don’t seem to work, but if you keep the button pressed for a little while it always works on the first try. Hope they fix it at some point (or maybe it’s just how it works IRL)

This! +1

Maybe you have the “global external lights” switch off? Don’t remember the exact name on the bindings, but its the switch on the left side of the left throttle axis. If its aft, no external lights will turn on. I usually have all them on, and just flick that switch aft when fencing in :P

Much better video card = same frame rate... Exactly like my setup. One logical core maxed out while the other 7 are not doing much...and the GPU at 60%. I’d say you’re CPU-bound, just like me. We don’t have too many options but cranking down CPU-heavy settings (trees, civ traffic, etc) and hope the Vulkan revamp to kicks ass and allows for better multi-core performance. [emoji20]

What Tippis said. And hopefully you only need to mess around with the axis tunning once per aircraft. No big deal...granted there’s no patch breaking all your bindings as it happened not that long ago :P At least we have options to configure our inputs to our liking. In that respect, DCS is way superior to similar software packages where the input bindings are real pain in the ass to manage.

Sudden lighting changes That could be the reason, yes. I’ll try to pay attention to the clouds next time . By the way, the “Global cockpit lighting” has nothing to do with it. It happens with and without it enabled.

Don’t know if this is helpful, but that same thing happened to me in the stock SU-27 campaign. Completed a mission, exited. Went to play again and the mission I got was the same I was supposed to have just completed successfully before. It happened twice; with different missions (same su27 campaign). Back in the 1.5 days; never witnessed that again since 2.5.

Don't know how to explain it, so I'm attaching a screenshot. It's been a while since I flew the P-51D (back in the 1.5 days); today I took her for a spin for the first time since 2.5, and I noticed a very werid thing around "red things" in the canopy; they look pixelated, way too much; and they are the only things that look like that. It's really weird; nothing critical, but annoying. You can see it clearly in the "Oxygen emergency by-pass" valve (the red geared thing on the lower right). It's the same with the other "red things", including the "Canopy Emergency Release Handle" (not as obvious in the screenshot). Jumped in the F18 right away just for checking the difference, and "red things" there look just right, which makes me think this is somehow related to the P51. Anyone else having this?

@Sub2K I know...it’s such a letdown. The impact of CPU/GPU stalling is definitely there, and it depends heavily on the nature of each software implementation. In the case of DCS and a hw setup like ours, it really matters. Again, keep calm. I’m sure you’ll be able to get a decent setup, maybe slightly lower quality than mine, but not much. I’m pretty satisfied with how DCS looks now. I have absolutely everything maxed out except for the trees; it looks gorgeous at 1080 (don’t yet have a 4K monitor). And if your rig is overclocked to 4Ghz...you might get even better performance than me, as I just have my i7 at its default 3.8Ghz. But then again, it’s a generation ahead which I suspect might help too. I won’t upgrade CPU/MB until ED releases the version with the new Vulcan based renderer. Then...I’ll see how it goes. I still have high expectations...time will tell.

Well...I can tell you my i7 3700K is not enough to use the full potential of the GTX 1080. That’s a fact. With the settings I have (and I’m comfortable with) the GPU usage doesn’t get higher than 60-70% on average. Which means the CPU is lagging behind and is not able to feed enough draw commands to keep the GPU busy. I can see it going up to 90-100% usage under certain conditions, when I get really high frame rates (over 90)...single player, simple missions, high up (so almost no trees), etc. To complete the picture, as I mentioned before, I can clearly see just one logical core doing all the work (peaking at 90-100%) while the other 7 sit idle (maybe going up to 25% from time to time). So everything fits and makes perfect sense with the results I see in DCS. As I said, I’m perfectly comfortable as it is right now. I’m really REALLY looking forward to the Vulcan refactoring; I really think it will help us get better performance. But right now it’s what it is. So far, my additional advice is (apart from checking power settings, vsync, etc) to bring down the “trees” slider in the graphics options. It’s so critical in my case, sliding it to full left (no trees) I get ludicrous FPS; don’t remember the figures because it looks awful without trees so I just moved it back around the middle (maybe a bit further to the right) where I can see quite a lot of trees but still get decent frame rates (averaging 50 I think). Hope this helps you getting better FPS; I know how it feels when you launch DCS after installing a brand new powerful GPU and going WTF?!?

Ok so it’s not just me. I thought I was going crazy, because it doesn’t happen every time. Some times it just works as expected. Some others it does not; but I haven’t found a reliable way for reproducing it. Must be a WIP thing then :) So it will be fixed at some point.

What CPU do you have? As we already know, DCS is still very CPU-bound mostly because it’s not very good at multi-threading. This same thing happened to me (sort of) when upgrading my ATI 7750 to a GTX 1080. I expected a great performance boost, but it just went up so little...I was disappointed. Having a closer look at it, and asking in the forums, everything seemed obvious that in the end: even when the overall CPU usage was around 30%, the ground truth was that all the load was being handled by just one logical core; while the other 7 remained almost idle. And the actual GPU usage never went higher than 60%. So the bottleneck in my case is my i7 3700K. My FPS are around 50-60, sometimes over 100; and the biggest game changer was tuning down the “trees” slider. That’s by far what makes my CPU busier; so a dipping it down a little really helped (I have to admit I got greedy and moved all the sliders and options to their limits after installing the 1080 :) ) On the other hand, after playing a while with the new card I could really tell the difference in performance; before the 1080 everything slowed down to 10FPS when zooming in, now everything is rock solid and consistent at all times. Long story short: right now you need a really powerful CPU to take the most out of a powerful GPU. I’m looking forward to the Vulcan thingy ED is working on; as that might help improving multi-thread performance (hopefully).

Mmm...maybe it’s not that obvious. AFAIK, as of today, more resolution means worse spotting...or so I understand (I’m currently playing @1080p so I can’t really tell the difference with a 4K setup).

I think we are still missing one feature we had before. I used to have labels disabled (when it was just a checkbox). Always flied without them, and only enabled them from time to time via SHIFT-F10 if things were terribly wrong for some reason. But now I can’t do that. The most similar approach is to have them enabled (either full, simplified or dot) and then disable them at mission start. Is there a way to have them as dots but DISABLED at the beginning? I could’t do it (didn’t give it too much time tbh :) )

Just a heads up; it seems that global cockpit illumination has nothing to do with it. Tried ON & OFF options and the sudden changes are still there on both.

Activate enemy aircraft with trigger Thanks for the detailed explanation. Will try it out tonight! EDIT: ok just tested it and it works! Can’t believe I missed that “Start” action in the “Perform Command” section. Thanks again!

Hi there, I'm experiencing a werid behavior after the latest update (OB); when I first select the AIM-9M and get the bandit in the right position, I get the lock-on tone, I uncage, and everything seems to be ok. But after a while (we are head on), the lock-on tone stops (the small AIM-9 circle still stays on the bandit) I fire and evade (as the bandid also fires a heat seeker); though I suspect my AIM is not tracking. Anyway, after that, I manouver to get on his six, but I can't get the lock-on tone; he's less than 3nm away and cold, after burning like crazy. I tried to cage/uncage, but nothing works; I don't hear any lock-on tone even when placing the small AIM-9 circle right on him. I managed to get a lock-on tone back just once by going close combat (boresight), locking it up with the radar and back to AIM-9. Is this a known issue? What can I be doing wrong? It always worked before the update...didn't try with the 9X; I can only confirm this behavior for the 9M. Maybe I'll try later with the X...just in case.

Hi there, I was just wondering...is it possible to have an ACTIVE enemy fighter, parked, and make it go live using a trigger? I mean, I know I can do it with the LATE ACTIVATION option, and then using ACTIVATE GROUP in the trigger command. But that makes the unit invisble in the mission until it gets activated, which is not as inmersive. I was trying to park two enemy fighters so they stayed there until certain contidions are met (i.e. player enters a given zone, some unit gets damaged, etc.). I tried playing around with advanced waypoint options & triggres like enable/disable AI, stop/resume group, but those options are not available for fighter groups. So I was not unable to accomplish the goal. Any hints?

If anything changed, its really subtle. I was under the impression that planes in the distance (2-6nm) were harder to detect after the update, but I took screenshots from the OB and Release and there is no noticeable difference; at least not in the scenario I tested (instant action ACM vs Mig29). And yet..it still feels it’s harder than before to me. But I can’t find any evidence to prove it; so I take NineLine’s word and just keep flying, trying to get over it and hoping someday this spotting thing gets better; maybe fixed and settled once and for all :)

Hi, From time to time (a few times in every sortie), there are some kind of "sudden ligthing changes" that completely change the tone of the image. It's subtle, and sometimes I just disregard it as if it was just my imagination, but on the F18 the effect can be seen quite easily on the HUD edges. I'm attaching two screenshots to showcase the two "lighting" states; they are taken with the aircraft in a different position/orientation, but the difference in the HUD edges/borders is not just because of the different lighting at each moment; the change happens suddenly, even when parked at the carrier (I just wasn't able to capture that exact moment). Can't be more precise than that, sorry. It simply happens from time to time. I might be parked or flying straight, and the HUD edges suddenly change from dark to almost 100% transparent. Anyone noticed that? Might not be a lighting issue, but can't find a better way for explaining it... EDIT: just came across this other post https://forums.eagle.ru/showthread.php?t=219012 could that be it? It makes sense...

Hi, I just noticed since todays update, the carrier's wake shows some ugly black artifacts at a distance; it's barely visible in the screnshot attached (just a black dot in the middle of the hud), but quite distracting in-game as it shimmers in & out (specially with Track IR). Upon that, it seems the wake itslef is no longer visible at close range as it was before; looks like the place where it should be is just transparent (screenshot attached). I tried deleting the fxo/metashaders2 folders; same results. Is it just me or is it happening to everyone? Maybe ED is trying some new things to overcome the aliasing problems of the wake reported in other thread?

Thanks for clarifying NineLine. At least we can stop wondering whether or not something changed; I even checked it out myself by updating to release a do some screenshots to compare with the a few ones I got from OB. I’d swear the dot was fainter in the OB after the update, but it’s not. And now that we’re at it...is there something being worked on/planned regarding this old spotting subject? 0:)

Exactly. It’s a love/hate relation I have with DCS mostly because of this issue. The older “dot” was visible from far far away; way too much. Now it seems that’s no longer the case, which is good. But there’s still a range bellow the 10nm mark up until where the 3D models are fully visible, where its almost impossible to pick up targets visually (at least for me); at those ranges, the dot helped, but now its gone (or so I think; again maybe its just me sucking big time at the merge). God I miss the freaking impostors from 1.5 :(