Shaderjoy 1.25

@IamSONIC
Be it enabled compositing or disabled in prefs:gui, you didn't have that ?

@kas1e

SYS:Prefs/GUI Compositing enabled, vertical Sync enabled and Optimizing for performance.

Did some retesting now...

so on 1920x1080@60 i also experience this kind of stuttering :(
using 1920x1080@76 i get supersmooth animation within workbench window. GUI Settings as above.

@IamSONIC
So its 60HZ cause this ? When you use @76, you also have 76 FPS everywhere with VSYNC ?

EDIT: my monitor seems can't deal with 76, 75 is the last one working, so tried 65, 70 : no changes. But 75 seems better. Workbench window movements are much better too. Through when i move window, i can see some tearing lines.

@Capehill
What your screenmode/refresh rates you use ?

@kas1e

Balls of fire vertical artifact is caused by something in its snoise() function. We might be able to see it also in Shadertoy web app if we could resize it. I found an old (2016) Windows clone and reproduced the same issue using it: https://sourceforge.net/projects/shadertoyforwindows/

Good news is that it's not a Nova bug.

I'm using 60Hz screenmodes.

@Capehill
Quote:

Oh yes, that nice for sure!

Quote:

I think we need just another topic about that general vsync stuff, because generally i can see tearing lines when just move workbench windowses if watch close.

I also found, that i have non-working RMB menu in shadertoy with disabled compositing effects because i use SilverGreen theme, while on default theme, all works. Maybe it related to the stiky-menus options somehow, dunno. But why it made such stange difference on menu..

Can anyone check just by loading silvergreen theme and disabled compositing, if menu in shadertoy works then ?

And bug about 30 fps on RadeonRX is here for sure. For example, i just do that now:

1). disabled compoisting effects fully (and use deafult Theme , so RMB menus works for me then)
2). load "ball_of_fire"
3). Disable VSYNC and swithc to fullscreen : there i have cleary 145 FPS all the time.
4). RMB, enable VSYNC (be it WaitTOF or WaitBOVP) => 30 fps ! While should be 60 surely. On RadeonHD it give 60 when same steps repeated.
5). RMB for disable vsync => 145 fps.


If i load for example another shader, like "Cellurar" , it give me 1700 FPS in window mode, then dbl-click for fullscreen => 340 FPS (because 1920x1080). Then there enable VSYNC give stable 60 fps.

Like, it depends on shaders, the very fast ones didn't have that, but those ones which without VSYNC around 150 fps in fullscreen, give just 30 fps when VSYNC them.

Or for example "kissing donuts". Load it with disabled VSYNC , and can see it just from 61 to 75. Then enable VSYNC (even in window mode), and it give just 20 (!) fps only. While it can be 60, but ok if it were one time 57-58, can be understanded, but 20 ? Not 30 ?

Or foot_torus, it give me 75 FPS in non-vsync mode, then VSYCN it and have 20 fps.

Maybe VSYNC code in shadertoy is more or less simple, like, if all the time we 200 fps, but one time it was 29, then 20 fps will be set as maximum in vsync, or so ?

Because at very begining, every shader can be slow (in first second), so maybe FPS counter borks because of that and we need to wait second or two after start to show fps. Or at least "clear" all values after few secs.

Maybe in end of all it related to powermanagment of RadeonRX ? As if it didn't happens on RAdeonHD ..

@kas1e

Quote:

I may be able to improve VSYNC. At least some tearing effects seem to be cured now. Problem with Shaderjoy 1.5 is that blitting is done by OGLES2 but VSYNC done by application so it looks like

Vsync();
aglSwapBuffers();

But drawing may not be finished by the aglSwapBuffers call. I could have let OGLES2 do the VSYNC but I'm now handling the bitmap myself so it should help, like:

aglSwapBuffers();
Vsync();
BlitToWindow();

Maybe glFinish would help too in the original scenario.

@kas1e

Quote:

On OS4 in Window mode, with our stack of Software/Drivers yes. But currently i have no idea which specific component is resonsible for this. 60 Hz (even 50 Hz) in general is not responsible for any kind of stuttering.

