invictius Posted April 25, 2015 E.g 1280 and 1920 are each listed three times - are they actually 8, 16 and 32 bit colour modes or something? 0 Share this post Link to post
Graf Zahl Posted April 25, 2015 To be honest, I never checked what is happening here. That code was inherited as-is from ZDoomGL, it's probably some bug in there. 0 Share this post Link to post
axdoomer Posted April 25, 2015 I saw that bug in Chocolate-Setup. It uses SDL to detect the screen resolution. It may have something to do with the graphics driver not being installed. 0 Share this post Link to post
invictius Posted April 26, 2015 axdoom1 said:I saw that bug in Chocolate-Setup. It uses SDL to detect the screen resolution. It may have something to do with the graphics driver not being installed. I don't think that's the case, it's happened on every video card I've owned since 2009. 0 Share this post Link to post
axdoomer Posted April 26, 2015 invictius said:I don't think that's the case, it's happened on every video card I've owned since 2009. Have you installed your manufacturer's driver for each cards? 0 Share this post Link to post
Graf Zahl Posted April 26, 2015 axdoom1 said:Have you installed your manufacturer's driver for each cards? It has nothing to do with the drivers, you can stop that. 0 Share this post Link to post
axdoomer Posted April 26, 2015 ^ If you're sure it's a bug in the code, then that's fine. Every time a saw a bug like this was because of the drivers. 0 Share this post Link to post
DuCT Posted April 26, 2015 axdoom1 said:^ If you're sure it's a bug in the code, then that's fine. Every time a saw a bug like this was because of the drivers. It's not because of drivers. I get the same thing, and I know for sure that I have my drivers installed. It's been happening for a while now too. 0 Share this post Link to post
Graf Zahl Posted April 27, 2015 I had a look today, it was just a stupid bug in the function that collected the resolutions. As I said, I didn't write it myself, so I have no idea where the idea came from, but it just assumed that identical resolutions are sorted by display frequency in ascending order. But that's not the case - on my system it often had 60 Hz first and 59 Hz second, no idea what the point is - and these duplicates were not filtered out. Will be fixed in the next dev build. 0 Share this post Link to post