Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
40 user(s) are online (19 user(s) are browsing Forums)

Members: 2
Guests: 38

Paul, samo79, more...

Support us!

Recent OS4 Files
OS4Depot.net




« 1 2 3 (4)


Re: Warp3DNova shader bugs thread
Not too shy to talk
Joined:
2015/6/11 9:51
From Cologne
Posts: 357
@kas1e
Quote:
Do you think that one also broken: https://www.shadertoy.com/view/tlXcR4

No, looks okay to me.

@Capehill
Quote:
Maybe we need to create Shadertoy accounts and start reporting these issues :)

Good idea! I just started, come join

   Report Go to top

Re: Warp3DNova shader bugs thread
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 6324
@Daniel
About unitialized vars: On ftp, reports_here/uninit_vars_tests.lha. Just packed 25 random ones (i think only few of them will be falsely positive, while in most it correctly warn).

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: Warp3DNova shader bugs thread
Not too shy to talk
Joined:
2015/6/11 9:51
From Cologne
Posts: 357
@kas1e
Fantastic, thanks This will surely lead to further improvement!

EDIT: improvements added Now all the ones you sent me are detected correctly too.
Had to add support for OpAccessChain and variants to catch component-wise assignments, add support for OpLoopMerge to be able to add some special treatment for stuff like for-loops, and added a hack to detect inout-variables (unfortunately SPIR-V doesn't decorate those).
Code grew from 150 to 180 lines

Quote:
Also another shader to discuss, maybe from visuall look some assumtion can be done so i can made proper BZ about. So, shader: https://www.shadertoy.com/view/tsjBRw

Phew, honestly: as soon as a bug is so severe that the GPUs internal CU workings are visually revealing and as soon as the shader gets more complex, I wouldn't waste my time on it considering the known register handler's state.


Edited by Daytona675x on 2020/6/10 12:52:10
Edited by Daytona675x on 2020/6/12 9:14:55
Edited by Daytona675x on 2020/6/12 9:16:03
   Report Go to top

Re: Warp3DNova shader bugs thread
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 6324
@All
So far all rendering bugs for all shaders I wrote about there were fixed in new betas of Nova, as well as many others. There still some other left, but Hans deals with them step by step.

Currently, I report about 50 rendering bugs, 30 of which were fixed and 20 left. There are also about 10 crashes to deal with, and then that SGPRs/VGPRs limitation. After that, only some missing instructions left, but in general, almost 90% of all shaders from shadertoy will works if there will be no rendering issues and no SGPRs/VGPRs limits.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: Warp3DNova shader bugs thread
Home away from home
Joined:
2006/12/2 3:55
From Italy, Perugia
Posts: 3335
@kas1e

That's a great progressing ... but when i come on that site i read there are more than 40.000 shaders examples! .. even assuming that fixing one in Nova could fix tons of them at the same time, i wonder how we can test all of them or even a part of

   Report Go to top

Re: Warp3DNova shader bugs thread
Just can't stay away
Joined:
2007/7/14 21:30
From Lothric
Posts: 1065
@kas1e

I have seen some of the reports. Great testing and great progress.

I cannot comment closed reports so regarding #526 (Jupiter II), the random placement of stars is also broken on my Win7/Radeon.

   Report Go to top

Re: Warp3DNova shader bugs thread
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 6324
@samo79
Quote:

but when i come on that site i read there are more than 40.000 shaders examples! .. even assuming that fixing one in Nova could fix tons of them at the same time, i wonder how we can test all of them or even a part of


It's enough to test just a few hundreds of random ones, to find out common errors and issues. But currently, I test probably around 2000 and have pretty good understanding of what kind of issues are left in general. After rendering issues the real remain issue is SGPRs/VGPRs limit, it makes too many heavy and very-good-looking shaders to fail. There are also some non-implemented instructions left too (like OpImageSampleExplicitLod and OpFwidth which used from time to time), but for real if all rendering issues I report fixed and SGPRs/VGPRs limitation removed, then we can say "all fine", even if some stuff will still fail.

Also, in ShaderToy base there lots of shaders of the same type just with minimal changes, or very-very simple ones, or just very-very dumb ones, so for real the number of normal shaders, not 40000, but much less.

Quite many shaders with video and added simple effects at the top, not of big interest too. Some just static ones, having no animation.

So for real, I think the amount of really cool and interesting shaders is about 10000, maybe less. Which is quite a lot, still.

But new ones keep coming every day, and in a few days there always a few new shaders of good quality.

@Capehill
Quote:

I cannot comment closed reports so, regarding #526 (Jupiter II), the random placement of stars is also broken on my Win7/Radeon.


Yeah, that one do have:

float rand(vec2 co, float seed){
return fract(sin(dot(co.xy + seed ,vec2(12.9898,78.233))) * 43758.5453);
}

As Hans says about their rand function: "function uses operations in a manner where precision makes a difference. A simple thing such as how precise the sin() approximation is, or whether multiply-and-accumulate instructions are used instead of a * b + c results in different behavior."

I find out a few more shaders with the same error, and just going as Hans suggests by reducing multiplier deal with. For example that one work as expected on a beta of nova when reducing 11000000.0 to 11000.0: https://www.shadertoy.com/view/3s3Xz2

See it had:

float rand(float seed) {
return fract(sin(seed * 11000000.0 + 11223.12332));
}


Or another one in which I had to change "gl_FragCoord.x * 0.482635532" in dither() function on "gl_FragCoord.x * 0.48232" to make it works as expected: https://www.shadertoy.com/view/lslGR8. See:

float dither()
{
return fract(gl_FragCoord.x * 0.482635532 + gl_FragCoord.y * 0.1353412 + iTime * 100.0) * 0.008;
}

So dunno if anything can be done about those on our side to auto-fix them.


Edited by kas1e on 2020/6/28 9:50:02
_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: Warp3DNova shader bugs thread
Home away from home
Joined:
2007/9/11 12:31
From Russia
Posts: 6324
@Capehill,Daniel
If there will be some minutes of free time, maybe you can look briefly at those shaders:

https://www.shadertoy.com/view/4djGzh - just black screen
https://www.shadertoy.com/view/MsSGWz - just black screen
https://www.shadertoy.com/view/3lscDf - almost everything black, just some pieces of effect visibly
https://www.shadertoy.com/view/4djGWV - just black screen
https://www.shadertoy.com/view/Md2GDy - effect didn't renders, instead whole screen filled by some solid color, and we can see how line at bottom and some few dots in some part of screen tried to render something.

First two i report already, but 3 other ones on hold at moment, just want to be sure that all those 5 shaders didn't broken by itself. As with latest beta of Nova it start to be more offten that shaders itself buggy.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites
   Report Go to top

Re: Warp3DNova shader bugs thread
Not too shy to talk
Joined:
2015/6/11 9:51
From Cologne
Posts: 357
My results are the following.

https://www.shadertoy.com/view/4djGzh - black screen
https://www.shadertoy.com/view/MsSGWz - ouch, system freeze, always

For those I took a quick look at the shader code:

https://www.shadertoy.com/view/3lscDf - almost black, only a handful of rotating sphere-like entities visible. didn't spot anything critical, in theory, with certain theoretically possible N / P constant combinations some math could become undefined, but not in this config, so didn't spot bugs in the shader.
https://www.shadertoy.com/view/4djGWV - pixel garbage revealing CUs, pattern depends on mouse input (which is to be expected for all shaders which use mouse-input). Didn't spot bugs in the shader.
https://www.shadertoy.com/view/Md2GDy - solid brown-red with pixel garbage in the center and at the right edge. Didn't spot bugs in the shader.

This was with Nova 1.71. I'd say it's fine to throw'em at Hans.

   Report Go to top


« 1 2 3 (4)



[Advanced Search]



Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project