derodo

Thanks! That did the trick.

Hi all, I've just got my hands on a DK2 and was able to try it. It's simply awesome; it really is. But I'm experiencing some annoying behavior. When I look down to get the cross over some switch I want to interact with and click the mouse button, DCS looses focus because the mouse is just one pixel over the windows taskbar; so the taskbar gets focused. I have checked my VR options in DCS and I have the "confine mouse to windows bounds" (or whatever it's called); I can clearly see the mouse is effectively being confined to the DCS window, except for that damn pixel at the very bottom of the window, which somehow overlaps with the task bar. Is anyone else experiencing this? I might have something to do with the last Windows Creator's Update, which changed a few things related with the task bar.

Yeah the shader folder deletion trick was the first thing I did :) Didn't get any better though. It's just this CPU bottleneck. Will have to deal with it until 2.5 comes out and hope for the best (I'm sticking with 1.5.x in the mean time).

Yeah kind of figured that out and finally "isolated and solved" the problem. I was reluctant to think it could be a CPU bottleneck (as I read on other posts), but that's what it was...a kind of "hidden" CPU bottleneck having to do with in-game object management. Just dialing down the tree draw distance (which I nahively maxed right away :) gave me 60+ FPS and everything is super smooth now (peaking at 150-200fps). CPU & GPU usage is more or less the same (not above 40%), and I can't get past 50% of the tree draw distance slider without suffering a lot of FPS drops. As lanmancz said, CPU at 30% might simply mean one core is at 100% while the others are almost idling; which is exactly what was going on. It dind't look that way looking at the performance monitor, but the tree count test kind of proved it has something to do with the CPU not being optimally used. Anyway, I'm quite happy so far; I can now play with everything else maxed out and have spare GPU power for VR :) Let's hope 2.5 and SpeedTree alleviate the issue even more (which I think it does from what I've read).

Hi, I know there is another thread regarding something similar, but it's quite old (from the 1.5.2 era), so I just thought to create a new one. This is the thing: I have an i7 3770K (16GB DDR3 + SSD), and upgraded from an ATI HD7650, to an nVidia GTX 1080. With the ATI, I got the GPU at 100% usage, and the CPU was around 20-30%; so I thought upgrading the GPU would help... But things are a bit weird; after upgrading, things haven't got as much better as I expected. The GPU stays around 30% usage, and the CPU at 30% as well (all of the cores, not just one stuck at 100%). It's weird...like DCS is not actually pushing the GPU, nor the CPU either... ...for the other game I tested (I just installed the 1080), the difference was HUGE; went from crappy FPS to outstanding steady 60+. So I was just smiling inside...waitingto see how DCS would perform...launched it...setup a sample mission and...wtf?!?! :) ...is anyone having this same issue? Maybe it got fixed on the 2.2 Open Beta?

It was already reported on the general forum; just thought I posted it here too. Maybe the admins can move it here and remove this one as they see fit. Since 1.5.8, there's something wrong when zooming out inside the cockpit. Everyhing is ok up until a certain point, from which a dark band starts sliding in from the top. The more you zoom out, the bigger it gets. The original report, with an explanation video where the effect can be clearly seen: https://forums.eagle.ru/showthread.php?t=198051

