Announcement

Collapse
No announcement yet.

Crash and AWE

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

  • Crash and AWE

    Joe, Corey et all

    FYI

    Using default visopt with 800x500 output on test model [15 MB]
    140043 edges-61359 faces-7410 groups/nested
    When tested in both SU 5 & 6 the render processes and when frame buffer screen appears SU crashes.
    Vray seem to choke on high poly and nested groups.
    I tested other larger files and these refused to even start to process and froze SU (both 5 & 6 )

    The test file ran without complaint in both Podium and Artlantis R export
    as did the other large files tested.

    Hmmm?

    Dave

  • #2
    Crash and AWE

    Could you make this scene available to us? Thanks.
    Best regards,
    Joe Bacigalupa
    Developer

    Chaos Group

    Comment


    • #3
      Crash file

      Joe

      How can I get the file to you.?

      FTP or equal as it is 15 MB

      Dave

      Comment


      • #4
        Crash and AWE

        ftp://ftp.asgvis.com/incoming - then either post the name of the archive here or email it to me. We'll keep the file confidential.
        Best regards,
        Joe Bacigalupa
        Developer

        Chaos Group

        Comment


        • #5
          Model sent


          Joe

          The model is in your mailbox

          Dave

          Comment


          • #6
            Crash and AWE

            email works too Thanks
            Best regards,
            Joe Bacigalupa
            Developer

            Chaos Group

            Comment


            • #7
              Crash and AWE

              I just started playing with it - I can render it in my debug build - but not in another configuration. Its throwing up some crazy MFC file exception somewhere. So I'm not totally sure whats going on yet. So it doesn't appear to be related to nested geometry - although the geometry does account for the long scene parsing time.
              Best regards,
              Joe Bacigalupa
              Developer

              Chaos Group

              Comment


              • #8
                Crash and AWE

                Joe

                As this file seems OK in other renders is
                the issue video ram or sys ram as accessed
                in Vray?

                My system has 256 MB video and 1 GB system.



                Dave

                Comment


                • #9
                  Crash and AWE

                  Its definitely a possibility. What you might try is going into the System rollout and decreasing the bucket size. This will decrease the amount of geometry that needs to be loaded for each calculation. It may solve the problem it may not. Something like 32x32 or 24x24 would work. I wouldn't suggest going smaller than that.
                  Damien Alomar<br />Generally Cool Dude

                  Comment


                  • #10
                    Crash and AWE

                    I'm not sure - I don't think its a RAM thing because it renders fine in my development build. I think its probably just a logic error on my part somewhere thats causing an issue in my non-debug build.
                    Best regards,
                    Joe Bacigalupa
                    Developer

                    Chaos Group

                    Comment


                    • #11
                      Crash and AWE

                      Joe

                      SU can build high poly and face values
                      and it is key for the render to be able
                      to handle file size and not have a
                      "September Surprise" after purchase.

                      FYI while not a really a PR sys ATL really
                      handles pretty big files and keeps right
                      on truckin.

                      Just keep those cards and letters coming.

                      Dave

                      Comment

                      Working...
                      X