ObjReader FBO & PP

[Michael Lobko-Lobanovsky]

Morning Patrice,

I haven't yet fully fixed FPS display in Canyon when it runs w/o a model, and there is still conflict of this shader with models rendered in FFP. But I'm halfway there and I made a few fixes for:

-- safer model reload
-- safer clear scene
-- cleaner error handling in case of missing shader file.

The patch is attached below (mods marked MLL 06-10-2019). The binary in my Reply #118 above already has these mods implemented.

[Patrice Terrier]

I don't know how to make OR recognize automatically from the shader code an arbitrary sampler2D's texture needs to be loaded linear rather than mipmapped...

What about something like:
lin_texture.png
mip_texture.png (that would be the default in case of "mip_/lin_" omission)

[Michael Lobko-Lobanovsky]

 

Good idea! Actually, m_/l_ would be sufficient and not so heavy for the eyes of the reader...

So, do we agree on that?

Yours truly,
M_L_L_

 

[Patrice Terrier]

Good idea! Actually, m_/l_ would be sufficient and not so heavy for the eyes of the reader...

OK, i agree on that

Thanks for the OR exe, fortunatly it looks the same than mine when using 2dclouds.fs (there is no merge error)...

[Michael Lobko-Lobanovsky]

Thanks for the OR exe, fortunatly it looks the same than mine when using 2dclouds.fs (there is no merge error)...

What can you say about my video?

[Patrice Terrier]

What can you say about my video?

Yours is smoother than mine 

I shall check the shaders on my Intel 4000, and let you know how it goes...

[Michael Lobko-Lobanovsky]

Well, I don't think that would be necessary, my friend.

You will probably be able to take a short nap between two successive animation frames.

You should understand we're at the very edge of technology with those raytraced shaders, in the land of no compromises.

[Patrice Terrier]

Report on Intel 4000

2dclouds.fs, jerky
allseeingeye.fs, perfect
anilight.fs, perfect
auroras.fs, jerky
blueplasma.fs, perfect
bluespace.fs, perfect
canyon.fs, jerky
carribean.fs, perfect
clock.fs, perfect
fire.fs, perfect
heartfelt.fs, perfect
mars.fs, see the attached screen shot
matrixradial.fs, perfect
moabius.fs, perfect
oblivionhud.fs, perfect
oblivionradar, perfect
pegasus.fs, jerky
protean.fs, very jerky
purplespace.fs, perfect
redhot.fs, jerky
seascape.fs, jerky
star.fs, black screen with small moving dots at the bottom
tori.fs, blow up
tunnel.fs, jerky
uroboros.fs, perfect
voronoi.fs, perfect

NeonHex, jerky
Luminescence, jerky
MoebiusObject, jerky
TinyClouds, jerky

end of report...

[Michael Lobko-Lobanovsky]

!!! THANKS !!!

The info is very valuable; it helps me spot latent errors in the shaders where nVidia deviates from the stricter GLSL implementation standards of the other brands!

Jerkiness is pardonable on an Intel integreted video chip and the results are quite expectable. But to see jerky 2D Clouds on a modern nVidia?...

I've just checked the shaders on my ATi Radeon box. Everything is very smooth (2D clouds and Canyon and other stuff). Of course the GPU usage is considerably higher. The box uses a 2GHz dual core Athlon-II, and Radeon has 2GB of on-board VRAM -- nothing much or special at all. You can see the GPU meter to the right of OR window.

And you know what? On an AMD/ATi PC, your skinned menu panes pop up on the wrong side of their main menu parents (to the left of them...) 

[Patrice Terrier]

And you know what? On an AMD/ATi PC, your skinned menu panes pop up on the wrong side of their main menu parents (to the left of them...)

This is a Windows setting. (see menu drop alignment)

https://www.sevenforums.com/tutorials/786-menus-open-left-right-side.html

[Patrice Terrier]

Report on Intel Atom x7-z8700 CPU
1.60 GHz
RAM 2Gb
64-bit
(Windows Surface)

2dclouds.fs, perfect
allseeingeye.fs, perfect
anilights.fs, perfect
auroras.fs, jerky
blueplasma.fs, perfect
bluespace.fs, perfect
canyon.fs, jerky
caribbeans.fs, perfect
clock.fs, perfect
fire.fs, perfect
heartfelt.fs, perfect
mars.fs, jerky
matrixradial.fs, perfect
moabius.fs, perfect
oblivionhud.fs, perfect
oblivionradar, perfect
pegasus.fs, jerky
protean.fs, very jerky
purplespace.fs, perfect
redhot.fs, jerky
seascape.fs, slighty jerky
star.fs, misalignments (horizontal bands)
tori.fs, blow up
tunnel.fs, perfect
uroboros.fs, perfect
voronoi.fs, perfect

NeonHex, slighty jerky
Luminescence, slighty jerky
MoebiusObject, slighty jerky
TinyClouds, slighty jerky

[Michael Lobko-Lobanovsky]

Hey Patrice,

Please overwrite your shaders everywhere with those 5 ones from the zip below and see if it cures your renders for them on both of your Intels. (they run fine for me on nVidia and ATi)

If it does, then please correct both your error report tables for me to clearly see what other shaders are still failing. (mark them in red or bold)

TIA

[Michael Lobko-Lobanovsky]

Haha, 2dclouds runs for you perfect on your Intel Atom!!!

Do you believe now you nVidia may be failing?

[Patrice Terrier]

post #127 updated with new color set to show the status.

[Michael Lobko-Lobanovsky]

Thanks a bunch! What about Intel Atom?