Vray proxy bug

[bassking1@libero.it]

Hi guys,
working with proxies I found a strange bug: If I created a new proxy and then imported it and repeated the procedure twice, when I rendered the scene, only one type of proxy showed up, also scattered in an insane way. To be more specific, if I ceated a pine tree, and then a palm tree, when I hit render, in the rend only the pine showed replicated and scattered insanely...any clue on this behavior?
Thanks for the help

PROFESSIONAL ARCHITECT & 3D VISUALIZER
http://archpaintvisuals.wordpress.com

[dkendig]

could you post a render of the final output?

[ALTO]

Same problem here...

Rhino viewport


Render

[dkendig]

edit: my previous post was made before I was able to see all of the attached images. I will have to look in to this. Is there a bug report about this yet in our system?

[ALTO]

Bug report sent!

[dkendig]

Alto - I don't think I see a bug report from you about this from yesterday. Was this tested in the build we posted this week? Did you use the bug reporting tool to send the bug report, or did you send us an email? Micha has reported some trouble with the bug reporting tool, so if you used that, maybe you are having trouble also. I need a copy of the error log to see what's wrong if that's the case. You can see the error log by opening the debug window. Just copy and paste the output in there in to an email, and send it off to vfrwip@chaosgroup.com.

[ALTO]

I've sent an email to vrayrhino@chaosgroup.com, Ticket is #504367.

Fernando told me to try the new beta, unfortunately problem is not solved, here is a screencapture of what happens: http://www.screencast.com/t/O3kgcMxn5kty

I don't have any error in the debug window, only this text:

About to make our qapp
after make qapp
C:\Documents and Settings\All Users\Application Data\ASGVIS\VfR564\VRayPlugins.xml
C:\Documents and Settings\All Users\Application Data\ASGVIS\VfR564\RhinoOnlyVRayPlugins.xml
Made it after UIManager.initialize
C:\Documents and Settings\All Users\Application Data\ASGVIS\Common\x64\vc10\Python26\lib\site-packages\Ft\Xml\InputSource.py:346: DeprecationWarning: functions overriding warnings.showwarning() must support the 'line' argument
  FtWarning, 2)
FtWarning: Creation of InputSource without a URI
=========Plugin Information=========
Plugin: V-Ray for Rhinoceros
Plugin Version: 1.48.19181
Host Application Version: 5 (x64)
====================================
FtWarning: Creation of InputSource without a URI

I'm using Rhino V5 64bit (24/01/2012), Vray 1.48.19181, Windows Xp 64bit with MUI (Italian)

[dkendig]

that video was extremely helpful, thank you. There are many ways to copy in Rhino. The Rhino copy command seems to be the most... evasive one to get to work properly. I'm going to try to reproduce this again, and then try the other copy methods to see if they produce the same results.

vrayrhino@chaosgroup.com is the wrong email address for the beta stuff. That is our general support email address for the released product. Support can't do anything about beta issues, only developers can, so the issue needs to be sent to our bug tracker. You can submit bugs from within Rhino now by going to the V-Ray menu in Rhino, and then clicking on Report Bug. Be sure to fill out ALL fields, they are ALL required.

[bassking1@libero.it]

Actually I had the same problem, but re-tried the scene (cube and Pyramid) with the new build and it seems NOT TO HAVE THE BUG ANYMORE. I re-produced ALTOS's scene and for me it worked.

[ALTO]

Even without copy only one proxy is exported...

Thanks for the new bug report system, so do i need to send you something (file 3dm, vrmesh...)?


Just an offtopic question, does the beta work with offline activation? I have a friend of mine who cannot use the license sent with the older version, should i give him the new email address (vfrwip@chaosgroup.com) to contact you?

Thanks

[dkendig]

in that particular case, no, he should send the email to vrayrhino@chaosgroup.com. Only bugs need to go to the beta testing vfrwip@chaosgroup.com email address.

You can attach additional files to the report if you think they would be of use. We automatically grab the error log and assets used in the scene (textures, vrmeshes, etc), but we don't grab the 3dm file yet, sometimes they can be quite large, and we need to split them up in chunks somehow if we are going to have them submitted to our bug tracker. I believe the current file size limit is about 30mb per file.

I just checked again, and I don't see the bug report. When you submitted the report, did the window close on it's own, or did you click cancel/close the window? Try submitting a bug report with the title "Devin broke it again".

[kostenurka]

It is confusing when bug is to be reported because there's no message confirming the bug has been sent. I must wait until dialog box mystically disappears to know my report has been sent. Few times happened to close the bug report window earlier..

Alto - I don't think I see a bug report from you about this from yesterday. Was this tested in the build we posted this week? Did you use the bug reporting tool to send the bug report, or did you send us an email? Micha has reported some trouble with the bug reporting tool, so if you used that, maybe you are having trouble also. I need a copy of the error log to see what's wrong if that's the case. You can see the error log by opening the debug window. Just copy and paste the output in there in to an email, and send it off to vfrwip@chaosgroup.com.

[dkendig]

it was added quickly to help capture some information for a couple of bugs during our beta process. It is not a finalized and polished feature yet. Confirmation messages and foreign character support still need to be added.