M01 No dialouge from launch

[CH4Pz]

Just got started on mission one, and apart from the logo on the screen and some music, there was nothing, no intro or talking of any kind, i started the jet, waited, no contact, tried taxiing, nothing. Assuming it was a bug, so i quit, restart mission, and this time my wingman did say grab atis and switch to ch2. But after that she just taxi's behind another plane, so wasnt even sure if i was meant to follow, OR if the plane to my left was even her, but then even after take off little to no dialogue/instruction. It was late, so i quit and now the next day, i try again, and the same thing, absolutely no dialogue. 

Is anyone else getting this? Could have the update wrecked it? FYI no mods etc

[CH4Pz]

So just tried again, same thing, initial launch no voices, but then quit and immediately restarted the mission and voices work.

I think the no voices after takeoff was partially my fault, as in the briefing it says use comm1/pri for switching, and comm2/aux is for tac, but it seems (so far) the switching is on aux (ground tower atis etc). So i may have had wrong radio set last night (2 in pri instead of aux), as i said it was late.

I guess the work around is launch mission, immediately quit and then restart from the debrief?! 

Edited December 7, 2024 by CH4Pz

[Evo]

I also had to restart the mission, but it worked fine. 

[5e EVC Chappy]

Just start your jet and the Lead will start talking as soon as there is one engine running.

[rob10]

@baltic_dragon I'm also having issue with getting any comms at the start of the mission.
Removed all mods, did slow repair on DCS, deleted and reinstalled the campaign.  Not sure where to go next.  Track attached for what it's worth.

Arctic Thunder M1.trk

[CH4Pz]

12 hours ago, 5e EVC Chappy said:

Just start your jet and the Lead will start talking as soon as there is one engine running.

Well that's if its not doing this issue. It does seem a restart gets it to work, although yesterday i had to restart twice, for the dialogue to work... then it crashed, but maybe thats a "me" problem, as i've had crashes elsewhere in the sim

Edited December 8, 2024 by CH4Pz

[rob10]

I tried multiple restarts and it didn't help.  Also tried flipping through radio presets (to ATIS and ground).  Likely something simple that's not triggering, but I can't figure out what it is

[CH4Pz]

4 hours ago, rob10 said:

I tried multiple restarts and it didn't help.  Also tried flipping through radio presets (to ATIS and ground).  Likely something simple that's not triggering, but I can't figure out what it is

Just to be clear, when i say restart, i dont mean restart the game, or the system, instead you just press quit from the menu, and restart the mission from  the debrief page. Is that what your doing?

I think this one may need to be fixed higher up, either ED or Baltic, somethings seriously fubar

[rob10]

7 hours ago, CH4Pz said:

Just to be clear, when i say restart, i dont mean restart the game, or the system, instead you just press quit from the menu, and restart the mission from  the debrief page. Is that what your doing?

I think this one may need to be fixed higher up, either ED or Baltic, somethings seriously fubar

Yep, tried all the different options including "fly again" from the debrief screen.  Thanks for checking.

This doesn't seem to be a widespread issue or I'd have expected to see more reports.  That's the really confusing part.  And it should be a really simple trigger so not a lot to go wrong with it. 

[rob10]

3 hours ago, rob10 said:

Yep, tried all the different options including "fly again" from the debrief screen.  Thanks for checking.

This doesn't seem to be a widespread issue or I'd have expected to see more reports.  That's the really confusing part.  And it should be a really simple trigger so not a lot to go wrong with it. 

It's random.  I managed to get the "F10 menu or tune freq" pop-up to come up when I tried it the morning and flew the mission.  It was a lot of fun.  But after I finished it I tried to run mission 1 a couple of more times and didn't get the pop-up.  Also no F10 options showing without the pop-up so not possible to get around it that way.  And the I and R windshield don't work without it either.

[CH4Pz]

So, not sure if related, but i was experiencing crashes in DCS (not just this campaign) and started this thread:

Now, if you goto the bottom, you can see all the things i done, thanks to the amazing Sleighzy, and i havent got a crash since, but the 2 times i started this mission, since doing all that its come up, first time, straight away. Basically updated my MB drivers, wiped my gpu drivers (in safe mode) with DDU and manually downloaded new ones from nvidia, disabled hot plugging in controls menu (RH side of buttons, below binding menu), and a couple other windows things. But yar, as i said, its been good so far. Dont see how drivers would effect game triggers, but thought was worth mentioning.

@rob10 maybe start with disabling hot plugging on your controls, see if makes a difference?

[rob10]

1 hour ago, CH4Pz said:

@rob10 maybe start with disabling hot plugging on your controls, see if makes a difference?

Unfortunately I've had that off for a long time now.  Thanks for the suggestion though.

[Reflected]

I haven't played this mission because I really s*ck at the Hornet but I find it very, very unlikely that restarting the mission would have any effect on the triggers. The same triggers are loaded each time. Chances are you did it right the 2nd time around. 

[baltic_dragon]

Hey guys, sorry for not replying earlier - I was AFK over the weekend. I had this report just before launch from one other fellow campaign dev and he had the same issue. We tested it with 3 different beta testers and none of us could reproduce this problem. The triggers are all set as they should be, frequencies are OK - there is nothing I can do on my end to fix this one unless I have more information about it. 

What sometimes helps in situations like this:

0) Obviously check that you are on correct radio channels
1) Make sure that EASY COMMS are set to OFF (that one is crucial)
2) Check that you don't have any unofficial 3rd party mods installed / enabled 
3) Apps like VAICOM / VOICE ATTACK also tend to mess up the mission logic for some people, try to disable those
4) If nothing helps, run a repair.

@rob10 I'll have a look at your track a bit later today and see what is happening (or what is not happening there). 

I'll get back to you guys with more info as soon as I can. 

[Bullen]

1 hour ago, baltic_dragon said:

Hey guys, sorry for not replying earlier - I was AFK over the weekend. I had this report just before launch from one other fellow campaign dev and he had the same issue. We tested it with 3 different beta testers and none of us could reproduce this problem. The triggers are all set as they should be, frequencies are OK - there is nothing I can do on my end to fix this one unless I have more information about it. 

What sometimes helps in situations like this:

0) Obviously check that you are on correct radio channels
1) Make sure that EASY COMMS are set to OFF (that one is crucial)
2) Check that you don't have any unofficial 3rd party mods installed / enabled 
3) Apps like VAICOM / VOICE ATTACK also tend to mess up the mission logic for some people, try to disable those
4) If nothing helps, run a repair.

@rob10 I'll have a look at your track a bit later today and see what is happening (or what is not happening there). 

I'll get back to you guys with more info as soon as I can. 

I had this bug as well yesterday. The communications worked the first time a played the mission, but DCS crashed mid mission so I had to start over, and every single time after the first playthrough, the communications would not work. But I might have found a solution, easy communications were off for me, but I enabled easy communication then clicked apply, then I went to options again and disabled easy communications straight away. I started the mission and if it wasn't fixed, I restarted the mission and then it worked. As soon as I shut down DCS, the mission would break in the same way, and I had to do this procedure again, I tried it twice, once without VR and once with VR, and got the mission to work both times. 

Edited December 9, 2024 by Bullen

[baltic_dragon]

Clearly this is something on the DCS side then, though it will be difficult to report it.. but those having problems, can you try the solution above?

[CH4Pz]

59 minutes ago, Bullen said:

I had this bug as well yesterday. The communications worked the first time a played the mission, but DCS crashed mid mission so I had to start over, and every single time after the first playthrough, the communications would not work. But I might have found a solution, easy communications were off for me, but I enabled easy communication then clicked apply, then I went to options again and disabled easy communications straight away. I started the mission and if it wasn't fixed, I restarted the mission and then it worked. As soon as I shut down DCS, the mission would break in the same way, and I had to do this procedure again, I tried it twice, once without VR and once with VR, and got the mission to work both times. 

Interesting, i also didnt mention, that i disabled the launcher around same time as the fixes above. In the past it was known for re-activating easy comms, not why i disabled it, i just dont like it, but maybe causing something to crap out?

[rob10]

7 hours ago, baltic_dragon said:

Hey guys, sorry for not replying earlier - I was AFK over the weekend. I had this report just before launch from one other fellow campaign dev and he had the same issue. We tested it with 3 different beta testers and none of us could reproduce this problem. The triggers are all set as they should be, frequencies are OK - there is nothing I can do on my end to fix this one unless I have more information about it. 

What sometimes helps in situations like this:

