DDraceNetwork

08:43

I cant find the 2025 map

yeah, there is a bug, @eidderFsT is working on it

Ham5terzilla (Макс)

Can't connect to certain server hosted on ger2, 176.9.114.238:8332. But can connect to any other server on same ip, for example 176.9.114.238:8341 or 176.9.114.238:8330 (edited)

Addition: 176.9.114.238:8297

176.9.114.238:8297[

] is an official DDraceNetwork (Type: DDrace) server. Quick join: https://ddnet.org/connect-to/?addr=176.9.114.238:8297/

ukr servers are getting ddosed

13:06

no idea how that works

## How can this be 30 %?

just imagine its correct

Cosmic Xenor {Yannik}

## How can this be 30 %?

it's logarithmic

DDNet 18.9 strange aim behavior (too smooth and sometimes incorrect) (edited)

exosphere

DDNet 18.9 strange aim behavior (too smooth and sometimes incorrect) (edited)

demo or spec?

Jupstar ✪

demo or spec?

demo

that's expected at such low speed. client doesn't get nearly enough information to show it accurately.

Also it's a literal aimbot from the dummy, the cursor immediately goes dead center when you click

ye it breaks with dummy, might be fixed if we have more input type info avaliable

16:41

currently no way to make dummy look ok

eidderFsT

that's expected at such low speed. client doesn't get nearly enough information to show it accurately.

but shouldnt it have pos0 - pos1 and never go beyond any of these?

16:43

like what info is it missing

16:43

i never seen that in my version tbh

16:44

or is this simply a dummy bug or smth xd

Jupstar ✪

but shouldnt it have pos0 - pos1 and never go beyond any of these?

it was lagrange interpolated to make curves, cuz the sample rate is so low the linear interp looked inhuman (edited)

16:45

which also means any non curve and super fast movement will look very bad

16:45

the linear interp looked bad is the whole reason spec cursor wasn't merged three years ago when i first PRed it

release candidate 18.9 after win+d hotkey my game freezes and crashes with no message (edited)

18:52

on previous versions its fine

Tsumugi

release candidate 18.9 after win+d hotkey my game freezes and crashes with no message (edited)

Do you have a crash dump in the dumps folder?

19:00

Which fullscreen mode? Which backend?

Robyt3

Which fullscreen mode? Which backend?

desktop fullscreen vulkan

Robyt3

Do you have a crash dump in the dumps folder?

i cant find it

Tsumugi

i cant find it

Does 18.8 work if you run it now? I don't think anything related to this was changed, maybe it's caused by a driver update

19:20

Try if it works with default settings

Robyt3

Does 18.8 work if you run it now? I don't think anything related to this was changed, maybe it's caused by a driver update

yes its fine on other versions

Robyt3

Does 18.8 work if you run it now? I don't think anything related to this was changed, maybe it's caused by a driver update

19:22

no driver update

Robyt3

Try if it works with default settings

what default settings?

All, rename the config directory from DDNet to DDNet.old temporarily

Robyt3

All, rename the config directory from DDNet to DDNet.old temporarily

it crashes (edited)

Did u try to restart windows xd

Run from the console to get a log, or set a logfile

Robyt3

Run from the console to get a log, or set a logfile

oh i found it

DDNet_win64-steam_crash_log_2025-01-02_22-37-39_9624_aaf817a1993ea361e27976d07e7acf0991564a69.RTP

9.9 KB

19:40

dump

Close steam

19:40

Completely

Robyt3

Completely

with steam closed it wont crash

19:43

yeah, I think it caused issues in the past

19:44

