Interface slow and freezes often

[mgibeault]

With the last two builds.
Mainly the Material editor, but I've seen it with the Options editor too.
Very slow to go from one field to the other, sometimes I get a "busy cursor" after each mouse click.
Material preview is unusable.
A few times I got all three windows all greyed-out but Rhino is still responsive, I click on the V-Ray Options icon and it comes back to the front but all greyed-out.

[fpedrogo]

Hi
We just fixed these issues. The fix is available in today's nightly build.

[mgibeault]

Great, I'll try this right now!
Thanks

[dmiko]

have got same problem with vray2 educational latest build 2.00.25251, do educational and commercial licenses get same updates? do they have generally same functionality?

[fpedrogo]

have got same problem with vray2 educational latest build 2.00.25251, do educational and commercial licenses get same updates? do they have generally same functionality?

Yes, but it is on a nightly build.

[fooprobe]

But the nightly builds are not available to edu users right? So the edu version only sees these fixes with official released updates, right?

this is is a mighty pain. My students have to restart rhino all the time to get control of their mat editor back. It would be great if the fix could be shared.

[fpedrogo]

Hi Emil
We fixed the slowdown on the material editor. The freeze is due a UI license time out. In V-Ray we have two licenses, the render license and the interface license. The idea is that if you have two users and only one V-Ray license, you can share the different licenses between both user. For example, while one user is doing renders (using the render license), the other user can be creating materials, working with setting, lighting, etc. using the UI license.
But how this work? If the main user is not using the interface for certain amount of time, the UI license is deactivated. So, the other user can use it.
The problem is that if you let the texture editor open and the UI license deactivated, V-Ray and Rhino freeze. This is a bug that we have to fix. The good news is that we have a workaround for that. The solution is manually deactivate the UI license timeout. To do that you will have to edit the "V-Ray For Rhino.ini" file.
These are the steps.
1. find the "V-Ray For Rhino.ini" located in the ASGVIS folder. "C:\ProgramData\ASGVIS"
2. open the "V-Ray For Rhino.ini" in any texture editor (notepad)
3. under "Licensing" you will find this: "gui_timeout_minutes=5"
that mean that the UI license will deactivated after 5 minutes.
4. replace the "5" by "-1"
it will look like this: "gui_timeout_minutes=-1"

You will have to restart Rhino if it was open while you were making the UI license changes.
This will deactivated the UI license timeout and you will not have that UI freeze anymore. However you will not be able to share the UI license with other user.

[fooprobe]

Thanks, Ferndando. ok, I see how to make this change. but i'm working at a college. We have MANY machines, and we have to change this by hand. you mentioned that this was fixed - I assume this was in the nightlies? does that mean when we get a new release, we won't have to change the ini file?

any idea when will we see an edu release with this fix? (i know, i know.)

thanks.

[fpedrogo]

We have MANY machines, and we have to change this by hand. you mentioned that this was fixed - I assume this was in the nightlies? does that mean when we get a new release, we won't have to change the ini file?

No, the time out issue is not fixed. Unfortunately, you will have to do it manually. What we fixed, was a slowdown on the material editor and also a very slow material preview.
Definitely, we are going to do something with the UI timeout for V-Ray 3.0.

[fooprobe]

Ok, I understand now, thanks!

[gantonski]

I know this is an older thread but i was pointed here from the thread I started.
here is my thread:
http://forums.chaosgroup.com/showthr...699#post652699

My rhino is fine but all vray windows are grayed out and windows 'beeps' or 'dings' at me when i click any of them. it sounds close to what fernando said, but not exactly. I may try that hotfix but for the sake of getting my thesis work done I'll skip the risk of breaking it further.

Also, i'm curious why these things can't be released on a patch and why it must be released on a new version with a new paid licence with a new subscription? It is a lot of payment from *students* to get what should be integrated in a 'working' release of any software. I know this is a snooty question but I cant seem to rationalize it to myself.

[fooprobe]

Also, i'm curious why these things can't be released on a patch and why it must be released on a new version with a new paid licence with a new subscription? It is a lot of payment from *students* to get what should be integrated in a 'working' release of any software. I know this is a snooty question but I cant seem to rationalize it to myself.

this is a very good question. There are a lot of little fixes that aren't so little actually, and they only get seen in the nightly builds for months or longer. It would be great if there was a way to offer more frequent updates, especially for UI bug fixes.

[gantonski]

It would also be splendid if they offered nightly builds to academic license holders as well. So sad : (

[fooprobe]

I couldn't agree more.

[mnewberg]

Which change in the nightlies do you need in the edu version? There have not been a lot of changes done to 2.0 since we have been focusing on 3.0 for some time now.