Rhino 4.0 crash caused by VfR since installing Rhino SR7?

[Boye]

Hi all,

This is not an actual bug report, as much as an attempt to find out if others are experiencing the same problem.

As subject line says my Rhino crashes when opening a file using VfR as renderer or even when I try to assign VfR as current renderer.

This is of course very frustrating so I have sent a report to Asgvis support as well as McNeel (Rhino).

[jlaucks]

Re: Rhino 4.0 crash caused by VfR since installing Rhino SR7?

Yes!

I have been having several different issue of the past few days and need to contact ASGVIS tomorrow.(please bear with me)!

-1) 2 modelers from my workplace are currently trying to work quickly through some architectural renderings and we decided to try to boost our vray render times by utilizing the DRSpawner.
It was installed on 6 machines (1 vista 64 bit, 1 XP 32 bit, and 4 Windows 7 64 bit). Renderings being sent from the vista host and the xp host were spawning the Windows 7 machine successfully for about a week... but recently the DRSpawners have been dropping out or turning off in the overnight if left idle, or sometimes not will not stay running on startup. Rebooting the machines seems to help but is hit or miss.

-2) our workplace has 4 floating rhino licenses and 4 floating VFR licenses: recently we have been having trouble picking up a license when only one other instance of rhino and vray are running. (this started happening during the second week of utilizing the drspawner)

-3) my workstation was recently migrated from the 32bit XP to a 64bit Windows 7. with Rhino SR6 ( i am continuing to use the XP 32 as a render slave)

-4) I started experiencing the rhino and vray licensing issues and tried installing the update to Rhino SR7

-5) Now on a 30,000KB - 60,000 KB model i am having trouble even making it through the Light Cache before windows 7 ghosts white- DRSpawner drops out, and windows try's to "resolve an issue with rhino", and then force closes the application

-6) I have been having this issue for the past few days with the available license issue mixed in to the point where Wednesday I probably had the rhino crash 5-10 times n the beginning of the day and with several reboots was working very smoothly and rendering 3000-4000 pixels by the end of the day. Today with some additional modeling I continued to tweek but still crash vray and rhino probably close to 20-30 times..

If anyone has any thoughts on any of these issues please let me know.. i know there is a lot of pinpoint problems rolled into one but i am hoping maybe one will solve some of the others..

I have a feeling it is somehow tied to SR7 or Windows 7 though because i have never had this much trouble on XP or SR6..

Thoughts..

(best way to contact ASGVis regarding these issues?)

Thanks in advance,

J

[Boye]

Re: Rhino 4.0 crash caused by VfR since installing Rhino SR7?

I'm sorry, J, but it seems your problems are somewhat more complex than mine, so please bear with me when I return to the issue I described earlier.

For some time I have successfully reinstalled Rhino and VfR. (Boy, it was time consuming to try to re-establish my favorite button configuration. Maybe I should learn how to save those.) Using SR6 seems to eliminate the crashing so far.

But the constant reminder about "Critical Rhino update" prompted me to try upgrading to SR7. This did work for some time. No problems with opening or closing files.

However, Rhino DID eventually crash again when I tried to paste objects copied from a recent scene into the now open scene. This was exactly what started the crashing behavior before.

Could it be caused by a conflict between different visopt-settings in the two scenes? I guess they wouldn't be included with copied objects.

[Boye]

Re: Rhino 4.0 crash caused by VfR since installing Rhino SR7?

It seems that the program crashes exactly at the time when the message comes that the imported objects contains materials with the same name as in the scene. I'll try to remove material from the objects I import to see if it makes a difference.

By the way, I tried to export a single object as a rhino file and then importing it succesfully in to another scene. There was no material name conflict there.