updating of DE-Raytracer

[Crist-JRoger]

Okay, okay... just Ctrl+C and Ctrl+V. That's all i can 

[knighty]

That was about making MORE complicated code! 
using Ctrl+c and Ctrl+v is the way to go... If it works it means you understand what's going on. For one, that's how I "learned" to program.

[Crist-JRoger]

Help me to fix AO shading 
I tried delete AO when use spotlight. Yes i know whats going on, but that's not enough for write workable code

[knighty]

 

[knighty]

A little update:
1- Multisample AO. A little bit noisy.
2- Now lights are affected independently by the AO.
3- Refine iterations to reduce banding artifact.

[Crist-JRoger]

Wow! Looks great 
Need to test it Thank you so much!!! Very glad that this renderer is getting better 
And happy Holidays! 

[Crist-JRoger]

tested DE with new AO 

[Crist-JRoger]

Some last renders with Knighty's AO fix

Treebroccoli.frag


Treebroccoli.frag


PseudoKleinianMenger_03.frag


PseudoKleinianMenger_03.frag

[lycium]

These are crazy good, great work

[Crist-JRoger]

I have a little question about final render: I use hard settings with a lot of raysteps, max detail, volumetric light, etc... So i use tile render and choose low tile resolution (400x200 for example) and offset 25%. I need a lot of small tiles for big resolution render otherwise GPU driver is crashed. Registry edit of TDR Registry Keys don't helps.
BUT when i set fullscreen in program preview window (1920x1200) with the same settings - they works! Slowly, very very slowly but GPU don't crash. I get over 2000 HD subframes!  Last renders i did in preview fullscreen window, because it's faster and stable than tile rendering.
Sorry for the long story, my question - why such a situation? Why tile render with small tile resolution crashed and fullscreen mode works well?

[3dickulus]

@CJR Awesome renders!

I have recently upgraded to win10 and haven't had time to test much on that machine.
On linux, for hard renders,  I use a preview size of 400x256 and render tiles @ 64x36 or 128x72 , this size keeps the rest of the desktop responsive and doesn't overwork the GPU, my latest image posts are done this way.

will try to examine this over the weekend, sounds like GUI event update timing for the progress output...

[Crist-JRoger]

I use a preview size of 400x256 and render tiles @ 64x36 or 128x72

Thank you!
I try to set tile bigger as much as possible, because bloom effect depends from prewiew resolution and needs offset-area for to "sew" image. Unfortunately, with such aggressive settings, render may hang in the middle or at the end.
I did not expect that the full-screen mode will work so stably. In the end I just pressed PrintScreen  

p.s. Maybe Syntopia will tell about fullscreen mode )

[3dickulus]

@CJR
The images I have recently posted use up to 10,000 raysteps and 512 subframes
yes, 20% to 25% padding, when using bloom, is required.
you can make tile size as small as 16x9 and your desktop should respond like there is nothing else running

you are using Win10? and what version of Fragmentarium ?

v1.0.23 has a new feature you might like, CTRL+MidButton Click will place the light source, this is still experimental, needs a little refinement but works reasonably well, I'm looking at using this to modify spline path control points (keyframe eye+target locations)

 there are a couple of things that affect the Z placement though...
1. DepthToAlpha should be on
2. NormalBackstep should be 0
3. FOV should be 1

without these set this way the XYZ calculation is not accurate but it should still help a lot with light placement

suggestions when placing light...

before making changes select the PosLight tab and click on the Copy Group button
make some changes adjusting the light pos with CTRL+MidButton Click
if you don't like the new pos selecting Paste Settings will put it back to where you started

 

[Crist-JRoger]

I use Win7 and Frag 1.0. Earlier, I wrote to you why this version ) Small tiles - small bloom area, I don't like that  That's why i was started talking about fullscreen mode (Ctrl+F)

[3dickulus]

I use Win7 and Frag 1.0. Earlier, I wrote to you why this version ) Small tiles - small bloom area, I don't like that  That's why i was started talking about fullscreen mode (Ctrl+F)

I would like to know if the latest exe, v1.0.23 , runs on Win7/8 , it was compiled on Win10 but only uses Qt and MinGW DLLs

are the bloom areas wrong in the water test, http://www.fractalforums.com/animations-showcase-%28rate-my-short-animation%29/testing-the-water/ 
the tile size should not affect bloom size , worst case might need 100% padding but should capture the bloom properly at the right size