[Bug] Analog steering cause no walk animation.

[Xenon]

Description
Steering with gamepad cause no walk and run animation.

Reproducible
Always.

What you were doing when the bug happened
I just walk using gamepad.
[spoiler]https://www.youtube.com/watch?v=7PDVLAIEW5U[/spoiler]

What you think caused the bug
Sync issue.

[rww]

I reported it before public relase 04rel005 :/

https://youtu.be/F35upJXyD-s

[rww]

it never was synced in 04

In Client-Side update topic:

Fixed players with joysticks/analog pads having bugged move animations.

[Stormeus]

Joysticks are probably still broken, what about directional pads?

[rww]

about 004 since it was before, now I got you are talking about private tests.

I know, but it's better that it's fixed? Sorry. I did not have bad intentions.

[Stormeus]

about 004 since it was before, now I got you are talking about private tests.

I know, but it's better that it's fixed? Sorry. I did not have bad intentions.

Sure, this is why Xenon posted it. It seems alot of stuff in this update are broken. I don't know a reason why.
Do betatesters informed about all those bugs to developer before public relase or it was unknown bugs for testers? I just don't know how it possible to miss such critical bugs while it was 'tested'.

Relax. rww did report the joystick issue before release and I figured it wasn't critical to hold the release back, putting it in the changelog was my mistake. Most of the other bugs being reported have been long-standing issues aside from the gunplay inaccuracies I'm working on right now. What you don't see is the critical issues they caught before I made the release public.

[NewK]

Do betatesters informed about all those bugs to developer before public relase or it was unknown bugs for testers? I just don't know how it possible to miss such critical bugs while it was 'tested'.

We've informed about the bugs we detected, unfortunately we didn't detect all of them. If you're looking to find a perfect beta testing team that will always detect 100% of the bugs you will not find it anywhere in any software team

And as stormeus has already said there were a ton of other bugs that the public never got to see because they were detected by the beta testers before public release, some of them alot more critical than these "critical" ones you say.

[NewK]

Public tests are better because it testing by people who actually playing vc-mp and at least using weapon to find such bugs. Don't take it as an offense but it's really something wrong there.

That's alright, no offense taken. But I disagree about something being wrong. It's just the nature of software development in general. Like when you develop any type of software product,  you don't push it directly to the client, first you test it internally, and only then, you test it publicly. It's the same scenario here.

[kennedyarz]

I reported it before public relase 04rel005 :/

https://youtu.be/F35upJXyD-s

if I had seen this on my server I swear I gave ban by speed hack since that is how hack trainer hack behaves..

and it is true that developers are only interested in people who do not play VCMP. people who already leave the game and who are there only to let go so many mistakes. until 'really we who play' explode in our faces so many errors causing an explosion like that of a Russian missile

[Stormeus]

and it is true that developers are only interested in people who do not play VCMP. people who already leave the game and who are there only to let go so many mistakes.

Here's a copy of VC:MP 0.1c's source code, feel free to go make your own better multiplayer: https://github.com/ziggi/vc-mp

[kennedyarz]

and it is true that developers are only interested in people who do not play VCMP. people who already leave the game and who are there only to let go so many mistakes.

Here's a copy of VC:MP 0.1c's source code, feel free to go make your own better multiplayer: https://github.com/ziggi/vc-mp

pfffffffsssss. what a great response

[NicusorN5]

and it is true that developers are only interested in people who do not play VCMP. people who already leave the game and who are there only to let go so many mistakes.

Here's a copy of VC:MP 0.1c's source code, feel free to go make your own better multiplayer: https://github.com/ziggi/vc-mp

pfffffffsssss. what a great response

You make me laugh.

[NewK]

If any of you beta testers would be a player those weapon sync bugs were found during private tests without making it public... It's just technically impossible to miss it if you are using weapon in the game. Testing this 'software product' you need to use it as typical user using (player), not as a scripter only.

Of course, I'm not saying public testing is unnecessary. But that doesn't mean private testing shouldn't be done either. It's as I said, releasing any type of software without doing some internal testing first is just silly. And just so you know there were other sync bugs that were detected by the beta team that the public never got to see, some of those related to DMing even though "we are not players" like you say. But it seems as if you expect us to catch every single bug, as I said before there are no perfect beta testers that will always detect all of the bugs. Not here and not anywhere. There's big game franchises out there with a paid beta testers team and still they fail to detect some of the "technically impossible to miss" bugs when their game is publicly released. This is just the nature of testing software, it's not easy as it looks. There's tons of books written about this matter alone.

So what you say is "technically impossible to miss" is merely your perception and it actually depends on how each player's play style. For example, DM players will discover DM related bugs, while RP type of players will discover different types of bugs and every one of them will claim those bugs are "technically impossible to miss", because of the nature of their tests.

[NewK]

It means there no DMers in "private tests". And yes, desync of weps and kicking for that by server's anticheats were not possible to miss if any of you were DMers.

But we did detect bugs while DMing:

And just so you know there were other sync bugs that were detected by the beta team that the public never got to see, some of those related to DMing even though "we are not players" like you say

Also some of the bugs were not reproducible 100% times and only happened after certain conditions were met. For example being kicked when exiting the seasparrow. That happened but only if the player was holding any weapons. That's an easy bug to miss. It's not "impossible" to miss it. So it's not because there were no DM'ers on the team (because we detected  other DM bugs too). It's simply because of the nature of how each players does his tests.