Yes, there's something definitely wrong with multi-threaded input.

During the weekend we did a small survey of pros: 2 of them felt multi-threaded input was clearly better, 2 said it felt a bit better, 1 said it feels different but couldn't tell how, 1 said it felt the same. I think this probably means it's working as expected if conditions are right (all of these people have decent setups).

But there is obviously something about it that creates a requirement gate and in some systems it's causing high latency in the input thread. High latency in the input thread would feel really bad so I understand the feedback. I suspect it's going to be something very trivial causing some timer to accumulate excessively. We never caught this during development because we just needed to have the engine exposed to a larger variety of specs. Now we have to do some A/B testing with systems like this and it should be easy to make it work correctly.

So if you have a really not...

Sorry, we will likely use a better procedure at the end of the next stress test which will allow at least most people that are in a match at the end of the stress test to be able to finish them

Thank you for playing in the Stress Test #2! The next Stress Test will start on August 8th 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 ...

It's possible to do so if you flip fullscreen or border less fullscren and then go to the epic launcher's settings, scroll down to Diabotical, enable launch command and set for example -width=1280 -height=720 It will be part of the video settings in the future. There's also something called Masks which can have a similar effect while still having the game on fullscreen you can try them if you go to Settings-Weapons and on the bottom right next to the Crosshair editor click Mask and you can try different types and sizes

That death in the last round is not intended to count in the next round

It's not intentional, it's a bug that hasn't been fixed, projectiles are meant to open doors in the future

Like funcchy said, that is a Mask, go to settings-weapons and next to the crosshair editor click masks, then disable masks in the dropdown

0.20.246

• Disabled more Victory/Defeat screen animations, to test if the crash at the end of matches continues to happen

0.20.245

• Disabled the thunder effect on the Victory screen, to test if the crash at the end of matches continues to happen

This is correct, we'll bring that element back. We need to implement a few features into our UI scripting language to be able to do that again (or redo it completely on the native side, we'll see).

Could you try

• Restarting the epic games launcher then try to start Diabotical
• Verify Diabotical (Library->3 dots button next to Diabotical) then try to start Diabotical
• Delete Diabotical.exe and Diabotical-launcher.exe then verify Diabotical then try to start Diabotical
• Restart your computer then try to start Diabotical

Could you try

• Restarting the epic games launcher then try to start Diabotical
• Verify Diabotical (Library->3 dots button next to Diabotical) then try to start Diabotical
• Delete Diabotical.exe and Diabotical-launcher.exe then verify Diabotical then try to start Diabotical
• Restart your computer then try to start Diabotical

0.20.244

• Fixed a very rare crash that could happen when firing (there is a more common crash that can happen when firing which this doesn't fix)

Hijacking this to leave some quick notes, mainly on stability.

• Sorry that some very obvious bugs like that are still there from the last week, we spent most of the week working on a new game mode, implementing voip in our audio engine (we replaced FMOD with our custom audio engine between closed beta and the first stress test weekend, and our voip implementation hadn't been ported to this engine yet) and fixing some game-breaking issues, like lack of feedback in some scenarios. We'll fix this bug as soon as we can.

• 90% of the crashes we are receiving from reports are again on a 3rd party dependency, which during the week got updated to a new version (to get a fix for another issue), so we didn't have time to experience it internally and it surprised us today. I'll do what I can to get them to do a hotfix release before next weekend.

• There's another crash that stands for 5% of reports that usually happens during alt+tabbing that seems...

0.20.243

• Potential fix for a crash that's happening when Alt+Tabbing
• When a player grabs the Diabotical powerup they now have orange flames surrounding their eggbot in third person
• When a player grabs the Vindicator powerup they now have purple flames surrounding their eggbot in third person

0.20.242

• More information from crash reports is being gathered with this version
• In Extinction the ghost particle effect has been toned down and now remains visible at long distances