Thanks, will install it then.
2 Likes
Hallo everybody,
I am on Blender 2.92 (Windows 10) but I canāt install the last version SSGI Native 1.13. Anyone can help?
1 Like
Iāve been putting the SSGI builds of Bforaritsts to some stress tests merged into 3.0.0 builds. It has been nice in viewport, but on Batch Render script rendering, I have encountered a number of issues with an Nvidia DLL. I have updated the drivers to most recent and still get the issue, checked validated geometry in the scene, dependency cycles on characters, image packing and optimization - etc. Itās a large file Iām working with, with up to 7 gig of ram used on peak - but itās not pushing through a queued batch script (Windows 10, GTX 1060, 16gig of Ram).
The crash is illusive. It renders some frames, then fails on others. Frame crash is agnostic to the particular frame. Usually crashes after 2-5 frames. I am writing to EXR Full Float
Characters Lookdev Turntable_02.crash.txt (21.7 KB)
Only clues that somes lists in the crash is based on the nvoglv64.dll, which can cause the EXCEPTION ACCES VIOLATION. It has shown in the console.
I have tried Blender native 1.13 build, and custom builds with the SSGI diff 1.13, and then Blender native and custom build without SSGI. The custom builds and native work, but the issue is triggered when compiled with SSGI.
Hope this points out to something obvious, I would love to use this in production - but the stress test provedā¦ stressful! haha
Great code though, love how it works and looks.
2 Likes
Download and unzip, run the EXE.
1 Like
@Draise
No obvious easy fix from that, sorry. I know there are potential issues with how the shaders are set up currently, and the 1.13 diff needs cleanup, but I havenāt managed to make it crash so far.
Iād like to set up similar builds to try and replicate the crash so I have something to validate against. Is just building the latest bforartists release source with a patch close enough or what would be the closest source I should use?
Just for extra clarity:
The crash only occurs on batch rendering in bforartists + 1.13 diff and not while batch rendering with standard 1.13 builds?
Iād love to try and clean it up, but I already put more time than I had under this at the beginning of the year, so Iāll have to do catch up with some other things. Wonāt really have any extra time if any till atleast the second half of june. Hopefully I can still find some moments to look into it before that.
@Duca
As Draise said you just need to unzip and run the Blender.exe from there - the Native versions arenāt an addon anymore, but a custom build of blender.
@MI65
Itās using OpenGL only, the Cuda and Optix are only mentioned for with what options Cycles is built. So Eevee still works as it used to on any hardware.
@jovlem
The Unity shader looks like it could work with Eevee. Iām not really familiar with that part of rendering code though at the moment.
I think it should be possible to modify normals in nodes too using same edge detection approach as the Gumroad materials seem to use. Not sure if thereās enough control to pull smoothed edge normals off though?
@bloox64
I havenāt seen any evidence of a deferred gbuffer so far, so it looks foward rendered. Only time some of that is written into buffers/textures seems to be for post processing inputs. But again, not really familiar with that part in Eevee or overall. The render passes seem to be done separately.
@Midphase
I donāt have enough experience for that, I havenāt touched anything in OpenGL before this. Itās a lot easier to modify someone elses implementation to be more in line with how I would like it to work than to do anything like that from scratch. Also Blender developers donāt have the luxury of occasionally breaking things and functionality they donāt care about. At best I hope this can illustrate how some specific implementations of some functionality could work. I do appreciate the support!
4 Likes
Yes. Extra AO node followed by a color ramp node or a map range to avoiding scene AO problem.
1 Like
Blender Builds with SSGI 1.13 and the custom build Bforartists with the SSGI 1.13 both crash on batch script. Without SSGI scene renders fine.
Scene was authored in 3.0, maybe that is whatās up?
I could try send you the project and trouble scene under an NDA (client project) and get it to you for June if youād like. Itās a few gigs though.
1 Like
do you think that you can render the viewport with overscan fo SSR / SSGI?
does anyone ever do 180 sphere render and then only use the center?
1 Like
Ah, okay, thanks both you and Draise!
1 Like
So the crash seems to be only occurring with one file?
Iād try the batch rendering script in isolation before (essentially just command line rendering for one file in this case?), but I gather thereās no reason to?
I sent you a DM about the file.
Hey @0451 the 1.14 prototype denoiser is awesome!! The fact that we can reproject the normals and keep the albedo color clean from the denoiser is amazing. the only issue im seeing at the moment is the random seeding the denoiser has. rendering a still camera over say 20 frames gives u a different denoise pattern everytime while the screenspace noise stays consistent.
1 Like
everything works ā¦ for me for sure
Iām overjoyed
man 0451 āsvaka ti dalaā (each woman gave you) as they say on balkan
I know Iām crazyā¦
but!
is it possible to get that half-res effect anyway
because although it happens in the viewport
there is no way to render it
6 Likes
removed by popular demand
1 Like
@philo_vivero
Should be due to this: https://developer.blender.org/rBa7b7f67fc4ad0a5bf4ffc2a64467b55479f4fd95
Seems like no functional compability issues, just only with applying the patch.
If I find the time I need to check howās the compatibility with latest masters and 2.93. Are you using / interested in the 1.13 diffusion or later?
@Pablo_Houmbre
Great looking scene!
With the half-res effect do you mean having the broken half res trace in renders?`
I currently only have plans to fix it in viewport.
@Naskomusic
I noticed that too. I hope that changing the denoising to run only on input where it has accumulated more samples will mostly make it unnoticable.
@BluePrintRandom
180 sphere render - like I wrote previously it would work in some cases, but I donāt think at least with fullres, that the performance cost justifies it. Iād rather look more into sampling offscreen data with miss rays from world probe and if I can make it work, from irradiance volumes or cubemaps.
Making overscan work for viewport would be nice, but itās not something Iām personally very interested in. Itās potentially a lot of work in areas I havenāt even looked at, and for my own use case camera with a full opacity passepartout already works well enough by hiding the edges.
@Zawardo
I looked at calculating another AO pass previously and it didnāt seem too complex to add (pre AO refactor) in the context where I was looking to use it. I might revisit that at some point, but itās pretty low priority, since Iām using a difference approach with world diffuse lighting for now.
2 Likes
http://fifthsigma.com/CoolStuff/blender-2.93-SSGI-latest-2021-05-08.zip (MacOS)
This build has been really stable for me. Iāve been afraid to re-build for fear of getting a regression.
1 Like
āhaving the broken half res trace in rendersā
thatās exactly what I mean
this has potential i belive
my painting teacher always said āthere are no mistakes hereā¦ā
thank you for your work and for what you do!!!
2 Likes
Just to inform for people who use 1.13 SSGI build from Gumroad with 3.0
Unfortunately there was a bug for new implementation of SSReflections and Ambient Occlusion Refactor. There was issue with specular light pass and over-darkening issues on metallic objects
The last 1.13 build with SSGI complied unfortunately has that bug and it can cause big problems for SSGI and how objects look in eveee
https://developer.blender.org/rBS3735986e875981e5525ec8cec379023abcc692bf
I know because I reported that bugsand they got fixed a little time ago but I downloaded 1.13 (new) and it looks like it still have that bug. So I just wanted to tell about it :))
1 Like
Thank you I was looking for a SSGI build without this bug https://developer.blender.org/rBS3735986e875981e5525ec8cec379023abcc692bf
and thank u
1 Like
I have found out what the crash was, there was non-validated geometry with some bad vertices crashing. It was ultimately crashing without SSGi, so it wasnāt the patch after all. Thanks for the support though!
1 Like