Announcements

Announcement: We’re aware of an issue affecting starting a new topic from category pages and creating new blog posts. New topics can still be started directly from the relevant board. Learn more here.

MAXtoA 5.6.6 is here!

MAXtoA 5.6.6 is here!

Stephen.Blair
Community Manager Community Manager
3,208 Views
20 Replies
Message 1 of 21

MAXtoA 5.6.6 is here!

Stephen.Blair
Community Manager
Community Manager

MAXtoA 5.6.6 is here!

 

The latest release brings a much-improved GPU renderer, faster volume rendering, improved imager usability, high quality curves, light AOVs in the toon shader, a text overlay imager, USDZ, and many more user experience improvements.

 

Check out the MAXtoA 5.6.6 Release Notes  for more about the latest enhancements and updates...



// Stephen Blair
// Arnold Renderer Support
0 Likes
3,209 Views
20 Replies
Replies (20)
Message 2 of 21

RenderQ
Advocate
Advocate

Is there no need to pre-populate gpu cache since the option is gone now ?

0 Likes
Message 3 of 21

lee_griggs
Autodesk
Autodesk

It is not necessary now.

https://help.autodesk.com/view/ARNOL/ENU/?guid=arnold_user_guide_ac_rendering_ac_arnold_gpu_html

Lee Griggs
Arnold rendering specialist
AUTODESK
Message 4 of 21

rsparwasser
Advocate
Advocate

5.6.6 is brutally slowing down my material editor...!

 

Kindly

0 Likes
Message 5 of 21

rsparwasser
Advocate
Advocate

If you use denoisers the Framebuffer has sometimes black frames, no way to use GPU...! CPU is only possible without denoisers. Is there a way to rollback to the previous version of arnold?

 

Cheers

0 Likes
Message 6 of 21

WojtekOgrodnik
Contributor
Contributor

Multiple problems with the latest arnold, crash after crash in different circumstances.

Easy to roll back - first remove the app with Windows (MaxtoA) and then install the previous one from here:

https://arnoldrenderer.com/download/archive/

0 Likes
Message 7 of 21

rsparwasser
Advocate
Advocate

Thx - after rollback - it´s working again!

0 Likes
Message 8 of 21

Stephen.Blair
Community Manager
Community Manager

@WojtekOgrodnik wrote:

Multiple problems with the latest arnold, crash after crash in different circumstances.

Easy to roll back - first remove the app with Windows (MaxtoA) and then install the previous one from here:

https://arnoldrenderer.com/download/archive/


Were you able to send CER reports for any crashes?



// Stephen Blair
// Arnold Renderer Support
0 Likes
Message 9 of 21

Stephen.Blair
Community Manager
Community Manager

@rsparwasser wrote:

If you use denoisers the Framebuffer has sometimes black frames, no way to use GPU...! CPU is only possible without denoisers. Is there a way to rollback to the previous version of arnold?

 

Cheers


Which denoiser? OIDN can use the GPU for denoising. What GPU and driver version do you ahve?



// Stephen Blair
// Arnold Renderer Support
0 Likes
Message 10 of 21

WojtekOgrodnik
Contributor
Contributor
That was the last thing on my mind - urgent job had to be done...
I should be able to replicate easily at some point.
All the crashes were happening on existing scenes, first one when opening standard material editor - instant crash.
Another when using active render and advancing from one frame to another (everything static, only the camera movement was animated).
Another one when batch rendering...
Tried to use different denoisers and rendering without them.
All on GPU.
Gave up and rolled back to get the job done.
0 Likes
Message 11 of 21

Stephen.Blair
Community Manager
Community Manager

The GPU denoising with GPU rendering is a known issue. For reference, it's logged as ARNOLD-14560
GPU denoising unable to run while GPU rendering. That's the ticket number to look for in future release notes.



// Stephen Blair
// Arnold Renderer Support
0 Likes
Message 12 of 21

rsparwasser
Advocate
Advocate

Hi Stephen,

 

