Al/Rich Just had a chance to give it a real go Feedback so far, Ray Trace only
1. Unless render size has even numbers you get small black pixels dotted around.(confirmed in accurender forum by Roy in I think one of Pete's posts). 2, Also then found when using sketch size render, and selecting custom to get an even number the dialogue reports identical numbers such as 1270x1270 even though image is not square 3. It seems to be worrying only use max 25% across of cpu rendering a seems to get progressively worse it you stop then carry on, maybe thats why Boothy is finding so slow as my self. 4. If show light bulbs is selected then extracts but batch render crashes immediately with errors, -no bug splat sketchup keeps working. 5. When using the lights channels while rendering, very occasionally when rapidly changing values the render window just disappears, no error messages, no bug splat just gone will check task manager next time. 6. Same as Boothy Material editor short cut does not work in Irender folder, or shortcuts tree editor or image editor but RPS material editor does. Boothy I tend to down load Accurender program and install that even though no full ACAD, and just use that for shortcuts. 7 You don't need spot light for caustics 8, When in rendering mode and you change say sunlight setting - the IRender sunlight and sky dialogues are not greyed out and still appear still to be working, even though the "use sketchup value" is selected. I realise you can use sketchup value when in render mode but for other it may be confusing.
After a bit more testing on cpu load, you get up to 100% on initial render, but if you stop and restart it then % of cpu decreases to approx 25% and then if you further stop and restart, it goes down to 13% or lower.
"3. It seems to be worrying only use max 25% across of cpu rendering a seems to get progressively worse it you stop then carry on, maybe thats why Boothy is finding so slow as my self."
I was able to duplicate this.
When using the Path Tracer, stop and resume lowers CPU usage dramatically.
Until we can get this fixed, always stop and restart with the green button.
I am not sure if I was suggesting that it was slow the actual like for like pass speed I found much faster - its just the number of passes required to get any where near a decent result is the limiting factor.
" Until we can get this fixed, always stop and restart with the green button." - Will do Al. Thanks for looking at It.
Sorry Boothy - your right, the passes are far faster and to get an end result equivalent to the packet method takes a lot longer. I just assumed you might be having the same problem as me when having change material property etc, and continuing rendering it was actually doing rendering passes a lot lot slower due to a lower and lower cpu usage.
Anyway there's one good thing - it gives me more time to have beer as it's getting late :-)