Welcome to ZDF!

I guess I'll probably just have to stick to older versions for a lot of my projects then.

Older versions won't get you any better experience on old systems.

I meant that I'll stick to older versions so I can still use the PBR and such.

Nothing has changed there. You can still use the full GL renderer on old hardware, but performance will be lower, just like it is with older versions.

Night Falls wrote:I meant that I'll stick to older versions so I can still use the PBR and such.

Was there a version that supported pbr / postprocessing with on gles renderer ?

No. GLES never implemented these effects. They simply require more powerful shader hardware. Also, the baseline spec fir GLES was mobile phones, not desktops - we only ported it to boost performance on old hardware.

Graf Zahl wrote:No. GLES never implemented these effects. They simply require more powerful shader hardware. Also, the baseline spec fir GLES was mobile phones, not desktops - we only ported it to boost performance on old hardware.

Thanks for clearing it up

Best regards ,

Graf Zahl wrote:Nothing has changed there. You can still use the full GL renderer on old hardware, but performance will be lower, just like it is with older versions.

Ah okay. Sorry I just thought that PBR and stuff was removed from the engine entirely, but I messed around with it a bit more and the PBR is still there.
It's just because none of the objects which were supposed to emit dynamic lights were emitting dynamic lights for some reason, but if I create a plain old dynamic light thing it works just fine. (I'll probably have to run a few tests and see if it's a bug in the update or a problem with my project)

Update: Figured it out, any actor which does not spawn with the level and does not have a dynamic light in it's first frame seemingly won't emit dynamic lights at all.

Night Falls wrote: Update: Figured it out, any actor which does not spawn with the level and does not have a dynamic light in it's first frame seemingly won't emit dynamic lights at all.

There have been a string of dynamic light-related bugs reported very few days shortly before - and after - 4.7 was released. They are currently being fixed as soon as they are reported, our hope for the next point release (shouldn't be too long from now), all of these problems will be gone.

These issues plague all renderers BTW.

I just installed v4.7.0 and submitted the survey. A couple of points to add:

1. I am still unable to run GZDooM, getting the "OpenGL driver not accelerated" error message. [I am not treating this as a bug, so I won't be reporting it on the other thread. I'm just mentioning it here as an additional reference point.] This is despite rolling the intel graphics driver back to the version that was supported in MS Win 8.1.
2. My BIOS version is dated 4/27/2011. This is the equivalent of having a dinosaur among mammals. Therefore, I suspect that even with GLES support (and because of the lack of intel graphics driver support), newer GZDooM will never run on this particular computer.

Regardless, I thank the GZDooM development for doing everything it can to accommodate users of older systems.

It doesn't automatically fall back to the GLES back-end if your system is too old to run the standard renderer. Edit your INI vid_preferbackend=3 or add +set vid_preferbackend=3 as a start-up option.

fakemai wrote:It doesn't automatically fall back to the GLES back-end if your system is too old to run the standard renderer. Edit your INI vid_preferbackend=3 or add +set vid_preferbackend=3 as a start-up option.

I checked the ini file and it already has vid_preferbackend=3

I also tried running GZDooM with batch files that respectively have the following parameters:

gzdoom -IWAD DooM2 -gles2_renderer
gzdoom -IWAD DooM2 -set vid_preferbackend=3
gzdoom -IWAD DooM2 +set vid_preferbackend=3

None of these work.

You need to run it on Windows 8 compatibility mode due to the driver bug else it will never run (that after installing the working Intel driver of course).

drfrag wrote:You need to run it on Windows 8 compatibility mode due to the driver bug else it will never run (that after installing the working Intel driver of course).

I switched to Win 8 compatibility mode but it still doesn't run. Should I be running a batch file with different parameters than the ones I listed above?

All those are wrong. It's '+vid_preferbackend 3' without the quotes. But why don't you just select the backend in the iwad selection window?