Announcement

Collapse
No announcement yet.

Iradiance Crush problem

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

  • Iradiance Crush problem

    Hi guys.

    I have a huge problem with vray 3.20.03 on all workstations.
    It happens with and without geometry in the scene.

    This error occurs with an Intel i7 system or a dual xeon.
    It always happens when I use IradianceMap.


    Any idea why it happens?

    attached a screenshot
    Click image for larger version

Name:	Error.JPG
Views:	1
Size:	78.7 KB
ID:	882656

    Click image for larger version

Name:	Error 2.jpg
Views:	1
Size:	414.9 KB
ID:	882657

  • #2
    Do you have a scene for this that we can test? Is this 3ds Max 2016? Do you have any other plugins (ForestPro/MultiScatter etc)?

    Best regards,
    Vlado
    I only act like I know everything, Rogers.

    Comment


    • #3
      itoo soft plugs and max 2016 whitout sp1.

      the error and crush It is when I render any type of IM and buckets (no progresive) and adaptive aa.

      The scene its around 550 mb, maybe you connect via teamviewer ?

      Comment


      • #4
        This looks like a bug but we have to investigate the scene in order to confirm that.
        Please request access to our FTP server at support@chaosgroup.com and include a link to this thread so we could track it back if needed.
        Svetlozar Draganov | Senior Manager 3D Support | contact us
        Chaos & Enscape & Cylindo are now one!

        Comment


        • #5
          Oka.. thx for all

          Comment


          • #6
            It's the same error code (but not number) i've been getting doing point renders with Phoenix. Also have i7 dual xeon. Any environmental effects in your scene? Does it still happen if you turn them off?

            Comment


            • #7
              i have pretty the same error with a very very little scene, only some multiscattered plants... !! sun is off AND Gi is off !!...two times it renders, maybe the third time it crashes

              max 2016 SP1 vray 3.20.03 multiscatter 1.3.5.2 and 1.3.5.6 tested

              do you have any ideas? i uploaded the small scene to your ftp called: renderproblem_red.max


              big thanks for help


              [2015/Dec/14|09:04:51] error: UNHANDLED EXCEPTION: Rendering region (248,20-(256,216)
              Last marker is at ./src/globillummap.cpp, line 1692: GlobalIllumMap::buildLightMap() {1}
              Attached Files
              Last edited by thomes; 14-12-2015, 02:20 AM.

              Comment


              • #8
                tracked it down to object AM126_061_v1 either object or material makes problems. if i kill the normal bump it renders fine !

                maybe it helps to find the problem in vray
                Last edited by thomes; 14-12-2015, 03:39 AM.

                Comment


                • #9
                  We really need to print out warnings for the normal map...

                  Best regards,
                  Vlado
                  I only act like I know everything, Rogers.

                  Comment


                  • #10
                    thanks vlado, but what is the problem in easy deep , coulĀ“d you explain me ?
                    Last edited by thomes; 16-12-2015, 07:39 AM.

                    Comment


                    • #11
                      Hello there,

                      I'm having the same issue. I'm rendering a city district with around 7 large apartment buildings, at a scale of 20000px by 11250px. These buildings are each in their own max file, Xreffed into a main scene. Memory usage is full during rendering (24GB). I am using "auto" with the dynamic memory limit setting.

                      At lower resolutions it renders fine. Using Max 2015 sp3 with Vray 2.55.01.

                      Code:
                      [2016/Feb/22|18:49:05]       error: UNHANDLED EXCEPTION: Image prepass
                      Last marker is at ./src/globillummap.cpp, line 1748: GlobalIllumMap::buildLightMap() {5}
                      I removed a FastSSS2 material and now it renders fine...
                      Last edited by elivnA; 23-02-2016, 05:56 AM.

                      Comment


                      • #12
                        The most common reason for "Unhanded exception" error is insufficient memory. Therefore you can set the Dynamic memory to 0 and track down your memory usage. If your memory is enough to handle the whole scene, it will be best to send the scene so we could debug it and investigate further.
                        Zdravko Keremidchiev | chaos.com
                        Chaos Support Representative | contact us

                        Comment

                        Working...
                        X