Hi Vincent
Thanks again. I was wondering if you knew of a way to render the layer id pass with the G buffer so that it is anti-aliased. Right now it is not and I cant figure it out.
I am trying to isolate my trees as a render pass separate from the imported max geometry. I want the base of the trees to be occluded by the max geometry. Does that make sense?
EDIT: OOPS nevermind. I realized I am supposed to render a layer mask not a layer id!
Thanks,
Davey
In reference to what Vincent mentioned earlier;
How do you go about synchronizing a camera in max, and bringing that information into Vue?
Yes, Vue has render passes for the following:
Post Processing
Atmosphere Gain
Atmosphere Filter
Indirect Lighting
Background
Reflections
Refractions
Ambient
Shadows
Specular
Diffuse
vue now has an update, it fix some (expected) bugs , if u bought it u have the rigt to get the updates 
request for them to e-on :shrug:
Hi piper1234,
it is not a bug, but underdeveloped software. I already forgot about Vue, it was a bad investment, or rather loss. Idea is good, but still in early phase, it should be treated as beta, and free, for now, but…
Regards
Srdjan
I have to agree with Srdjan here. Its a complete waste of money at this stage. I’ve had Vue5 Infinite with Xstream. Hopeless. I gave up trying to get it to work. I’ve been looking forward to getting Vue 6 Xstream hoping all the bugs would be ironed out, and also getting rid of the “out of memory” errors due to it now being 64Bit. Well, the memory errors have gone. But if I try to load ACTUAL real world terrains, (I’m in the mining industry), and populate that, it takes forbloodyever to populate it in Xstream. Lets say about about 20 minutes for a piece of topography 10km x 5km. Then, when it does finally populate it, very sparsely might I add, I save it as a vue file. ‘All good’ so far. Open the Vue file in Max, press the render button, CRASHHHHH…
Max has no problem whatsoever loading these terrain data files. I’ve been doing it for years. I’ve used Forest Pro and put millions of mapped trees all over them to see whether its memory errors. No problems at all. I have 16Gb’s RAM on WinXP64. Introduce Xstream into the picture and the whole thing just crashes. And yes, I’m using the 64bit version of Xstream.
If you want to use actual real world terrain data, all I can say is, forget it. I’m hoping I can change this post one day and say that they’ve got it working smoothly. I really do…
hi there,
just call tech support. they will help you.
They helped me already with many other tasks.
I’m using Vue xStream with Lightwave (actually, not even with Lightwave…I don’t have the guts to use it concurrently with any software) and it’s been a nightmare for me too.
I’ve had the same problems as described by others above, plus not being able to see any cows on the render farm. Vue support is MIA and I’ve got a show to deliver.
NEATO!
Hi All,
Please dont hate me, but I love xstream with Lightwave, and have been able to do some cool stuff with it. Basically, it allows me to use my animated LW objects (characters with motionbuilder fbx files) and have them interact with the vue environments, particularly the atmospheres and shadows coming off the trees etc.
Yes, its not stable (you pretty much have to save after every adjustment) but you can difinatly get some awsome results, you probably couldn’t otherwise, without doing a crap load of stuff in a buch of other programs or plugins.
Who knows, it might end up stable one day.
Hate? No way man! I’m completely jealous! =)
I'm admittedly not using xstream as it's meant to be used. I'm making crazy meta cloud formations and flying spaceships around in them. It's driving me absolutely nuts that I can't spit out an alpha from the meta clouds, it's driving me nuts that it crashes on the farm, and it's driving me nuts that xstream randomly won't load up a file that it just saved out.Cool,
I definatly have issues…create a scene (lots of time spent) then save and cant reopen…You should hear me scream, people think I’m crazy! 
I have scene with hypervoxles, pretty simple, crashes everytime during render as its starts to get into the middle of the cloud of smoke, both LW and vue just closes down…Bang! GONE! just like that.
Also found little black squares in the images of a render sequence, each frame taking 15 minutes or so…very random and unusable…AH, what do you do?..But for the most part seems pretty stable. I suppose its pretty good with still images atm, but not confident with animations.
Hello,
I've been using xstream for only a few weeks with max for creating an airport. we where orginally going to do every thing in v-ray but the time it was taking to produce each frame was unrealistic for our needs. So instead we switched to xstream to produce the sky, lighting, and trees around the airport. for the main plot of land we exported a proxy model from 3d max into xstream and then had a 7000x3000 map working on the plane. this proved to be the only way we could get a good idea of where assests lay in relation to each other as near 3d max objects where showing up in the xstream vue window or the vue objects where showing in the max view port until we rendered the scene in metal ray.
I wanted to ask if people have had problems with the plug in now rendering when in max. we have had a lot of instances where rendering from a camera created in 3d max, metal ray would just render a black screen, which has meant we need to baby sit any renders that go to the server incase they render a few hundred black screens.
The other was if it was normal for the xstream objects not to be appearing in the 3d max view port?
thanks guys.
hello again,
after scatching my head for a bit i figured that in order to see the objects that are inside the xstream window u need to have 3d max in opengl mode. so in order for every thing to be seen inside xstream max you need to export the object to xstream, hide it in max. and then it should appear under the xstream node in your 3d max view port. hope this is helpful to some one
I’m so happy reading this. I was on the point of buying it, being totally in love with the promised features, got a little error on the PLE (in fact, I got errors immediatly after opening max), searched around what to do, then I found this thread.
going to search on a little further.
thanx guys.
Hello all,
First Vue is great softwares 
I never regrets my buys !
Well about 3ds max and xStream that’s right Vue <> Max synchro is clunky…but first be sure you are in opengl into 3dsmax and try to adjust xStream plugin OGL compatibility with 3ds max. I readed in manual that’s 3ds max ogl have compatibility issues, so maybe it’s not e-on but Autodesk questions of ? don’t you think ? 3ds max 9 have a lot of display issues…
3dsmax -> utilities menu -> Vue xStream -> Options : Check Use Vue’s OGL ans try to play with still Vs Playback quality sliders.
If 3ds max vue synchro failed maybe try to use Vue Exporter when you 3ds max project is done, load it into Vue and render it with Vue
You can speed up 3ds max vue syncrho rendering with select mentalray AA to 1/4 - 1.
As I tested all 3D softwares with xStream and the best to use with Vue actually is C4D, great feedback with synchro plugin.
Lightwave handle also Vue scene as well, just few camera placing troubles. Very important with LW and Vue rendering : you must use Perspective Camera !!
Normal camera render time is about 7m40s and with Perpsective about 1m48s !
For Maya that’s work fine as I tested now.
Not tested Xsi for now 
not time to…
Be sure you always go to e-onsoftware.com -> my account and check for updates ! I know e-on’s guys release update often !
I hope my 2 cents tips and help can be usefull for somes…
I’m using Cinema 4D 9.1 and VUE 6 PLE Xtreme. The VUE 6 Xtreme plugin isn’t working. My C4D crashes every time I load it up. But then I pull that VUE folder out of my C4D plugin folder and lo and behold, C4D is working. Something very glitchy about that. Also my VUE PLE crashes if I try to render an animation.
Well, the answer is easy in your case, allfiredeup: Vue 6 xStream is for cinema4D 9.5 and up.
Well, what do you know. I figured it was for 9.0 and up, since in the Install it asks where my Cinema 4D 9.0 directory is. Oh well.
I do have C4D 10 Studio on the Mac at work, but it looks like they don’t have Xtreme for Mac just yet.
Yeah, no mac at the moment, but they might work on it soon, now that the XSI plugin is out.
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.