Huge File Sizes

[luckett_jason@hotmail.com]

Hi guys,

Is anyone else getting huge .vrscene files with the latest update? Mine have gone from 1.5gb to over 14gb, same file, just a couple of small updates.

I'm finding rendering inside 3dsmax through the livelink function a very big no as well, this maybe to do with my scene size, approx 840mb, maybe this is onlt meant to work on small files?

Kind regards,

Jason

[vladimir.nedev]

Is anyone else getting huge .vrscene files with the latest update? Mine have gone from 1.5gb to over 14gb, same file, just a couple of small updates.

Do you mean the new V-Ray for 3ds Max version ?
The Vantage version doesn't affect the .vrscene export, as this code is part of V-Ray for 3ds Max.
This is something to be reported to the V-Ray for 3dsMax team.

I'm finding rendering inside 3dsmax through the livelink function a very big no as well, this maybe to do with my scene size, approx 840mb, maybe this is onlt meant to work on small files?

These huge files (when you have deforming meshes) are precisely why we implemented the live link animation feature, it saves you from exporting a .vrscene file with the full animation range.
What issues are you having with this ?

Greetings,
Vladimir Nedev

[luckett_jason@hotmail.com]

Thanks for the reply,

File sizes are still big, I have tried a fresh merge into a new file to remove any problems, used remove re-timers script, no luck there. There are no deformable meshes. One of the routes exports normally, the other 3 are 10-20 times larger than before. I will take another look after my current deadline.

There are 4 different routes in the 3dsmax file, each one saved out separately so as to hide non-visible geometry, this ensures memory translation success into Vantage. The workflow here is using the export and send the current animation range as a vrscene.

I also seem to have unearthed another strange issue, when trying to shorten the animation range in 3dsmax to only render the end segment for one of my routes, this just failed, inside vantage it rendered out a still frame repeated 1100 times instead of the animated 1100. It also locked my 3dsmax file's export to Vantage to a maximum of 1100 frames, even when clicking on a camera with 3900 frames and ensuring the timeframe matched. I finally remedied the problem by importing everything into a empty scene, ensuring the scene had 3900 frames, not sure if this will happen again tbh.

Kind regards,

Jason

[vladimir.nedev]

Can you send us any of these files ?
We can try doing the export to .vrscene here in V-Ray 5 update 1 and update 2 and see what changed.

I'm finding rendering inside 3dsmax through the livelink function a very big no as well, this maybe to do with my scene size, approx 840mb, maybe this is onlt meant to work on small files?

Is the live link a big no because it's too slow to export and start rendering ?
I guess this can happen with lots of Forest Pro instances for example.
Reducing the number of generated instances can speed it up.
But that's only a guess without having a look at the scene.

Greetings,
Vladimir Nedev

[luckett_jason@hotmail.com]

Thanks for the reply, I will also try reverting back to 5.1 later.

I can't send the files as they are confidential and too large.

I think it is an issue somewhere in the file as one route doesn't get bloated, maybe Vantage has a new issue with something? I will try to find the problem here and let you guys know.

The live link is great for smaller/medium sized files but obviously less so for the heavy scenes, in future I will only use lo-poly models when doing animations, also as you say the Forest Pro instances probably don't help, I've noticed the Forest Pack component has the biggest impact on successful translation.

It would be good at some point to get some general guides do's and dont's, the Vantage help docs aren't comprehensive, appreciate it's still sowewhat in it's infancy.

Vantage is a fantastic tool and we appreciate all the updates as always

Kind regards,

Jason