[photomg1]

Hi just had a go with network rendering on the 3.1 beta and the saved mxi does not open up as an image in maxwell render. I have no issues if its a non network mxi . Anyone else running into this ??

[Mihai]

Do you get any error messages?

[photomg1]

Hi Mihai ,
no nothing , the image saved at the same time is fine . The mxi opens up maxwell render in the console it tells me the mxi was generated in a merge process . But nothing is loaded in the viewport.

[photomg1]

the interesting thing is if I try and resume it , it tells me

All channels are disabled. Render channel will be enabled, are you sure you want to continue?.

So that looks to be the root of my issue , either something I'm doing when I'm setting up the network render or how its saving out the mxi. (this could be user error on my part it has been a while since I've networked rendered,but I don't think so)

[photomg1]

I can see the issue now (at least I think I can) , the network monitor setup is missing the render tickbox next to the embedded diffuse plus reflections.

[Mihai]

So no MXI is saved then. Does this happen with any scene you try to render with 3.1 network?

[photomg1]

Hi Mihai ,
just downloaded latest version as of today ! had a look at the monitor and the warning is due to where I'm trying to save the files . Its on a storage drive(second drive) of the master rlm server . It wont let me save there, so is saving them in a temp folder on my C drive on that computer (so at least I have them). This was not something that has been an issue for me before ( prior versions ). So I'm not sure what has changed .

warnings are :

Final MXI could not be copied in the selected path

what would be the cause of that ? the network is super simple just two computers linked via a router .There is no hardrive attached via the router (which I assume is what you would be referring to when requesting a network drive? )

[T0M0]

Yes, I experienced same bug.

If your final MXI is in same folder as MXS you will have blank viewport when you open MXI.
Move your MXI (or MXS) file to different folder and now open MXI. Voilà

- this bug happens only with cooperative network rendering since beta 3.0.99.3

[photomg1]

Thanks for posting TOMO , at least we are starting to circle the issue now.

[zparrish]

I was under the impression from Juan's blog post that the network tools were being upgraded and distributed outside of the 3.1 beta. Are they now embedded into the beta? TBH, I haven't tested 3.1 yet but have been very anxious to test out the new networking tools. If they are now part of the beta, then you guys got yourself another tester on board I only ask this because it's being spoken of in this thread like it's already been updated.

My work load has just been too high to justify beta testing 3.1 core/plugin functionality. I could justify it for the interruptions I experience with the current networking tools. Plus, status via web server would be awersome! I have to use VPN at the moment to check on my render queue from home, which is OK but not ideal.

[zparrish]

Sorry to stray off topic. The OP was about a network rendering render channel bug in 3.1 beta.

This is probably common knowledge now, but for thread continuity (to answer my own question), the new network tools are being previewed in the 3.1 Release Candidate. They were not part of any previous beta release.

http://www.maxwellrender.com/forum/view ... 37&t=43157

I was under the impression from Juan's blog post that the network tools were being upgraded and distributed outside of the 3.1 beta. Are they now embedded into the beta? TBH, I haven't tested 3.1 yet but have been very anxious to test out the new networking tools. If they are now part of the beta, then you guys got yourself another tester on board I only ask this because it's being spoken of in this thread like it's already been updated.