If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
New! You can now log in to the forums with your chaos.com account as well as your forum account.
You can always render them through the Maya "render.exe" command; in any case we are trying to reproduce the issue here, but it does not seem to occur (or at least not that often), which makes debugging somewhat hard.
For -display=1 you must enable VFB in Render Settings. You can add there the render hosts too.
It seems that we've catched another bug... Is this the same scene that you've send us? And are you using a new build? Can you reproduce the bug each time with the same render settings/command line? Maybe try to render using different hosts. We must catch some pattern there (or lack of it ).
No luck: The attached image was rendered overnight via Render.exe and what do we get, the same bugs as via standalone. This drives me crazy! If we only could find out why this is happening and why only we have this problem!?
Yesterday we tried to render some tests via standalone and we found that old bug (which I thought was fixed already), that when you did not specify the region and crop, then the standalone renders outside of the image. Also we specify the image size in RenderView, in the standalone flag and we also changed it inside the vrscene file. The region=none flag was no help.
When the Render.exe way also is not working, what can we do anymore?
Here are the results from the test renderings we had done over x-mas:
upload.sequenz.com/vray/seq101228_all.jpg
All images are nearly the same scene (just some AA and IR map settings changed).
Result: Wether we render via Render.exe or standalone the bug appears everytime. Sometimes more obviously like in the one at the top right corner and sometimes it is hard to see. Render with fewer hosts didn't help either. Only when we render without DR and standalone (image still render at this moment) the bug disappears.
In the VRMayaSpawner.log only appears the following alert:
0: [2010/Dec/23|17:31:06] ========================== Starting new session ==========================
1: [2010/Dec/23|17:31:06] Got this module name: C:\Program Files\Autodesk\Maya2011\vray\bin\vraymayaspawner20 11.exe
2: [2010/Dec/23|17:31:06] Got this INI file name: C:\Program Files\Autodesk\Maya2011\vray\bin\VRayMayaSpawner.i ni
3: [2010/Dec/23|17:31:06] *** ALERT! Could not open INI file: "C:\Program Files\Autodesk\Maya2011\vray\bin\VRayMayaSpawner.i ni". Using defaults.
4: [2010/Dec/23|17:31:06] --
5: [2010/Dec/23|17:31:06] Dumping current settings...
6: [2010/Dec/23|17:31:06] VRaySpawner temp dir: "C:\Program Files\Autodesk\Maya2011\vray\bin\network"
7: [2010/Dec/23|17:31:06] Application name (MAX/VIZ): "C:\Program Files\Autodesk\Maya2011\vray\bin\vray.exe"
8: [2010/Dec/23|17:31:06] --
9: [2010/Dec/23|17:31:06] Executing ""C:\Program Files\Autodesk\Maya2011\vray\bin\vray.exe" -server -portNumber=20207"
Crazy thing is if we us the same scene and turn the camera so that we see the opposite wall, we get a clean image (rendering with standalone and DR).
Comment