0) Obviously check that you are on correct radio channels
1) Make sure that EASY COMMS are set to OFF (that one is crucial)
2) Check that you don't have any unofficial 3rd party mods installed / enabled 
3) Apps like VAICOM / VOICE ATTACK also tend to mess up the mission logic for some people, try to disable those
4) If nothing helps, run a repair.

@rob10 I'll have a look at your track a bit later today and see what is happening (or what is not happening there). 

I'll get back to you guys with more info as soon as I can. 

No worries.  I think it's going to be a challenge to track down.  In likely 10-15 attempts so far I managed to get comms to come up once.  Fortunately I made it through the mission on that run .  Quadruple checked the freqs (even made sure the presets were coming up with correct freq) and even turn off that preset and back onto it to see if that jogged it.  Never use Easy Comms but I had gone in checked, closed, reopened and unchecked because I know that can be an issue.  I had all mods (except Tacview and SRS (which wasn't running)) removed and did a full slow repair.  Have never had Vaicom or voice attack installed.  I'm running with a WinWing full MIP setup so SimAppPro running.  I think that's about the only thing I didn't try without and just because I knew you were using a WW setup so I figured it wouldn't be that.

Ping me if there is anything else I can do help you track down the issue.  It can't be a complex trigger so there's got to be some weird little quirk on some systems not triggering it.  And it definitely doesn't seem to be happening to many people.

[CH4Pz]

10 hours ago, rob10 said:

No worries.  I think it's going to be a challenge to track down.  In likely 10-15 attempts so far I managed to get comms to come up once.  Fortunately I made it through the mission on that run .  Quadruple checked the freqs (even made sure the presets were coming up with correct freq) and even turn off that preset and back onto it to see if that jogged it.  Never use Easy Comms but I had gone in checked, closed, reopened and unchecked because I know that can be an issue.  I had all mods (except Tacview and SRS (which wasn't running)) removed and did a full slow repair.  Have never had Vaicom or voice attack installed.  I'm running with a WinWing full MIP setup so SimAppPro running.  I think that's about the only thing I didn't try without and just because I knew you were using a WW setup so I figured it wouldn't be that.

Ping me if there is anything else I can do help you track down the issue.  It can't be a complex trigger so there's got to be some weird little quirk on some systems not triggering it.  And it definitely doesn't seem to be happening to many people.

Did you try disabling the launcher? I think that may have been what fixed it for me, but really need someone to confirm

[rob10]

3 hours ago, CH4Pz said:

Did you try disabling the launcher? I think that may have been what fixed it for me, but really need someone to confirm

I've had it turned off since after about the 1st time it ran.

[baltic_dragon]

@rob10 can you contact me on Discord? I have an idea what might be done to fix the mission, but I need some people who experienced the problem to launch the updated version..
My Discord alias is balticdragon. Thanks!

[baltic_dragon]

Guys, I think we found the issue - you should move the HUD brightness knob far enough for things to start working. Obviously, I'll update the mission so that it doesn't cause any extra issues. 

[rob10]

1 hour ago, baltic_dragon said:

Guys, I think we found the issue - you should move the HUD brightness knob far enough for things to start working. Obviously, I'll update the mission so that it doesn't cause any extra issues. 

On further testing, it seems if you have it bound to a physical knob and the "sync controls on start" option checked, you may need to turn the HUD brightness OFF, then back ON.  Seems to cue on the HUD actually powering ON rather than specifically the knob.

[MAXsenna]

On further testing, it seems if you have it bound to a physical knob and the "sync controls on start" option checked, you may need to turn the HUD brightness OFF, then back ON.  Seems to cue on the HUD actually powering ON rather than specifically the knob.

Nice find! A "trick" I've found regarding getting axis to trigger triggers, is to set them as sliders, and add a deadzone in one end, and reduce the saturation a tiny bit in the other end.

Sent from my SM-A536B using Tapatalk

[rob10]

7 hours ago, MAXsenna said:

Nice find! A "trick" I've found regarding getting axis to trigger triggers, is to set them as sliders, and add a deadzone in one end, and reduce the saturation a tiny bit in the other end.

In this case, once I figured out the WHAT it worked no problem.  It was just a case of I never bothered to turn if off and because it was a physical knob that synced already at 1/2 or whatever at game start the HUD was turned on so never triggered the changed state from off to on.  So once I turned it down far enough to turn the HUD to OFF, then back ON it worked.

Good general tip though!