Mattressi

I'm constantly getting this crash too. I tried updating my C++ Runtimes to 2010 SP1, which didn't help, then C++ 2012 Runtimes, which still didn't help. I've got the latest graphics card drivers. I've got DCS:W running as administrator. I'm using Windows 7, 64 bit and I've got 8 Gb of RAM. I seem to get this in all missions, with seemingly no reason. I've tried never using the radio (taking off without permission, too) and I've tried just flying straight without doing anything else (setting up and using weapons, for example). The crash is always a C++ Runtime crash (same screen as in the OP). It usually happens 10 to 20 minutes into the mission, but it doesn't seem to have a specific time where it will crash. I think the longest I've gone without it happening is 40 minutes. The main things I'm doing are flying the Su-25 (not 25T) in instant mission and flying the very first mission of the campaign, over and over and over; because it always crashes. Every time I read something on here and try the mission again, thinking "surely this will be the fix". And every time, it crashes :( I can't work out what's causing this. My specs seem fine (GTX 560, i5 2500k, 8 Gb RAM) and I don't experience crashes with most other games (only buggy betas, usually). Is there any confirmation that 1.2.6 caused these problems? I spent most of 1.2.5 just messing around in freeflight, so I didn't fly long enough to know whether it was crashing like this or not. Is there anything else I can do to try to fix this? I literally cannot progress through the campaigns, because I can't finish a single mission due to this crash. Edit: I just had a thought - in missions, I usually use time acceleration (I'm not such a hardcore realism fanatic that I enjoy flying level for 120 km in a slow-moving Su-25. Especially when it's in a mission which I've played probably 20 times). One time the game crashed when I turn it back down to real-time, but that could have just been a coincidence. But perhaps using time acceleration is bad, in the same way using ATC is? I might try playing through without it when I get some time; but I don't exactly look forward to spending 1 hour on the same mission (for the 20-something time...) without time acceleration, lol.

:surprise: :clap:

I'm one of the "invisible" people (I know you didn't mean it like that; I just didn't know how else to word it) who was interested in the Mi-8, but not for $50. I picked it up at $20 and am very happy with it :) One thing that you might want to consider, if you find that initial sales at full price drop too much (because of veteran/core supporters waiting for the first sale), you could try releasing at $30 (or $20), but with the option to increase the amount paid (a tip, like with most bundles nowadays). That way, veterans/core customers can feel like they've been given a fair choice - to pay a discounted price or to pay more because they like the product/want to support it and have enough money to do so. You could potentially add in some kind of small bonus for $50+ purchases (perhaps earlier access to patch content, as beta testers, or even just a little icon for their forum account, saying they're a supporter). Alternatively, I guess you could go the direct route and just tell everyone what they already should know - that you're releasing it at full price and you can and will reduce that price with the next sale (whenever that may be). I can't say I envy you; you have a seemingly sizeable core of players who would ordinarily pay $50, but won't if you make the game go on sale in a few weeks. But not putting it on sale could mean that you just get a small burst of $50 sales and miss out on a big burst of $20 sales. Rock and a hard place, really.

I don't think it is. I'm still having the same problem. When I used a different browser instead of my default one, I was able to to the discount in the e-shop, but after I clicked "buy" and agreed to the terms and conditions, it took me to the cart where the price was still $49.99.

So in a real Huey, would the trigger be used for both ICS and regular radio, or only intercom? I'm guessing both. If so, do I only need to map one (ICS or RADIO) to the trigger and just select which one is used, using the intercom panel? Or do I need both ICS and RADIO mapped to a button?

I've been flying the Huey a bit now, but, as usual, I never bother with the communications side of things. I thought I might try it out, but I don't know what I should be mapping my trigger to. In the manual, the Huey's trigger is mapped to the radio ICS. In game, there's and option for "radio trigger ICS" and "radio trigger RADIO". I'm guessing I should just map the ICS one, but I'm wondering what the "radio RADIO" one does. What's the difference between radio ICS and radio...RADIO...? Thanks :)

Are you sure that the prompt box is for the Huey? I had a prompt come up for A-10C (even though I'd already activated it) when I tried to activate my BS2 key. All I needed to do was cancel that box and the next activation box to come up was the BS2 box. You can tell what the box is for by looking at the top left of it (the border around the box) and it should say the name of the module. Hope that helps :)

Damn, I was hoping it would be a little different, rather than just an A-10C with less features. Thanks for the reply. So it basically sounds like it's just a module for people who don't already own the A-10C module - something cheaper, but with less features. I guess I'll hold off for now, then.

I've bought the Su-25A, since everyone seems to think it's great (it sounds fun - simplified avionics, better handling than the 25T) and now I'm trying to work out whether to get the A-10A. Most threads on here seem to be negative, but they're mostly about bugs. So, assuming that all bugs will be fixed; is there any reason to get the A-10A when I already have the 10C? I like simplified avionics (steam gauges rather than electronics), but I'm not sure whether this is enough of a difference for me. Is there any other difference? Is the performance any different? Does the 10A fly better/worse, have different armament options or a different "play-style" (for lack of a better word) compared to the 10C? Or is it essentially the same plane, but without the electronics?

Yep, that's what I came to realise as I looked into it a bit more. I think I prefer more fixed-gun strafing run style of combat, but I've admittedly had very little experience with the more modern "lock a target from far away and fire" style. I'm interested to see how I find it, compared to fixed-gun aiming.

Ok, thanks for that :) I think I'll pick it up then. If I can fly around fine without autopilot/trim, then I'm happy. I enjoy combat without autopilot, but from what I can tell, combat in the Ka-50 is often based on hovering far away and deploying your weapons (or otherwise using autopilot to move, while focusing on weapons deployment). That seems to make sense to me, now, so I'll get it and see how I like it. Thanks again :)

With the Steam sale currently on, I'm suddenly much more interested in BS2 (I just picked up the A-10C, already). I've had the Huey module for a while and I love it. I'd really love a Hind simulator (please don't mention ToH:Hinds - that was painful), but the Black Shark might be a decent replacement. The thing I worry about is the flight of it. I don't trim the Huey when I fly it - I enjoy just controlling it myself. Similarly, I like the A-10C for its "stick and rudder", rather than fly-by-wire, controls. I'm not sure about the Ka-50, though. Every guide and manual I read practically starts with telling me how to set autopilot and trim. So, what I'm wondering is; how necessary is trimming and, especially, autopilot, in the Ka-50? Can it fly as well without autopilot/trim as it does with autopilot/trim? Even if it takes a lot more effort, I'm fine with that. But I'm just not interested in flying with autopilot all of the time. Thanks everyone :)

