CGRU Forum

Awesome! Upgraded without a problem.

Hi there,

I finally got CGRU to wake up all the clients (with a little help from ChatGPT that fixed a problem in the "wolwake.py").
Now I found this entry in the CGRU Changelog:
But how to I use or enable this feature?

Yes, there is also a "hython.exe", that's basically a renamed version of "hython3.9.exe"

Works fine here for me.

Yes, but I'm an extreme coding noob and at least I can't do it.

Thanks for you quick reply :) Yes, I just found this: Fra:1 Mem:840.29M (Peak 1682.40M) | Time:00:06.59 | Remaining:18:15.69 | Mem:1147.60M, Peak:1153.71M | Scene, ViewLayer | Rendered 1/12 Tiles, Sample 80/4096 So there is info about the current tile / total number of tiles and of course the sample...

Just noticed that my "fix" is only partially working. As soon as Cycles uses "Tiles" (e.g. when you render resolution is > 2048 px in a default scene or you deliberately told Cycles to use tiles e.g. to save some memory), every single tile reports its render progress in the range...

BTW this same thing is still happening in Blender 3.x when trying to submit a scene with an empty "Scene Collection". >>> active_scene = bpy.context.active_object >>> print (active_scene) None As soon as I add e.g. an empty I get the following >>> active_scene = bpy.context.active_object >...

To get it running you have to update every client's blender_cycles.py and restart afrender

OK, I fixed it (hopefully, it's more like an educated guess at copy&paste ;) ). # -*- coding: utf-8 -*- from parsers import blender class blender_cycles(blender.blender): """Blender Cycles """ def __init__(self): blender.blender.__init__(self) def extractPercentage(...

Hi there, I noticed that Afwatch doesn't show a per-frame progress bar when rendering with Cycles any more (3.x+). The syntax of the render log has changed to: Fra:31 Mem:1232.12M (Peak 2206.01M) | Time:02:15.69 | Remaining:02:00.57 | Mem:1139.36M, Peak:1237.26M | SHOT010_Scene, ViewLayer | Sample 2...