Tweet
Hi, I've been taking a look at this build, and I've found some things that think I should report.
If this is a wrong way to do it, or its preferred we mail directly to Chaosgroup members, please, post it.
DISTRIBUTED RENDERING
The behavior of the 5 may build respect the distributed rendering is next:
From Maya:
If we try to use distributed render from Maya, when we launch vray in the host we have two options:
Using vrayslave: In this case Maya will contact with the host, but the host says: "warning: Scene is empty.". So the high part of the render will be nothing rendered.
Using vray -server: In this case Maya will throw a warning: "Could not connect to host nnn.nnn.n.nn: Unknown error.". If we add, besides -server, -portNumber=20207 we got the same that vrayslave (then is exactly the same)
It's impossible use Maya for distributed rendering. The Question is: Why Maya did not sent the scene to host?. I've been reading the debug messages, but I'm sorry, I am unable to find where is the error or how solve it.
If we try to use distributed render from standalone, when we launch vray in the host we have two options:
Using vray -server: In this case Standalone will contact with the host, and will work perfectly, but will be impossible it show us the virtual frame buffer to see something although we use flag -display=1. We're completely blind till the end of the render, when we can go to the output folder and take a look.
Using vrayslave: In this case standalone will give us the same error it throw us form Maya using the vray -server option, "Could not connect to host nnn.nnn.n.nn: Unknown error". This error is caused because vray standalone is searching in port 20204 (Max port), or at least, it is not searching at 20207, Maya port. Using -portNumber=20207 works perfectly. (But still user remains blind).
So, or we use Maya and we leave ourselves limited to use only one machine, renouncing to use all our machines for distributed rendering for adjust quicker all our renders or we use it, but how we are blind, we must wait till all our machines finalize the render for access it to see and evaluate the result.
WHITE COLOR
The white color of shaded mode can be disturbing for the eyes. In really, for people who work at daylight hours, white is cool, but for people who prefers work at night... I can feel my disturbed eyes paining me for receiving excessive brightness, and if I bring down the brightness of the screen, I am unable to evaluate correctly the result of my render forcing me to be playing with the buttons of my monitor more than I should want. Neither is matter that vray looks operative system clock for choose automatically a brighter or darker color, but If this would depend of me, I would let the user choose their own shaded default color putting a color chooser in "Misc" or in "Vray UI" section of Vray Render Settings. This is quite curious... I never been conscious of this question always have been there till my eyes have started to talk... with pain. The background (alt+b) always I have it black or this sky-to-black from Maya 2009, but in the materials, Maya standard gray never disturb me...
This issue, brightness or darker, the well lit or poor lit environment of work, and the sight problems, would deserve an exclusive thread for it.
IPR
If we push ipr button, use vfb will be unmarked automatically. I guess you're oriented this to the future Vray RT for Maya and surely its not an error...
VFB
If we want save the render from the Virtual Frame Buffer window, right now we need, besides write the name of the output file, write their extension. If we simply write "render", the image will not be saved, we need write "render.png".
I guess this pop up (the one at push save icon in virtual frame buffer) should let us save our render in more formats (tiff, exr...)
For other side, respect the VFB. The idea is replace the original Render View Window?. If is it, Besides add a "launch render" button, realize yourselves till VFB haven't a buffer for compare two results, we still feel the need to keep using Maya Render Window. In my opinion, there is no hurry about this feature, so for me, easy with it.
Finally at this respect, the other cool feature of Maya Render Window is the snapshot, getting us a clue for choose exactly the render region we want to render, although this always has been improvable, because the majority of times, we not want render with "squared region" shape, maybe we need to render a circular region, elliptical, polygonal... if would be possible choose exactly what pixels we want Vray renders, we could save time at working hour... but for other side, appears Vray Rt for Maya comes step at step, so well, I suppose being as is, you should decide what to do about.
WARNINGS
Why this warnings?. How to avoid it?.
1)// Warning: Unsupported texture VRayMtl //
2)// Warning: Unsupported texture kEnvBall //
If this is a wrong way to do it, or its preferred we mail directly to Chaosgroup members, please, post it.
DISTRIBUTED RENDERING
The behavior of the 5 may build respect the distributed rendering is next:
From Maya:
If we try to use distributed render from Maya, when we launch vray in the host we have two options:
Using vrayslave: In this case Maya will contact with the host, but the host says: "warning: Scene is empty.". So the high part of the render will be nothing rendered.
Using vray -server: In this case Maya will throw a warning: "Could not connect to host nnn.nnn.n.nn: Unknown error.". If we add, besides -server, -portNumber=20207 we got the same that vrayslave (then is exactly the same)
It's impossible use Maya for distributed rendering. The Question is: Why Maya did not sent the scene to host?. I've been reading the debug messages, but I'm sorry, I am unable to find where is the error or how solve it.
If we try to use distributed render from standalone, when we launch vray in the host we have two options:
Using vray -server: In this case Standalone will contact with the host, and will work perfectly, but will be impossible it show us the virtual frame buffer to see something although we use flag -display=1. We're completely blind till the end of the render, when we can go to the output folder and take a look.
Using vrayslave: In this case standalone will give us the same error it throw us form Maya using the vray -server option, "Could not connect to host nnn.nnn.n.nn: Unknown error". This error is caused because vray standalone is searching in port 20204 (Max port), or at least, it is not searching at 20207, Maya port. Using -portNumber=20207 works perfectly. (But still user remains blind).
So, or we use Maya and we leave ourselves limited to use only one machine, renouncing to use all our machines for distributed rendering for adjust quicker all our renders or we use it, but how we are blind, we must wait till all our machines finalize the render for access it to see and evaluate the result.
WHITE COLOR
The white color of shaded mode can be disturbing for the eyes. In really, for people who work at daylight hours, white is cool, but for people who prefers work at night... I can feel my disturbed eyes paining me for receiving excessive brightness, and if I bring down the brightness of the screen, I am unable to evaluate correctly the result of my render forcing me to be playing with the buttons of my monitor more than I should want. Neither is matter that vray looks operative system clock for choose automatically a brighter or darker color, but If this would depend of me, I would let the user choose their own shaded default color putting a color chooser in "Misc" or in "Vray UI" section of Vray Render Settings. This is quite curious... I never been conscious of this question always have been there till my eyes have started to talk... with pain. The background (alt+b) always I have it black or this sky-to-black from Maya 2009, but in the materials, Maya standard gray never disturb me...
This issue, brightness or darker, the well lit or poor lit environment of work, and the sight problems, would deserve an exclusive thread for it.
IPR
If we push ipr button, use vfb will be unmarked automatically. I guess you're oriented this to the future Vray RT for Maya and surely its not an error...
VFB
If we want save the render from the Virtual Frame Buffer window, right now we need, besides write the name of the output file, write their extension. If we simply write "render", the image will not be saved, we need write "render.png".
I guess this pop up (the one at push save icon in virtual frame buffer) should let us save our render in more formats (tiff, exr...)
For other side, respect the VFB. The idea is replace the original Render View Window?. If is it, Besides add a "launch render" button, realize yourselves till VFB haven't a buffer for compare two results, we still feel the need to keep using Maya Render Window. In my opinion, there is no hurry about this feature, so for me, easy with it.
Finally at this respect, the other cool feature of Maya Render Window is the snapshot, getting us a clue for choose exactly the render region we want to render, although this always has been improvable, because the majority of times, we not want render with "squared region" shape, maybe we need to render a circular region, elliptical, polygonal... if would be possible choose exactly what pixels we want Vray renders, we could save time at working hour... but for other side, appears Vray Rt for Maya comes step at step, so well, I suppose being as is, you should decide what to do about.
WARNINGS
Why this warnings?. How to avoid it?.
1)// Warning: Unsupported texture VRayMtl //
2)// Warning: Unsupported texture kEnvBall //
Comment