DDraceNetwork - developer

ddnet-maps

[ddnet-maps:master] 1 new commit

a458b76 A Timebreaker - def-

@Deleted User so you are telling me it is my fault I can't use the new client?

what hardware i told you

10:19

you are paying few hundered bucks for your pc, and they can't make working drivers.. i would blame your manifactures

Lol I can hardware really be the problem with this game. Almost every pc runs teeworlds

yes it can, because almost every pc runs

10:26

so what GPU do you use?

Hmm, i guess that is the problem then. But I can play games with way more graphics. processing unit: AMD A4 4000 Apu with Radeon HD graphics 3.0 ghz

yeah most game u play probably have a directX backend, opengl didnt got huge acknowledge under windows always. and sadly older AMD hardware has alot of trouble under windows with opengl, it's not the first AMD only bug i see.

10:36

You can ofc try updating your GPU driver: https://support.amd.com/en-us/kb-articles/Pages/desktop-apu-drivers.aspx

10:38

but the drivers are from 2016.. so 2 years without any support from AMD

Hmm

Shouldn't there be a warning sign for people with bad gpu's at the download page and when you automatically update?

can we know every single GPU, that isn't working ? :/ under linux it very probably works

as long as the software renderer keeps working for everyone, we should be fine

@Deleted User why do we have the Win10/8.1 stuff in manifest?

17:46

Shouldn't vista/7 be enough?

def-

[ddnet:master] 1 new commit

36e1ace Windows manifest: try Vista/7 instead of 10/8.1 - def-

no more the opposite

@Deleted User the problem is that one can't fix hardware

17:56

one can only fix software

17:56

the linux kernel also has lots of workarounds for hardware bugs

https://community.roonlabs.com/t/opengl-error-after-upgrade-to-1-1/3266/4

OpenGL error after upgrade to 1.1

that’s insane… I dont understabd why opengl viewer is able to see the intel gpu and Roon isnt. The white screen minimize issue is known as an Intel driver bug with the 3000 and 4000 that even affects Microsoft Office

17:57

But they said they turned off Win10 in manifest and the problem disappeared

but that doesnt fix the dpi awereness in win10 then

So if you run an executable that was written before win10 existed, you have to recompile with correct manifest?

17:58

sounds a bit weird, i thought win 10 would fallback to the older ones then

17:58

since the old versions also supported dpi awareness

well the wiki said, you have to declare all version you support

17:59

but just try and see

anyone got a win10 to confirm?

i do

nightly now available, please try: https://ddnet.tw/news/nightly-builds/

was 10.8.6 with manifest?

18:04

i dont think i worked back then on the client

18:05

because for some reason, that version already works without scaling dpi, does SDL2 has this DPI awereness already?

[quakenet] <deen> yes, with

18:05

[quakenet] <deen> dunno

mhh what was the first verison without manifest?

18:06

old version

[quakenet] <deen> 10.6 or something before

ok then it seems to work

18:07

does that fix the intel bug or what?

18:07

im too lazy to read your forum

18:08

the thread i posted in forum just says manifest

[quakenet] <deen> thanks for checking.

not specific to any DPI awareness

[quakenet] <deen> I'm too lazy to answer you

np xd

lol

deen you ahve to ask ravie, if his client breaks