I downloaded the latest MS CE16 and tried to render some of my projects. Unfortunately, VUE still produces very, very poor results. Here is a couple of screenshots:
Demo no.1 - a view was rendered with Maxwell renderer (I have a token for Maxwell renderer for CE16). Rendering was slower than with VUE but materials look good and RPC cells render fine, too.
Demo no. 2 - The same view was rendered with VUE & path renderer. All materials look strange and RPC cells are gone...
Demo no. 3 - the same view was rendered with VUE & ray tracing. The image looks just as bad as demo number 2
I am seriously worried because my Maxwell token will stop working after 31.12.2021. That means, there is less than two months left and VUE is still pretty much useless for production...
I tested configuration variable 'MS_VUEFURPROXY=1' briefly. It doesn't work as desired. Here is a comparison between Luxology rendering engine and VUE in CE16. I use fur for grass materials but also for creating shrub plantings. The material which I have attached to the shape element on the left hand side uses an image of an shrub to create shrub shaped billboards for fur stems. It works like a dream in Luxology, even in a large scale model. The first image was rendered with Luxology and the second one which looks pretty awful was rendered with VUE using variable MS_VUEFURPROXY=1.
I am sorry if I sound upset but I am seriously upset regarding the recent 'development' of the rendering engine.
Yrjo Ala-Heikkila said:I am sorry if I sound upset but I am seriously upset regarding the recent 'development' of the renderin engine.
I think you are not alone.
After years, when Luxology / modo was used, existing knowledge base (discussions, materials created by Jerry etc.) allows to find a solution or at least the right direction.
Now, everything is different, moreover it often does not work. I would expect quick intros / tutorials for all typical situations, where VUE is different, like "When RPC cells are used", "When XFrog cells are used", "When grass or fur material need to be used" (which is always), "When new tree, plant ... need to be defined" etc., because they are tasks common to the most of visualizations.
For me, as "visualization amateur" (and need it only few times per year), it's easier to use anything else but not VUE in MicroStation, because I will quickly find explanations and tutorials how to do any task in software like Blender, for example. Information and videos about how great is Nvidia denoiser in VUE are completely useless in this situation.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
With regards to Vue Ecosystems, they would need to be defined in Vue and saved as a .mat file from Vue, which can then be brought into Microstation. Yes this would mean purchasing a license of Vue, if this is a feature you wanted.
With regards to fur, the support which I added is only a partial solution and will not be a full replacement of fur, as the ability to use Vue Ecosystems is a much more powerful workflow.
With regards to availability of educational content etc. Yes, we need to work on this further, I recall that Jerry did a number of Visualization SIG's over the last year or so where he demonstrated a workflow with both Vue and MicroStation on using Vue Ecosystems. These should be available to watch from learn.
Basically I would like to get back all features which you have removed from MS CE16's rendering cababilities, prefrerably without pushing them to a costly 3rd party application.
BTW - what is a SIG? and where should I find it? If VUE ecosystems are so powerful then why wouldn't you document the workflow properly so that end-users could benefit it? And provide a good selection of samples so people would get an idea what they are capable of?
it's a Special Interest Group about visualization, you can find that video's here: