rob10

Is this the same as what you're describing? Just started to happen to me and I'm just starting to try and figure out what's causing it. Always seems to happen on weapon impact.

Thanks, I was just wondering if I needed to do a repair (if you were seeing INST now).

Interesting. Does it still show INST next to the fuse when you change pages now? If not then I'd say there is a bug there, just not the one you were originally thinking.

Testing the mission, they don't actually "disarm" it's just missing the text to say INST beside the EFUZ on the Stores page. If you set it to INST, go to HARM page and back it will only show EFUZE but if you drop it it will blow. If you set it to OFF it still only shows EFUZ after you change to the HARM page but it doesn't blow. That might be a bug but I have no idea. But they do still work which is why there haven't been a bunch of reports of this. And further testing, this ONLY seems to happen with the HARM TOO page (changing to other pages it still shows EFUZ status when coming back. FWIW, I would be shocked if it was supposed to defuse when you moved off the page, esp if you haven't deselected it. If you deselected it then it would make sense, but since you have to leave that page "active" to get it to align it doesn't make sense that it would disarm.

There are reports that the latest Beta for that is causing issues again.

If you're using the new launcher it is causing that setting to default to ON (show them) every time you run it. IIRC it should be in the MISC section of the settings (could be wrong on that).

There is at least one person reporting on the forums that the latest Meta PTC update is causing them issues like this.

Since this obviously isn't a widespread issue, you should post a track and see if others can recreate what you're seeing in the same mission.

Have you tried RIGHT CLICKING in the appropriate binding box and manually picking what you want to assign it to (rather than moving the control to pick the assignment)?

You didn't mention it and reality is that, as I mentioned, I've seen too many threads that go on for pages of in depth troubleshooting only to discover in the end it was something that simple. So it's actually preventing wasting peoples time to make sure the basic steps are covered. It may seem obvious and be your 1st thing on the list to try but that doesn't mean it always gets done 1st. Thanks for coming back with what did fix your problem . That could help someone else down the road.

That could be your problem. If you look at minimum requirements it says Windows 10.

I'm sure other's can give you a better answer from the log, but if you're getting repeated shutdowns that would usually suggest a hardware issue and power supply does seem like a good starting point.

Not really related directly to the download folder itself, just you don't have enough disc space to download the update. It checks BEFORE it starts to download things and if there isn't enough space it won't start to download so that's why there's nothing in the download folder. The actual D/L might be bigger than the final needed space (because it will replace a bunch of existing files after it's downloaded/unpacked) but you'll need to find a way to free up space on that drive or else get a bigger drive.

And I believe the 1st number is what the actual current angle of the unit is and the number in brackets after is the maximum allowed.

You really need to add some more details and a track file of what's happening. I have dropped a quite a few different bombs from the F-18 with no issues since the update.

Not sure how the hot-start aircraft work, but in the re-arm menu click on the little yellow triangle in the upper left corner of each pylon and check that it properly has fuse in there. If it was an old mission you may need to re-save it to have the fuses work properly. If it was a new mission then I'm not sure.

You really might want to chill a bit. I dropped 5 LGB's after the update with no issues before I ran into this. If you can see it every time you'd be a great candidate to post logs/tracks showing it so they can track down the problem because not everyone is having the issue consistently (which means it hard to reproduce). Clearly there is a bug and it's been reported internally according to one of the testers, but it's not as clear cut as you seem to think it is.

What are you using to pull up the comms menu in air? It sounds like you are using the "Communication menu" binding which works on the ground (and should work in the air with EASY COMMS. Check your bindings are correct and use the "COMM Switch - COMM 1" and "COMM Switch - COMM 2" bindings if you are using realistic comms.

16 GB RAM is probably tight to get DCS to work well. I'd look at 32 as a minimum and probably just go 64 GB if you can. Probably any of the HOTAS setups will be fine. They all have their pluses and minuses. I'd take a browse of the inputs subforum for each brand to get a better idea. I have a mongrel setup of WinWing, Virpil and Thrustmaster which all work together with no issues, so don't be afraid to mix and match. And you'll want lots of space on a fast drive for storage. DCS is big and getting bigger all the time as stuff gets added. Squadron is a tough one. Take a look and see what you're after. They range from laid back with few or no rules through hard core milsim with high attendance and performance requirements and everything in between. Personally I like semi-milsim where you aim for generally proper procedure but no one is going to yell at you if you don't get it right every time.

Is it perfect? Obviously not. Personally (other than the Bullseye issue) I couldn't name issues off the top of my head. I've enjoyed flying it a lot since it been out and I've spent a fair bit of time flying on it. Not sure it's acceptable to have had to wait a year for fixes, but for me there was nothing stopping me from enjoying it so it really hasn't bothered me much waiting for that year.

I do hope it has some improvements to come or ED goes back to the drawing boards for how they make new maps. It's great that they can make them quicker, but the apparent lack of any mesh in the non-detailed areas (looks like a picture slapped on a flat surface on most of it) is very disappointing. And that's running it in 2D. It's even more noticeable where you have a more detailed square that actually has topography right next to the flat area with a picture of topography. Framerates are much better than initial Kola release, but I'll take the hit on that for a better map at 6-10K.

Do a search in your root directories for *.miz That should point you to where they are. Copy them to your Saved Games/DCS.openbeta/Missions folder (you may have Saved Games/DCS/Missions in which case put them there).

I doubt there is enough trust/goodwill on either side for that to happen (no matter who is in the right). Would Razbam agree to provide an update if ED promised to pay them once they did? I really doubt it. And by the same token I doubt ED is going to pay Razbam on a promise that they will deliver a new update. No way this moves at this point without some serious legal actions/guarantees in the background.

Primarily because he publicly admitted he had put that in (and that it was aimed at Razbam, not ED) and had told Razbam at the time when he inserted it. Why would he admit that if he had other stuff in there? Secondarily, certain AV's (McAfee being one of the leading offenders, ESET and Kapersky being right up there with it) have regularly had hissy fits with DCS files and quarantined them as long as I've been around here (> 10 year). So it's more unusual that you haven't had a problem like this before with McAfee than the fact that it's quarantining a file around the same time as a radar issue in the F-15.

It would be reaaalllllyyy helpful if more people would post their crash logs. This is an inconsistent issue (for most people) so tracking it down is going to challenging since it's not easily recreatable (and doesn't seem to have a common cause yet).