rob10

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.

Unless something has changed/been broken recently, it always shows where your TDC bars are in relation to bullseye in the top left corner UNLESS you don't have a bullseye entered OR if SA page is not priority in which case it will show TCN info if you have one tuned. If you're not seeing it I would check that you have actually assigned a bullseye (A/A WP) in the HSI / DATA page.

If you're getting a complete freeze of Windows, that's almost always a Windows issue or a hardware problem. It's pretty rare that DCS can cause a Windows crash from what I've seen.

I would switch it back in SimAppPro and assign it in DCS in the AXIS options as Phantom71 said. You'll be a lot happier with the results.

On top of everything else said above, and I can't remember exactly when it happened, but there definitely has been a trend of people moving FROM Steam to standalone since you can only get trials on standalone. It might not account for all of the decline, but I'd guess it could be a substantial part of the decline just based on comments in the forums.

Post a track of what you're doing (shorter the better, so an air start with just setting up the Walleye is good). You can save a track from the debriefing screen when you quit the mission. Otherwise it's a guessing game as to what you're missing, but set up properly you should get a video feed before launch with the Walleye and D/L pod. Double check that you actually have the D/L pod installed.

The two things I find are you need to make sure you are LEVEL when your wheels contact the deck (if you have any bank one side takes a bigger hit) and keep your rate of descent <800 fpm. Weight also plays. Typically it's overdoing a combination of these things that will get you -- i.e. if you're overweight but level and low descent rate you're likely OK, but if you're overweight and slightly high on your descent rate you'll break things.

What keybind are you using to contact JTAC? Sounds like you might have easy comm's ON on your computer but OFF on your server.

Worth posting the mission if you can. Trackfile might or might not be useful. Right now there is very little info to work on. Flew last Saturday with a combination of F-18, F-18, Harrier and had no issues, but might be the particular ground units (start by removing any MOD ground units) or something else.

Does sound like a sticky TDC or sensor issue. Random since basically the stick wasn't perfectly re-centring every time after you moved it which left a little bit of input sometimes after you released it. Usually a little bit of deadzone in DCS would zero it out. The stock Warthog throttle was notorious for this but TBH I haven't seen it on my original Orion WW throttle.

You've got a P/INS advisory in your LDDI which means you have your INS in NAV with GPS available. Switch your INS to IFA and it may solve your issue.

You need just the right conditions and positioning to be able to see it, so it's not really common.