@phoe-nix-art@BloQi@mag.py thanks for the reports, but it’s actually better for me if you do those per mail with:
your CPU and GPU model,
OS and driver version
the exact E-Cycles version you used.
The Blender Foundation with a lot more developers only accept bugs reported on it’s official report channel too. I already have 2 platforms with different system and in the current situation, I prefer to invest time to make E-Cycles better. It’s easier for me to follow mail threads and you also get faster reply and fixes
which build should be used atm for production?
Which one is the most fast/stable?
I am on win10 with 2x1080ti, I9-7940x CPU/ Nvidia DRV 436.15
edit: And how does the experimental ai-viewport denoiser work?
I got the standard cuda e-cycles version.
Using: E_cycles_2.90_v20200421_win Build
When i enable it, it tooks about a minute to start rendering in the viewport and then when start rendering, the whole viewport gots white after 2 seconds of rendering…?
(I enabled both 1080ti and cpu under pref.)
cheers dave
For me it works with any of the latest release from E_cycles_2.83_v20200408_win to E_cycles_2.90_v20200421 though it didn’t work with the first release (can’t remember which version was that).
For me it works too. Maybe it’s specific to a scene. You can provide a link to a .blend per mail (Gumroad answer) or Blender Market messages. Please specify your OS, GPU, driver and E-Cycle version there too so that I can make the link.
IES lights seems not working in latest E_cycles_2.83_v20200408_win and E_cycles_2.83_v20200331_win builds. When switching to CPU and enabling OSL seems OK. Official 2.82a build doesn’t have this problem.
Thanks for testing more. Again, it’s working for me and you are the only one reporting this behaviour. Can you try with today’s builds and factory settings reseted to defaults? Does it work in stable 2.82a for you?
AO: as the name says, renders with AO. It’s the fastest one and actually real time in the viewport, vidéos coming soon.
Clay: renders like if your scene was made of clay, with lights and HDR to render with shadows. Still extremly fast, perfect for setting up the lightning and inspect modeling details.
A lot of polishing work was done:
SSS is working again properly with CUDA
adaptive sampling is now much faster with OptiX
normal nodes and IES lights are also working again in 2.90.
Known bugs in current builds: Debian 9 is not working currently. Debian 10 and all other tested distros work.
E-Cycles 2.82a is very stable and still has no known bugs since over a month!
I’m working on new experiments too like fast caustics:
An impressive viewport rendering session by @johannes.wilde with very complexe lightning (very small opening, lots of reflections, etc.) using the latest E-Cycles 2.90 optimizations
Because you are the first one to report it. I think 2 weeks to fix a bug is still ok in covid time, even more when it requires to make a complete new build system for a single user, which I’m doing, but as I said, I’m also ok to refund you if you want.
Edit: actually, I double checked, I know about this bug with a proper bug report since not even a week.
I understand about COVID-19 situation. And I assume it. Perhaps 15 days is a normal period of days to solve a bug. I dont know.
If you have to develop an environment just for fix the Debian 9 error and just for me, please stop. I understand its time and resources consumming for just one user.
I will try to use other versions (hope some one work in Debian 9). If not, I will have to migrate to Windows.
Issue end. No more bad feedback abot E-Cycles. I will try to find a solution with other versions or Os´s.