Quote:

Yes! (Except some shaders banging the Hardware that 76 fps is not possible)

@kas1e

Quote:

ok, also to discuss stuff related to screen refresh frequencies higher than 60 Hz.

@all

Version 1.6:

- Improve VSYNC mechanism.
- Remove FPS counter flickering in fullscreen mode.
- Allow toggling of FPS counter.
- Add SHOWFPS tooltype.
- Add SCREENMODE tooltype.
- Disable Iconify menu option in fullscreen mode.
- Drop command-line argument support in favor of icon tooltypes.

@Capehill

Start testing 1.6:

Found one little bug already : run in window mode, load shader, dbl-click to go to fullscreen, dbl-click to go to window mode => black screen. Dbl-click back on fullscreen - works again.

But to see that all still works in window mode, you can resize window to twice bigger as it originally, and you can see that shader output just shifts down a lot.

Now about VSYCN drops to 20/30 while can be more : those issues are gone on RadeonRX. There still those small hickups every frame, but i am sure that related to just moninor/HZ settings of screens/etc.

Options "FPS Counter" hide the whole info-output in title bar : time, fps and size. So probabaly it can be renamed to "title bar info".

Also seems that fullscreen modes (any of them which creates from tooltype) creates with some oldschool way, so usuall RMB menu didn't works as before in 1.5 and previous one, but instead show some oldschool menu at top.

For example if i comment them all out (as initially it done), then it take fullscreen as workbench (which is 1920x1080 for me), and RMB menu shows fine as expected. But if i uncommented 1920x1080 in tooltypes (which by logic the same), but which seems then create fullscreen with different flags , then RMB sticky menu gone.

@Capehill

Just for fun tried to start version 1.6 on my Sam440, and don't start of course
However it give the chance to ask for a better error checking atleast :)

Right now when can't run. it print this on shell:
Quote:

Maybe instead you could add a better requester telling users about the necessary hardware/software required to runs it

Also unrelated, in workbench titlebar along with program's name you may add also the release version, so to have an immediate visual check

@samo79

Do you have ogles2.library installed? I'm asking because if it would have failed to open the error message would have been "Failed to open ogles2.library" rather. Context is created after library is opened.

@kas1e

Quote:

Well that's bloody annoying after all the testing I have done ;) Can you take the verbose log and paste it because I saw that kind of issue happening earlier but it was supposed to be fixed.

Quote:



Probably some magical tag missing above. Need to read some Autodocs.

@Capehill

Yes i have installed latest version (2.11) from the Enancher Package

About the context, when i double click on shadertoy icon i can see the program window opening, just for a fraction of second, then it print that message in shell ..

@Capehill
Quote:

Sure, there is:

@Capehill

Version 1.6 shows now:

58.8 FPS for 1920x1080@60 and
75.8 FPS for 1920x1080@76

can this xy.8 FPS be the reason for the stuttering every second? Especially @60 Hz?

@kas1e

Quote:

Switching Window -> Fullscreen -> Window ... works here with Version 1.6 as expected. Double clicking and Menu.

@IamSONIC

Quote:

I don't seem to have any stuttering. If you disable FPS counter, is there any impact? Window or fullscreen? Which shader?


Quote:

Same here, seems to work.

But to be on the safe side, I could remove "bitmap creation optimization" and just create bitmap again on every re-size, even when making the window smaller.


@kas1e

Do you have more detailed issue reproduction steps?

Hi,

Here switch to fullscreen by double click works too, but sometimes one click is sufiscient to switch fullscreen<>window mode.

If I switch off fps counter, render is smoother (like with 3Dcow program).

Regards,

@Capehill
Quote:

No, just run it, load shader, switch to fullscreen and switch back to window make whole shader like shift down. So only way to see it resize window. And even then, it didn't shown correctly, but resized. Sometime window after switch to fullscreen and back overlap borders of window by content. Will do more tests.

@Petrol
Quote:

Issue on my side when swith from window to fullscreen, and then back to the window.