Althar93

The drop isn't half as bad as it used to be but it is there (dropping from 60FPS to ~25FPS). My repro is to simply run the Freeflight instant action mission in Caucasus. I am sporting an RTX 2060 with the 465.89 Nvidia drivers (I just noticed there is a brand new driver out today so I'll try that). I initially thought the clouds could be the culprit, but I can toggle the radar on/off and the framerate picks up straight away as a result.

I have just updated to the latest DCS 2.7 and been trying out the Mig21-bis. With the improved visuals & lighting the Mig's cockpit looks amazing. One small caveat. The performance issue that was previously plaguing the Radar seems to be back, with the same behaviour or chugging for a few frames, before picking up again. Am I the only once with this issue?

Thanks a lot for taking our feedback onboard & I look forward to 2.7! After reading my post from a few weeks ago again, I realise it might have been a bit brash/unfair in places. I just wanted to clarify that my intention was not to be insulting or discouraging & want to reiterate that you have done a stellar job with making the most immersive & engaging DCS campaign that I've played so far.

Nevermind, I had a closer look at the track and.... J-P Lambert committed unintentional suicide. Essentially just after releasing the weapons, rather than fly away he decided to make a dive and actually got under his own bombs. I thought the whole point of CCRP was that you could release the weapons at a safe altitude/pitch & you didn't have to get close to your target. In case the images weren't clear, his own bomb hit him in the rear & I guess that must have caused enough damage that he was unable to recover later during the CAS run. Oh well... DCS AI I guess...

I have been trying to play through mission 06 of the campaign and realised after the arrival of the Hinds and switching back to the main frequency that my character was speaking by himself with no one replying on the other end. Suspecting the mission broke I exited and reviewed the mission in TacView only to realise that my lead (J-P Lambert) crashed in the ground when turning back from his successful CAS run on the objective. I have attached the TacView, J-P Lambert will meet his demise at +00:38:53. I am guessing this is going to be specific to the AI in DCS, but perhaps there is something that can be done about this? I will re-attempt the mission again at some point and hopefully it does not occur again after nearly 40 minutes in flight. Cheers, M2000_Campaign_Mission_06_Glitch.acmi

The server/game was really laggy stuttery for me tonight on Two Towns. The stutters & lag were actually causing my Mig21's engine to spool up and down, stall and require a restart (had to restart about 5 times in the space of two sorties), which was interesting, to say the least. Even weirder, I spontaneously died after getting hit in the back when I thought the area was clear - after ejecting I had a rant at having been tk'ed because I saw a Mig21 fly over my parachute. An hour later, I load up the replay in TacView and... I apparently just vanished from the air with nothing & no-one in the vicinity of my aircraft... strange (and the flight path of the friendly pretty much exclude him/her from the equation).

I had to taxi ahead of him and takeoff before. Goes against what the briefing says but I was able to complete the mission that way.

I think people also have their preferred aircraft to fly, and/or may only own a restricted set of modules. Up until very recently, the only aircraft that I could fly on the Cold War server was the Mig21 so that pretty much anchored me into playing Red (which I'm fine with as the Mig is still to this date my favourite module & I'm yet to properly learn the Tomcat enough to fly it). Time zones are definitely an issue & when you play seems to make a huge difference in terms of the experience you'll get on the server. I'll occasionally log in during the week in the evening but I am usually tagging along 2 other Migs against a swarm of F-5's and we stand absolutely no chance, on those days I rarely stay more than a sortie. On the other hand, my most fun & challengine games have been at the end of the week/weekends where both teams might not ncessarily be quite so balanced but there are GCIs and people communicate & there is teamwork. I think BlueFlag's approach of having AI interceptors does somewhat cater for the occasional inbalance/lack of players but I'm not overly convinved this would help the Cold War server much. DCS is unbalanced by nature & to be fair I am fine with that. I don't mind somewhat unrealistic loads or some artificial balancing to even out the playing field for each team but what makes the experience enjoyable for me is the fact that the respective aircrafts/teams have different advantages/disadvantages & learning how to adapt with every mission.

Yes, that's also what I was expecting. Obviously I have never flown in a real Mirage so I don't know how it really works but your second example is what feels to be the most intuitive & likely behaviour of the dashed line in the real plane.

