Vray 2.1 Seems to be saving the proxy within the max file

Vray 2.1 Seems to be saving the proxy within the max file.

Since moving to 2.1 it seems that when you create a Vray proxy it saves the actual proxy in the max file as the max should be tiny once the proxy is created…but it’s huge!!

Anyone else have this issue???
max 2008
vray 2.1

Thanks
Jamie

hmmmm …wierd

I just re-installed 2.0 tested both it & 2.1 but they both created proxys fine.???

Must have been a bug or something in the max file???
I have tried to merge the proxys into another blank scene but it ends up massive as well.

Any ideas anyone?? or do I just waste another hour doing all the proxys again

Thanks

As usual it appears to good ol MAX corrupting things again.

It seems that max is adding somthing into the file that is causing it to get massive even if there is virtually nothing in the scene.??

anyone had this befor???

update- I have deleted EVERYTHING & the file is still 18mb compressed…something really messed up in that file…is there anyway to check??

Vray 2.1 ? when it released?

yes we had some kind of same problem, and savetime took ages.

it’s because max is creating nodes and duplicate everytime you save, so each time it’s dubling the save time and the saved file

here is the script to get rid of it :

while (numNoteTRacks TrackViewNodes.Max_MotionClip_Manager > 0) do deleteNoteTrack TrackViewNodes.Max_MotionClip_Manager (getNoteTrack TrackViewNodes.Max_MotionClip_Manager 1)

When you will lunch that script, it can take some time to delete everything so be patient, after that it should be fine again. well if it’s the same problem that what we had at least.

Stan

Thanks so much STAN!! I owe you a beer or two.

I will do the script tonight..fingers crossed it all goes well

Thanks again

Jamie

Hi Stan,

I copied the code into a text file & changed the extension to .ms
Nothing seemed to happen when I ran it though??? Did I create the maxscript file properly.[sorry I am clueless when it come to scripting]
I am also running 64bit max …does that matter??
It really does sound like the same problem so I am sure the code will fix it???

Thanks again for your help.
Jamie

I can assure you this is not the case - we never store the proxy in the .max file.

Best regards,
Vlado

Yes…I tested creating a new proxy afterwards & everything was fine…as usual…another 3ds max problem…NOT vray

Thanks