rob10

I'm actually going to say my comments in my 1st post still stand. I am running the full 3 WinWing MIP screen set up and run SimAppPro and I've NEVER had it want to restart from changing any F-18 controls. There are definitely some display settings that do require restart, but I can't remember having many issues with that and WinWing MIP's either. I won't argue against having an option, but I can see why it would be a low priority to add it.

This is probably a good starting thread to look at:

Sorry, but if this was strictly a DCS bug you'd be seeing posts all over about it. There aren't many. Typically if it's crashing you to a full system restart you should be checking your hardware to start.

Was fixed in a recent patch.

Thanks to all the creators that keep updating things as DCS changes! Appreciate your work!! I wish you didn't have to do it, but I'm not sure how you get around continually updating/(hopefully) improving DCS without ending up with things broken in previous missions . It's an unfortunate tradeoff.

Off the top, you should expand your pagefile to at least 32 GB. You only have 16 GB physical RAM and currently you only have 5 GB pagefile. That's not enough to run DCS. You really should aim for minimum of 32 GB physical if possible. From your logfile: System RAM: 16305 MB, Pagefile: 5120 MB

Yes, but not necessarily ones that DCS has in it (i.e. Canada)

Likely yes (NOTE: only likely). BigNewy or Nineline indicated it was in testing but wasn't going to make the previously released patch but hopefully would make the next one. So as long as they don't find any significant bugs that need fixing I would expect to see it in the next update.

Not sure why your DCS is restarting with changes to controller bindings in the main menu. What setting/which aircraft/window? I can change settings and it doesn't cause a restart whether done from menu or in game. Usually it's display settings that cause a restart. I'd RE-NAME (so you can get your settings back if it doesn't help) your DCS Saved Games file and see if it's still doing it. Sounds like a config file is corrupted somewhere.

I have no issue with this being added (I don't use VR so it really doesn't effect me one way or the other). But I'd just like to point out that a) VR is not a majority of DCS users (likely). b) don't assume that everything "simple" is actually easy/fast to program. c) EVERY OPTION no matter how simple is going to have have a performance hit. It may be negligible on it's own, but when you add a bunch of them it's eventually going to add up and matter. So while this seems simple and easy and no cost and something everyone wants, reality is it may not be easy, no impact and something that benefits a large part of the user base (in fact as pointed out above, not all VR users want it). So just because THIS particular wish hasn't been implemented since 2018 doesn't mean that ED doesn't do things that users request (they have), and isn't evidence that DCS is a pyramid scheme.

Reported bug from a a while ago:

1.0 isn't really a magic number. I'd start lowering it until you get the results you're looking for.

FROM THE CHANGELOG (I highlighted the part you apparently missed): Input. Partial fix for lag based on high poll rate mouse movement.

There is currently a reported bug with landing events not being triggered. That could be what's causing the problem.

That sounds like you are ending up running in ST rather than MT. Check the bottom right of the main screen once DCS has loaded and make sure it says "multi-threaded preview" (or something similar) before the version name.

Might be better if you could upload the .miz file so we can take a better look. And unrelated to your specific question, it's worth making flag names that relate to what they do (i.e. startconvoy and stopconvoy) rather than just numbers as that makes understanding/debugging easier. And your naming (Convoy "Stop") appears confusing as this looks like the "START" condition. I'm confused as to how you're actually getting it to work once actually. From your screenshots: when you STOP the convoy the 1st time it sets Flag 1 to "1". In the 2nd screenshot this will work the 1st time because Flag 1 is set to TRUE yet (so condition met) and Flag 2 isn't set yet (so false condition is met). So I'm actually surprised you're getting it to start again because you never set the opposite flag back (i.e. the STOP flag to false if you want them to restart or the START flag to false if you want them to stop). That's likely part of your logic problem as to why it's not working.

Both sides on this issue need to take a chill pill. Clearly it's working fine for some in the current version and very poorly for others. Guess what: in a lot of cases those sides have changed over the course of the tweaking ED has done. Most rational people are willing to say that it's not ideal yet and still needs tweaking for whichever side is currently not seeing it well, but too often this thread only has people screaming "it's totally broken" or "it's perfect the way it is" with no acknowledgement that both of those statements are true currently and ED needs to work on bridging the divide (which I have full confidence they are trying to do).

And we're all guessing blind as to what you are or aren't doing. PLEASE just post a track and probably someone will be able to get you sorted out pretty simple. What you're describing makes no sense if you're doing things right. And can I suggest reading the manual starting at page 315 because that should answer most of your questions.

Please post a track. This may be something you're doing wrong or could be a bug but without a track it's hard to know.

The short version is yes, that's one option. You could also just go in and change them in the MISSION PLANNER option when you enter a mission or just re-arm when you get into the plane. And likely any mission older than a couple of months could have this issue. Yes, ED should update their older missions, but technically this isn't a bug, just a change in the game.

If you're using the new DCS launcher, turn it off (there's switch in the top right of the options screen) and launch DCS directly and it should work again.

Working fine for me as long as you rearm it on to your plane. I'm guessing you are using a mission that was created before the new fusing system was set up (or possibly a fast mission). In either of those cases it will not have the new fuses and therefore won't work. You can leave it on the default fusing when you add it to your plane. In the future it will make it a lot easier to check your issue if you attach a track file of the problem. I'm making an educated guess that the above is your problem but I could have confirmed that if you had added a track.

Those logs are still showing a whole bunch of errors/warnings due to mods. Check that you have actually removed them all from your saved games folder. The other thing you can try would be RENAME your DCS saved games file (so you don't lose anything if that doesn't work). DCS will create a "clean" new one and see if it launches at that point.

Now that you say that, I wonder if it's the day change bug (not sure what it's actually called). The one where if you cross over a day it can mess with things. Somehow your symptoms seemed familiar but I couldn't remember from where. Could be from that. Of course I can't find it in a search right off to get the details. Glad you got it fixed!