Vue Rendering errors

When testing the Vue Rendering I get some errors. 

- Changes in reference files are visible in MicroStation, but is not rendered. If I move an object for instance, It keeps the first position when rendered, and not the new one I see in MS. It is not enough to re-open the file, I  need to close MS and load the file again to make Vue render the change. Why is this happening?

- Sometimes when I do changes in a reference file and reload it, the Vue Rendering dialog and then MS crashes. This can also happen if I just adjust the time of day. With Luxology I almost never experienced crashes even with large assemblies of 5-6 GB DGN files, with Vue I experience crashes too often.

- Material on imported files (*.FBX, *.OBJ etc.) into a *.DGN file which then is referenced is visible when first loaded and rendered. When re-visiting the file, the material is still visible in MS, but Vue Rendering does not render the material anymore. What has happened?

- Some materials in DGN files renders fine with Luxology, but is not visible with Path Tracing in Vue. I use the same material file settings for other material that renders fine, the only difference is the link to a different Pattern  Map. 

I still have to use Luxology for some projects and  use MS Connect Edition Update 15. Maybe these issues have been solved in Update 16?

Parents
  • Hi, as Paul mentioned please send us your files and workflow and we will try to fix any issue we discover. You can also open a Service Request and attach all info and data to it if that suit you best.

    Thanks

  • Hi, sorry for my late reply. I have now had some time to investigate the errors that occurred further. One reason why Vue Render crashed was probably due to very low disc space. "Suddenly" my disk space was reduced by over 200GB after making a series of 4K mages with Relightning turned on. I have now learned that these  files can require a lot of disc space.

    The critical and strange errors I see now is when moving reference files around to a new position. The update is visible in MicroStation but not in Vue Rendering I think this can be caused by Parametric Solids? I have a dining table which is modelled in MS 10-12 years ago using Feature Modelling. This file was later updated with chairs using Parametric Modelling. When I move this file in my assembly, the Chairs are not rendered in the new position, while the Table is. This "ghost" rendering/path tracing  is very strange; what you see in MS is not what you get in Vue. I have imported a Sketchup file of a sofa into a DGN file. The embedded material is then lost in Vue, so it is probably better to reference to the SKP file instead. This model is using Mesh Surfaces, and it seems these have the same issues as with Parametric Solids. The Sofa is rendered in it is first position and not in the new. 

    I can have4-500 reference files in my assemblies. These are arranged in groups that are moved around to make new configurations. I then get some strange errors when some parts are moved and others are not in Vue. I have to use Luxology still to avoid this and other issues in Vue. I am then still using MS Update 15 (10.15.02.11). Below is a simpler assembly showing the errors I experience:

    Sofa in rearward position, rendered as it should
    Sofa (Mesh Surfaces) rendered as it should.

    Sofa moved, not visbe in Vue

    Sofa (reference file) model moved, vhange is visible in MS, but not rendered correctly in Vue

    Dining Table and Sofa moved

    Reference files of Sofa and Dining Table is moved. Table (Feature Modelling)) is rendered in the new position, while Sofa and Chairs (Parametric, not visible here) is not.

    Chairs are in old position, while Table is moved to new

    Dining Table Chairs are still in the old position, while the Table is moved to the new in Vue. They are both in the same DGN file, strange!

    Changes visible in Vue when restarting MS

    I have reloaded the reference files, but they are still in the old position. Similar if I close and reload the Vue Rendering dialog. I have to shut down MS and restart it to make the changes becoming visible. This is not very efficient.

    What is happening? Is there an issue with Parametric Solids and Mesh Surfaces in Vue, or is this caused by other factors? Have someone else experienced this behaviour? I have made a Service Request and uploaded the actual DGN models in this assembly.

    IMAGE SIZE INFORMATION
    Another error I see in the Vue Rendering dialog is the width and height of the image in pixels. When scaling the View with View Size, the dialog is not updates as in Luxology. I have to Unlock and Lock the ratio to see the changes. 

  • Hi,

    Do you have the view attribute clip volume on ? if not can you switch it on, this will clear the cache geometry maintained between renders. See if it fixes the issues with moving reference files.

    I havent seen a problem with imported skp files not finding materials for vue but working with smooth and luxology, I will look at your testcase and see if I can reproduce this.

    There were some fixes made to updating the view pixel x & y values for U16, I will check if this fixes your issue.

    Regards

    Paul



  • HI,

    I have now rendered the files in MS Update 16.2 and experience the same errors. They appears both with Path Tracing and Ray Tracing, while Luxology renders all object in their new positions. Similar when transferred to LumenRT. I also tried the Clip Volume with no success.

Reply Children
No Data