Same here

Thanks.

In T56674#532756, @Bastien Montagne (mont29) wrote:

Please launch Blender from the command line with --debug-cycles option and attach as text file here any error printed out in the console (do not paste it directly in comment).

@Brecht Van Lommel (brecht) might have more to suggest here though?

Please launch Blender from the command line with --debug-cycles option and attach as text file here any error printed out in the console (do not paste it directly in comment).

Thanks guys :)

This is indeed a feature request, that is planned to be solved in the future with overrides in 2.8. The other thing is that we should add support for a world position pass at some point.

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

Well, this is like trying to simulate data pass with a light setup, which is already kind of weird. So probably this is something to look at as well.

@Brecht Van Lommel (brecht) @Sergey Sharybin (sergey) while much more like a feature request than a bug, think that totally make sense… Maybe change the task to TODO type?

Sorry, forgot about this. But it's a quick to fix.
I will update this soon.

Thank you for feedback!

This option properly should rename "Build JPEG quality" to "Bitrate percentage"

Thanks for the test-build. I had to run it in compatibility mode for Windows 7 to get it to run on Windows 8.

If anyone wants to test patch D3597 here is 32bit windows build
https://drive.google.com/open?id=1Gc5lrk08hK2XsCg94JVzJDE9ZJCMseak

Please try to reproduce this problem with Blender 2.79b from blender.org .

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

@Brecht Van Lommel (brecht) after CUDA issues, OpenCL one…

Thanks, closing then (think those double-triangles were causing excessive stress on GPU for some reason…).

In T54259#526451, @Richard Antalik (ISS) wrote:

I can provide windows build

Just a notice to anyone interested:
I started working on this and will need a week or 2 to polish it

@Antonio Vazquez (antoniov) Could you look at T56284 I'm not sure if it's GPencil related or the linking/appending system.

As I went to confirm that this bug got resolved I found that F12 rendering now doesn't work at all (Blender doesn't crash, but it freezes and must be forcibly closed), 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. :)

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.

Thanks!

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.

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.

@Brecht Van Lommel (brecht) @Sybren A. Stüvel (sybren) iirc, this is known limitation due to how our cache works currently?

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).