Removing Mission will end in xxx seconds Chat message [Solved]

[Superblu]

Hi fellow pilots,

i couldn't find any answer anywhere so i'll leave the question here:

is there a way to disable the "mission will end in xxx seconds" message ?
It does get annoying even though we can hide it by hiding the hud, since it still procudes the chat message "beep" sound.

 

 

Thanks


S!

 

 

 

edit: edited the title to better resemble the topic and added [solved]

Edited January 25, 2017 by AMVI_Superblu

[Sketch]

This is a global message generated by the "Subtitle" MCU  that was created by the mission editor, and can't be turned off. The mission editor can set the size, duration, and location of the message though - Food for thought.

[KG200_Volker]

Edit your sds file in dediserver and change the "Mission end time out" , there you can see how many seconds before the end of the mission you ll get the warnings for it.

Edited January 18, 2017 by KG200_Volker

[Superblu]

This is a global message generated by the "Subtitle" MCU  that was created by the mission editor, and can't be turned off. The mission editor can set the size, duration, and location of the message though - Food for thought.

Thanks for the hint.

Will play around with it later tonight

[curiousGamblerr]

You can turn off the chat sounds, I think it's interface sounds or something in the settings. It's great to get rid of that annoying sound.

[coconut]

1. Set the mission duration in the sds file to unlimited (-1).

2. Modify the mission to make it end after the desired duration: Mission Begin -> Timer -> End Mission

 

 

 

Sketch' timestamp='1484701621' post='433511'] This is a global message generated by the "Subtitle" MCU that was created by the mission editor, and can't be turned off.

 

No, I think he's talking about the chat message. These can't be controlled by the mission.

 

 

 

Edit your sds file in dediserver and change the "Mission end time out" , there you can see how many seconds before the end of the mission you ll get the warnings for it.

 

Not 100% about this, but I think this is the dealy between the end of the mission and the start of the next mission. This is useful to let people look at the final score board, and more importantly to let the server load the next mission. If it takes 2min for the server to load the mission, you don't want clients to attempt reconnection for the next mission too early.

[Superblu]

1. Set the mission duration in the sds file to unlimited (-1).

2. Modify the mission to make it end after the desired duration: Mission Begin -> Timer -> End Mission

 

 

Hi coconut and thank you for you tip.

 

I'm probably doing something wrong though as i am not having much luck.

I manually edited my server's .sds file to set MissionEndTimeout = -1 (from the DServer interface i can't go lower than 0)

I did add Mission Begin > Timer (360 minutes) > Mission End as you suggested

 

But when i load the mission, it just ends after about 1 minute and rotates to the next one.

I tried the same mission but with the MissionEndTimeout = 0 just to make sure but still same result. 

 

Am i missing something else ?

 

 

 

edited to fix some typos

Edited January 22, 2017 by AMVI_Superblu

[coconut]

 

 

I manually edited my server's .sds file to set MissionEndTimeout = -1

It's the maximum round time (as it's called in the interface) that you want to change. Check "unlimited"

[Superblu]

Here, i'll attach my dserver settings screenshot.

As you can see, the max round time is already set as 'unlimited' (always has).

 

What i noticed prevents the rotation to the next mission after approx. 1 minute is the 'Mission End Timeout' (if set to 0 it rotates after 1 min, otherwise after the given amount of time in seconds).

 

Might be worth mentioning i have my mission set as "Deathmach" In the editor.

 

[coconut]

If you are referring to the chat messages shown when you finish a flight, try setting the "Finish Mission Timeout" to 0. However, that will cause your plane to despawn instantly.

[KG200_Volker]

Your mission most propablly ends because you have 0 points set for victory condition. Put something like 5000 and check again

Edited January 23, 2017 by KG200_Volker

[Superblu]

I'm probably not managing to explain the issue properly.

I am referring to the exact parameter on the dserver named "Mission End Timeout" which needs to be valued in seconds.

This parameter decides for how long a mission will go on. For example for a value 21600 (seconds) it will run for 6 hours, then rotate to the next mission in queue, doesn't matter if mission objectives were completed or not.

 

Now, having this parameter set with whatever value, leads to a chat message that is automatically sent every minute saying "The mission will end in XXX minutes." 

I am searching for a way to disable this message.

 

At first i thought i could just set the "Mission End Timeout" at 0 but doing so just makes the mission end after 1 minute.
Same result if i try setting it at -1 by manually editing the .sds file.

 

I hope i managed to explain the issue better this time around.

 

 

 

I think Volker might be on the right track as my mission is a training grounds type for my wing mates and as such there are no objectives set.

How do i set a given amount of points as a victory condition ?

Edited January 24, 2017 by AMVI_Superblu

[coconut]

 

 

This parameter decides for how long a mission will go on

That is not correct. I have mine set to 30, and missions on my server run for longer than 30s.

 

 

 

I think Volker might be on the right track as my mission is a training grounds type for my wing mates and as such there are no objectives set. How do i set a given amount of points as a victory condition ?

Set it to 42. Seriously, in your case anything that isn't 0 or less will be OK.

[KG200_Volker]

" Team points per round "

[Superblu]

" Team points per round "

Holy cow i'm blind!

Why the heck i didn't see that untill now ... that did it!

 

That is not correct. I have mine set to 30, and missions on my server run for longer than 30s.

 

 

 

Set it to 42. Seriously, in your case anything that isn't 0 or less will be OK.

After using the suggested parameter it does last longer than the mission end timeout.

So i guess said timeout only starts after the whatever victory condition is met.

 

 

Thanks both of you!