Open def- opened 2 years ago
What version? I've tried multiple builds and get the same behavior on all of them.
He should make a video I do not understand what technique he is refering to but, you can do auto laser shots in latest master. https://youtu.be/rB_TZPvIeCg
But if you do it with 16.1 on a latest master server you will probably get minor prediction errors (I tested it, it still works but looks sometimes like wrong timing), because of: https://github.com/ddnet/ddnet/pull/5032 as we use now a new input handling that is in master fixed here: https://github.com/ddnet/ddnet/pull/5320
Any way to post a demo? I can't seem to post a .demo here.
I am using 16.1 native app, not steam
cl_dummy_restore_weapon 1 fixes this
I am using 16.1 native app, not steam
@def- He messaged me and we tried a number of things, but without success. A clean settings file, multiple dummy settings. Whatever it is, it's most likely due to performance. Hes using a laptop, quite a old one aswell, or atleast not very powerful.
Would be good if he would try the latest master build (or nightly), if it with that version works, then we can be kind of sure it is the change that I mentioned above.
I have tried 16.0.3, 16.1, and nightly build. It worked briefly with 16.0.3 then proceeded to stop working.
Please tell me if y'all can see my messages. GitHub flagged my account for some reason, even though I have never used GitHub.
He tried older builds and the nightly, no changes.
Smells like a race/UB, such a hard to investigate one as well. Not quite sure what we could do here. I'll try to investigate the entire codepath see if there is anything suspicious.
It is a weird one. It did start happening when I downloaded the most recent update, but going back an update and also trying nightly didn't fix it. It's never been an issue before so I have no clue.
cheeser0613 just reported this aswell. Happened whilst playing Stronghold and apperantly fixed itself somehow after some time.
On Stronghold there is no laser. So I probably do not understand whats the technique they are using. Maybe he used gun.
It is probably strongly related to the shotgun bug. (Thats what I told at the beginning. Because we are handeling inputs now one tick earlier). We could test it, if you set prediction margin to 300 (or 200) and try the technique on our servers but with 16.1 client.
On Stronghold there is no laser. So I probably do not understand whats the technique they are using. Maybe he used gun.
It is probably strongly related to the shotgun bug. (Thats what I told at the beginning. Because we are handeling inputs now one tick earlier). We could test it, if you set prediction margin to 300 (or 200) and try the technique on our servers but with 16.1 client.
The title is abit misleading. This bug happens when turning dummy hammerfly on/off in rapid successions. Whenever dummy hammerfly is turned off, the tee changes to a random weapon, regardless if cl_dummy_restore_weapon is set to 1 or 0. (becomes a problem when using deepfly aswell)
the tee changes to a random weapon, regardless if cl_dummy_restore_weapon is set to 1 or 0
Does this also happen on master/nightly, could you reproduce it, or do we still only have the reports?
the tee changes to a random weapon, regardless if cl_dummy_restore_weapon is set to 1 or 0
Does this also happen on master/nightly, could you reproduce it, or do we still only have the reports?
Only reports, cheeser0613 says he is able to reproduce this, but I didn't quite understand how. You can message both people on the DDNet discord ^^
Toasty Loaf reports: