derodo

Just a bit more info. This only happens when the contrails are "small in size"; that is, zooming in will cause the "blue/dark" spots on the smoke to disappear. Seems like a mip-mapping artifact...

Wait what? Wing vapor on the SU-27 back then in Flanker 1.1 ?!?! OMG!!!

Just tried it and it worked like a charm this time. Thank you Baltic!

Hey Baltic, no problemo! Keep it up man, you rock! F*ck#ng awesome campaign, and superp customer support.

Downloaded and tried the latest version of the mission yesterday (file dated February 22nd), but Claw is still stuck somehow. I get to the point where we take out the bandits; Zeus says we stay with Claw (which has already started the attack). I get back to them, and they keep circling around WP5. It seems they're doing their attack run; I see one of them dive, but the weapons are not released (?!). I can clearly see previous runs were successful, as the tunnel entrace has some craters and quite a few vehicles smoking; but there are still 2 tanks there alive. It seems claw is trying to take them out but they can't...so they keep circling around and doing "something" to no effect. I tried taking them out myself, got a few hits but the tanks are just too strong for my guns I guess. There were only two of them left, by the way (Claw 4-1, and Claw 4-4); the bandits took two of them out before we could even get close enough. Maybe that's why they're stuck somehow?

Ooooh my...I knew it could be just me. How stupid am I? Jeeeeesus...I even stepped throug all pages in the kneeboard and didn’t find it. (facepalm) Sorry guys, and thanks for the eye opener.

By the way (and maybe this should go in a different thread), it would’ve been nice to have the lat/long coordinates of the starting parking spot on the briefing. I’d swear I saw them in a youtube video of a guy that was playing mission 11; in the briefing slide showing the parking spots marked for departure and arrival. But I can’t see them in my briefing. I’m just about to finish de campaign, so it doesn’t really matter that much now. But it may come handy for future players. Maybe they are there and I’m just blind (that wouldn’t be surprising :).

Ok, glad to hear it was not cancelled. I'll have a look at the Red Flag for the Mirage meanwhile. Thanks!

Thank you so much! I was eagerly waiting for it :)

Hi, Sometime ago, I saw a video from Bunyap about this upcoming campaign of yours Is that still an ongoing project? I'm currently doing the default Mirage Campaing and I'm LOVING it; so this campaign came to my mind, as I'm not experienced with the A10-C and it seems it would suite me. Just wanted to know if it's still planned to be realeased any time soon.

Ok, thanks for being so supportive and fast! As for the Claw bug, I think they did their did their job fine; it was just that AFTER that, they kind of kept circling around waiting for something...maybe me? I don't know; I went back and rejoined with them, but they never resumed the mission. To be honest, I'm not really sure they did their job; I know they started pushing towards their target, but don't remember hearing any calls about the result (I was just busy with the bandits, so I might have missed that). Is there any link to download the fixed mission? Or maybe I should wait for an upcoming update.

Hi there. First, let me say the campaign is just awesome. Best one I've ever played so far (I already said that in other posts, just wanted to stress it even more :)). Ayway, to the point. I've played mission 12 two times now, and it kind of got stuck both times for different reasons. The first time, Claw started to do its thing and I got the call for intercepting the bandits. I manged to kill them both, but I think one of the phantoms was shot down. I got a new radio message telling me everything was OK, and to anchor again with Claw. I got there, started circling around Claw and...nothing else happened. I was monitoring both main and element channels. My wingman reported bingo and I just quit and restarted. The second time, Fang started the SEAD strike. Everything was going OK. The last thing they reported was they took out a tunguska. And then, silence...Claw kept circling around WP3 forever. No more radio calls (again, I was monitoring both main and element channels). Am I doing something wrong? Or maybe there's some kind of bug in 2.5?

Ok, I think I know what's going on; or at least It can be reproduced. Take off behind the leader, turn on radar, wait for it to show, and lock it once (TWS); as long as you keep it locked in TWS the closure rate readings are negative; lock again to switch to STT, and then the closure rate goes positive. I have a track file, but it's 12MB and I can't attach it, so I uploaded it to WeTransfer (https://we.tl/AVQ6hWhEPe). Skip to take-off; you can see how the closure rate reading changes sign as I switch back and forth from TWS to STT. Maybe that's how it is IRL; I don't know (it seems odd if it is though :)

I understand that might happen when dogfighting; if you’re pulling Gs the computatiions will vary wildly. That’s fine. I don’t usually look at the values in that situation. The thing is you will still get negative closing values when flying level, no Gs, no ECM. I’m just targeting the flight lead in front of me, and the readings are conistent and steady. If I’m closing in, they are negative; if he’s going away, they’re positive. Is that the expected behavior?

