- Posts: 2
- Joined: Thu Aug 27, 2015 2:26 pm
+1 to both of your questions! Though, I'm really curious about your question number 1. ( sorry to hijack your thread.. )
We've had issues with the render node also since the updated Fusion..I think it was on 7.7.1. I can't seem to find anyone that has had similar issues, and BMD hasn't responded to my emails. ( probably too busy fixing Fu 8 bugs.. )
We've run across other render errors that make me believe that there is an issue with the render node exe. I've listed here a few errors that seem to come up when rendering on the farm, that do not happen locally, or rendering through Fusion.exe.
General error command-line error:
This is the first error that started up a couple fo versions ago. The frames render, but the commandline renderer isn't happy. It tends to kick out this type of error. I haven't been able to find a pattern. I seems to happen towards the end of an allotted sequence of frames..as if the memory is filling up and not being released. But that's just general observation. I have been able to reproduce anything conclusive.
- Code: Select all
*++++++++++++++++++++ Royal Render checks the return code of the
executable ++++++++++++++++++++***
*R 12| ++++ Executable returned -1073741819 (0x c0000005) as exit code
for frame 1.*
**
*R 13| Error: Renderer or plugin contains a bug. Crash was caused by a
NULL pointer memory access.
-The Duplicate.Fuse
This node is shipped with Fusion. It renders fine in Fusion, but as soon as it renders on the farm I get these types of errors:
- Code: Select all
[string "--- Begin FFI Script ---..."]:12047: attempt to index field 'LabelControl' (a nil value)
stack traceback:
[string "--- Begin FFI Script ---..."]:12047: in function 'BeginControlNest'
...esign\Fusion Render Node\Fuses\Blackmagic\Duplicate.Fuse:135: in function <...esign\Fusion Render Node\Fuses\Blackmagic\Duplicate.Fuse:15>
If I render over the network to a machine with Fusion.exe, the render works. But as soon as it goes to the rendernode consolenode.exe it fails, as it does on the farm going through royal render.
I've been discussing it here with other users: http://www.steakunderwater.com/wesuckle ... ?f=6&t=435
-TimeMachine.Fuse ( a modifier Fuse by Pieter van Houte)
This is a 3rd party node, so I understand that BMD may not offer any support. However, it reinforces my belief that the command-line render node is broken somehow.
Local Fusion renders and network Fusion renders are fine. As soon as it goes through the command-line renderer it bombs. Royal render kicks out these errors:
- Code: Select all
"\fusion\7\fuses\TimeMachine.Fuse:1409: attempt to perform arithmetic on local 'time' (a nil value)
stack traceback:
***\_WORKGROUPS\fusion\7\fuses\TimeMachine.Fuse:1409: in function 'XSheet'
***\_WORKGROUPS\fusion\7\fuses\TimeMachine.Fuse:1798: in function <
***\_WORKGROUPS\fusion\7\fuses\TimeMachine.Fuse:1584>"
I've asked the Fuse author, and he hasn't run across this, as he doesn't use a render farm.
http://www.steakunderwater.com/wesuckle ... 4&start=45
I would love for the devs to take a look at this and see what's going on. Maybe when they tweeked the render nodes for "Fusion" vs "Fusion Studio", something got stripped or something. All I know is, we rarely if at all had these types of render farm rendering issues. Anything rendering on the boxes was rendeirng on the farm in 6.4 and 7.0.
It's sad to say, but I'm kinda happy to see we're not the only ones having issues with the render node exe. I don't feel completely crazy. Have you have any issues like these?