I was going to write some feedback myself & saw that riplikash has essentially summarised my feelings about the campaign so far. This is the first DCS campaign that I am playing through (recently acquired the M2000C), so I have no frame of reference for quality, polish or robustness of other campaigns for DCS. So far, I love : The atmosphere The context The radio chatter & personality/stories of the various characters The build up of the campaign is great (just completed mission 3) & I am looking forward to playing through the entirety of the campaign. That being said, and similarly to what riplikash posted above, I am playing through it on tip-toes, not because the missions are hard but because the missions/game seems so easy to break & it can be a while before you realise it is completely borked. In total : I had to restart the first mission 5 times due to radio issues & scripts not triggering until I finally figured out that the frequencies in the kneeboard didn't match with those in the briefing I restarted mission 2 three times because a script didn't trigger, because I didn't realise I was actually meant to deviate from the mission and finally because I couldn't actually spot the target. I restarted mission 3 three times because I was on the wrong frequency when triggering the script to taxi and that broke the mission, and subsequently because the Chevy 1-1 wouldn't taxi ahead as per the briefing (turns out, I was the one who had to take the lead and take off first, which contradicts the briefing). Essentially for what could have been 3 hours of perfect immersion, I have spent about 5 hours redoing some missions and having to play through them obsessing over 'triggers' and 'scripts' rather than the actual mission/story for fear of breaking anything, constantly anxious that a script may or may not be triggering until the very end of a mission. The discrepancies between the dialogue, briefing notes and kneeboard, and the occasional bug further exacerbates what otherwise feels like a great campaign. I am staying strong and pushing through the frustrations of having to replay what should be fairly mundane missions but I am secretly hoping this on-rails & trigger-senstive nature of the campaign becomes less of an issue later down the line. I realise DCS is a simulator but in the context of campaigns & due to how rigid the script/trigger system can be for anything but the simplest of missions, I feel like there should be more feedback (even if it is a bit 'gamey') for the player, in the form of a 'F10' list of completed/pending objectives just so that the player can be at ease that he/she has/hasn't been completed yet just to put him/her at ease that the mission is still ticking along as it should. Similarly, a recap/repeat of the last instruction would be extremely useful : I've had instances where I was listening to some dialogue, absorbing, then expecting a prompt afterwards only to forget what the instructions were and not being able to recall them. I love that the campaign strives to be realistic but there is a rift between what the mission expects you to know and as the seasoned pilot in the US airforce you portray and the actual average skill / knowledge of the player who probably isn't flying fighter jets for a career & will need hand-holding a bit more.

Hello all, I've been practicing ILS landings with the synthetic runway and while I understand and am fine with getting the chevrons in the brackets for speed & chasing the localizer symbol, the behaviour of the dashed line is just driving me mad to the point where I have to completely ignore it for fear of it throwing me off my approach. Is it the correct/real behaviour for the dashed line to indicate deviation, or is this a bug/oversight & should it really be a projection of the localizer onto the ground (which would make much more sense & be far more intuitive to fly). It just seems strange that a system capable of projecting & rendering a virtual runway wouldn't be able to project & render a dashed line along the axis of the localizer. At the minute I mostly ignore the dashed line and rely on the TACAN needle on the HSI to place myself because the way the dashed line works makes it incredibly difficult to gauge how much deviation needs to be corrected for as the line swings about like crazy with respect to the aircraft's roll even with minor corrections. What do you think? Is this a bug or is this genuinely how the APP hud symbology works in the real aircraft (and if so, do you have any tips so that I may better understand how it works and maybe it'll click for me)? Cheers,

Out of curiosity, is there already, or are there plans for a Discord dedicated to the Cold War server?

I definitely wasn't getting anything near as good as you with my previous settings - at least you can see the specs whereas I simply couldn't . I've been playing PvE/instant missions all of yesterday evening with the view distance pushed all the way (from medium to ultra which seemed to be the main culprit) in the option & running at 1080p instead of 1440p (it isn't so bad with MSAAx2 and the specs are far easier to spot) & it made a night and day difference, I could actually see my targets & my SA was so much better as a result. I don't expect this will turn me into an ace pilot overnight but I'm sure my next time on the Cold War server will be slightly less of an exercise in frustration.