00007FFB8FAFDD1D 000001C25FB91C70 0000008055FFEDF0 000001C26A95DA90  amdvlk64.dll!boost::serialization::singleton<boost::serialization::extended_type_info_typeid<_SC_PRIMSHADER_CONTROL_FLAGS> >::singleton<boost::serialization::extended_type_info_typeid<_SC_PRIMSHADER_CONTROL_FLAGS> >+0x1f69d
00007FFC1BD0F90E 0000008000000000 000001C26AC5D5C0 0000008055FFF1A0  SteamOverlayVulkanLayer64.dll!vkGetSwapchainImagesKHR+0x42e
00007FFC1379D3AE 0000008055FFF370 0000000000000002 000001C25FC5BED0  graphics-hook64.dll!dummy_debug_proc+0x3b5e
00007FFBACEC645D 000001C26AE900E0 0000008055FFF650 000001C200000033  vulkan-1.dll!vkDestroyDescriptorPool+0x47d1d

oh well on 18.8 it crashes too

19:44

i just needed 5 times to use hotkey

vulkan calls some generic graphics hooks dll, that calls the steam overlay, that calls the AMD driver which crashes

Robyt3

vulkan calls some generic graphics hooks dll, that calls the steam overlay, that calls the AMD driver which crashes

ok well i just need to disable steam overlay?

yeah, either disable steam overlay or switch to OpenGL

19:46

And potentially report to Steam as bug I guess

Robyt3

And potentially report to Steam as bug I guess

too much work for me

19:47

Do you also use other software that uses overlays, like OBS?

i disabled steam overlay but it still crashes

Robyt3

Do you also use other software that uses overlays, like OBS?

no, but maybe my amd software overlay causes it?

Tsumugi

i disabled steam overlay but it still crashes

Steam probably still injects the DLL into the game process

i dont use it and i dont really know if it works on ddnet

Tsumugi

no, but maybe my amd software overlay causes it?

Maybe the interaction between different overlays

ok i also disabled amd overlay and nothing changed

19:51

imma restart my pc

Robyt3

Maybe the interaction between different overlays

i disabled every overlay and it still crashes

Tsumugi

i disabled every overlay and it still crashes

And SteamOverlayVulkanLayer64.dll still appears in the latest crash dump files?

Robyt3

And SteamOverlayVulkanLayer64.dll still appears in the latest crash dump files?

ye

DDNet_win64-steam_crash_log_2025-01-02_23-03-52_14048_658b13939515263d53d93792b188eae4c77579e7.RTP

9.9 KB

20:05

on opengl its fine i just tested

Tsumugi

ye

So Steam just always adds the DLL regardless of whether the overlay is enabled

20:07

thats why i shouldnt use steam for ddnet bruh

20:08

first time decided to play through steam to play betas and its already non-playable

20:08

I guess you could manually remove the Steam vulkan layer from HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\ImplicitLayers using regedit

Robyt3

I guess you could manually remove the Steam vulkan layer from HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\ImplicitLayers using regedit

ye its fixed now

20:11

thanks

That will break the overlay for everything though justatest

but its obviously not universal solution cuz it disables overlay on every game (edited)

20:13

or no

20:13

it seems like it works for other games

true, it's only the vulkan layer

wtf

Robyt3

true, it's only the vulkan layer

ah

20:13

well only for few games

20:14

ok its not that bad then

20:14

it cant be fixed in game?

is your steam even up to date?

Jupstar ✪

is your steam even up to date?

yes? XD

20:15

it updates itself every launch

I'm just surprised we dont have more reports like this

20:15

i mean basically all ppl use steam

Seems like a bug in either the Vulkan-based Steam overlay or the Vulkan AMD driver, I don't know if we are doing something wrong in the Vulkan backend that we could avoid this

Jupstar ✪

i mean basically all ppl use steam

idk

20:16

im not

Where do you have graphics-hook64.dll from? Can you search for the file to find how you got it and what version it is?

20:18

Maybe you installed software X that provides another version of the DLL

im gonna install everything w8

Looks like graphics-hook64.dll is from OBS, so maybe that also plays a roll

Robyt3

Looks like graphics-hook64.dll is from OBS, so maybe that also plays a roll

true