Understanding VfS Error Log

[omegaslasher]

Re: Understanding VfS Error Log

Sorry for the slow response time. I'm trying to wrap up my current project before I start exploring the beta. What's slowing me down is that I have to go back after modeling content and strip the scene down to the bare minimum materials and geometry in order to render a particular view. So it's it's been slow going trying to avoid vray freezing up. ThomThom, at this point the only way I can get a rendering larger than 1000px in either dimension is to render to file, and even then it tends to lock up. Anyone interested in looking over my rendering settings? I can take a bunch of screen shots sometime soon.

If there is something that I am doing wrong in how I model or use materials, is there a way that I can send a model and the associated files to you guys to take a look at? It would be great to find out if it's just my ignorance causing the problems, and if corrected, I can start to get some flashy highres images produced.

I should be wrapping up my work this week and begin playing around/trying to crash the new beta ASAP. Looking forward to it, thanks again.

[SAF]

Re: Understanding VfS Error Log

Hi Thomas..
Same problem presists- cant get the VFS window..
any update yet...?

[dkendig]

Re: Understanding VfS Error Log

SAF- If you are having difficulty getting a scene to render (even at small resolutions), and you don't believe that the issue is caused by running out of memory, if you post a copy of your V-Ray for SketchUp error log, we could see if there was something you could change in your scene to get it to render. I'm not sure what you mean by "cant get the VFS window" though, I'm assuming you mean that you can't get a scene to render though, since you said it was the same problem as what was mentioned earlier in this thread. This thread is supposed to be all about trying to understand what's in the error log, so just post the contents of your error log, and let's see if we can fix your problem

[SAF]

Re: Understanding VfS Error Log

noted.. will post the error log as soon as there is anything...

problem fixed for the time being, before i read your post above..
problem: VFB window was not getting activated, after pressing the Render button- and there was no rendering.
fixed it by removing some 3dmodels and purging the scene thru - model info-statistics-purge
(http://forum.asgvis.com/index.php?to...;topicseen#new)
thanks again..

[dkendig]

Re: Understanding VfS Error Log

Oh good, glad to hear you're up and running again!

[demon2005]

Re: Understanding VfS Error Log

Hi guys,

me and my colleague both use vray for sk and both have identical computers, recently mine stopped rendering and
has continues to work, settings are the same. so here my error log, any suggestions please would be fantastic!

kind regards




=========System Information=========
platform = win32
country = UnitedKingdom
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.326000 seconds is how long it took to read in our
scene file
0.056000 seconds is how long it took to add the plugins to our renderer
1.752000 seconds i
s how long it took to render
got to app_quit
Just called cancel render of VRayArchiveRenderer

[dkendig]

Re: Understanding VfS Error Log

Nope, not a single error in that log. Would you mind starting a new thread about your issue so we can troubleshoot it? Or contact support@asgvis.com with details about your problems.

[Arq.chaconb]

Re: Understanding VfS Error Log

hello this information about errors that occurs in VFS surprised me because I did not know of the existence of the same but I would like to know usd meant to suggest you have the option of providing file, which preserves more memory, and I find this option on my computer?

thank...

[Arq.chaconb]

Re: Understanding VfS Error Log

hello this information about errors that occurs in VFS surprised me because I did not know of the existence of the same but I would like to know usd meant to suggest you have the option of providing file, which preserves more memory, and I find this option on my computer?

[Vray Bob]

Re: Understanding VfS Error Log

Hey all, Im getting this error, what can I do??? Thanks for the help Entering renderArchive
About to start readArchive - C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
8.244000 seconds is how long it took to read C:\Documents and Settings\All Users\Application Data/ASGVIS/VfS/current_skp.xml
0.141000 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)
Traceback (most recent call last):
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayplugin.py", line 215, in add_to_renderer
vray_param = param.to_vray_param(renderer)
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayplugin.py", line 92, in to_vray_param
return self.value.to_vray_param(self.name, renderer, final_gamma )
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vraytypes.py", line 348, in to_vray_param
return PyVRay.VUtils.DefStringParam(name, self.to_vray(renderer))
TypeError: argument 2 of PyVRay.DefStringParam() has an invalid type

Traceback (most recent call last):
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 328, in render
self.addAssetsToRenderer( self )
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 102, in addAssetsToRenderer
ref.plugin.add_to_renderer( self )
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayplugin.py", line 215, in add_to_renderer
vray_param = param.to_vray_param(renderer)
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayplugin.py", line 92, in to_vray_param
return self.value.to_vray_param(self.name, renderer, final_gamma )
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vraytypes.py", line 348, in to_vray_param
return PyVRay.VUtils.DefStringParam(name, self.to_vray(renderer))
TypeError: argument 2 of PyVRay.DefStringParam() has an invalid type