Ok...I just checked again and I'm confused. Does the closure rate indication change sign depending on wether the target is hot/cold? Targeted (TWS) my flight leader (mission 6 in the campaign), and I'm 100% sure the closure rate is negative when I'm closing in (going faster than him), and positive when I'm slower (and he's going away). Didn't check against a hot target yet; I guess the actual indication on the HUD is the relative speed of the target with respect to me? That is, if he's cold and I'm following him faster, his_speed - my_speed will be negative (his_speed being positive as we're going in the same direction). But then, if we're head on, how would that go? Will his_speed be negative (he's in the opposite direction), so his_speed - my_speed is still be negative? That would seem ok to me, but as myHelljumper said, if you're closing in, the closure rate is positive. What am I missing here?

Exactly. I’m not alone then. Hope we can get to solve the mistery...

Can’t remember. I’d say it happened in both cases. It definitely was the case for cold targets, since that’s the last time it happened. Need to check again and take good note about it. I understand the radar might not detect the target if cold and close to my speed; but I think it also happened with hot targets. But don’t take my word for it. I’ll come back when I have more detailed info. Anyway, is it recommended to switch to low/mid PRF when chasing cold targets, then? I’m sure I switched modes and waited for a while to see if the contacts showed. No joy until I did the close-combat/stand-by/on trick.

Yeah I must be tripping when I wrote the post and siwtched postive/negative values. Anyway, it seems the values shown are not consistent. I’ll try to have a closer look at it today; maybe it’s only when you are very close to the target as the other poster said.

Is the closure rate displayed in the HUD (when you have a lock) working as expected? I mean, I know it was broken in the past; and I'd swear I read it was fixed in some update. But it seems it's still off. AFAIK, if I'm going faster than the target, the number displayed should be negative; and if the target is faster than me, the number should be positive, right? If that's the case, then it's still bugged; but maybe I just got it wrong.

Good call Ramsay; Indeed, that could be the case. But then, switching to low/med PRF should make them appear, shouldn't it? It's weird though; because every time that happens, switching to close-combat and then back to VBR always makes the targets show on radar. It might be just coincidence, and maybe it simply works because at that time the closure rate is not zero anymore...but that's suspicious; specially when it happens every time; and some of the times I spend quite a lot of time playing with the radar making sure everything is in place, and it never works until I do the mode switching... I'll take a closer look whenever it happens again, and try to accelerate/decelerate like crazy to see if the targets appear.

Hi all, I made a quick search and didn't find anything specific on this topic; at least nothing that explains/addresses what I've experienced in 2.5 (and possibly in 1.5; not sure). The thing is, it's been already a few times where I got contacts right in front on me, co-altitude, not beaming, less than 30nm, and the radar is unable to pick them up. I verified antenna elevation, tried changed PRF, but nothing. Until...I switch to close-combat mode (still nothing, they're too far for that), then put radar on stand-by, then back to on again, and voila, the contacts show on the radar. Is anyone experiencing this? It might be just coincidence, but as I said, this has happened to me a several times. Don't know if the radar is *that* bad IRL; I'd say it's not. Goddamit, I even get to spot the contacts visually before they show up on the radar (at least some times); and everytime that happens, I do the trick combat-mode/stand-by/on and the targets show...maybe it's just the way it is, or I simply suck at this (which is probably true too). I'm so confused :(

As much as I love DCS 2.5, [night] lighting is still broken. Having to mess with deferred/gamma settings depending on which type of mission you're fliying is weird. During daytime, it looks gorgeous; but at night...it's like there's a blackout in the whole Caucasus. Cities look dead from the distance; as you get closer, you can see there are actual street lights and everything, but they are way too dim and fade out soooo quickly as you get away. Same thing goes for runway lighting and position/nav lights; I it's an old issue this lighting thing I guess...it's been in the forums forever :) one way or another. I hope it gets better in time (I'm pretty sure it will, but better sooner than later). I'd like to see night city lights on DCS as they look on that other GA/civil sim; that would be awesome. Maybe some day.

You know what? That kinda makes sense. I screwed up taxiing out (shame on me), and I quit and reloaded. Maybe that’s why I dind’t see the tracers. And in the previous attenpts I remember I had to reload too for whatever reason. Hope you can find the bug and fix it.

Hi all, I just tried the campaign in with the new DCS 2.5OB, and I can't spot the tracers. Even when I know exactly where to look; I had to cheat and open the mission file in the editor just to verify the indications given in the mission were correct (which they were) and I was looking in the right direction. I think I'm doing everything ok; and in fact, when I dive and drop the flares the mission tiggers the condition and everything continues as expected. But I can't, for the life of me, see the tracers. I tried three times because I thought it was my fault; I did the mission in 1.5 and had no problems spotting them. But now I just can't. I even went to external view to triple check. Everything else in the mission is ok (or superb, I should say; I just love Baltic Dragon's campagin :); but this tracer/explosion spotting is driving me crazy. I know it's a minor issue, but it really got into my nerves. I have everything maxed out, deferred rendering. Could it be something related with the new lighting system? TBH, the night lighting is still off. Overall, 2.5 is awesome, but at night ... cities look dead, the lights are barely visible from 1 mile away (even runway/taxiway lights). Anyway...has anybody experienced this? I seems is should work as I read in some posts, but I still can't spot those damn tracers. And as Baltic Dragon said, that's what the cue you are supposed to relay on...

The trees! Drop down the trees slider as much as you can. In 1.5 that is key to maximize FPS if you don't have a very powerful CPU. I have an i7 3770K + GTX 1080, and it's pretty difficult to get 60+ FPS on the ground at Kobuleti. Cranking the trees slider down to 0 gives me 100+ FPS. Up to 100% and it goes to < 30FPS. I hope it gets better in 2.5 (it seems that's gonna be the case :))