Bashibazouk

I'm not having problems with engine warmup. I rush to get the engine turning over before everything else, and if it's cold, I do use the oil dilution (it's working on my setup). I don't wait until everything is exactly according to the book, as I mentally calculate including the taxi to takeoff as part of my engine warmup. I'm sure it's frustrating to have your engine die because you're rushing to form up, but I'm just not having that problem. And typically, I have all sorts of problems because I'm a bit slapdash and my system is overloaded with mods . Luck of the draw, I suppose, although I had a doozy of a problem with the Mirage F-1, which I eventually solved through manual filtering of my mods. While I'm here, I'd like to say how much the DCS changes to the AI, specifically not allowing AI to firewall everything on the climb, has made these campaigns more enjoyable for me. In the past, I would climb at about 180 and keep the engine on 28.5/12. The flight would draw away from me and I'd catch up over the channel or France. It made the first part of a mission quite dull and I never liked doing the climb. But now the DCS gods have told the AI that they need to be more realistic in engine use, I'm climbing in proper formation. I even have to drop the throttle from time to time to stop me overtaking, as you usually need to do with formation flying IRL! It makes this important part of a mission something I actually have to pay attention to, and something I enjoy rather than dreading doing it.

I know nothing of this, I moved away from VR a while ago, it was just too costly and separated me too much from my family and the environment around me. Don't get me wrong, I think VR is fantastic and even worked in VR production from 2014 until 2018. It's just not for me, at the moment. Anyway, I had a quick look at this fellas channel. The clickbait title screens are striking. Googly cartoon eyes pasted on, lots of soyjack gurning. I know that stuff works to get attention but for me I find it manipulative and indicative. If someone does it once or twice as a satirical thing I get it, although I still find it hugely annoying. For me, it works as a dog whistle - scammer, grifter, or at least, a person who values the attention market more than the subject they're covering. I'm sure that not everyone who has that surprise face, pointing etc is like this, but really. It rubs me up the wrong way.

Thanks, Max. No, I don't use a mod manager. I was setting one up years ago and screwed everything up by having two at once. But I do use batch files to move them in and out, so although my idiocy has landed me in this mess, that side of it's not too bad from where I sit now. But never mind! The problem has gone away. I believe it was related to a mod of some kind, when I consolidated the ridiculous list I had, the problem vanished. So, kids. Don't be greedy, don't be messy. Thanks for the help, BB. BTW, I have my DCS directories excluded from anti-virus. For speed, apart from anything else.

My DCS takes an inordinate amount of time to start, and the problem I have with the campaign may be related to this. I've removed all mods, deleted the two folders suggested in other posts (fxo and metashaders2), repaired my build (using the shortest option) but I still have this problem, currently only with the Arctic Thunder campaign. I start the mission (from mission 2, mission 1, the passive one, is fine), get the mission review box, click start and then wait for maybe a minute or two, and the mission starts up with me in the cockpit. This is usually the screen with the final step to start a mission and where I get the largest delays in missions that do work. With Arctic Thunder F-16, I hear the theme music play with the screen still frozen. Then nothing, until, a ridiculous amount of time later (5-10 minutes?) DCS crashes. I've done a rebuild, all the stuff usually suggested. And this is with zero third party mods, I should add. The reason I've put my problem here is this campaign is the only one I cannot play at all, all the others I have do start, eventually. And I was wondering if whatever allows the music to play before the mission is setup might be intefering with my long start problem. This is a nice feature, the music, but not something I have in any other campaign. Any suggestions or anyone else having this problem, even if you don't know why, please let me know. Thanks for your time.

Ok, I have resolved the problem. At least I can stop it happening, I'm not 100% sure what it is but I know it's related to a mod. I had the time to remove all my mods and did a small bit of fault finding (still not complete) to work out which one. I've narrowed it down to something in a list of 58 items (!) but they are in the 'tech' branch of the mod tree. As I get the time I'll go through these remaining mods (I said I had far too many!) to work out which one is causing the problem but for now, I'm back in my beloved F-1! Huzzah! It will be some time until I get around to working out exactly which mod caused the problem but if you are having the same problem, perhaps remove all the mods in the /mods/tech branch then check to see if the problem has gone away. My game takes about 2 minutes to boot into an active simulation, which is why I'm taking so long. I've been trying to get to the bottom of why it takes so long to start a mission but at least they always start! But because it takes so long, it's not a quick process to eliminate mods 50% at a time to find out which is causing the problem. For a start, I have so many that I need to make a list of the mods I have in and out of active loading. Yes, yes. It's a me problem but I do spend a lot of my time playing around in the ME with various mods so I like having them for the most part. Wow! Those are strange. All I can suggest is the removal of all mods, see if the problem goes away. If so, move 50% back into their usual place, see if the problem reappears ad nauseam. And, of course, make sure you have the latest video drivers.

I'm getting the same issue where the left most tumbler is not displaying the numbers as I'd expect. The tutorial for rockets requires 800 mils depression, if I click 8 times, the tutorial moves on (I assume internally it is indeed moving the pipper for 800mils). But it's barely displaying a one for the number, it's just shy as if it's actually displaying a tenth of a movement of the tumbler for each actual step. I hope this explanation isn't too confusing, I can use the sight as long as I count up to the number I need for each click. I don't know anything about the accuracy, I'm not experienced enough with the plane yet.

It might just be my setup, but just in case: Missions 6, 7 and 8 (that I know of) all have problems with the carrier deck. Various flights block other flights. Mission 6, for example, the Hawkeye pulls out, looks like it's heading for Cat 4 (the far left one) but stops just short of the Tomcat. One time I ran the mission, it actually collided with the Tomcat, starting a fire. Anyway, I have plenty of BD campaign stuff to be getting on with. I just wanted to make a note here in case it's not just my combination of mods etc that are causing the problems.

Sorry for the delay, I missed your comment. The problem seemed to fix itself with one of the updates. Huzzah! You may be right in the terrain physics thing as I understand the terrains have been updated since then.

Thanks for getting back to me. BTW, I really love the F-1. It hits all the right spots for me - single pilot, pre FBW, most things are done heads up rather than looking at a computer screen. And it's implemented so well. Before this problem the F-1 was my goto for fun, speed, A2A and A2G iron bombing and rockets. The perfect mix for me. Ok, if the whiteout screen is not repeatable it's probably a mod or install problem. In other words, a me problem. I don't have the spare time at the moment to reinstall. My SSD just fits all the terrains but it doesn't have enough spare space to install everything so I have to create directory junctions to temporarily store the largest terrains on my spinning data HDD whenever I do an update and then copy the relevant files back to my SSD so it's an enormous faff that takes about 4 hours as my antivirus seems to mistrust DCS stuff and insists on scanning everything when I move it from drive to drive. I'll update you when I do an update/reinstall. Maybe next month's update. As for answer to the bug report - I don't think that one in the post is mine. I'll have a look to see if I have something under my name apart from this and respond if I find it. EDIT - I will try a full repair first, though. As suggested above, great info - I hope it works for me!

OK, turning the power to the right hand TGP mount after the engines and electrics seems to do the trick. I was in the habit of switching this on nearly first thing, in case I forgot later. Never mind. I can live with this, assuming it's realistic.

Jebuz, really? I felt I'd just got a handle on the quirks of the Lightning TGP on the F-16. And now it's not powering up. I'll try some of the things suggested above. Grrr.

Right. An update. I haven't checked with all maps, but this glare problem appears to be on the Afghanistan map only. Weird. It does make the plane unflyable on that map, but I just made a mission on the Sinai map and... no white out! I don't know if that helps, or if anyone who has power to do anything reads this, but at least it's documented. I'm chuffed actually. I've been very patient about this problem, and to keep my frustration low I've only been doing testing on the Afghanistan map. Which is a mistake, obviously. I love the F-1, it's definitely one of my favourites. I thought the F-4 might dethrone the F-1 in my heart, but that hasn't happened . I guess not having Jester is why I prefer the F-1. Don't get me wrong, I find Jester an incredible achievement and the way it's been implemented in the F-4 is stunning. But it makes me feel like I'm a bit of a passenger sometimes whereas in the single seat planes, I gotta do everything myself. I also love flying the F-1. In car terms, the F-4 is like one of those American 70s cars with a massive V-8. It feels like a brute, but it also feels like it's on the edge all the time. Yeah, yeah. Probably skill issue. Whereas the F-1 feels like an E-type Jaguar. Still bestial and potentially out of control but a lot more refined than a pure muscle car. I'll probably change my opinion at some stage.

Yes, I do, a ton of mods installed. And very messily installed as well, I'm afraid. I'm trying some other stuff (modification of the XX:\Eagle Dynamics\DCS World OpenBeta\Bazar\shaders\model\functions\glass.hlsl file) , I'll come back and report my findings. OK, commenting out the lines (88 and 89 in the current build) - if(!(Flags & F_DISABLE_SHADOWMAP)) //two lines - 88 and 89 commented out to remove F1 canopy whiteout shadow = min(shadow, applyShadow(float4(mp.pos, input.projPos.z/input.projPos.w), mp.normal, true, true, Flags & F_IN_COCKPIT)); Fixes the whiteout problem. It removes any reflections, from what I can see, but the F-1 is currently my favourite plane so I'll live with that. No doubt the next update will reinstate those two lines, so hopefully whatever interaction is causing this will be gone by then, otherwise it's back to Brackets (or whatever the replacement for Brackets is called, I can't remember off the top of my head!)/ Correction, it doesn' t kill all reflections. Just the bad ones! I'm not gonna investigate further, I do that sort of stuff at work, I'm on smoko https://www.youtube.com/watch?v=j58V2vC9EPc Nope. Still no good.

