Light shader code not compatiable with old GLSL version

Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.

If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is ON
[img] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Light shader code not compatiable with old GLSL version

Re: Light shader code not compatiable with old GLSL version

by Redneckerz » Sat Jun 12, 2021 12:10 pm

Thanks for making this thread, Emile.

For the record, GPU is a Geforce 6150 SE (GLSL 1.20 format) wih OpenGL 2.1 support.

Ill recap them here (and remove them from the main thread):
Redneckerz wrote: GZdoom launches correctly, but as soon as you start a new game, the following appears.

[imgur]https://i.imgur.com/Vqaqsja[/imgur]

It does not outright crash, just does not start until you disable lights.pk3.
That was with 4.6.0a.

Test with "+set gles_force_glsl_v100 true":
Redneckerz wrote: That bombs out with a slew of errors:

[imgur]https://i.imgur.com/Nga6WG4[/imgur]
Then tested with latest g.4.6.0b:
Redneckerz wrote:Just tested 4.6.0b.
Sprite Shadows work perfectly with no performance impact. Looks nice, too!

However,when lights.pk3 is selected, the issue seen in the first picture reappears. So lights.pk3 does not play nice on the renderer.

Light shader code not compatiable with old GLSL version

by emile_b » Sat Jun 12, 2021 9:45 am

When lights are enabled, even with "+set gles_force_glsl_v100 true" there are shader compilation errors.

Reported by @Redneckerz here:
viewtopic.php?f=1&t=72361&start=30

Need equivalent hardware to debug and fix (Unless someone can work out the issue from errors shown)

Top