It looks like the 2.54 exporter doesn't work with blender 2.55. Any idea whether it's a simple tweak to get this working or will it be a rewrite?
Cheers
exporter for 2.55?
-
enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
I'm doing some tests with the last 2.55 beta, seems to work but would like to make some additional tests and change some behaviours in the material conversion before release a new script, with few changes by the way.
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
Yes ,I have try the script for 2.54 on 2.55,it works fine.
But I have some question for enricocerica:
1.you have put .obj export code in this script,why don't you use import moudle? is it because you need to make some change to the export code?
2.the alpha value in .mtl file(d) is not import in octane,is that a missing function of octane?
And I notice that there are many useless message output (class ...)in console windows,maybe you can fix it in next release.
Keep on good works!
But I have some question for enricocerica:
1.you have put .obj export code in this script,why don't you use import moudle? is it because you need to make some change to the export code?
2.the alpha value in .mtl file(d) is not import in octane,is that a missing function of octane?
And I notice that there are many useless message output (class ...)in console windows,maybe you can fix it in next release.
Keep on good works!
Seven 64bit | GTX 260 896mb | Phenom II X4 965 3.4GHz | 4GB DDR3
I am still having trouble as well. I have put the script in the scripts/io directory but it is not appearing as a render option. My small lux render script is in the same place and that has appeared as a render option. Is there something in the script itself that I need to change, is it version specific? Sorry, I know zero about python scripting.
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
I think I have the same problem as ycarry above. My log reports the same errors anyway. Anyone got a workaround??
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
try opening the script in wordpad and find the text in my pic.
remove some letters from the word 'sample' to make the whole name less than 31 characters.
just leaving the 's' ought to work.
havent tried running this but saw the issue here when passing
HTH
remove some letters from the word 'sample' to make the whole name less than 31 characters.
just leaving the 's' ought to work.
havent tried running this but saw the issue here when passing
HTH
- Attachments
-
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
As I suspected, you can't go changing variable names, willy nilly, the script complains like crazy now.
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
ah ok, I fixed the problem, the variable was used later in the script. I changed it there as well and i think we are in business.
Cheers
Cheers
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)