devtrackers.gg
-Bug type: Sound
-Description: No rear audio. Left, right and forward work but rear audio does not.
Tested directional audio in other games (CS:GO, QC, QL) no issues.
I believe this should now be fixed, can you confirm in the latest version?
-Bug type: Sound
-Description: No rear audio. Left, right and forward work but rear audio does not.
Tested directional audio in other games (CS:GO, QC, QL) no issues.
I believe this should now be fixed, can you confirm in the latest version?
Hit that jump pad directly in front of you in your screenshot while running forward and you can join the bot. There are some space ships out there for you to explore.
As you have identified, bots don't collide with props right now. We plan to fix that relatively soon.
-Bug type: Performance
-Description: Game keeps randomly crashing. Happened about 8 or 9 times now since launch at 1pm, never had any issues in past closed beta
-Reproduction: Seems completely random, but happens more often in 3v3s. In the middle of play game just goes straight to desktop and I submit the error reports
Hardware: nvidia GTX 1080, Intel i7-6700K, 16gb DDR4ram
The game has been very unstable today. There was one crash that's on us that received three failed fixes through the evening, where I thought I was fixing different things but I was just covering symptoms of a root problem that was finally fixed in v212 or v213. We are not receiving reports of that crash any longer and that has been the most significant one. Unfortunately we are also seeing two crashes of lesser frequency that we cannot address because they are happening on 3rd party dependencies, so unfortunately those have to way until the parties responsible can contact us back and couldn't be fixed today, sorry!
Bug Type: Gameplay
Description: Randomly, There appear PNCR "ghosts" on the map when turning some corners. Mostly its 2 pncr tracers which do not seem to have any direction in common. This is extremely distracting and can lead to you running somewhere because you think there is a fight.
Reproduction: It started after 3 minutes in my first game, then persisted through Brawl, Instagib and Wipeout. Didnt test wee-bow, 3v3v3 or the ranked modes yet.
This bug was fixed in v214. We missed this even though it's very obvious because it was the byproduct of last-minute fixes to get rid of some hiccups. Sorry!
Read more-Bug type: Performance
-Description: 50-60fps with win10 / 3900 / 2080ti / 32GB (was way over 200 with previous beta a few months ago), its not locked to 60 because it does 75 when facing a wall
-Reproduction: Start game, go into practice mode
EDIT 1: 150fps when only sky is in view on practice level, then 50fps when facing the rest of the level
EDIT 2: Sometimes stays at capped 200 fps on starting game, then after 30-60secs goes back to 50/140 fps
EDIT 3: GPU 100% whether at 50/150 fps, and normal fps (200+) randomly works, then back to 50/140, hmmm it just went to 250fps with 40% GPU, then back to 100% at 50fps, wtf?
EDIT 4: GPU 40% with vsync on with solid 120fps, but vsync :-(
EDIT 5: Raven fixed it by telling me to update to 451.77 from:
https://www.nvidia.com/download/driverResults.aspx/162469/en-us
I just installed it without u...
This shouldn't be happening anymore. The extreme slowdowns were caused by looking at a volumetric light. We were using old middleware from Nvidia for this as a placeholder, and apparently it doesn't play nice at all with certain GPU's or driver versions. We have taken this out and we will replace this with a custom implementation that won't be anywhere as slow, consisting of either proper volumetric lights or something more efficient and archaic that does the job. The idea was always to replace this as we've done with many other unsuitable dependencies over the years, because it was always quite slow, although this catastrophic level of performance was obviously new to us and we didn't see it in our private testing group. You do report a bunch of things in there, though, and some of these may be different issues that we have yet to identify, though I'm pretty sure most of that can be attributed to this issue.
For performance reasons the HUD is now rendered by the engine which included having to remake the HUD elements, because of that the G-Meter stopped working and it is not available at the moment
In Settings-Weapons you can set your normal sensitivity from csgo, click mouse details, select Quake/Source, click apply
-Bug type: Performance/UI
-Description: Screen only showing 1/4 of the game. Can't change resolution even after changing settings and restarting game. Everything else seems normal (main menu, settings tab). Only ingame.
-Reproduction: Happens instantly when launching the game and in practice range. Screenshots: https://imgur.com/a/JLV03KM
-Specifications: AMD ryzen 7, NVIDIA Geforce RTX 2070 Super, 32Gb ram
Render scales lower than 100% should work in the latest patch without zooming in
[deleted]
Lower than 100% render scales should be working now
-Bug type: Performance
-Description: Getting between 50-70 FPS on Refinery and Furnace but getting 150+ on Wellspring. When FPS is low GPU utilisation is ~15%.
-Reproduction: Playing on Refinery and Furnace
-Specifications: R5 3600, RX 580 8gb, 8gb of RAM
Have you tried the most recent version? If yes and you still have the issue some people have reported that using the latest recommended 20.4.2 has helped them, it hasn't helped others, got 1 report that the latest /beta) drivers helped
Read more-Bug type: Performance
-Description: 50-60fps with win10 / 3900 / 2080ti / 32GB (was way over 200 with previous beta a few months ago), its not locked to 60 because it does 75 when facing a wall
-Reproduction: Start game, go into practice mode
EDIT 1: 150fps when only sky is in view on practice level, then 50fps when facing the rest of the level
EDIT 2: Sometimes stays at capped 200 fps on starting game, then after 30-60secs goes back to 50/140 fps
EDIT 3: GPU 100% whether at 50/150 fps, and normal fps (200+) randomly works, then back to 50/140, hmmm it just went to 250fps with 40% GPU, then back to 100% at 50fps, wtf?
EDIT 4: GPU 40% with vsync on with solid 120fps, but vsync :-(
EDIT 5: Raven fixed it by telling me to update to 451.77 from:
https://www.nvidia.com/download/driverResults.aspx/162469/en-us
I just installed it without u...
I've heard a report that updating to nvidia drivers 451.77 has helped them
-Bug type: UI
-Description: Can't rebind ready key in settings-Bug type: UI
-Description: No movement key overlay in hud
To rebind the ready key for now, you can type the console command /bind KEY ready
Bug type: performance
Description: fps hovers around 70 instead of the usual 240. Sometimes it works properly and drops to 70 the next map.
Reproduction: happens every time after a map change, sometimes even on the first map after game relaunch.
Specs: 3900x, Vega 56, 16 GB 3200 MHz CL14 RAM
Various people have been reporting issues with some of the newer AMD drivers (that have been released after 20.4.2) and have had their fps return to regular levels with by reverting to the recommended version 20.4.2, is that the case for you?
-Bug type: OS Integration?
-Description: Unable to route audio output to different device using "App volume and device preference" aka "sound mixer options" in Windows 10.
-Reproduction: In Windows 10, open start menu, search for "mixer", best match should be "sound mixer options", open that, find Diabotical in the list of open apps, change output device to something else, check OBS to see if audio is being routed to that output. (Currently the output is permanently stuck to Windows' default audio output device)
Currently it's not possible to change audio devices after the game has started, only before
-Bug Type: Game freezes when the game launches and the bot salutes
-Description: When the intro animation plays and your bot salutes mid salute the game crashes
-Reproduction: Me just launching the gameI've tried varifying files and theres always more to install too
What are your computer specifications?
