Mon, Feb 3, 9:51 PM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2025 Jan 30 6:52 am)



Subject: Problem with Vue 8.5-9 xstream using 3ds Max


AlexEx ( ) posted Sun, 30 January 2011 at 4:46 AM · edited Mon, 03 February 2025 at 6:51 PM

The problem is that Vue crashes whenever i trying to render my scene in 3ds Max, containing a few of Max's objects. But if I trying to render a part of the scene, where Max's object is invisible, it works fine. I've started to build my scene using Vue 8.5 and 3ds Max 2011, but at some point this problem appears. I've tried vue 9 then, and my problem is gone. I saved the scene in particular file and continued my work. But few days later i've faced to my problem again. I've tried to render my scene file, saved previously but it still crashes. It's no matter if using either Mental Ray or V-Ray. It's like nightmare. I'm out of ideas. If anybody faced with similar problem, please help me.


hobepaintball ( ) posted Sun, 30 January 2011 at 11:19 AM

I use 9 INF so Vue and 3ds max work independantly. Have you tried a VERY simple pair of scenes? Very high res terains etc could be a problem.


AlexEx ( ) posted Tue, 01 February 2011 at 11:58 AM · edited Tue, 01 February 2011 at 11:59 AM

I've tried, it renders fine. Indeed, it seems like Vue don't suite for using it's large terrains in Max. But it still vry weird that Vue crashes now when I try to render scene, wich was rendered perfectly some time before.


surveyman ( ) posted Tue, 01 February 2011 at 7:11 PM

Can you report on memory utilization?   ie... Are you running out of memory?


AlexEx ( ) posted Fri, 04 February 2011 at 2:09 AM

No, I'm not. I have 8 GB RAM and when rendering it is used only 4 GB of them


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.