[32-bit X86] Legacy Renderer "issues"

[Csonicgo]

This is going to be one of those "I can never give specifics" because I'm still actively trying to track this stupid bug down. But it goes like this picture:

http://imgur.com/a/6ySDh

(The bad textures in the status bar are due to COMP_RGBA, I was trying to see if it would change based on texture format, it doesn't)

When this happens, the frame rate tanks, then pops right back up when out of the "offending" area + angle. The automap also likes to screw up sometimes if textured automap is on.

Now I'm well aware I'm running this on a 32-bit netbook with a 915GM intel chipset (OpenGL 2.1!), but I'm running the latest intel drivers as of December 2016.

This really sucks because otherwise, everything is fine. This happens on all maps, all mods, all modes. even weirder is that changing the rendering quality from "Speed" to "Quality" (or the other way around) sometimes causes this tutti-fruitti mess to go away.

[XristoferLee]

Personally I have had to quit using opengl and use direct 3d because the game freezes in certain place like ep1 lv 08 or ep1 secret lv when it never use to before the last updated of gzdoom. My computer is rarely online due to the fact I have to use my phones tethering to do so. Seems similar to this in that if I turn from the angle it goes back to full speed

[Rachael]

@CSonicGo:

Are you using Windows or Linux on this netbook? I have a very old HP Pavillion with the exact same GPU chipset and have not encountered this issue.

[XristoferLee]

I am using windows 10 home 10.0.14393 on a dell inspiron 3521 x64 based. intel core i3-3217u cpu @ 1.80 GHz, 1801 Mhz, 2 cores, 4 logical processors. Intel HD graphics 4000 gpu. I am running the 64 bit version of gzdoom instead of the 32bit but posted here because his issue sounded similar to the one I am having.

[ibm5155]

if you are running the creators update, then you'll have really sad problem with your graphics driver, for some reason in that specific Windows update, almost all doom engines suffers from a huge lag.
-Vavoom runs at 0fps even on menu.
-Zandronum runs at 0fps. (that can be fixed by doing the vid_fps 1 command)
-Gzdoom runs at 0fps on 64bits version (or it was with teh 32 bits one) (cant fix with vid_fps 1 )

And I don't belive this is gonna change since the last driver update for the hd 4000 was released in 2016

[Rachael]

I am running creators update on a same gen Intel and not having this issue. I am using an Intel HD 4600.

Does GZDoom properly report the correct GPU when you start it with your Intel? Does it specifically say Intel HD 4000 for the GL Renderer string?

[ibm5155]

the HD 4600 has newer drivers (last one from 3/30/2017) while the hd 4000 was from (3/13/2016).
I saw people with the HD 4000 or lower (3000 and 2000) with the same problem on creators udate.
Yeah it shows the intel hd 4000, but it get stucked with 0% gpu usage and even 0% of cpu usage.
There's more info about this in this "old" thread viewtopic.php?f=7&t=56774 or here in zandronum

[Csonicgo]

@CSonicGo:

Are you using Windows or Linux on this netbook? I have a very old HP Pavillion with the exact same GPU chipset and have not encountered this issue.

This was Linux, Debian 9 Stretch 32-bit. I use this netbook frequently, so I can do whatever needs to be done testing-wise. It might be a bug in the Xorg Driver, but since those are Intel drivers, I dunno.....

[XristoferLee]

the HD 4600 has newer drivers (last one from 3/30/2017) while the hd 4000 was from (3/13/2016).
I saw people with the HD 4000 or lower (3000 and 2000) with the same problem on creators udate.
Yeah it shows the intel hd 4000, but it get stucked with 0% gpu usage and even 0% of cpu usage.
There's more info about this in this "old" thread viewtopic.php?f=7&t=56774 or here in zandronum

The hd4000 now has new drivers as of April 2017. The information on Intel's website is miss leading. I downloaded and installed it and the date the install had on the driver was 4/21/17 or something like that. Ever since then I have been able to run in opengl.