rhino 5 + vray 1.5.22840 Micha

[renee81]

Micha,

I remember I saw your post on the Rhino NG,saying that you were not able a file,because the access was denied.
I updated Rhino 5 to SR 2 last week,and I did not have any problems.Today I installed Vray 1.5.22840,and since I have the same problem you have.Did you find a solution ?

Looks like something in Vray is causing the problem.

Thank You

Renee

[Micha_cg]

The problem was gone on the same day without I changed anything.

[tashko.zashev]

Hi Renee,

Could you describe the problem in more details, so i can try to help with this issue?

[Micha_cg]

Here my initial post of the problem:

http://news2.mcneel.com/scripts/dnew...ed=View+thread

[renee81]

I don't do anything special.

First rhino 5 -64 SR2 was installed last week,I was using Vray 1.5.22642 I did not have any problems
Then yesterday I installed Vray 1.522840,and the problem started,I know there is quite a few builds between the 2,but none of them was installed,so the problem is somewhere between the 2 I installed

Open a Rhino file work on it do whatever you want as long as you don't start a rendering,it saves without problems.Do a rendering and you get exactly this .

Does not matter if you are using DR or not,the problem is still there

Thank You for your help

Renee

[tashko.zashev]

Hi Renee and Mitcha,

I'm getting the same issue here with this software configuration, it looks like a problem with the V-Ray build but it needs to be confirmed by the developers.
So i will make a note about it.
Many thanks.

[renee81]

Thank You for your help

[joe_b]

I am not sure how we would be causing this issue, as we never directly interact with the 3dm files on disk - Rhino does that for us.

We'll look into it nonetheless, I suppose we could somehow be screwing it up indirectly as part of our serialization/deserialization process, although I'm not aware of any changes to that recently.

[Micha_cg]

Today I got this problem one time again. My solution was to use incremental save and some time later the standard save was working again. Looks like a temporary process blocked the save process.

[renee81]

Found something, you can do as many render in window as you want,you can always save,Do one full render bang can't save.

[joe_b]

I came across one problem that could cause an interruption to the Rhino autosave process, and potentially cause the autosave file to remain locked.

I just manually made a nightly build, 1.50.22873, that has a fix to this issue. Hopefully that will resolve the problem. Let me know if it persists.

Sorry for the inconvenience

[renee81]

unfortunately still have the same problem.

Renee

[joe_b]

Does this only happen to you with larger 3dm files or is it any of them?

Here is what I am doing, let me know if I am missing a step anywhere

1. I set the autosave time to be 1 minute, just so I don't need to wait
2. I open a relatively small scene, about 50MB or so
3. I add a sphere somewhere and wait for it to autosave
4. I render
5. I add another sphere and wait for it to autosave

Basically I just make minor tweaks here and there and wait for it to autosave. I try different rendering types (RT vs production, etc )

Is it always completely reproducible for you? Or does it seem random?

[joe_b]

Regular saving doesn't seem to cause any issue for me either

[renee81]

The problem was not on the autosave,but on the manual save.Doing a full render was causing the problem,while doing render in window,did not.
I installed the lat build,and still had the problem.
I had that problem all day long and it was completely reproducible on many files.
Suddenly just like Micha,it did disappear,so right now everything looks OK

Thank You