rob10

Per Flappie there should be a fix incoming in next patch.

There is some discussion of this closer to the end of this thread. May have been discussed elsewhere too if memory serves, but this was what came up in a quick search.

Yes. For those who are interested, here is a link to the original (and detailed) post that includes this (note that it was at line 18 (rather than the current 19) at the time):

Pretty sure it gives the warning if either side to side or front to back are out of acceptable range. It doesn't differentiate or separate out the two.

I would contact customer support. Something isn't linking properly if that's the case. I asked the question because there have been a number of posts from people who discovered they had forgotten where they purchased it and turned out it was the other and that was the issue. I'm guessing it's not the case, but do you currently have your Steam purchased FC3 bound to ED instead? That also can cause issues.

Yes, and there are older reports of random failures turning themselves on in a user created mission (i.e. user did not turn random failures on). May relate to last update or may be random chance that this is happening now rather than before.

Those that have had WinWing for a while will remember back to when running SimAppPro had a significant performance hit. Then a user discovered there was a setting in the wwtExport.lua file in the Saved Games/Scripts/WWT file that was causing it to poll the controls at about 100 fps. They changed it eventually to 1.0 which solved a lot of the issues. Somewhere one of the recent updates it seems that it got changed back to 0.03 AND the setting for it to NOT change this file no longer works. Set it to READ ONLY and it will stop it from changing back each time you re-launch SimAppPro EDIT: see this post for a workaround on it changing on re-launch without going read only: I discovered all this because my performance on the deck on the carrier had got crappy.

Side effect of the patch, but it's running the new launcher that's turning this on. If you turn it off and don't run the launcher it will stay off. If you run the launcher it will turn it back on every time. Along with stick showing and mirrors on (or off, can't remember which).

Did you originally buy FC3 direct from ED rather than through Steam? Lots of people that went the other way having that issue. You have to buy FC4 wherever you bought FC3 to get the discount.

Post a track. There have been issues in past where random failures were turned on in missions without the user turning it on. Could be that.

That makes total sense, but it appears that ED doesn't have it modelled that way. It was brought up in this thread: And appears to have been corrected based on that thread according to this in the patch notes (unless I'm misunderstanding): Fixed: Selecting different nose fuses will produce dud bombs. So maybe it's now incorrect to what it should be and that need to be reported. From your post it sounds like it should go back to pre-patch behaviour but with an added ADV warning indicating the problem.

If you go into your profile (your user name at top right), click on "My attachments" and it will show you how much of your quota you've used and allow you to delete previous content to free up space for new.

I agree that it would be good to have these hidden in game. Definitely adds a lot of clutter to the map. I really don't think adding these all as active FARP's would be a good idea as I suspect it would destroy any possibility of getting even marginal performance out of the map. It would also need a method of being able to remove them for mission creators (which would get complex). It's relatively easy to create a FARP template and drop a bunch if you need them.

Someone else pointed out you can do this in the planning screen when you open the mission rather than going into the mission editor which may be simpler (but won't make the change permanent since you can't save it).

Are you using the current version? The mixed fuses for same bomb type causing them to DUD should have been fixed according to the change log. If you're still seeing it post a track. I agree that it would be really nice if ED could give more details on the fuses. It's definitely not very clear yet. I'm not sure the air fuzing actually works, but I know ED has said that any extra/different effects of that aren't yet modelled (so even if it did visually explode in the air it wouldn't have any different effect).

In a different thread Flappie has indicated they have a fix that should be in the next patch. Hopefully we won't have to wait too long for it, but ED has indicated they are trying to get a bunch of the big bugs fixed before they release it.

First I'd follow Flappies advice. Then I'd try RENAMING your saved games folder and let it create new one and see if they show up then. If they do then your bindings files could be corrupted/damaged somehow. If not then you can rename it back and you won't have lost anything.

There is NO open beta since earlier this year. Everyone is on the same version (except internal testers).

That's really good news! I was concerned it might be a problem to track down. Thanks Flappie!

Reported already and ED is looking into it. Unfortunately it's not consistently repeatable. Seems to be a MP + F-18 issue when you arm the laser. See the F-18 subforum bugs section.

Great that you have things working again. But in case you weren't aware, single thread is going to be discontinued at some point in the short(ish) term (I would have bet it would be gone by now, but they seem to still be working on some MT issues with newer systems so it's hanging on still) and even now there are bugs popping up in it which aren't being fixed likely for that reason. I only mention that so you can plan for when that happens (especially since you mention you have an old system).

Already reported.

I have the same pedals and it's working fine for me in F-18. I'd try a repair on your DCS or possibly plug them into a different USB port (check that it's fully seated). This seems to be a problem on your end rather than a general DCS problem.

Those are excellent tips for learning AAR