I've setup a quick mission to test various spotting distances with F14s placed 10km, 20km & 40km. At the default zoom level in the Mig21 cockpit, running 3440x1440 with MSAA 2x, The F14 straight ahead of me at just under 40km is simply not rendered. I have to use max zoom for the pixel to appear. Even worse, the two F14s placed at 20km and 10km are visible ONLY when I am perfectly stationary & still but as soon as I move my head in the cockpit (I have a poor man's TrackIR) the specs disappear out of existence. Finally, the F14 placed at 10km actually becomes more difficult to spot as it get closer since the game switches to the mesh & depending on the aspect, the plane might be less than 1 pixel tall & as a result becomes virtually invisible at certain angles. No wonder I can't spot anything unless there are trails or we are in a circle fight. Hopefully there will be a fix for this at some point in the future alongside all of the nice clouds and other visual improvements in the works. [EDIT] Ran some more tests & it appears my 'Visible Range' setting was set to Medium which seemingly just stops rendering the specs past a certain distance/FOV. I increased it to 'Ultra' and now all three dots appear regardless of the zoom level ; I also tried running in 2560x1080 and the dots are so much easier to see. I do like the sharpness of 1440p but I might have to make this sacrifice to have a slightly better chance at surviving in PvP.

Thanks a lot for all of this sound advice. I guess the difficulty (especially as a relatively new DCS player with just under 100h & far less in PvP) is in knowing those F-14s existed in the first place & being able to build this spatial awareness and anticipate where aircraft are or going. I just got the F-14 in the Lunar sale, so I'll hopefully get to learn a bit about the capabilities of the Tomcat and maybe get a better feel for how to counter or at the very leasy avoid it. I already find it near impossible to see a contact during a merge, let alone anything beyond the range of radar and/or weapons. I have had targets locked on the radar and pursued until I was at point blank range on the scope which I couldn't visually spot. I imagine this will get better with experience but I am just amazed at the amount of activity and traffic around me when I debrief in TacView after a session and realise just how much I did not see, even at close, and what should easily be "within visual range". Most of my deaths are from ambushes (I'm sure this is the case for a lot if not most pilots) with an IR missile shot at close range which takes me out of the sky unexpectedly, when I thought I was being sneaky running cold with radar off a few feet above the ground completely oblivious to the fact that anyone was around my space at the time.

Those F-14s are certainly quite the challenge (that and the fact I am still fairly new to the PVP game in the Mig21). Got shotdown a few times yesterday by F-14s and I never saw them coming. Looking at the TacView, they were able to spot/detect me 40km away whilst I was flying cold & close to the ground. I am sure this is realistic with regards to the capability of the radar but I am going to need a loooot of practice to survive any of this.

I originally posted a question to the training subforum thinking it was user error on my end but this looks like a bug after all : I am currently trying to play through the second training mission of the Mirage, specifically 'Introduction to the INS'. I am unable to progress past the point in the mission whereby I am required to overfly the railway bridge to update the INS. The instructions are that I should fly over the target & select 'REC' to initiate the INS update. There are two issues with this : The instructions omit the fact that 'REC' should be followed by 'VAL' to complete the INS update (I found this out through trial and error) Regardless of how close to the mark (or far) following the INS update, the training mission will not progress any further ; the script will not fire even after several attemps or any amount of time. I have had this issue twice in a row now attempting this training mission ; I have been able to overfly the railway bridge multiple times and can confirm that the INS update does indeed work as I am able to purposefully decalibrate it by picking a random spot & hitting 'REC' and I am also able to get the INS to update so that the marker sits virtually on top of the railway bridge but the training script is seemingly broken and/or stuck (perhaps the margin of error for INS alignment in the script is too low).

Hello all, I have recently acquired the Mirage and been playing through the various training missions. I have been having issues with the INS training mission (02) whereby I can't get the overfly update to work. The tutorial seems to imply I should hit REC when overflying the railway bridge. When I try that, REC and VAL illuminate but nothing happens as I keep flying over the landmark. I tried checking the status of the INS but there are no changes there and the training mission just stays stuck in that state. What am I doing wrong? Is this a bug with the INS update or should I be using the REC button ahead of time and validating? My understanding is that the INS would work out the ground position under the aircraft when hitting REC and use this as the new origin for the waypoint, thereby computing the error from its internal frame of reference and adjusting it back to reflect the true long/latitude coordinates entered into the system? Any help/information would be much appreciated. Cheers,

Believe me I do but not every multiplayer server will allow custom labels and/or labels at all.

FWIW, I played on the BlueFlag Caucasus server for the first time this evening with my stubborn Mig21-bis and whilst I ended up being taken out by some interceptors way beyond the range of my radar and/or weapons, I was actually able to spot the missile coming for me as well as the flight as it got closer to me when I'd ejected & was slowly descending towards the ground. I know I need to actively practice my spotting (and overall tactics/flying to avoid BVR deaths) but it did seem like disabling FXAA and going back to MSAA 2x has improved the situation enough for me to take notice in the last session. Spotting a pixel is still a tough exercise but at least the pixel doesn't pop in and out of existence. Next step is for me to get a clean canopy mod for the Mig. Whilst I love the worn look of the cockpit and dials, whoever thought a dirty canopy was a good idea...

I did think that - I've switched FXAA off and enabled MSAA 2x again. A few updates ago it completely killed my framerate but they must have fixed something since because performance is on par with FXAA. I'll see if my spotting ability improves.

Hello all, Whilst not a complete beginner with DCS or flight sims, I am still very much learning the ropes of spotting and fighting with the Mig21-bis. My issue is that spotting other aircraft is next to impossible beyond 1-2nm without anything but custom dot labels (which aren't available on most multiplayer servers). I was flying in the Cold War server yesterday with my Mig21 and spotted F-5s maybe twice in the entirety of my 2-hour session : those were engaged in fights and the smoke/flares kind of alerted me to their presence in the distance ; in the meantime I got shot down with guns about 4 times without ever seeing the enemy plane sneak up, until it was too late and I was staring at them through my mirror before meeting my demise. I also lost a fellow Mig21 flying straight & level right in front of me (we took off at the same time) and that can't have been more than 1-2nm and I knew exactly where to look but just couldn't see him past a certain point. After the session I opened up TacView and watched the replay to see what I missed and where I went wrong. To my surprise I had enemy planes constantly flying right in front of my face at ranges between 1-4nm (I was following the bogey dopes so I knew where to look) but I never ever saw a thing. I even got a merge with both of us flying head on, same altitude above the horizon, I just carried on in a straight line completely blind as he/she flew right past me and shot me in the face at point blank range. Flipping to my foe's view, I can tell from the replay that he/she had me figured out at about 5nm. I am sporting a 34" ultra wide monitor and playing the game at a resolution of 3440x1440p with FXAA enabled in the Nvidia control panel but MSAA disabled in game (absolute performance hog if I enable it, even at 2x). In single player I can just about spot things with some custom dot labels. What is your trick for spotting ANYTHING in multiplayer servers which do not allow labels/custom dot labels? Could changing the resolution from 1440p to 1080p help? Is the FOV of running ultra-wide a factor? Does MSAA improve spotting? Am I just a terrible pilot for not being able to spot a single pixel? I mean I have no problems spotting specks of dust or dead pixels on my monitor, which should be the same size. I guess my other alternative is to switch to a more modern jet and look into BVR engagements but to be fair, this isn't really something I am particularly interested in... Thanks for reading my little rant!

Are you running DCS 'Open Beta'? I don't think it shows up if you are running 'Stable'. Est-ce que tu es sur la version 'Open Beta' de DCS? Je ne crois pas que le serveur s'affiche avec la version 'Stable'.

Thanks, that makes complete sense - I'll have to check the TacView (assuming they are physically present on the map) but I'm pretty sure even at close range of the airfield, or the objective I was not getting any reply.

Just tried "Open Range" in a Mig21-bis. This is only my second time joining the server (ever) but I was having issues using the AWACS (on Channel 0), I could send requests but got no reply ; a fellow Mig seemed to be having the same issue. Is this intentional or beginner mistake on my part?