Sending file: C:/Users/Andrew/Desktop/Untitled_LuxCore/00001.bcf Remote node has the same pyluxcore verison Job started: C:/Users/Andrew/Desktop/Untitled_LuxCore/00001.bcf New render farm job: C:/Users/Andrew/Desktop/Untitled_LuxCore/00001.bcf Creating single image render farm job: C:/Users/Andrew/Desktop/Untitled_LuxCore/00001.bcf it's really distributed network rendering and caustics that keep me on Lux.Ĭode: Select all LuxCore 2.3 Of course after years of using Lux I'm pretty comfortable with its material pipeline, but with the switch to node-based materials and the fact that I run most of my texturing through Substance these days. I'm slightly surprised that no one else is clamoring to get network rendering working, as I consider it one of the main reasons for using LuxCore (the other being caustics). Hopefully will be able to post some logs from that PC tomorrow though. At the moment I have a render running inside Blender though, and I don't want to screw it up running tests in the external renderer. My main PC is having the other issue where the Node seems to time out on itself after a few seconds. These look identical to the logs I was getting when trying to use this PC as a Node for a network render. On my slave PC, here are the logs when trying to start up the job locally (I moved the BCF and all supporting files for the basic cube scene to the local PC's desktop, and am running both Console and Node on this PC which I previously had configured as only a Node). Right now I'm still having the same two (different) issues on each PC when using the external renderer. I'd be fine to manually start the render on both PCs instead of using the network render capability, my only concern would be that if both PCs are on the same network anyway, aren't they going to detect eachothers' nodes and cause problems? But we can deal with that later. blend, caches, etc) are located on this same network file share. When rendering locally in Blender all files (textures. For what it's worth, in all cases I was hosting the BCF and related files on my network file share (a 3rd computer running FreeNAS), but both Windows PCs running LuxCore have the file share mapped as a network drive (so shouldn't behave any differently than a local file), and both were connected to the drive at the time of testing.I've expressly allowed both public and private network communication for pyluxcoretool on both computers (maybe something else also needs permission?).I've expressly allowed both inbound and outbound connections on the port.It makes several attempts at this with the same errors before giving up. If I run Node on a networked computer only, I get the error "Permission denied" on the Node when trying to receive the BCF file (and the Console reports that the Node shut down the connection).It's roughly the same amount of time that passes (5-10sec) in both scenarios. If I export just the basic startup scene (single cube), processing stops later (after receiving the mesh file, but before rendering starts).For the complex scene, processing stops in the middle of receiving one of the mesh files.The Console continues running, just waiting infinitely for the Node to have a film ready. ![]() It just stops work, and the status reverts to "Waiting for new connection". ![]() It doesn't crash, as I can still interact with the window (eg scroll through the log). Running both Console and Node on the same computer results in the Node randomly stopping work a few seconds in to receiving the files.Generating the BCF file appears to work fine.Rendering inside Blender with LuxCore works fine.I'm running Windows 10 on both computers.I think I'm encountering two separate issues, but not sure. Just found myself with a scene complex enough that I wanted to bother with network rendering again, and I can't seem to get it to work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |