Announcement

Collapse
No announcement yet.

Rendering doesn't start (new version of V-ray)

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

  • #46
    Re: Rendering doesn't start (new version of V-ray)

    I'm having same issues as original poster. Win 7 64 Bit, I just upgraded to SU 7.1 so reinstalled Vray. Some of my larger models that I have run tests on just wont render, rendering message comes up but the buffer window doesnt and it just quits out without starting the render. Used the debug tools etc. and still not got it to work.
    Guess I will have to wait for the patch, in the meantime I hope a client doesnt ask me for any amendments on older jobs!
    Keep up the good work guys, we sure keep you busy.

    Comment


    • #47
      Re: Rendering doesn't start (new version of V-ray)

      I am also having the same problems as the original poster. I am running 1.48.77 for VFSU on SU7.1, with windows 7 64 bit. I have just created the simplest of models. It entails a few basic solid objects and some google earth terrain which I have cleaned up and re-textured myself. This is my first real test of this beta version and it's not working as i expected. Render will not start, and displays error in which it reffers you to the VFSU error log. I also closed the app, reopened, and then debugged with force sync. I only 1 material in this model and it still will not render. Here is my log:

      =========System Information=========
      platform = win32
      country = UnitedStates
      language = English
      ====================================
      About to make our qapp
      after make qapp
      Made it after UIManager.initialize
      C:\ProgramData\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
      Entering renderArchive
      About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
      0.301000 seconds is how long it took to read in our scene file
      Traceback (most recent call last):
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 290, in initFromArchive
      self.addAssetsToRenderer( self )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 92, in addAssetsToRenderer
      self.__findReferencedPlugins( asset, refList )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 129, in __findReferencedPlugins
      self.__handleReferencedPlugin( param.value, referencedList )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 121, in __handleReferencedPlugin
      raise Exception(u"In __handleReferencedPlugin could not find %s"%paramUrl)
      Exception: In __handleReferencedPlugin could not find /Image1

      Traceback (most recent call last):
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 321, in renderArchive
      self.initFromArchive( filename )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 290, in initFromArchive
      self.addAssetsToRenderer( self )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 92, in addAssetsToRenderer
      self.__findReferencedPlugins( asset, refList )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 129, in __findReferencedPlugins
      self.__handleReferencedPlugin( param.value, referencedList )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 121, in __handleReferencedPlugin
      raise Exception(u"In __handleReferencedPlugin could not find %s"%paramUrl)
      Exception: In __handleReferencedPlugin could not find /Image1

      Traceback (most recent call last):
      File "C:\ProgramData\ASGVIS\VfS\PyProcMsg.py", line 46, in procPyCallback
      callback( argList )
      File "C:\ProgramData\ASGVIS\VfS\pyCallbacks.py", line 181, in start_render
      renderer.renderArchive( argList[0] )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 321, in renderArchive
      self.initFromArchive( filename )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 290, in initFromArchive
      self.addAssetsToRenderer( self )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 92, in addAssetsToRenderer
      self.__findReferencedPlugins( asset, refList )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 129, in __findReferencedPlugins
      self.__handleReferencedPlugin( param.value, referencedList )
      File "C:\ProgramData\ASGVIS\Python26\Lib\site-packages\ASGVIS\vrayrender.py", line 121, in __handleReferencedPlugin
      raise Exception(u"In __handleReferencedPlugin could not find %s"%paramUrl)
      Exception: In __handleReferencedPlugin could not find /Image1

      I notice that it says it cannot find image 1, in which case I am very confused because there is not such bitmpa being reference anywhere in my sketchup model or material editor for VFSU. Can anyone help?

      Comment


      • #48
        Re: Rendering doesn't start (new version of V-ray)

        Problem fixed.....

        Something for VFSU to explore. When I imported a jpeg image, it was automatically grouped. I noticed after I added that image as a material, copied that image, exploded it, and then draped it on a mesh surface (and after futzing with force sync and other debugging tools), i realized in my outliner that the original imported and grouped jpeg was not identified. All of a sudden it clicked, and I realized that this is most likley the unidentified "material 1" that could not be found and was cauing the rendering problem. So, I exploded the original imported jpeg image, and regrouped it, and then it showed up in outliner. Then purged materials, force synced, and then I was able to render. However no actual parsing, light chahing, etc. started, but this was an unrelated issue as I was using a visopt. that I had brought in from version 1.05.03 that I really liked. Of course I then tried the default settings and it does render now.

        Is there a problem with VFSU being able to recognize imported jpeg images in sketchup? Also, I will try the same operation with the latest WIP to see if my custom visopt. will work and let you all know. Maybe this wan'st to be started as a new bug topic?

        Comment


        • #49
          Re: Rendering doesn't start (new version of V-ray)

          I am having the same problem with vrfs 01.48.66, sketchup 7.1 win xp 64 bit. Its been a couple weeks since the last post for this issue. Has there been a fix?

          Comment


          • #50
            Re: Rendering doesn't start (new version of V-ray)

            Yes it has been fixed. You need to have one of the beta versions installed, specifically 1.48.83.

            Comment


            • #51
              Re: Rendering doesn't start (new version of V-ray)

              A render will stop when an error occurs. It's hard to say what issue you are experiencing specifically, but we have fixed a number of issues that will cause this symptom to occur in our current beta. We are planning on releasing a patch to 1.48.66 as soon as we have a version that is stable for release. This has taken a lot longer than originally planned, but we are definitely working on it.
              Best regards,
              Devin Kendig
              Developer

              Chaos Group

              Comment


              • #52
                Re: Rendering doesn't start (new version of V-ray)

                thats great, look forward to the patch
                i have been trying to figure out what's causing the stop rendering in my models but so far once i feel i've found the problem it happens again out of the blue.
                first time i figured out rectangular lights were not working, it worked once i deleted them. But then continued to happen without the rectangular lights.
                2nd time i copied all the components one at time into a new file and it worked. when i copy them all at once it doesn't work. Unfortunately this takes a lot of extra time for bigger complex models.
                does one have to be a registered beta tester in order to download the beta that has the fix?
                thanks
                L

                Comment


                • #53
                  Re: Rendering doesn't start (new version of V-ray)

                  I believe you can ask to be a part of the beta testing and it might help resolve some of your problems. As for the rendering not starting, it's hard to nail that down without checking the VFSU error log for hint's as to what might be wrong.

                  Comment


                  • #54
                    Re: Rendering doesn't start (new version of V-ray)

                    http://forum.asgvis.com/index.php?topic=7679 << The Mighty Bug Hunt

                    That's where you can sign up to be a beta tester.
                    Best regards,
                    Devin Kendig
                    Developer

                    Chaos Group

                    Comment


                    • #55
                      Re: Rendering doesn't start (new version of V-ray)

                      Hello. I also have a problem with render. I have difficulty scene, but it worked few days ago. Now if I anything change in the scene or in the render option, after push the R buttom, my render doesn´t start.

                      =========System Information=========
                      platform = win32
                      country = Slovakia
                      language = Slovak
                      ====================================
                      About to make our qapp
                      after make qapp
                      Made it after UIManager.initialize
                      C:\ProgramData\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
                      Entering renderArchive
                      About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
                      Traceback (most recent call last):
                      File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray render.py", line 285, in initFromArchive
                      readArchive(filename, self )
                      File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\arch iveRead.py", line 145, in readArchive
                      asset_parser.parse( filename, asset_read_callback)
                      File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\arch iveRead.py", line 124, in parse
                      print >> sys.stderr, traceback.format_exc()
                      File "C:\ProgramData\ASGVIS\Python26\Lib\codecs.py" , line 686, in write
                      return self.writer.write(data)
                      File "C:\ProgramData\ASGVIS\Python26\Lib\codecs.py" , line 351, in write
                      data, consumed = self.encode(object, self.errors)
                      UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 227: ordinal not in range(12

                      Traceback (most recent call last):
                      File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray render.py", line 410, in renderArchive
                      self.initFromArchive( filename )
                      File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray render.py", line 285, in initFromArchive
                      readArchive(filename, self )
                      File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\arch iveRead.py", line 145, in readArchive
                      asset_parser.parse( filename, asset_read_callback)
                      File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\arch iveRead.py", line 124, in parse
                      print >> sys.stderr, traceback.format_exc()
                      File "C:\ProgramData\ASGVIS\Python26\Lib\codecs.py" , line 686, in write
                      return self.writer.write(data)
                      File "C:\ProgramData\ASGVIS\Python26\Lib\codecs.py" , line 351, in write
                      data, consumed = self.encode(object, self.errors)
                      UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 227: ordinal not in range(12


                      this is my error message. Can you help me?
                      Thanks

                      Comment


                      • #56
                        Re: Rendering doesn't start (new version of V-ray)

                        looks like the issue is related to non English characters being used somewhere. This should be fixed in the current beta, and will be fixed in the next release. As a workaround, make sure that you avoid using any letters not found in the English alphabet.
                        Best regards,
                        Devin Kendig
                        Developer

                        Chaos Group

                        Comment


                        • #57
                          Re: Rendering doesn't start (new version of V-ray)

                          Hi,

                          My problem is generated after making fur (carpet), with Make Fur plugin. First scene is rendered normaly, but when I switch to next scene, after few seconds nothing happened. If I restart Skechup and go to second scene, it starts rendering.

                          Here is Error log:

                          =========System Information=========
                          platform = win32
                          country = SerbiaAndMontenegro
                          language = Serbian
                          ====================================
                          About to make our qapp
                          after make qapp
                          Failed to construct the class...traceback...
                          Traceback (most recent call last):
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 1613, in __new__
                          return cls(*args)
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 261, in __init__
                          self.set( value )
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 264, in set
                          self.value = helperToFloat( val )
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 13, in helperToFloat
                          res = toFloat(val.strip())
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\visu tils.py", line 253, in toFloat
                          raise ValueError( error_msg )
                          ValueError: <unprintable ValueError object>

                          Traceback (most recent call last):
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\Defa ultHandlers.py", line 116, in UpdateValue
                          newValue = VRayType( "float", unicode(value) )
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 1613, in __new__
                          return cls(*args)
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 261, in __init__
                          self.set( value )
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 264, in set
                          self.value = helperToFloat( val )
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray types.py", line 13, in helperToFloat
                          res = toFloat(val.strip())
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\visu tils.py", line 253, in toFloat
                          raise ValueError( error_msg )
                          ValueErrorMade it after UIManager.initialize
                          C:\ProgramData\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
                          Entering renderArchive
                          About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
                          6.779000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
                          0.016000 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.942000 seconds is how long it took to add the plugins to our renderer
                          303.505000 seconds is how long it took to render
                          Entering renderArchive
                          About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
                          Traceback (most recent call last):
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\arch iveRead.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.001000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
                          Traceback (most recent call last):
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray render.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:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray render.py", line 407, in renderArchive
                          self.initFromArchive( filename )
                          File "C:\ProgramData\ASGVIS\Python26\..\VfS\ASGVIS\vray render.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!

                          got to app_quit
                          Just called cancel render of VRayArchiveRenderer
                          What "WindowsError: [Error 8] Not enough storage is available to process this command" means?

                          I have 15GB of free space on C disk (50GB), 64bit win7, 4GB of RAM.

                          Update: I extended C partition to 100GB, and problem remains.

                          Thanks

                          Comment


                          • #58
                            Re: Rendering doesn't start (new version of V-ray)

                            Depending on which version of VFSU you are running, there are problems running multiple renderings in one session without a crash or render error. This could also be due to the # of poly's introduced in the scene with the Fur.....however I don't think that's the issue. What release are you using?

                            Comment


                            • #59
                              Re: Rendering doesn't start (new version of V-ray)

                              Version is 1.48.89 ?

                              Comment


                              • #60
                                Re: Rendering doesn't start (new version of V-ray)

                                Hmmm, well maybe that's not the issue either. Generally, from what I have heard, if your crunching a final render, it is good practice to save and restart SU before running another final render. Also, you can access beta versions if you request to join the beta testing group. This may also help with a few other bugs they are fixing along the way.

                                Sorry, not much help.

                                Comment

                                Working...
                                X