To update other people having similar issues. I had a chat with VegetableVampire and I suspect this is a congestion issue from a less than ideal connection to the server and not an issue with our backwards reconciliation implementation. The main thing I want to focus on right now is that he has good aim with pncr but poor aim with shaft. Shaft is a lot of packages very fast so if the connection is not great and our transport has some issues that's gonna cause some congestion and momentarily increase your latency. With the latency changing so rapidly the backwards reconciliation algorithm starts failing.

We have a tentative fix for this and it's being tested. For anybody having a especially bad experience with LG compared to other weapons, I'll update when we think we have a fix.

UPDATE: Got good feedback on the fix so going ahead and pushing this as v294.

Ah good to know, thanks for confirming. Unfortunately Diabotical may be more likely than other games to expose issues like this as it leans very heavily on the GPU and tries to keep CPU usage lightweight (1,2). This is desired for stability/smoothness because, to oversimplify, GPU workloads are more predictable (less variability between frames). It has the inconvenient that cards get a bit hot and people freak out a little.

(1) This is not to say that our current GPU power usage is entirely justified in relation to the frame-rates we are achieving, this can and will be improved over time, and things won't have to get quite so hot to get the same FPS.

(2) This is also not to say that we have been completely successful in making CPU usage super light either, we are getting there.

So far I haven't seen a delta so high, people report a few % difference, and we are going to improve that, right now we are trying a pure conservative approach to make sure it's completely solid. But it shouldn't be that bad right now. Could you DM me on Discord? Thanks!

Ah, sorry, actually I meant "report" in the general sense, as in just saying so on this thread for example. We don't have a bug report form in game yet.

When you say that the screen gets frozen and yet you "can still play", I'm going to assume that you mean that the visuals become static, nothing changes, but you still hear sounds as if the game is still going on.

Your settings folder is C:\Users\AppData\Roaming\Diabotical (You can there by going to %appdata%/Diabotical in Windows explorer or in Windows+Run)

After closing the game, rename "settings.txt" in that folder to "backup-settings.txt" to reset your settings without losing them.

If that fixes it, send us the offending "backup-settings.txt" for analysis. You can send me this on Discord or you can put the context in a pastebin and DM me the link on Reddit.

If that doesn't fix it and you have the Nvidia overlay enabled, try disabling it.

If that still doesn't fix it:

• Can you tell me if you are on a laptop?

• Can you tell me if you on a setup where you are using multiple graphics cards simultaneously?

...

0.20.292

• Fixed players not being able to grab items from the item spawn locations
• Fixed the map vote in the Game Report not showing up
• In Aim Arena and Rocket Arena you no longer get a Smoke Weeball in the Weeball rotation, only Explosion, Slowfield and Implosion

Please report if this happens again after reading this message. We pushed a tentative fix for this to the servers 20 minutes ago, though the bug had more to do with picking weapons than swapping to them. Could it be that's what you both experienced, were you actually getting the weapons in the weapons list? Thanks!

For this bug thread we would also be interested in hearing from people that had performance problems, crashes, or input problems in the last stress test, who no longer have those problems in this stress test, if you can provide information about your issue in the past and your computer specifications as well, that could be helpful.

There are some bugs that we haven't gotten around to which we are aware of:

- Taking damage from your previous life including dying on respawn after dying if you fall off the map

- Doors not being openable by firing projectiles at them

- Grenades going through doors, going through walls, not bouncing, doing more than 100 damage

- Nvidia Shadowplay not recognizing Diabotical, you can try using desktop capture or adding Diabotical as a game

- Dodge getting stuck on repeat when you press it as you die, if this happens to you, press your Dodge key again

- Firing animation on some weapons remaining act...

This is the last planned Stress Test. It's possible there may be a sporadic stress test if we need to test netcode. For now Diabotical will be available until Monday morning 10 AM CEST https://www.timeanddate.com/worldclock/fixedtime.html?msg=Diabotical+Stress+Test+4+End&iso=20200817T10&p1=239

0.20.297

• Fixed the missing bouncing sound when grenades bounce on the ground
• Renamed the minimap creation command /discover to /radar so that /disconnect can be tab auto-completed from /dis, as requested by winz. Example usage: https://i.imgur.com/BnYclaQ.png - note that leaving an ongoing ranked match will result in a queuing penalty

0.20.296

• Improvements to Rocket Jumping and Blaster Jumping feeling...

For the record, you shouldn't feel bad about that :) We work with both objective and subjective feedback, and sometimes subjective feedback is very important where hard data is incomplete or hard to analyse. In fact I do often ask specifically for "subjective feedback" on changes, like having someone jump around shooting at things for a while back and forth between two versions and just see what feels better. You'd think this is error-prone but it is actually exceedingly rare that a player gets it wrong when it comes to telling which is better between A and B (at least in my experience). The same goes with "feels like X" statements as you mention. There is more commonality with the way we choose to describe sensations than one might expect and it is rare that things are described in a way that is so abstract that you can't make sense of it.

OK, we might need to subdivide this issue yet again because there's also two things in here that we could be talking about.

The issue that affected mouse input, the one that we think we have improved/solved, also affected keyboard input. That would be conceivably consistent with what you are describing, if so this may also be solved.

To know if the issue is the other thing that I was mentioning in my post (i.e, you find friction is just too low), during the next test, start a custom game pasting this in the Commands field:

phy_surface_friction: 20;

phy_accel_ground: 20;

This is going to make you super grounded, pinning you to the ground as soon as you touch it, kinda like Super Meat Boy. It's an extreme so you can see if that's at the root of your feedback. The ground acceleration is increased in this example to compensate for the increased friction, the value is not exact to keep things as they were, just ...

Regarding this issue with multi-threaded input:

https://www.reddit.com/r/Diabotical/comments/i31g0s/game_started_feeling_slow_or_floaty_is_it_just_me/

We made several improvements and fixes to multi-threaded input yesterday. We have had good results in our internal testing group.

• People who previously felt ON was better than OFF, now think the the difference is more pronounced and multi-threaded is even better. The qualifier "crisp" has come up a few times.

• On the si...

Thank you for playing in the Diabotical Stress Test 3! The next Stress Test will start on August 15th at 19:00 CEST. Check it in your timezone here

If you played during this stress test or during the closed beta weekends in March you do not need a new key to play in the following stress test, the game will receive an update in your library that will re-enable it when the stress test starts. If you haven't played Diabotical yet and don't have a key you can sign-up to receive one on ...