Traceback (most recent call last):
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 408, in renderArchive
self.render()
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 328, in render
self.addAssetsToRenderer( self )
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayrender.py", line 102, in addAssetsToRenderer
ref.plugin.add_to_renderer( self )
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayplugin.py", line 215, in add_to_renderer
vray_param = param.to_vray_param(renderer)
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vrayplugin.py", line 92, in to_vray_param
return self.value.to_vray_param(self.name, renderer, final_gamma )
File "C:\Documents and Settings\All Users\Application Data\ASGVIS\Python26\..\VfS\ASGVIS\vraytypes.py", line 348, in to_vray_param
return PyVRay.VUtils.DefStringParam(name, self.to_vray(renderer))
TypeError: argument 2 of PyVRay.DefStringParam() has an invalid type

got to app_quit
Just called cancel render of VRayArchiveRenderer
Just called cancel render of VRayPreviewRenderer

[dkendig]

Re: Understanding VfS Error Log

That error was happening quite a bit in our older versions, but I haven't seen it since 1.49.01 was released. Have you updated to 1.49.01? Basically the error is saying that the value of one of the parameters somewhere in either your materials, lights, or render options, has sent the wrong type of data (Like letters rather than numbers, or a texture instead of a number). It may be related to unrecognized or invalid characters, or it may just be something random. Either way, I do believe this issue was fixed in the latest update.

[Vray Bob]

Re: Understanding VfS Error Log

Dkendig youre fast as a bullet man lol thanks for the help... well i havent updated my software yet (dont have much time) but this error has happened like 3 or 4 times to me... Ill try and update and ill let you know... thanks so much... if theres anything strange in my typing im sorry (i speak spanish), thanks again man

[mabc246]

Re: Understanding VfS Error Log

Hi, this is an error log that appears every time I render one especific model, what does it means? thanks

=========System Information=========
platform = win32
country = Paraguay
language = Spanish
====================================
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
About to start readArchive - C:\ProgramData\ASGVIS\Python26\Lib\site-packages/MaterialPreviewScene.xml
0.440000 seconds is how long it took to read C:\ProgramData\ASGVIS\Python26\Lib\site-packages/MaterialPreviewScene.xml
0.021000 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.038000 seconds is how long it took to add the plugins to our renderer
findExisting could not find any assets in our asset table with url: /DefaultMaterial
error in getCurrentAssetVals, invalid curAsset
0.002000 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.023000 seconds is how long it took to add the plugins to our renderer
0.001000 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.024000 seconds is how long it took to add the plugins to our renderer
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.927000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.473000 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.104000 seconds is how long it took to add the plugins to our renderer
109.161000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.938000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.154000 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.105000 seconds is how long it took to add the plugins to our renderer
139.331000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.940000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.114000 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.106000 seconds is how long it took to add the plugins to our renderer
109.631000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.988000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.158000 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.109000 seconds is how long it took to add the plugins to our renderer
84.399000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.991000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.158000 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.112000 seconds is how long it took to add the plugins to our renderer
2.889000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
1.211000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.143000 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.111000 seconds is how long it took to add the plugins to our renderer
16.078000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.975000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.121000 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.124000 seconds is how long it took to add the plugins to our renderer
3.968000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.984000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.116000 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.109000 seconds is how long it took to add the plugins to our renderer
161.594000 seconds is how long it took to render
Entering renderArchive
About to start readArchive - C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.997000 seconds is how long it took to read C:\ProgramData/ASGVIS/VfS/current_skp.xml
0.116000 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.110000 seconds is how long it took to add the plugins to our renderer
57.186000 seconds is how long it took to render
got to app_quit
Just called cancel render of VRayArchiveRenderer
Just called cancel render of VRayPreviewRenderer

[dkendig]

Re: Understanding VfS Error Log

findExisting could not find any assets in our asset table with url: /DefaultMaterial

That's the only actual error in the error log. The rest is just information, and/or warnings that you don't need to worry about. This error means that a material called "DefaultMaterial" could not be found when you rendered. What version of VfS are you using?

[mabc246]

Re: Understanding VfS Error Log

It is V-Ray for SketchUp v1.48.89...thanks for the help man, should I update it, or there's something I can do about this error in the courrent version?