Announcement

Collapse
No announcement yet.

my scene can be rendered in lastest version 1.48.88, finally

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

  • my scene can be rendered in lastest version 1.48.88, finally

    my scene which can not be rendered after version 1.05, finally can be rendered till version 1.48.88.
    so exciting, congratulations to the developing team. ;D
    I will shift to new version now.

  • #2
    Re: my scene can be rendered in lastest version 1.48.88, finally

    hooray!
    Best regards,
    Devin Kendig
    Developer

    Chaos Group

    Comment


    • #3
      Re: my scene can be rendered in lastest version 1.48.88, finally

      it will be great if the material list can be sorted by Alphabet, alway difficult to find my material when the list is very long.

      when trying to change the name of a material, sku became very slow, a full processor calculate a long time. dont know if it bug related.

      Comment


      • #4
        Re: my scene can be rendered in lastest version 1.48.88, finally

        Originally posted by jason.dong
        it will be great if the material list can be sorted by Alphabet, alway difficult to find my material when the list is very long.
        I intercede for this too

        Comment


        • #5
          Re: my scene can be rendered in lastest version 1.48.88, finally

          renaming materials is a lot harder than it sounds. It's a 5 or 6 step process which involves iterating over all materials in the scene... It's not pretty. Of course this wouldn't be a problem if SketchUp had a way to do simple things like rename a SketchUp material. Unfortunately they never thought that'd be a necessary thing to do I guess, so we have to do a big work around to get the rename to work.
          Best regards,
          Devin Kendig
          Developer

          Chaos Group

          Comment


          • #6
            Re: my scene can be rendered in lastest version 1.48.88, finally

            for help with sorting, it may be easier to select the material in the SU material editor, and then go to the V-Ray material editor, the material should be selected in the material list there too.
            Best regards,
            Devin Kendig
            Developer

            Chaos Group

            Comment


            • #7
              Re: my scene can be rendered in lastest version 1.48.88, finally

              You can type the first letter of the material and V-Ray will jump to it, If you press the same letter or character V-Ray find the next one.


              \Best

              Comment


              • #8
                Re: my scene can be rendered in lastest version 1.48.88, finally

                Originally posted by dkendig
                for help with sorting, it may be easier to select the material in the SU material editor, and then go to the V-Ray material editor, the material should be selected in the material list there too.
                Yes its possible too i know, but my normally way of work with mat is in VrayME (habit of other soft)

                Still thx you ...

                So I am going test last ver

                Good job

                Comment


                • #9
                  Re: my scene can be rendered in lastest version 1.48.88, finally


                  bag thing happen again, a new scene size 44M can not be rendered

                  =========System Information=========
                  platform = win32
                  country = UnitedStates
                  language = English
                  ====================================
                  About to make our qapp
                  after make qapp
                  Made it after UIManager.initialize
                  C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\Lib\site-packages\Ft\Xml\InputSource.py:346: DeprecationWarning: functions overriding warnings.showwarning() must support the 'line' argument
                  FtWarning, 2)
                  FtWarning: Creation of InputSource without a URI
                  in getBRDFList, current asset we were passed cannot be found, searched for url: /glas_stair/Diffuse
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\assets.py", line 624, in load_asset_from_xml
                  return self.__loadAssetsFromList( asset_list_creator.loadedAssets, shouldNotify )
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\assets.py", line 600, in __loadAssetsFromList
                  MaterialEditorWorker.MaterialEditorWorker.getInsta nce().ui.asset_tree.populate( [newAsset.getName()] )
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\assettreewidget .py", line 201, in populate
                  self.populate(assNameList=subItemList, parentItem=newAssItem)
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\assettreewidget .py", line 198, in populate
                  subItemList = AssetsTable.getBRDFList(self.buildURL(newAssItem))
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\assets.py", line 713, in getBRDFList
                  if ((asset.type == "material") and (asset.plugin.has_parameter("brdfs"))):
                  AttributeError: 'NoneType' object has no attribute 'type'

                  Entering renderArchive
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  19.219000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  2.860000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  3.469000 seconds is how long it took to add the plugins to our renderer
                  91.313000 seconds is how long it took to render
                  Entering renderArchive
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  20.500000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  0.813000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  3.406000 seconds is how long it took to add the plugins to our renderer
                  109.423000 seconds is how long it took to render
                  Entering renderArchive
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  20.297000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  0.829000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  3.390000 seconds is how long it took to add the plugins to our renderer
                  364.896000 seconds is how long it took to render
                  None

                  About to start readArchive - C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\Lib\site-packages/TexturePreviewScene.xml
                  0.109000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\Lib\site-packages/TexturePreviewScene.xml
                  0.000000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  0.000000 seconds is how long it took to add the plugins to our renderer
                  0.000000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  0.000000 seconds is how long it took to add the plugins to our renderer
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\Lib\site-packages/MaterialPreviewScene.xml
                  0.171000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\Lib\site-packages/MaterialPreviewScene.xml
                  0.015000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  0.000000 seconds is how long it took to add the plugins to our renderer
                  0.000000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  0.016000 seconds is how long it took to add the plugins to our renderer
                  0.000000 seconds is how long it took us to correct the file paths for all external texture file references in the scene.
                  (to ensure this process goes as quickly as possible, please be sure all references to external texture files are correct prior to rendering)
                  0.016000 seconds is how long it took to add the plugins to our renderer
                  Entering renderArchive
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\archiveRead.py" , line 97, in parse
                  buffer = mmap.mmap(file_ptr.fileno(), 0, access=mmap.ACCESS_READ)
                  WindowsError: [Error 8] Not enough storage is available to process this command

                  0.000000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 407, in renderArchive
                  self.initFromArchive( filename )
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Entering renderArchive
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\archiveRead.py" , line 97, in parse
                  buffer = mmap.mmap(file_ptr.fileno(), 0, access=mmap.ACCESS_READ)
                  WindowsError: [Error 8] Not enough storage is available to process this command

                  0.000000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 407, in renderArchive
                  self.initFromArchive( filename )
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Entering renderArchive
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\archiveRead.py" , line 97, in parse
                  buffer = mmap.mmap(file_ptr.fileno(), 0, access=mmap.ACCESS_READ)
                  WindowsError: [Error 8] Not enough storage is available to process this command

                  0.015000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 407, in renderArchive
                  self.initFromArchive( filename )
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Entering renderArchive
                  About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\archiveRead.py" , line 97, in parse
                  buffer = mmap.mmap(file_ptr.fileno(), 0, access=mmap.ACCESS_READ)
                  WindowsError: [Error 8] Not enough storage is available to process this command

                  0.000000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Traceback (most recent call last):
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 407, in renderArchive
                  self.initFromArchive( filename )
                  File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 286, in initFromArchive
                  raise Exception("[VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!")
                  Exception: [VRayArchiveRenderer.renderArchive] -- No assets were loaded--nothing being done!

                  Comment


                  • #10
                    Re: my scene can be rendered in lastest version 1.48.88, finally

                    WindowsError: [Error 8] Not enough storage is available to process this command

                    what does that mean?

                    Comment


                    • #11
                      Re: my scene can be rendered in lastest version 1.48.88, finally

                      I got the same Windows memory storage error with my large file...

                      Comment


                      • #12
                        Re: my scene can be rendered in lastest version 1.48.88, finally

                        I reopened that and it rendered, i orbit the view a bit, then it wont work anymore, the issue still not fixed, but it's not "memory error", it's "not enough storage", any how, still can't depend on it for real project so far

                        Comment

                        Working...
                        X