it started when I opened the material editor, 5.6.6.6 unable to use it, roll back to 5.6.5.2 editing was okay, still way slower as scanline,, but okay to work. Rendering in 5.6.6.6 was full of random crashes on gpu and black saved renderframes with both gpu/cpu. In 5.6.5.2 both cpu/gpu FB was fine. This time I saved the files on a local harddrive, so I am not sure if the black frames were saved incorrectly because of the network.

0 Likes
Message 13 of 21

WojtekOgrodnik
Contributor
Contributor
Noted, but I rendered files that rendered fine in a previous version (and still render fine after rollback). Never had any issues with denoising and rendering (both gpu). Also - never had any issues with arnold render view with denoising and running on gpu - with going between animated frames. This version was crashing.
0 Likes
Message 14 of 21

WojtekOgrodnik
Contributor
Contributor
Had the same experience - black frames in an animated sequence - saved to local disk.
0 Likes
Message 15 of 21

rsparwasser
Advocate
Advocate

That is my system:

Prozessor  AMD Ryzen™ 9 7945HX Prozessor (2,50 GHz bis zu 5,40 GHz)
Betriebssystem Windows 11 Home (64 Bit)
Operating System Language Windows 11 Home 64 – Deutsch
Microsoft Productivity Software Microsoft Office Testversion
Selectable Memory 32 GB DDR5-5200MHz (SODIMM) - (2 x 16 GB)
Festplatte 512 GB SSD, M.2 2280, PCIe 4.0, TLC
Zweite Festplatte Ohne
Bildschirm 16" WQXGA (2560 x 1600), IPS, matt, Non-Touch, HDR 400, 100% sRGB, 500 cd/m², 240 Hz, schmale Ränder, „Low Blue Light“
Grafikkarte NVIDIA® GeForce RTX™ 4090 Notebook-GPU 16 GB GDDR6 Ausgewähltes Upgrade
 
I use the latest nvidia driver...
0 Likes
Message 16 of 21

Stephen.Blair
Community Manager
Community Manager

@rsparwasser wrote:

5.6.6 is brutally slowing down my material editor...!

 

Kindly


The Slate Material Editor? I'm not seeing any difference here. What's slowing down? The preview renders?



// Stephen Blair
// Arnold Renderer Support
0 Likes
Message 17 of 21

rsparwasser
Advocate
Advocate

ME is absolute unusable, neither in node or alternative editor. It’s slow when opening, maybe it’s the calculation of the thumbs. Picking from scene is slow. Any change is slow, Laptop fan is getting crazy 🙂 If you use the colorpicker, the mousecurser will freeze for a second or two after releasing the mousebutton. I have the same on a different pc, so I guess it is not based on hardware.

nothing in 5.6.2.6 ! 

 

cheers! Arnold is cool!

0 Likes
Message 18 of 21

Stephen.Blair
Community Manager
Community Manager

@rsparwasser wrote:

ME is absolute unusable, neither in node or alternative editor. It’s slow when opening, maybe it’s the calculation of the thumbs. Picking from scene is slow. Any change is slow, Laptop fan is getting crazy 🙂 If you use the colorpicker, the mousecurser will freeze for a second or two after releasing the mousebutton. I have the same on a different pc, so I guess it is not based on hardware.

nothing in 5.6.2.6 ! 

 

cheers! Arnold is cool!


Ok, I see that 3ds Max QA just logged a bug for this, so they hit the problem too.

Thanks for reporting the issue.



// Stephen Blair
// Arnold Renderer Support
0 Likes
Message 19 of 21

giuseppe.schiralli
Autodesk
Autodesk

We identified the cause of the regression, and working on fixing it.

You also may notice that the rendering session is slower to start. Same problem.

 

There's no workaround for it.

 

Sorry for the issue.


Giuseppe Schiralli
3ds Max - QA Analyst>
0 Likes
Message 20 of 21

ingmar.wittmann
Contributor
Contributor

The latest update is unusable. My latest scene that was working fine with the last version, is now crashing when i open the material editor.  Rendering animations with GPU is not working....
How about testing?

0 Likes