It’s a niche issue with a couple moving parts which are probably difficult to deal with
Game 2 ending before Game 1 ends is likely key- Game1 had a target to add the RP to but when it finishes and calculates that module is no longer in need of RP so it just gets destroyed
Changing module targets for RP is likely the issue, it’s likely that it’s locked in when the game starts for score-keeping purposes
“Fixing” this bug would make the grind easier which is not something that motivates development
It’s way easier to be aware of this bug and avoid triggering it than to fix (and it could even be by design).
The only RP I lose is, as soon as I have bought the last boat/ship to unlock the next tier, the RP that was left is gone and 0 RP goes to the new selected one.
What??? Please highlight where you drew that conclusion. Also how can he make anti consumer posts when he is the consumer? Your comment has zero credibility.
Did you watch the linked video in the OP?
This issue has been around for as long as I remember. I’ve even tested this myself on several occasions with the same result. More RPs added to new vehicle research than to modules…
I’ve experienced and known about this for some time. Absolutely no excuse for this bug to still be around. Could’ve likely been fixed by one person in less than a week, but 7 years and still nothing seems more intentional than anything.
Seriously, don’t mind him. He can be best compared to one of those annoying siblings.
Seriously he tried to tell me, the 4.3 SKR got moved up in BR in the previous changes, then it became “at some point” (it was 4.3 on release, and has never been moved), then tried to tell me the RBU-6000 had a range of 1.5km (it’s 6000m, like the name suggests) then deleted all his comments lol.
He’s a good laugh, but I wouldn’t worry.
Anyway, back on topic:
I’m not sure whether to be horrified or impressed. I’m guessing it was bug reported on the old forum and archived?
Which, I will be fair, is perfectly understandable, considering there’s more than one thread on this. However my counterpoint would be, “the more threads and posts exist on the issue, the more incentive there is for Devs to notice and do something” (though 7 years is an awful long time to do nothing!)
Thanks for the plug. Was wondering if there was another post like this!
@Firestarter claiming that those that critique War Thunder are bad things… -_-
Apparently me saying SKR-7 is 4.3 and stating the effective [accurate] range of RBU-6000 along with its maximum range of ~5500 meters is wrong.
Keep demeaning everyone that criticizes War Thunder, all that does is protect War Thunder from criticism.
I wonder if the bug itself is just weirdly complex or nearly impossible to fix without redoing a bunch of essential code. They’ve definitely known about it for a long time, but I am skeptical about it not being fixed is malicious.
@Firestarter There are 8 year old Reddit posts talking about the bug, so it’s been around for a long time.
Wait you really tought Gaijin is taking a second of their time to come here and read what community feels like or want to see??? hahahahahhahahahha
To be fair after what I saw here, how people talk, think of them selves Im not suprised Gaijin is not wasting a nanosecond in here.
Game is good, comunity is garabage.
If you wanna change something use Support hopefully you can change something.
I mean, I’d like to think it isn’t malice, but the near complete radio silence on it makes little to no sense. A transparent, community orientated game dev might at some point say “hey, we’ve identified a bug with the game, we’re struggling to identify a fix, please bear with” at some point - it might even be the case that that has happened at some point, and someone in the know needs to trot out a link to aforementioned statement. (Alternatively, I could go snooping, but it could be anywhere on the old forum, an old Q&A video or post, and that would/will take some considerable time)
It being 7 to 8 years old seems pretty naff.
I feel like that’s a bit unfair. Sure, there are some members of the community that, on balance, aren’t that great, but calling the community outright garbage seems a bit excessive.
This be the problem - there’s been a bug report active and acknowledged for 3 years on the CBR ( Not recieving XP for modules when playing games in quick order // Gaijin.net // Issues), relating to this exact issue. My thoughts behind this post is bringing it back (and keeping it) in the minds and eyes of people - the more people interact with content about this particular bug, the more incentive there is for Gaijin to fix it.
I think there should definitely be a better system of communication in place between the player base and the devs… it is difficult to gauge what is being listened to, ignored, or forgotten when bug reporting in general. Us Baz Meshupar players were pretty much ghosted for a month in response to the lack of TWS/HMD complaints until the snail mercifully blessed us with a patch.
It’s obvious running a forum like this is chaotic and complex, and there is no perfect solution available for directing feedback to and from the players and developers. I also appreciate all the work moderation has done so far to that end. I also think the way that bug reports being shown as community discovered and prompted in devblogs and patch notes is a great step in the right direction. That being said
Even if it probably is not intentional, leaving such a significant bug as research just vanishing for (aproximately) 7 years virtually ignored reads like a major lack of respect for the playerbase on gaijin’s part. When problems like this appear (and they do very often) and get unrepresented it drives a wedge between both parties. Some serious changes need to be made or at least brought up into public discussion if Gaijin wants to avoid a second coming of the big red line on the steam review page.
Hard to find lol
I can point straight away 3 places where to look on top of my head. Account verification code, Battle result code, Code that ties Battle result with Account status/verification or in other words code that ties game client to the user databases. This is where any competent programmer would look first.
Wow so hard to find. Yeah if your code was written like a mess where everything holds by hopes and dreams of employees going home and seeing their familes for once then sure and if you want to look in the first place.
Bugs are not some “Oh it is so hard to find that bug oh I wonder where it is” most bugs if code is well structured are easy to find. Programmer will know exactly where to look. Everything will have clear label. Fixing might take some work or trial and error but it wont take 7 years. Here it would be as simple as add queue reward system or simple check.
It was proven times and times again Warthunder code is just a mess. If it was not, Gajin would not break stuff that was not broken patch before. Every single patch adds bugs in places that do not make sense because they should not been touched based on patch notes.
To be fair, this is all running off the back of a foundation laid 11 years ago which hadn’t (at least probably was not) ever intended to reach this level of feature creep…messy code is an understatement what is probably a pit of despair that has been stretched far beyond its limit
It’s so stupid that Gaijin are still looking into this after so many years. Bugs that increase the grind get ignored but the second there’s a bug that decreases the grind it’s fixed immediately (think faster respawning air rb bases).
I’ve probably lost enough mod rp to spade a top tier aircraft.