I've had a look but I can't see anyone else reporting this. That gives me a little bit of a concern that it may be my system, but I'll report anyway. By the way, this only happens in the F-1 (currently I'm in the EE, I don't recall if it was all of the versions) which is why I'm reporting it here rather than elsewhere. All other aircraft don't have this problem that I've seen. I've attached a screengrab showing the problem below. Glare from the sun (I assume) completely 'whites out' the canopy. This has happened on multiple maps (South Atlantic and now Afghanistan I know for sure). I do have the sun low on the horizon to provide some nice golden hour shading when I'm just having a tour, but this glare makes it hard to see anything at all, so not that great for a tour of a new map . It does come on and off depending on the angle, but I was flying a mission on South Atlantic with the sun behind me (roughly) and I had to quit as I couldn't see a thing on a very long commute from the Falklands to Argentina, the whole canopy apart from a little bit in one corner was just full white. Just thought I'd let people know, in case it's one of those problems everyone assumes someone else has reported. I've switched cockpit GI on and off, no change. null

Thanks Ramsay. That's really helpful. I've been having trouble with the IR Mavs for actual years. Your laying out the procedures in such an easy to understand way really helped me. I still couldn't lock the damn things and was still having all sorts of trouble and I'd got to the stage where I'd given up on the Harrier altogether. But your clear instructions made me realise the problem wasn't me. So, what I did was: 1. Saved all my key commands/Hotas etc to external files. 2. Deleted everything so there were no assignments on the controls page. 3. Reloaded my controls, which had been carefully curated over the years to use similar keys etc for similar actions on different planes. 4. Celebration time! Everything worked as it should. I'd been thinking of doing this for a while, but I'd always assumed it was a skill issue so hadn't got around to it. 4a. - OK, not everything works. The tutorials, for example, still don't work for some reason. But Campaigns and Missions that had been created more recently work like a charm. It's been night and day. I used to think the Harrier was a weird floaty thing, the autopilot being worse than useless because I couldn't rely on it. If I looked away, despite being set, when I looked back the aircraft was in a death spiral heading for the drink. But now the plane is fun to fly, easy to control and I can set the autopilot and grab a coffee. When I come back it will be flying straight and level as I set it! This problem I've been having may be my HOTAS setup (T16,000, TWCS and associated pedals, so the cheapest usable setup really) but whatever. It works like a charm now. I don't know exactly what the problem was, but deleting and reloading every control fixed it. If anyone else is having the same issue, I understand how ridiculously frustrating it is. The problems appear to be intermittent (there might be a certain combination of actions that cause things to go wrong, I don't know) and no matter how many times I reviewed the manual, checked videos, came to the forums, I'd still have some times when the IR Mavs just wouldn't work at all, they wouldn't lock, or they'd develop a mind of their own and the seeker would fly around like a crazy thing. The Harrier is hell of a lot of fun when it's working!

I've played this mission about 10-12 times already and am yet to complete it (yes, I know - skill issue). One thing I've found is because the AI can act differently each time, a time window to complete the task can close. Sometimes the 4 Migs die easily, especially if they stray over the northern airfield and a barrage of stingers go for them. But it's important they are dealt with quickly by the friendly AI. I've never had much luck taking part myself with the loaded down plane, I just end up getting to the CAS too late and I need that time to bait the Iglas into firing at me or the Mig-23s come at me before I've done the business with the ground advance troops. And if I've fired off the sidewinders at the 21s, am still loaded with bombs, then even the Mig-23s, in combination with the iglas and SAMs.... well. I'm not good enough to deal with all that at once. I read above that the MANPADs have 3 Iglas each. Ok, that's where I'm at. I couldn't work out why I died last time after baiting four and having everything else done perfectly. Also, don't go too far east when baiting as there are SAMs there thirsty for your blood. Now, I'm going in again, wish me luck. Hopefully my F5s and F4s will dispatch the Mig-21s quickly, then I can go and bait those Iglas from about 10k (six of them to trigger - I assumed there were only four!) then get the task done before the 23s turn up and home in time for breakfast. This has been a tricky one for me, but I think I'm there, maybe one or two more goes, assuming one of them goes my way with the AI dogfight near the reservoir. I haven't found it particularly frustrating as every attempt I learn something new and I have a decision tree to follow. I only find the missions where I have no idea of what to do next frustrating, this isn't one of them once I'd learned the ropes. [I am really looking forward to DCS implementing the mid mission save. With a mission like this it will increase the enjoyment a lot, I could do a savegame just after takeoff, avoiding the whole startup rigmarole, maybe 10 minutes or so, or I could do a savegame after a quick successful AI vs AI dogfight, as that can be a bit random and go straight to the CAS section.]

UPDATE ----NEVER MIND! I looked through previous comments, I had no idea there was a wonderful guide in the actual files in PDF format for the whole campaign. I now know where that Gori Plain demarcation line is. I wish I'd seen this earlier! Back in the cockpit. ====================================================================================== Ok, I've worked my way through to mission 12, although I had to skip the snow bound one. But where is this line that bisects the Gori plain? What is the Gori plain? I keep crossing it but I have no idea where it is. cheers, BB PS the 'sticktion' problem I was having with the Gazelle seems to have been fixed in a recent update. I haven't done any formalised testing, but I'm not being thrown to the side in the mildest of crosswinds when trying to take off from dirt. Fingers crossed!

This is an old thread, but I looked it up because I was surprised to be exceeding Mach 1.02 in level flight at angels 22 without AB. I had two heaters on the outside pylons and an empty pylon in the middle after bombing a runway with BAPs (or whatever they're called). I don't know how realistic this is, or if the indicator in the HUD is correct, but using F3 (external flyby) I was definitely witnessing the DCS sonic boom. Whether it's accurate or not, the DCS M-2000 will kind of supercruise with the lightest AA combat load. Now, as I write this I a few things have occurred to me. At Angels 22, it wasn't getting past 1.1 so maybe I was using a ton of fuel, probably less than when using AB but still. It may not be the most efficient way to get around. When I find the time I might see what it's like above Angels 30, maybe it's further away from transonic and thus more efficient. Any other comments, criticism or knowledge is welcome on my part. EDIT - IIRC, I did use AB to get past Mach 1, but it was definitely holding steady without AB at those low supersonic speeds once it was over the worst of the hump.

Ok, I've been having this problem since I bought the Harrier about 2 years ago. I'm thinking there's some conflict with my HOTAS. I've basically given up on the Harrier and retry it every update but so far, firing IR Mavs is unreliable at best, doesn't work at all at worst. I've tried removing all my mods but that doesn't help. When I can be bothered, I'll reset all my bindings and try again but it's been so damn frustrating that I just hate the plane now and the campaigns I've bought are all done up until an IR Mav is needed, then I abandon it. EDIT: Problem solved! For me, anyway. I reset all the bindings and reloaded from externally saved files. Things still don't always work with the supplied tutorials, but Campaigns, missions, stuff I whip up myself - they are all working like a dream. The Harrier is a joy to 'fly' now. Maybe the tutorials are so old now (some of the instructions are waaay out of date) that they still trigger the problem somehow, but I can live with that. The Harrier is, right at this point in time, my favourite fly-by-wire jet.

How are you dealing with the skids? For example, in MAD mission 9, I have to be ridiculously careful to face into the wind (not the direction as specified over the radio, BTW, it's more 360-000 rather than 270-80 or whatever is said). I can fly all the other choppers well enough and the Gazelle is great once in the air. But taking off or landing, it's like the skids are glued to the ground and rip loose. Unfortunately for me, if the wind is even 1 degree off at 5 m/s one skid will rip loose before the other, causing the heli to roll suddenly, lurching to try to tip over. I can catch this most of the time but it doesn't seem right. I've tried yanking the collective (yes, I know that's not recommended) or doing it as slowly as I can but it seems to be a characteristic of the friction between the chopper and the ground. Anyone else notice this? If not, what am I doing wrong? I don't have a great HOTAS but I've adjusted it fairly well, I believe. If this happened on all the helis, I might just assume I'm totally crap at taking off or landing but it's only the Gazelle. In flight, it's a dream. It's just taking off or landing, when the ground friction with the skids seems weird.

Yeah, I'm finding the sticktion on the skids in the Gazelle maddening. Surely this can't be realistic? If it was like this IRL we'd have dead Gazelle pilots everywhere, even if only the inexperienced ones. The other chopper in game with skids, the Huey, is nothing like this and I'd have thought wheels would be more likely to stick (sideways) than skids but none of the other helis are anywhere near this bad. Thought I was just a really bad virtual pilot, so I've given up on the Gazelle campaigns. They are challenging without this, but to regularly tip over on take off or landing makes them rather frustrating. And no, I'm not that bad, I can fly all the others fine. It is possible to get by, but it takes an inordinate amount of concentration and sometimes it just seems to happen regardless if there's any wind, even if I'm careful to only land or takeoff directly into the wind.

I'm just gonna add to the noise to say thank you for these. As a onetime 3D artist - in motion graphics mainly, so the focus was on rendering and lighting rather than modelling - anyway, I know how much time such work can take. You plan to take a week, it takes four. Much appreciated.

I agree absolutely. I'm really loving this campaign! It has, for me, about the perfect mix of detail and action. Not too much fiddling with radios, tacan, entering waypoints etc, but enough of this navigation, comms and formation flying to make it an interesting exercise (outside the boom boom pew pew) without getting too OCD. I'm up to Mission 13. Which, by the way, is possibly revealing my lack of skill. Does anyone have any suggestions for NOT getting hit by the MANPADs at the port (I won't say more to try to keep it a surprise). No matter what I do, jink, drop throttle, launch all my countermeasures, bank left, right or straight ahead, I get zapped as I'm past a particular point. And yes, I'm flying low. Very low.

Thanks. I was very frustrated when I was rerunning the campaign with the new changes. It's a lot better now, I've readjusted my curves and the Gazelle is quite flyable, so that helps a lot! I've managed the night missions and your advice that 10m is ok rather than 5 really helps with that one. Seriously, I was brushing the top of the waves trying to stay under 5, which realistically, with that wind, and my level of competence, means flying at 2-3 metres. So effectively 0-1m with the chop. So, all good. Except one thing in mission 11. The snowy one. Is there any trick to getting the IR to see through the snow? I've been adjusting brightness and contrast and the best I can do is a white on black, with oversaturated blobs. Am I doing something wrong here, or is it the changes to the IR system? I completed the mission by cheating and turning on labels, but I try to keep that to a minimum. BTW, I've been manually adding the HOT missiles in the appropriate missions as they are not currently loading by default, something to do with the changes to the versions of the chopper? If not, it's probably my overload of mods. I'm gonna have to setup OVGME, I have so many and it's a bit of a faff moving files around if I'm looking for an error caused by a particular one. I have been enjoying the missions, the one where I have to hide (I won't say more) is nail biting. And there's a quite shocking one later on, narrative wise. I love the Gazelle, moreso now it's less of a UFO. My only current whinge is the skids sometimes seem to magnetically stick to the ground on take-off, particularly noticeable if not taking off directly into the wind but still a thing even if I rotate the craft while it's still on the ground to ensure I'm facing the right way. This doesn't happen with any other choppers, so I'm fairly sure it's not a skill issue although most of my other problems are

I'm gonna do this one again. I loved it when I first went through and enough time has passed that I've hopefully forgotten the narrative, I just remember how much I enjoyed it. I know Mr R loves going for realism above all, but in this case, realism doesn't result in too many long commutes. I wouldn't want that changed, BTW, it's just nice to sometimes play a mission that has action almost from start to end.