[REPORTED] yellow hitmessages appear, even when server turned them off

[D4n]

As can be seen here, on left side of my screen. I flew Mi-8, hit target (UH-1) with UPK. (occured on BlueFlag caucasus server)

 

 

[D4n]

edited description.

[D4n]

Also red message appeared "DanielNL Mi-8T destroyed", when the UH-1 player crashed... so NOPE, it was NOT me who got destroyed, it was the UH-1!

[Nirvi]

Uncheck realtime bomb damage assistance

 

[Lixma 06]

In Options/Misc see if this box is checked...

 

 

It was introduced, and enabled by default, in the last patch.

[D4n]

This should NOT overwrite the existing enforced MP serversetting called "client kill-messages off"!

Please fix asap (not to overwrite server-setting), this is ruining the realism and is an advantage for everyone who has it enabled currently.

Edited April 6, 2019 by DanielNL

[norbot]

Wow, serious problems...

[D4n]

Kinda... I mean if a pilot's fire-n-forget missile flies at you, you dive behind a hill, missile followes but bandit aircraft looses line-of-sight, you don't want him to know when his missile misses you, right?

[ams999]

DanielNL, sometimes when I read your posts I get the impression that you are close to a heart attack :lol:

 

Anyway, there is no bug.

 

1. "What the...? This should NOT overwrite the existing enforced MP serversetting called "client kill-messages off"!"

 

Those two are not related, the "client kill-messages" are those in the chat.

 

2. If you look in the mission editor you'll notice in the options that, as with "Cockpit status bar" etc., there is the option to switch off 'realtime bomb damage assistance' and to enforce that option.

 

Problem solved, I guess.

[D4n]

Those two are not related, the "client kill-messages" are those in the chat.

Oh ok, didn't know that ED added a 2nd system for showing kills now. (1 system was enough imo)

 

 

2. If you look in the mission editor you'll notice in the options that, as with "Cockpit status bar" etc., there is the option to switch off 'realtime bomb damage assistance' and to enforce that option.

 

Ah wow thanks! As I created this bugreport solely with multiplayer in mind, I hope somebody mentions that mission editor setting to the BlueFlag admins (to ask them to enforce disable that option).

 

Problem solved, I guess.

Yes, thanks! (sorry if you think I'm getting a heartattack)

[Grimes]

Reported.

[D4n]

Thank you

[QuiGon]

Reported.

Now I wonder what you did report, as there is no bug, because server admins can already enforce disabling those messages through the respective setting in the mission editor?

[ams999]

As I was wondering that myself I did a short test with a simple single player mission (Huey and some enemy trucks) and I have to admit that the 'enforce' option for rtbda in a mission doesn't enforce at the moment, i.e. the messages are still shown in mission with enforce 'off' when they're switched on generally (and, vice versa, are not shown even if you enforce 'on' in the mission and in general they are switched off).

Labels can be enforced for example.

I didn't test multi player (i.e. when I'm the client, not server) and I didn't test the enforcement of other options.

[Grimes]

I reported that the BDA setting saved in the forced mission options is not being used and that clients can circumvent the option.

[D4n]

So now it's been over 2 months since report, can we please have this fixed? For realism PvP-servers it's unfair if users get notification that they hit a target (and then also that mouse cursor bug, but the notification client circumvention really really has priority)

[Grimes]

https://forums.eagle.ru/showpost.php?p=3797108&highlight=BDA#post3797108

 

If it is still appearing ensure that the setting is forced in the miz file.

[D4n]

Apparently STILL occuring, according to a mentor in BlueFlag Discord (the huge PvP community). He just wrote

"it is forced off, and yes it's a bug that it can be overridden by player settings"

Edited April 7, 2019 by DanielNL

[Dagger71]

I haven't seen these messages since the patch. DanielNL Why do you say it's still appearing?

[D4n]

I still see them on BlueFlag... so...

[Grimes]

If the track file from last week is to be believed the setting hasn't been enforced in the miz. At least not on the PG mission.

 

   ["forcedOptions"] = 
   {
       ["fuel"] = false,
       ["easyRadar"] = false,
       ["accidental_failures"] = false,
       ["optionsView"] = "optview_myaircraft",
       ["immortal"] = false,
       ["easyCommunication"] = false,
       ["easyFlight"] = false,
       ["radio"] = false,
       ["tips"] = true,
       ["userMarks"] = true,
       ["geffect"] = "realistic",
       ["externalViews"] = false,
       ["padlock"] = false,
       ["civTraffic"] = "",
       ["weapons"] = false,
       ["birds"] = 0,
       ["labels"] = false,
   }, -- end of ["forcedOptions"]

[Dagger71]

so it's not a bug. just a server setting.

[D4n]

so it's not a bug. just a server setting.

 

It seems so, if you have it enabled and you don't get these messages on at least one other MP server, then yes.