bonfor

Yes still there with the latest stable release, and it happens with the f16 too. I can reproduce it consistently in a fighter sweep mission when aim 120s are in the air

I ended up with this setup: In voiceattack i have these commands executed when I say "startup" : 6x time speedup Auto start Wait 30s Time normal So I'm ready to go in 30s having left the dumb operations to the computer to do. The modified autostart macro does the stored alignment and I have also added commands to setup the hud, cmds etc how I like it. In the IC I don't see the file I modified mentioned, I suppose that means it passes IC?

That's the point. I want that as an option when doing autostart. And it is a chore anyways. But never mind, I have made a mod and now when I click left win + home the autostart sequence does the stored alignment ins alignment instead of the full one.

I like the high fidelity of weapons systems, sensors etc and that's why I "fly" the f16. I don't want them dumbed down. But starting it up is a chore. There is no learning, no enjoyment in doing so after you've done it a few times. As I said I have to choose how I spend the time I have. My car starts with the push of a button. I certainly don't want it more complicated than that. If you like manual start you're free to continue doing so - this would be an option for those who can only "fly" when the kids are in bed

... To fly? I click buttons all day, if you don't have your daily fill click all you like

I think it would be great to have an alternative auto start command that does the stored alignment cold start. It may be seen as cheating by some, but the "cheat" auto start exists already. I am one of those users whose time is short and is better spent flying rather than on the ground. All workarounds I can think of are cumbersome. Thanks

I had the same issue esp in vr. The fix was for me to clear the content of c:/... /appdata/temp/dcs

This mission is f****d up. The wingman will rtb halfway because of bingo fuel.... But that is because although he has the wing tanks they are not used. If you delete him, save mission, close and reopen the mission then add him again with the tanks he won't run out of fuel. However he won't attack his objectives. Haven't figured out what's wrong yet...

@Icaro_07sorry for the late response, I updated the missions. Let me know if the link stops working

Hi, not sure how many tried the F-16 instant action missions (esp the Persian Gulf ones), but a number of them do not work, either because of possible bugs or incorrect trigger logic. If you're wondering why you can't win bee swarm bay, barcap, silkworm or threading the needle even if you do everything right, you may want to try the ones linked instead (zip file now mod manage friendly). Also there was smtg wrong with island style but don't remember what I changed Also quickstart.lua in C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\F-16C\Missions\QuickStart is incorrect as one mission is missing and bee swarm bay appears twice. The included lua solved the issue. https://drive.google.com/file/d/1eqrSNC5M32epCO9f6fMKQPwsfR2iELgH/view?usp=sharing

Hi Flappie, that worked, many thanks for the tip

Hi Flappie, yes I get a crash every time I play this mission. It may be at different times, but I never managed to avoid the crash in VR. In 2D there are no crashes.

Hi Flappie, thanks for the link. I however think there is still something wrong. If you run the mission I attached you'll see that it ends after about 20s from start, when all the player's wingmen (and the player) are still alive. So it looks like on pilot dead is just not taken into account. This seems to be a different behaviour in the latest stable release. With the previous one I did not have this issue. The logic of the KIA loser control would seem incorrect anyways: it says that if the player is dead and all attackers are <76% alive then the red coalition wins....so to avoid that one would have to kill less attackers before dying.... However this is an mission design issue, not related to the on pilot dead.

Hi thanks for getting back to me. No it's not overclocked. This is the only mission when DCS ever crashed on me. I never had any crash before.

When playing this mission in VR (oculus rift s) DCS always crashes when I am past steerpoint 3, if I use the VR zoom or I go up from 200ft before I release the bombs. In 2D mode it seems to work. log attached, tested with latest stable release dcs.log-20201228-172601.zip

tested with the latest stable release. The F16C swarm bay mission would end prematurely, and this is due to the on pilot dead event not working as intended. To show the problem, I added a trigger to the mission where after 10s one unit in each of the attack groups is made to explode (see attached). Then the trigger (KIA loser) that stops the mission if pilot is dead and each of the attack groups is at <76% alive kicks in and stops the mission. Fly the attached mission and you'll see that it stops after about 30s, when the pilot is still very much alive. F-16C - Persian Gulf - Bee Swarm Bay3.miz

Hi @LSM224556, could you please tell me exactly in which files you hardcoded the path? I have the same issue with the operation red bear campaign. It's not MissionScripting.lua, as the TF74-flanker campaign works ok Many thanks