just created a bug report about the issue that the naval vessel collision alarm (when boat is destroyed during alarm) is still active after changing into a plane. This is very annoying. I wonder why there wasn’t already such a report in the system.
If you might support my report by addding “same issue”
naval: collision alarm still active after spawning a plane // Gaijin.net // Issues
3 Likes
in the meantime the issue was closed - as there are also no replies to my post I wonder if no one else has the same problem.
1 Like
nope its an issue
only part of the issue though
as
that whole stupid over reporting of tea breaks and brass shining over torps and bombs coming has to be removed asap
Yeah it’s back again - had it a year or more ago :(
With how the bug reporting system works in this game, I really feel sorry for the people trying to deal with this whole mess. You can see how you basically waste your time on this. Trying to help and improve the game is very often like hitting the wall with your head.
This issue is present in the game since the devs changed the depth alert sound. Knowing the devs, it will take years before they even acknowledge this problem.
Moderators who never played Naval will close your reports if they don’t understand what you are talking about. That’s just how bug reporting system works in this game. It’s sad, but it is what it is.
A long time ago I tried to be very patient and after one of my reports was closed without any sense, I PMed a few staff members about this situation. I got a reply from one of them, that in his opinion I’m right and it’s a bug that should be forwarded to the devs, but he can’t do anything about this, and his suggestion was to wait for the next version of the game to be released, write my bug report again (just change the game version to a new one, so I don’t create two exactly same bug reports), and hope that some other moderator will see my report and pass it to the devs. I think this is a very good summary of how the current bug reporting system works. I decided I don’t want to waste my time on doing silly things, and I don’t report bugs nowadays.
BTW: Here is the video I recorded a few months ago as an example of this very annoying issue:
3 Likes
The issue is still present in naval matches - in the meantime they are fixing really minor defects which doesn’t matter anyone …
1 Like
encountered this like 3 times already, despite playing Naval rarely
1 Like
as I am myself developing software I assume that fixing this is much easier as to correct the wrong moustache of a crewmember…
1 Like
Another thing to assume - is how this bug even appeared and whom to blame.
also which guy closed my bug-report w/o even ask some regular naval players about this… ok maybe he didn’t know any naval player at all… :-)
1 Like
Yes, that bug has been active ever since they add the collision alarm. I don’t remember it being ever fixed at any one time since. After a couple hours of gaming session, it can get annoying.
Also:
Fiji map is still bugged for 11451. It gets beached on spawn. Like Tucumcari back in the day.
There is also a spot on the North side of the Black Sea port map, when leaving the spawn. It will catch the bottom of the foils if your not at full speed when leaving. Effecting only the 11451.
The annoying hit to your bridge by MG/Low caliber shell/Shrapnel that doesn’t show up to repair. You have to set repair to “auto (A)” to get it recognize the bridge is officer is knocked out before replacing… which for some reason takes 12 secs, instead of the normal 10 secs.
After last update? The Zoom bug was added as a new naval feature. At the start of a game, when selecting zoom (Z default) instead of showing the POV on the gun direction, it shows POV of the hull direction.
I wish repairing bridge/replacing bridge crew was #1 priority in the repair chain. Its seems to be near if not, last on the priority list which is extremely annoying in some cases.
There are a couple more bugs that are floating around, but these are the ones that bother me the most.
1 Like
imo the reason this will not be fixed is that they think it means they admit that the whole warning system has sucked since they overstocked it with garbage no one wants to know
sadly
the whole warning system has sucked since they overstocked it with garbage very very few want to know
at the expense of all the very important stuff everyone needs to know … as soon as possible
This is one of the weirdest theory I ever hard. If anything, having this kind of bugs in the game shows the incompetence of the devs and that the current reporting system is flawed.
I never saw the original bug report about the issue from this topic, so I don’t know why it was hidden or deleted. But in War Thunder to reach the devs with your bug report, you first have to go through moderation. Bug moderators are not Gaijin employees, they are volunteers. In fact, you can also apply, when they open the application. The last one was here:
Because Gaijin is not paying these guys, the devs are happy that someone is doing the job for free, even if that job is not done very well.
That’s why we have a lot of problems with the bug reporting system. As a player, you can’t reach the devs directly, your bug report has to be passed to the devs first by one of the bug moderators.
If a bug moderator decides that this is not a bug:
Then you can do nothing about this, your opinion doesn’t matter. Your only option is to wait for the next update, create another bug report about this issue and hope that some other bug moderator will pass it to the devs sooner or later. But there is no guarantee it will happen (sometimes the same bug moderator will keep rejecting your bug report), so many players just don’t want to waste their time fighting with the bug reporting system.
I’m quite sure that the devs are simply unaware of this bug. So it’s impossible to fix something they don’t know is faulty. But yeah, it’s pretty funny that this annoying bug exists for more than half a year now. Someone would have to make another bug report about this issue and hope it will be passed to the devs this time. Basically you have to fight the system. I’m too old for this, I have better things to do with my life.
2 Likes
i had one experience with the bug reporting procedure
never a fing gain
this is a screenshot from my (closed) bug report - maybe I should have added a screenshot from the issue (sarcasm)
2 Likes
I suspect it was somehow misunderstood by the bug moderator. Usually putting a video is a good way to show the problem. Especially if the bug moderator doesn’t play Naval, it will help him to understand the issue.
Keep in mind, even if a bug is obvious for all players that play Naval game mode, it doesn’t have to be obvious for a bug moderator that never played Naval.
It would be great if bug moderators only moderated the part of the game they know, but since they do this for free, there is only limited number of volunteers. Serious people are busy with their own lives. If Gaijin offered like 2k€ monthly for this job then I bet they could choose from many great candidates. But with how it works, they have to be happy that someone applied at all.
You would have to create another, more detailed bug report about this problem. If you have time and will, you can also use my video to show this problem. Even if someone never played Naval, watching this video should prove to them that the collision warning is definitely not supposed to work this way.
1 Like
thx, maybe I try to do another one using your Video - but as I had many negative experience with bug reports or suggestions I have not much hope.
1 Like
This is the new bug report:
collision alarm sound is still active after spawning a plane // Gaijin.net // Issues
please feel free to add your “I have same issue” on it
… maybe they now want to have a dxdiag or game log for this… or suggest that I update my sound drivers… lol
I just found another bug report on this
Naval proximity warning still active when flying // Gaijin.net // Issues
This ticket has a very interesting conversation with the moderator and the reporter…
I also added my “same issue” to this
3 Likes
I expect to have my report closed as this is clearly a duplicate - but maybe its passed to another moderator not #1 as in the older ticket… So I didn’t add a link to mine in the older one…
I haven’t seen it this time around - might try to deliberately create it…