Just updated to 1.5.8 Official, and can confirm this effect (didn't happen on 1.5.7). When the zoom out reaches acertain point, a dark band starts appearing on the top, and stretches down the more you zoom out. Not a killer, but a tad annoying.

And yet, no word about the Mirage...there are like three different updates, one is stated as "For Open Beta Only", though it seems it made it to the public release anyway. I'm assuming that since the udated was from 1.5.7 to 1.58 and the mirage updates were already pushed for the beta version previously, everything is carried over to the official version. But again, there's no easy way to tell what the update is about (not for me at least).

So...does the latest official 1.5.8 version (not the Open Beta) include the latest updates on the M2K? I'm so confused...I guess it does, but the release notes of the official update don't say anything about it.

You're right. Just noticed it yesterday. Don't know when it started to happen, but external views certainly don't work when playing track files. This is quite an old post, so either nobody cares about it, or it has been solved and we're doing something wrong?!?

Thanks for the headsup Baltic, appreciated. I know it's just a minor thing, don't rusht it. I only posted it in case it was just me failing to set up the RWR system. Already getting hands on with the next mission. I LOVE this campaign! (had to say it again)

Just out of curiosity...could it be the latest DCS patches somehow changed the how RWR works? I just played mission 8, and when pushing to WP4, my pilot says he's spotted a Snow Drift search radar but I see no trace on it on the RWR. Had to replay the mission (I failed misserably :) and it was the same. I completed it on my second try, and then I jumped on youtube because I was curious...and on the video I saw the SD icon appeared on the RWR just at the right moment when the pilot says he's spotted it. I checked the docs and it seems there's no too much to do for the RWR apart from turning it on :P The rest of the contacts show correctly, airplanes, other SAM sites, etc; but the Snow Drift doesn't. Any hints? I'm playing the current official version ( 1.5.7.10872.388 ).

Ok...I just had to get here and say it too. This campaign is AWESOME. Haven't finished it yet; I'm still on mission 8 and I'm loving it. It's freaking amazing. Never tried anything remotely close on DCS. As Piston85 said, I don't think I ever had such fun in DCS before. I don't play MP (I probably should try, but I haven't) and this one is beyond anything else. Seriously; it's top quality work. Congratulations to Baltic Dragon and all the people involved in it. Never thought about buying a DLC campaign before; and after having seen this one, my next DCS purchase is going to be a Baltic Dragon campaign. That's for sure. Thanks Baltic Dragon (& the rest) keep it up!

Seems like "shadow acne" to me...might be wrong though. Try disabling dynamic shadows and see it it goes away; if it does, it's shadow acne, and might be mitigated by using a bigger shadow map. It will probably be there, but won't be as noticeable. Just my 2 cents.

Yup. Just tested it right now (it's been while since I last flew the Albatros). Morpheus' mod fixes the annoying head position limits (which are still in place in the lastest patch). It doesn't work when saved under Saved Games/DCS/... so I guess it might not be IC safe; but I usually fly alone (so far) so I'm OK with it :P

As far as I know, it only happens on the Albatros (I don't own all the modules, though). As MikeMikeJuliet said, it doesn't have anything to do with the zoom; zooming is just ok. It's leaning the head forward that has ben ridiculously restricted since a certain patch (can't tell which one). I fly with TrackIR, and it's the same. You just can't move your head forward past the control stick; before you could, but now you can't.

Ok, my bad. I double checked and everything seems to be in order. It so happens that the first time I flew the mission I didn't turn on the weapons control system, so the external tanks didn't have power; that's why the lights didn't turn on the upper front right pannel. Now I was about to save a track file; but this time I noticed the weapons control system was off, so I turned it on. And guess what: this time the lamps lighted up as soon as I siwtched on the external inner tank pump. Sorry for the inconvenience guys. TL;DR: turn on the Weapons Control System!

Just that. So you can try any already comleted mission again, just for fun. So far the only way to replay a mission in a campaign is locating the .miz file and copying it to your own missions folder. Not terrible...but I miss the option for moving back and forth between the completed missions in campaign.

I tried the Courier mission today; I completed it, but I think there might be something wrong with the external fuel pump indication lights. I did everything I was supposed to do, and I finsished the mission; so the external fuel tank worked; but I saw no indication lights in the upper right pannel telling the the external pumps were on. Is that a bug? I thought those lights were supposed to go on as soon as you turn on the external fuel pumps, and go off once the fuel has been completely pumped into the internal storage. As I said, everything worked; the internal storage did actually fill (as the fuel quantity indication went up) but I never saw the indication lights on.

Hey MadDog! Your modified version was one of the first things I tried, but the FARP comms problem is still there. As I said, it's not the comms are misconfigured; I'm able to call for aborting take off, and the FARP acknowledges the message. It's simply that once you are airborne, the "Abort takeoff" command never dissapears; so you can't do nothing but that. Still need to check Holton181's workaround abot contacting the "next entry" in the ATC list...which is *weird*

wait...what? Really?!?! I'll give it a try, just in case. It still smells like bug, though...

I started the deployment Campaign (about time!), and I noticed the FARP comms might be broken... Up until now I always departed from an actual airbase, so I'm not familiar with FARP procedures, but it seems something's wrong. No matter the mission, if I select the FARP frequency and open the ATC menu, I can see the "Abort takeoff" option, which is ok (since the mission starts with the engines running and everything's ready); but after I take off, the ATC menu for the FARP stays the same forever, with just the "abort takeoff" option, no matter what I do. I can sucessfully communicate with ATC as I'm able to "abort takeoff" (even when I'm already airbone). So it's not a radio problem; it's useless anyway since now I can only request permission for startup and I cannot declare inbound. It's not a big deal, I know. I've been able to complete the first 5 missions with the FARM comms broken; though it's quite annoying having to locate it at night if you can't declare inbound so they turn on the lights... Has anyone experienced this? Is it just the campaing or does it apply to all FARPS?

Just bought the M2000 on the summer sale. Is this campaign included as part of the module? Or is it a separate DLC? (can't find it anywhere)

I'm also one among the many who learned and enjoyed with your videos back in the days, Ironhand. It's a bit sad to know he site is no longer available, but we all have to move on at some point :) Anyway, THANK YOU mate. You did a great job. Appreciated.

Have you tried tunning the axis? I usually find that setting it as a "slider" with a curve of -18 gives a center position roughly equivalent to the default 5 key; but you can play with it to find a more convenient setting that suits you.