Thu, Aug 16
actually fixed it. I remembered I had a similar problem with a mesh deformer lately once I exported it to C4D.
Okay I noticed that I can provide the jacket very simple. I can make a substance painter file that only includes the important subject too if so requested.
If we cannot reproduce the problem, we cannot fix it. I suspect you have the texture coordinates set incorrectly in Blender.
This would be fixed by commit 8e8d93eb8610
Tue, Aug 14
@Brecht Van Lommel (brecht) after CUDA issues, OpenCL one…
Mon, Aug 13
Sun, Aug 12
Thanks, closing then (think those double-triangles were causing excessive stress on GPU for some reason…).
Just a notice to anyone interested:
I started working on this and will need a week or 2 to polish it
Sat, Aug 11
Thu, Aug 9
As I went to confirm that this bug got resolved I found that F12 rendering now doesn't work at all, either with release or debug builds, and regardless of whether Freestyle is enabled or not. This only happens when EEVEE is the active Render engine.
Eeeeh ok, then I guess we can close as solved. :)
Sun, Aug 5
UPDATE - problem solved
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Fri, Aug 3
I have 6gb VRAM and 16gb RAM
I think that memory is not the case here - because I was rendering this model in earlier versions of Blender EEVEE without any problem.
Scenes were even more complex - consisted of the engine (attached model) and the whole vehicle & the driver as well.
Please always attach files here, outhers sources are never 100% reliable.
Mon, Jul 30
As of Blender 2.8 f08f6c1adec I'm not able to reproduce the above issue anymore (with a release build). Freestyle still doesn't get rendered correctly with EEVEE (F12 render shows a black screen), but I guess that's to be expected at this stage.
Thu, Jul 26
Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
@Bastien Montagne (mont29)
This time I even used a debug build, quickly obtaining a crash within 1-2 attempts of rendering the image with Freestyle enabled, as of e91bdb10e9c. Note that it says RX580 but it's actually an RX480 (there should be no difference OpenGL-wise; this is due to a GPU modification).
Same problem here as well
Crash confirmed. @Brecht Van Lommel (brecht) think that one’s for you, here is ASAN backtrace:
Could be a lot of things, but would suspect some OpenGL issue… Can you please run it with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment)? Thanks. Also maybe worth trying with -t 1 option (to run in single-thread mode).
I was sad to see this functionality lost as well, I used it to preview scenes with a compositor performing image manipulation. It was (almost?) the only way to buffer the compositor for a play-blast.
Wed, Jul 25
Hi, cant verify crash with your file.
May Windows/Driver problem?
Hi, cant open the file. It is only a file called RAR.
Please provide a .blend with packed textures and enable compress when you save.
Tue, Jul 24
I confirm that it works fine with the latest build so this can be closed.
@Brecht Van Lommel (brecht) assigning to you, no idea who/if OpenCL is a valid topic currently…
We need an example .blend file that crashes, otherwise it's unclear which type of material or other render setting leads to the crash.
Cannot confirm that here on linux (though psys code spits out a huge amount of asserts…), mind re-checking with latest 2.8 build? thanks.
Yes, problem appears in Jul 23 2018 release
Mon, Jul 23
Is it still crashing with latest builds?