Soft2Octane 2.52c [Obsolete] Tweet

[face]

Maybe you need the Microsoft Visual C++ 2010 x64 Runtimes and Redistributeables as Peter?

face

[PeterCGS]

Hi Face!

Got a problem with a object I bought. Its not really high poly, but the UVs are CRAZY (extreme big and repeatable etc).. Well, the problem is when I export it to Octane. The object that it saves down is 9.9GB in size! I think it has to do with the way this object is UV mapped. Of course I cant use it in Octane for anything, and I got five more similar models, that has the same problem. First it takes forever to export them, they get huuuge and it takes forever to import them.. Would it be alright to send it over for you to test?

and DI2011.. Install Mirosoft Visual C++ 2010 x64 and 32bit, and restart, and it will work!

/Regards Peter K

[monkeyjet]

Hi face,
First, thank you for making this plugin. I've been enjoying using it.
I have one problem.
My newest client makes his blueprint in "inches", so I've been modeling using 1 XSI grid = 1 inch.
When I tried to render them, I'm getting strange rayepsilon marks.
Am I doing something wrong?
Please check my settings.
Thank you

[face]

Hi Face!

Got a problem with a object I bought. Its not really high poly, but the UVs are CRAZY (extreme big and repeatable etc).. Well, the problem is when I export it to Octane. The object that it saves down is 9.9GB in size! I think it has to do with the way this object is UV mapped. Of course I cant use it in Octane for anything, and I got five more similar models, that has the same problem. First it takes forever to export them, they get huuuge and it takes forever to import them.. Would it be alright to send it over for you to test?
/Regards Peter K

Yes, no problem. I will check it.

face

[face]

Hi face,
First, thank you for making this plugin. I've been enjoying using it.
I have one problem.
My newest client makes his blueprint in "inches", so I've been modeling using 1 XSI grid = 1 inch.
When I tried to render them, I'm getting strange rayepsilon marks.
Am I doing something wrong?
Please check my settings.
Thank you

The problem with the scaling is, you can model in which unit you need. The important thing is the overall size of the scene.
Means, you can have a scene which has a size of 100.000.000mm, then you should export it in km.

face

[DI2011]

Maybe you need the Microsoft Visual C++ 2010 x64 Runtimes and Redistributeables as Peter?

face

Hey Face, You´re Right.

It´s Working!

Thanks!

[mixepix]

Hi,

The focalDepth range under export camera only goes up to a hundred. I've read in some other thread that this was changed but not for me?

cheers

[face]

When you work in dimensions like 100m, switch from decimeter to meter in the "Project Configuration" tab.
This will change the aperture range from m to dam (10m).

face

[mixepix]

Yes, thanks that is how I usually solve it. I was just wondering if there is some reason for it not to go higher?

[face]

I think because no one has used values >100m or used an other unit size.
The problem is, when you work in such dimensions like this, Octane can produce scaling errors in the rendering.
http://refractivesoftware.com/forum/download/file.php?id=6912&mode=view
But i can make the limit higher in the next release, after my current project

face