Update 283512 is out of Beta

...and is crashing on network renders with imported Poser objects (and possibly imported objects of other types).

Support tickets have been opened, but it never hurts to get more reports.

It crashes for me even with nothing imported. My native vue scene goes down when i try to render.

Your normal renders or network renders? If you're getting crashes with a normal render, you should definately open a new ticket, because that's different from this issue.

Network rendering sorry. I was replying because no one has mentioned that non-imported renderes are crashing as well. Seems that everyone has some sort of imported poser or other object imported and its crashing, i have all vue objects (for a scene background) and it's crashing...or was...I reinstalled my vue and used the old patch and will not update until this is cleared up.

I just got Vue infinite as part of my Lightwave 9 upgrade. Should I load this patch or do you experienced folks recommend letting things be?  I am unfamiliar with E-ons upgrade practices... All I can see is that this patch went from beta to final recently and doesn't seem to be fully working... Does this mean that there will be a future patch or is 5.10 the last version to be replaced by 6

In a thread on e-on's site there was a mention of a 5.11 patch so I'm guessing this won't be the last patch for 5.

It had better not be. I would like to see some patches that fix the functionality rather than just tweak the performance.

Here is a list of the fixes in this release.  Quite a few of them are , what I would consider, fixes to functionality.

• Fixed illegal 'Replace-By' and 'Bake to polygons' actions on Metablobs objects.
• Fixed potentially zero width poser hair.
• Pixel aspect ratio is now properly stored within scene files.
• Improved Poser import when the option to group figures as single meshes was not checked.
• Fixed a crash that could occur when populating an EcoSystem material edited from the material world browser.
• Fixed size of procedural terrains baked to polygons.
• Added a new command line switch to recover HyperVue tmp files in a given directory ( -t"[path]" ).
• Improved memory management of Vue and RenderCows when sending/receiving the scene and when sending/receiving rendered images.
• Fixed a memory leak when rendering to screen.
• Fixed rendering of transparent materials on terrain (shadows).
• Fixed a multithreading issue with shadow maps.
• Negative light sources were not properly handled.
• Fixed multipass artefacts when using radiosity on objects holding mixed materials.
• Fixed a problem with the preview of mixed materials depending on the altitude on a per object basis.
• When splitting a mesh, the center of each resulting object could be incorrectly computed.
• Applying a glowing material on clouds could lead to crashes.
• Fixed inverted 2D planes preview in material editor.
• Improved wireframe preview of Shade objects.
• Fixed a problem where the mapping mode could change when editing a material with the basic editor.
• Fixed Lens Flare shape when the pixel aspect ratio is not 1, or when using field interlacing.
• Fixed greyed out "Edit Object" option when selecting more than 1 object and opening the context menu.
• Embedded synchro data is now cross-platform.
• Fixed a rounding issue for start and end frame.
• Fixed a problem saving/loading a scene containing animations from a VIM file.
• Accelerators could stop working on MacOS in certain cases.
• Some keyframes, such as for the lights, were created, even when the auto-keyframing was disabled.
• Other minor interface fixes and improvements.

Thanks Mark! This is a real help, you're posting the list of fixes here.

Yes, thanks, that's nice to know.

However, the most critical thing needed is to fix is to prevent the automatic merging of material zones and stop Vue overwriting the name of a material zone when loading material settings. This screws up the Poser import function, and is generally annoying, requiring tedious workarounds in managing materials. This causes so much trouble, and it should be trivial to fix.