rob10

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!

Have you checked that the date didn't accidentally get changed to a PRE-GPS year? That sounds like a GPS issue if it works in NAV but not IFA.

Thanks for sharing, there will probably people who find it helpful. Personally I took the easy route and I use an AutoHotKey (AHK) script to press the appropriate buttons. Keeps it simpler than having to figure out the DCS commands. All I need to know is what binding I have for a button and have AHK send those in the appropriate order and with delays as needed.

I'm curious if others have a different experience, but I haven't found any difference from changing the power setting. I know in MP with SRS there are definitely distance effects (transmission can become broken or totally unreceivable), but not sure if this is controlled by power setting at all.

You really need to post a track it at really sounds like you are doing it wrong. If you're getting a CODE error in your HUD that means that the code you set in your targeting pod doesn't match what the bomb has set. LGB's are pretty simple to use and mostly the Hornet will yell at you if you do something wrong so you can fix it. The new fusing options allow you to enter the code once and with a click change it across all bombs of the same type. You SHOULD NOT touch the code in the SMS page (it will automatically show what you entered on the fusing page when you rearmed), but if you do it won't actually effect anything (the code on the bombs will stay the same). Also note that if you go back into the rearming page after you have set things up in the SMS page (even if it's just to add fuel for example) it will rearm the plane and wipe out any settings you've changed in the SMS page. That's the only way I can think of that you could get fuses resetting to nothing. Either that or this was an old mission build before the new fusing was a thing in which case you need to update the weapons either in the mission editor or by re-arming from the rearm/refuel comms option.

Not an ED issue. If you send those files off to your AV provider there is pretty much a 100% chance that they'll whitelist them and the problem goes away. There are a handful of AV's that have consistent problems with DCS. If DCS had an actual virus problem it wouldn't always be the same ones picking it up and the rest not. And when those ones stop being flagged it will be because the AV whitelisted them, not because ED "fixed" (i.e. changed) them.

In fairness, ED found a workaround to include to fix the radar. Razbam didn't fix it. No idea if anything might be happening in the background (doubt it, but it's possible), but there nothing is being released by Razbam currently.

THIS! I can't count the number of times where people have insisted they didn't need a track because it was soooo simple to reproduce and people spent a bunch of time trying to reproduce and couldn't and in the end the OP finally realized (or finally posted a track that showed the issue) they had missed something simple. THAT is why a track is asked for even if it seems simple. This is a legitimate question (not meant to be snarky, I really do want to understand): why are people so resistant to posting a track? It's pretty simple to do. Most of the time people probably spend more time typing why they shouldn't need to post a track than it would have taken to post it. So why not? I really am curious.

You can open the log in Notepad etc and take a look at it.

Unlikely. If you have the same issue as the log mentioned in the post before yours then the only way a reinstall might help is if your AV updated to whitelist the problem file before you reinstalled. If it's not your AV then repairing should solve most problems that reinstalling would. The authorization issue *should* be solved in most cases by ED already. If that's what's happening (and not AV related) you need to post logs or contact support so ED can look into it further.

Scroll down through this forum and you'll see a bunch of threads in the 1st page alone reporting this. There are a number of AV's that seem to flag DCS files fairly regularly and while Norton isn't one of the top 3 offenders it's pretty commonly implicated.

It will send you direct to WP13, but enroute to WP13 you should get a call to push the F-4's back a 2nd time. If you went thru all the other WP's on your way to WP13 you may have missed a trgger zone/timing that would make the 2nd push call play. Make sure you only make radio freq changes when told.

It's technically a trigger issue (even though you're not making the mission) which is what makes mission editor the appropriate place for it. It's not always obvious where things need to go when you're newer to the forums, so just do your best and it will get moved if appropriate.

Are you using the latest Occulus Beta and Open XR? If you disable OXR you can use the latest Occulus, or you can use an older version of it and OXR. Current known issue on Meta side.