Wings 3D Development Forum
[Fixed] please help me!! (POV-Ray - wrong path exported) - Printable Version

+- Wings 3D Development Forum (https://www.wings3d.com/forum)
+-- Forum: Wings 3D (https://www.wings3d.com/forum/forumdisplay.php?fid=1)
+--- Forum: Bug Reports (https://www.wings3d.com/forum/forumdisplay.php?fid=12)
+--- Thread: [Fixed] please help me!! (POV-Ray - wrong path exported) (/showthread.php?tid=1409)



[Fixed] please help me!! (POV-Ray - wrong path exported) - changho21 - 10-06-2015

I use povray to rendering...
but I can't rendering with error...
Preset INI file is 'C:\Users\HCH\Documents\POV-Ray\ini\quickres.ini', section is '[512x384, No AA]'.
Preset source file is 'D:\3D\ex\ex_export.pov'.
Rendering with 4 threads.
Parser Options
Input file: D:\3D\ex\ex_export.pov
Remove bounds........On
Split unions.........Off
Library paths:
C:\Users\HCH\Documents\POV-Ray\include
C:\Windows\Fonts
Clock value: 0.000 (Animation off)
Image Output Options
Image resolution.....512 by 384 (rows 1 to 384, columns 1 to 512).
Output file..........D:\3D\ex\ex_export.png, 24 bpp PNG
Dithering............Off
Graphic display......On (gamma: sRGB)
Mosaic preview.......Off
Continued trace......Off
Information Output Options
All Streams to console..........On
Debug Stream to console.........On
Fatal Stream to console.........On
Render Stream to console........On
Statistics Stream to console....On
Warning Stream to console.......On
Possible Parse Error: Cannot find file '../../../2012021717515117728.jpg', even after trying to append file type extension.
Possible Parse Error: Cannot find image file.
Fatal error in parser: Cannot open file.
Render failed
-
CPU time used: kernel 0.05 seconds, user 0.00 seconds, total 0.05 seconds.
Elapsed time 0.48 seconds.
----------------------------------------------------------------------------
please help me...


RE: please help me!! - micheus - 10-06-2015

changho21, which Wings3d version are you using?


RE: please help me!! - changho21 - 10-06-2015

I use 2.0.1 now


RE: please help me!! - micheus - 10-08-2015

changho21, that was already fixed but still not released.
You can download the files for replacement from this link (please, read Readme.txt file first)