That's a good point. I've only tried learning a Russian aircraft with the Su-25 (the free one in DCS World), but I found it difficult to use the Shkval (is that the right word?) system, because it was all just foreign letters to me. There were no tooltips to tell me what I'd done when I used the Shkval, so it just seemed to be changing from one collection of strange symbols to another. Perhaps with the tooltips over the switches (and no Shkval to give me problems), the Mi-8 will be easier to memorise. I might still wait for an English cockpit to come out before I buy it - just in case I can't work out the Russian at all. Also, your English isn't just "not bad" - it is excellent!

I, as an English-only speaker, find it quite easy to work with German, French and Italian cockpits, with not a single word in English. They often have words which sound similar or which, if you know a handful of military/aviation words in those languages, you can discern. Worst comes to worst, I can look them up. However, Russian cockpits just don't work for me. I'm glad that BST are planning an English version, but I'd love to learn the aircraft with the Russian cockpit. I just don't know how - the letters used don't relate to English/French/German/etc characters, so I don't know how to approach it. Are there any English speakers out there who don't know Russian, but have learnt how to fly the Ka-50, Su-25, or similar, in Russian? Is there a trick to it? Like, if I can just learn the Russian letters, I might be able to use the cockpit as well as I can with other foreign-language pits? Or is the only way to simply either learn Russian or memorise each label/switch? It's such a different language to Western European languages, that I'm not sure whether there's much I can do to "get by", rather than learn the whole language.

This is exactly what I've been hoping for. I find it way too hard to keep my head still enough to click on things, so I usually end up pausing (or active pausing) until I manage to click it right. I can be really frustrating, so I'd love to see something like this implemented.

Sorry, I can't help you with your other points, but I might be able to with this point. If I understand correctly, you're saying that the screen shakes when you use the Saitek slider to zoom? If so, that's a very common problem. The problem is the X52 slider has a "jitter" or "shaking" problem. If you open the Saitek control panel, you'll see that after you move the slider a little, it will start to jump around a small amount. The way to fix this is to set up the slider axis to zoom in stages. This thread (http://forums.eagle.ru/showthread.php?t=79562) talks about how to do that. Specifically this post (http://forums.eagle.ru/showpost.php?p=1292722&postcount=5). If you go to the slider in the control options and "tune" it, you'll get the same screen as in the post I linked to. Then just copy his settings and the image shake will be gone. However, it will mean that when you use the slider, your zoom will not be continuous. Moving the slider will cause your zoom to "jump" from one level to the next. Personally, I prefer to just zoom by holding down a button and zoom out by holding down another button.

Yep, pressing Num/ on the keyboard works perfectly fine (zooms out, as it should) for me.

I have "Enable Clutch Mode" unticked, if that's what you mean. If not, is there something else I need to do to turn it off?

I'm trying to get my X52 Pro to zoom in with the clutch button (the button with an 'i' symbol) and zoom out when the pinky toggle is held and the clutch button is pressed. So, I've mapped the default zoom out key (Num/) onto the pinky toggled clutch button. When I use it in notepad, it works fine (types a /). I then went into the DCS control settings and made sure the zoom out was set to this key by double clicking on it, then using the pinky toggle and pressing the clutch button. This worked and it said it was set to Num/. The problem is that when I'm in game I press this and nothing happens. When I press the actualy Num/ key, it zooms out fine; but the mapped Num/ key (pinky+clutch) does nothing. Pinky toggle plus E does what I've mapped it to (reset zoom to default), but pinky plus clutch does nothing. Has anyone else experienced this. Anyone know how to fix it. Thanks :)