Announcement

Collapse
No announcement yet.

***Various Issues***

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ***Various Issues***

    Hi,

    I have been using Vray for Revit for a over a week now. I have completed a few renderings already for a specific project and would like to add more. After inserting new scenes in Revit, applying all materials (or leaving them mapped per category), adjusting camera and lights, etc. I have found that my rendering process is entirely different from before without having changed any settings.

    First off, under the rendering dialog, vray is rendering objects way outside of the scene and the far clip offset (box is active as well). I tried also to turn off in my Visibility and Graphics everything that was not needed for the scene but those items are still being rendered according to the dialog. Which brings me to my second point...

    Secondly, Vray has started crashing revit often, even on draft renders at 75 dpi with simple scenes... I don't get any error messages either. Just force-closing. When it DOES render, it goes extremely slow. Using the settings aforementioned, it will take 15 minutes for a draft.... Back when my vray was working correctly, the same scenes could be rendered in about 30 seconds on draft quality. Nothing about my hardware has changed. Note: vray was working very efficiently beforehand with my computer specs so I know that isn't the issue.

    Lastly, most of the scene materials that are mapped through vray are pathed correctly and correspond correctly to the materials in revit, do not show at all in the renderings.

    Again, all of these items started happening a few days ago and I do not know what is the problem. I cannot find any topics related to these on the internet either. Someone please help!!


  • #2
    Thank you for your feedback!
    Next time when Revit force closes, send us the Revit journal so that we can check if there is any info regarding this problem. Navigate to C:\Users\Ana\AppData\Local\Autodesk\Revit\Autodesk Revit 20**\Journals, order the journal files by date and send us the most recent one.

    Best,
    Ana
    Ana Lyubenova
    Product Manager

    www.chaos.com

    Comment


    • #3
      Another questions: what Aspect Ratio do you use for the resolution? Is it set to Crop Region or to any other value?
      What is the type of the 3D view that you are rendering (perspective or orthographic)?
      Ana Lyubenova
      Product Manager

      www.chaos.com

      Comment


      • #4
        Hi Ana,

        Thanks for your response. I discovered something interesting... If I switch my render engine from my GPU (also checked C++/CPU) to just using the CPU it seems to do fine without crashing and is very quick at rendering. Though, I never used this setting before when it worked properly.

        I could locate a previous journal file, but with so many of them I'm not sure which would indicate a crash.

        I am using 16:9 Widescreen at 1920x1080 resolution. Draft renders are set to 75 DPI as well. I am using a camera view within revit so it is in perspective mode

        Comment


        • #5
          What is your machine configuration?
          Ana Lyubenova
          Product Manager

          www.chaos.com

          Comment


          • #6
            See attached screenshot
            Attached Files

            Comment


            • #7
              Ok, let's check the Revit journal as well.
              You need to reproduce the crash once again and then go to Journals and find the most recent one. Usually, after it crashes, there is also a .dmp file with the same name as the journal.
              Ana Lyubenova
              Product Manager

              www.chaos.com

              Comment


              • #8
                Update since yesterday: using just the CPU was working fine until I switched from an exterior camera view to an interior camera view. At that point the CPU-based rendering started going very slowly... Now after switching back to the GPU/CPU engine, it isn't crashing even on very high quality/ 300DPI/ 16:9 aspect ration at 1920x1080. It is decently slow, but I figure that is expected from those settings.

                I attached the most recent journal from when the CPU was the engine, running slowly.
                Attached Files

                Comment


                • #9
                  I got your ticket in our support system and I responded there.

                  Best,
                  Ana
                  Ana Lyubenova
                  Product Manager

                  www.chaos.com

                  Comment

                  Working...
                  X