rob10

That is incorrect. I just used it the other night and it's still there. It opens to white by default, but there is a keybind to change it to green.

Not sure IMHO that this is an EA issue. I see this more as an issue that the new map making tech ED is trying to use (and I get why they've moved that way; being able to create bigger maps with less work/$ is a good goal) is currently not up to the task. I hope the upcoming update to Afghanistan proves me wrong on that, but I'm currently in the camp of just double the price of maps and go back to the old production methods unless massive improvements to the new system is possible. That's why I'm holding off on Iraq when in past I'd have pre-ordered without thinking.

Yes, by AIRCRAFT TYPE. So if I have a flight of F-18's on CAP and a different flight of F-18's on SEAD I can't have a different kneeboard each that only shows up for each -- i.e. the CAP kneeboard only for the CAP flight and SEAD kneeboard only for the SEAD flight. Currently only option is for both flights to have both CAP and SEAD kneeboards.

The docs are 100+ pages long all in one file. There is only one scripted mission (the file in your folder), whatever happens after that is based on what happens in each successive mission. If you read the 1st few pages of the docs it will explain this.

This is purely a guess since it's the same .dll all the time: double check that your anti-virus isn't quarantining or removing that file. EDIT: appears that was a recently changed file (Oct 2) so could be either AV flagging it or something messed up in it.

You imply this is the case for EVERYONE. It's not. It may be "NOT FULLY USABLE" for YOU, but your posts imply that's the case for everyone which isn't the case. It's "fully usable" for me. Please note that I'm not saying (nor do I think) that you don't have a problem and I have no doubt that it's not fully usable for you. I just have an issue when people presume their issue affects ALL users. The version before this was equally "NOT FULLY USABLE" for a different subset of users which is why ED is still working on the system.

I'm guessing you already figured this out, but to save you pulling out hair in case you didn't think of it, make sure you set your parking brake after you move out and leave it on while you're aligning. Won't align without it set.

A big part of the problem is that the maps may be built on different technologies (depending which maps, but definitely something like Iraq and Syria), so it's not as simple as "allowing" joining of the maps. In order to allow joining would likely require a complete re-write of (presumably the older) map. Not going to happen.

For starters I'd set your pagefile to a static 32GB. With 32GB and your current 5ish GB pagefile your likely running out of memory.

Seriously, he has you blocked. I know you like to get a rise out of him, but responding to him every time is just cluttering the thread up.

Which is a whole different kettle of fish, but 1st draft of Afghanistan using whatever the new methods are IMO flopped badly enough that I'm holding off on Iraq until I see if they can make it actually look acceptable to me. And I'm not a helo driver complaining about down low. Kola managed to improve to a decent place, so I have hope, but I feel burned enough by Afghanistan that I'll hold off this time.

I agree with MAXsenna's comments. While you might not have people tripping over each other with map development (especially things like creating different airports), but there is going to be a sweet spot maximum after which the returns of adding more are meaningless. Assuming ED has enough people to hit that and have people left over, it makes sense to have multiple maps on the go. My guess is that this is different to plane development where the optimum maximum number before people get in each others way is likely lower, but also I'd guess that the map making skills required are a lot more "generic" so it's probably a lot easier to hire a bigger pool of people on that side than say for flight model.

Honestly, go yell at Steam if that bothers you. It's not ED's choice.

SCS switch toward whichever DDI (or the HUD) you want make priority (a few information type screens can't be made priority, but most can). SCS towards whichever DDI you have SA page on, which also allows you control of the TDC bars on it. Whichever screen (and thus whatever page is on it) has priority will have a * in the upper right corner. If the HUD is priority it will have an * rather than the DDI's or AMPCD screens.

Just to clarify, you don't need to unselect TCN as long as you make SA page priority. TCN info on SA page should only show if it's selected AND SA page is NOT priority. When SA page is priority, which it should be if you're moving the TDC bars around on it, and as long as you have defined bullseye in HSI data page, it should give you TDC bars to B/E in the upper left.

I really don't have a dog in this fight as I use 2-D and haven't really had issues either way. But I will point out to all the people screaming in this thread that "no one" was complaining previously that you can find LOTS of complaints from people who were screaming that they couldn't see anything before this change and how all the servers they played on were losing players because of this. I get it sucks for people with big blobs now and hopefully ED manages to find a happy medium really soon, but I just want to point out that there were clearly people who the old system wasn't working for either. Would be nice if the ON/OFF worked, but "simple" things like adding that back don't take into account what might have changed in the background that mean it would take as much work to re-add it as it would to get a more proper fix.

What would you expect them to "officially" say? "Our lawyers have met with Razbams lawyers for 6 hours in the last month and have exchanged 8 legal letters"? What would that tell you beyond what you could find in the 1st post here? Any details of negotiations would be conducted in confidence so they wouldn't be legally able to say more than that (if that) and for all you know those could all be discussions of how long of lunch break they were going to take in the negotiations or what time they start in the morning. I truly don't understand what more people think that ED can say and no one that complains that they aren't saying enough ever seems to say what they expect to hear.

Not typical no. I recall having seen someone else in the forums that had a similar issue. Can't remember what their solution was.

Swapping in ATFLIR for LITENING should be fine. I doubt it is directly used in trigger condition. The triggers MAY look for specific weapon, so a MK10 vs a MK12 bomb might not get detected and if it's expecting a MK10 and you use a MAV that definitely wouldn't. That's what the caution in the Player Guide is about.

Believe me, F-18 or F-16 bugs are not fixed that much faster. There are only so many devs go around, so yes modules that have sold more units or bugs that affect all weapons on a jet etc. will have slightly higher priority, but you can find "major" module bugs that have taken equally long to fix. They'll likely get around to it, unfortunately you'll have to be patient. Do I like it? No, but it's reality and sometimes it's about actually finding devs who can do the work as much as $$$.

As MAXsenna said, your best best is playing with the order. Not sure what you need for the stuff you've got in there, but with other typically used exports as an example you'd want: TacView SimAppPro SRS in that order for them all to work.

The good news is that while it needs 200GB to update, it won't actually take that much more space since it will mostly be replacing existing files. It will definitely grow, just not that much. It downloads and unpacks the whole thing before it actually starts replacing old files and deleting the update files which is why it may need 200 GB to update.

I think you mean "UNinstall maps", then update and reinstall maps one by one.

Since that's not general problem, I'd start looking at what mods you have in common.

Yes, and maybe that's because MP is calling a corrupted Windows file that doesn't get used in SP or a file that's on a bad spot on a drive or MP just pushes the hardware overlimit somewhere. I can't guarantee it isn't some really obscure bug between your system and DCS, but almost always when it's completely locking your system or BSDing it's not DCS that's the actual culprit.