01:10 <+bridge> [ddnet] <Jupstar ✪> update drivers
01:10 <+bridge> [ddnet] <Jupstar ✪> tell him
12:12 <+bridge> [ddnet] <n000b> @Jupstar ✪ so you are telling me it is my fault I can't use the new client?
12:18 <+bridge> [ddnet] <Jupstar ✪> what hardware i told you
12:19 <+bridge> [ddnet] <Jupstar ✪> you are paying few hundered bucks for your pc, and they can't make working drivers.. i would blame your manifactures
12:25 <+bridge> [ddnet] <n000b> Lol I can hardware really be the problem with this game. Almost every pc runs teeworlds
12:25 <+bridge> [ddnet] <Jupstar ✪> yes it can, because almost every pc runs 😉
12:26 <+bridge> [ddnet] <Jupstar ✪> so what GPU do you use?
12:30 <+bridge> [ddnet] <n000b> Hmm, i guess that is the problem then. But I can play games with way more graphics.
12:30 <+bridge> [ddnet] <n000b> processing unit: AMD A4 4000 Apu with Radeon HD graphics 3.0 ghz
12:33 <+bridge> [ddnet] <Jupstar ✪> yeah most game u play probably have a directX backend, opengl didnt got huge acknowledge under windows always.
12:33 <+bridge> [ddnet] <Jupstar ✪> 
12:33 <+bridge> [ddnet] <Jupstar ✪> and sadly older AMD hardware has alot of trouble under windows with opengl, it's not the first AMD only bug i see.
12:36 <+bridge> [ddnet] <Jupstar ✪> You can ofc try updating your GPU driver:
12:36 <+bridge> [ddnet] <Jupstar ✪> https://support.amd.com/en-us/kb-articles/Pages/desktop-apu-drivers.aspx
12:38 <+bridge> [ddnet] <Jupstar ✪> but the drivers are from 2016.. so 2 years without any support from AMD
12:58 <+bridge> [ddnet] <n000b> Hmm
14:08 <+bridge> [ddnet] <n000b> Shouldn't there be a warning sign for people with bad gpu's at the download page and when you automatically update?
14:10 <+bridge> [ddnet] <Jupstar ✪> can we know every single GPU, that isn't working ? :/
14:10 <+bridge> [ddnet] <Jupstar ✪> under linux it very probably works
15:11 <+bridge> [ddnet] <Learath2> as long as the software renderer keeps working for everyone, we should be fine
19:46 <+bridge> [ddnet] <deen> @Jupstar ✪ why do we have the Win10/8.1 stuff in manifest?
19:46 <+bridge> [ddnet] <deen> Shouldn't vista/7 be enough?
19:48 < ddnet-commits> [ddnet] def- pushed 1 new commit to master: https://git.io/vp981
19:48 < ddnet-commits> ddnet/master 36e1ace def: Windows manifest: try Vista/7 instead of 10/8.1
19:55 <+bridge> [ddnet] <Jupstar ✪> no more the opposite
19:56 <+bridge> [ddnet] <heinrich5991> @Jupstar ✪ the problem is that one can't fix hardware
19:56 <+bridge> [ddnet] <heinrich5991> one can only fix software
19:56 <+bridge> [ddnet] <heinrich5991> the linux kernel also has lots of workarounds for hardware bugs
19:57 <+bridge> [ddnet] <deen> https://community.roonlabs.com/t/opengl-error-after-upgrade-to-1-1/3266/4
19:57 <+bridge> [ddnet] <deen> But they said they turned off Win10 in manifest and the problem disappeared
19:57 <+bridge> [ddnet] <Jupstar ✪> but that doesnt fix the dpi awereness in win10 then
19:58 <+bridge> [ddnet] <deen> So if you run an executable that was written before win10 existed, you have to recompile with correct manifest?
19:58 <+bridge> [ddnet] <deen> sounds a bit weird, i thought win 10 would fallback to the older ones then
19:58 <+bridge> [ddnet] <deen> since the old versions also supported dpi awareness
19:58 <+bridge> [ddnet] <Jupstar ✪> well the wiki said, you have to declare all version you support
19:59 <+bridge> [ddnet] <Jupstar ✪> but just try and see
19:59 <+bridge> [ddnet] <heinrich5991> anyone got a win10 to confirm?
19:59 <+bridge> [ddnet] <Jupstar ✪> i do
20:01 <+bridge> [ddnet] <deen> nightly now available, please try: https://ddnet.tw/news/nightly-builds/
20:03 <+bridge> [ddnet] <Jupstar ✪> was 10.8.6 with manifest?
20:04 <+bridge> [ddnet] <Jupstar ✪> i dont think i worked back then on the client
20:05 <@deen> yes, with
20:05 <+bridge> [ddnet] <Jupstar ✪> because for some reason, that version already works without scaling dpi, does SDL2 has this DPI awereness already?
20:05 <@deen> dunno
20:06 <+bridge> [ddnet] <Jupstar ✪> mhh what was the first verison without manifest?
20:06 <+bridge> [ddnet] <Jupstar ✪> old version
20:06 <@deen> 10.6 or something before
20:07 <+bridge> [ddnet] <Jupstar ✪> ok then it seems to work
20:07 <+bridge> [ddnet] <Jupstar ✪> does that fix the intel bug or what?
20:07 <+bridge> [ddnet] <Jupstar ✪> im too lazy to read your forum
20:08 <+bridge> [ddnet] <Jupstar ✪> the thread i posted in forum just says manifest
20:08 <@deen> thanks for checking.
20:08 <+bridge> [ddnet] <Jupstar ✪> not specific to any DPI awareness
20:08 <@deen> I'm too lazy to answer you
20:08 <+bridge> [ddnet] <Jupstar ✪> np xd
20:08 <+bridge> [ddnet] <Ryozuki> lol
20:21 <+bridge> [ddnet] <Jupstar ✪> deen you ahve to ask ravie, if his client breaks
20:22 <+bridge> [ddnet] <Jupstar ✪> bcs thats the problem now
20:22 <+bridge> [ddnet] <Jupstar ✪> and as far as i understand the problem is a manifest itself
20:22 <@deen> Well, I'd link you to the forum, but you're to lazy to read
20:22 <@deen> too*
20:23 <@deen> but that's exactly what I did
20:26 <+bridge> [ddnet] <Jupstar ✪> I read the forum thing
20:27 <+bridge> [ddnet] <Jupstar ✪> he said "ok then we cant use win10 specific features"
20:27 <+bridge> [ddnet] <Jupstar ✪> but not "ok then we dont use manifest anymore"
20:27 <@deen> exactly, which is why I asked if we're using any win 10 specific features
20:27 <+bridge> [ddnet] <Jupstar ✪> or better, it implied, that he does
20:27 <+bridge> [ddnet] <Jupstar ✪> doesnt use it anymore
20:27 <@deen> i guess we shouldn't since we want to keep supporting win vista and higher
20:27 <+bridge> [ddnet] <Jupstar ✪> no he doesnt use manifest anymore
20:27 <+bridge> [ddnet] <Jupstar ✪> since they just drop any new features
20:27 <@deen> oh...
20:28 <+bridge> [ddnet] <Jupstar ✪> the problem is the manifest
20:28 <@deen> i thought it was the win10 version in manifest
20:28 <@deen> too bad
21:18 <+bridge> [ddnet] <n000b> @Jupstar ✪  "can we know every single GPU, that isn't working ? :/
21:18 <+bridge> [ddnet] <n000b> under linux it very probably works".
21:18 <+bridge> [ddnet] <n000b> 
21:18 <+bridge> [ddnet] <n000b>  No I meant more like, a warning sign like. If version 11.7 didn't work well try the solid 10.8.6 with less problems on weaker pc's
21:19 <+bridge> [ddnet] <Jupstar ✪> ah ok
21:20 <+bridge> [ddnet] <Jupstar ✪> just spam AMD support to fix it xd
21:24 <+bridge> [ddnet] <n000b> Haha
21:24 <+bridge> [ddnet] <n000b> They won't
22:23 < ddnet-commits> [ddnet] def- pushed 1 new commit to master: https://git.io/vp9gE
22:23 < ddnet-commits> ddnet/master 5726d56 def: Version 11.1.8
22:40 <@deen> @Jupstar worked for Ravie :)
22:57 <+bridge> [ddnet] <ezy> ddnet 11.1.8 lags really hard for me
22:57 <+bridge> [ddnet] <heinrich5991> what was your previous version?
22:58 <+bridge> [ddnet] <ezy> 10086
22:58 <+bridge> [ddnet] <ezy> i reinstalled now xD
22:58 <@deen> oh no
22:59 <@deen> another one
22:59 <+bridge> [ddnet] <ezy> on block servers
22:59 <+bridge> [ddnet] <ezy> its like
22:59 <+bridge> [ddnet] <ezy> everyone
22:59 <+bridge> [ddnet] <ezy> that has lags like this
22:59 <+bridge> [ddnet] <ezy> xD
22:59 <@deen> with ddnet 11.1.8?
22:59 <+bridge> [ddnet] <ezy> yes
23:00 <+bridge> [ddnet] <ezy> some people even had with
23:00 <+bridge> [ddnet] <ezy> 11.1.7
23:00 <+bridge> [ddnet] <ezy> and maybe .6
23:00 <+bridge> [ddnet] <ezy> but im not sure bout .6
23:03 <+bridge> [ddnet] <ezy> gfx_asyncrender_old 0 helps a little
23:09 <+bridge> [ddnet] <deen> cl_refresh_rate 0?
23:10 <+bridge> [ddnet] <deen> opengl3 on/off?