DDraceNetwork

Gumba

It's so sad, somehow debian based distros were not working anymore (performance governor broken, CPU often stuck on 400mhz, so I couldnt play at all) and now this on Fedora. Please save me from reinstalling windows cammostripes

Client 18.2 from website btw, building myself didnt work cuz i miss dependencies ... (edited)

so you are sure it is the CPU that causes this?

05:57

you could defs try amdvlk https://github.com/GPUOpen-Drivers/AMDVLK which are the open source vulkan drivers by AMD, instead of RADV which are from Valve & RedHat try other backends too. For CPU problems i'd start with cleaning fans, use net energy, set all power targets to max performance, don't use gnome

Do we calculate fps from frametime? Is it possible that we somehow skip a frame? That would create a very steep spike. Overall this sort of thing is veery hard to debug. Not like other issues where we can reproduce and debug it ourselves

1

Yeah I definitely am close to too much heat and throttling issues (laptop gaming) but thats why I set an fps cap. I guess the experiments continue but I'm really exhausted. Gonna try amdvlk soon, after work i g

Jupstar ✪

so you are sure it is the CPU that causes this?

I'm not sure, but Indefinetly had issues with throttling and performance. On Fedora it seems to work quite well in Desktop tasks but I migbt be hitting some temperature targets in gaming

Gumba

Yeah I definitely am close to too much heat and throttling issues (laptop gaming) but thats why I set an fps cap. I guess the experiments continue but I'm really exhausted. Gonna try amdvlk soon, after work i g

Have you kept an eye on the cpu and gpu usage? Is anything interesting happening when the spike happens?

Gumba

Yeah I definitely am close to too much heat and throttling issues (laptop gaming) but thats why I set an fps cap. I guess the experiments continue but I'm really exhausted. Gonna try amdvlk soon, after work i g

and cl_refresh_rate also doesnt fix it?

Jupstar ✪

and cl_refresh_rate also doesnt fix it?

i didnt touch that, as this modifies the actual game updates, when i had that on 300 by accident once it really felt bad, I'll try limiting it later tho, when im home from work

Ctrl+z breaked my anymation + can't go back version

texnonik at this point you should record everytime you're mapping :D

1

texnonik

Ctrl+z breaked my anymation + can't go back version

https://discord.com/channels/252358080522747904/757720336274948198/1236384953265029120

17:29

i guess they working on it

17:30

(hopefully)

48 gb bruh

murpi

Thanks, fixed

is that normal (look the dates)?

Chairn

is that normal (look the dates)?

I'm not sure what I'm looking at or what problem you're referring to.

bot responding to last year report

19:09

august 2023 then yesterday message

You've created a ticket yesterday which got closed due to inactivity (you couldn't close the ticket yourself due to a bug)

19:12

(the message from 2023 is an entirely different ticket)

yes, but why the bot answered as well on that old 2023 ticket ?

..because thats.. what the bot does whenever a ticket is closed?

19:17

Just to clarify, the timestamps/dates are all client-side. They're based on when you received the message

Chairn

yes, but why the bot answered as well on that old 2023 ticket ?

discord sometimes shows already read messages as unread (edited)

19:17

perhaps that's what happened here?

but then the message would show the date in august 2023, not yesterday

sooo, I see two messages in your screenshot