OTOY Forums

Hi There; I had a go at making a generic mass a proxy object, and selecting an xfrog OBJ file:

The only peculiarity; the proxy tree loaded with a black outline around the leaves (as if the opacity map for the leaf didn't load)
Also tried the same OBJ in MAX and has the same issue (in standard perspective viewport, not Octane). Anyone know what I can do to fix it?

Also had some issues with level - the object was at project elevation 0 - shared level (AHD 30000 iirc), and the object loaded under the toposurface?

I didn't have time to play around with it - family life called. but thought I'd ask here before I waste time if there's a simple fix from you guys?

Andrew

Hi Andrew

I had this error too when originally testing the XFrog trees. For some reason Xfrog use some non-standard codes in the MTL files, in particular for the opacity map - so Octane does not pick up the transmap. You can either fix up the MTL file, or edit the leaf material in the plugin to manually connect the transmap to the opacity pin.

As per the plugin manual - the Xfrog props are scaled all over the place, so you need to manually set the scale - and they are also in a different axis system, so check the manual - it gives the rotations needed to get them upright again.

Paul

Thanks Paul,

I worked out the scale, and had remembered the x:90, y:180 orientation changes.

I'd prefer to fix the mtl file: might be able to write a Linux script to make the change if its something simple? - I have a lot of them to fix; but I'd prefer them to all be correct- its disruptive to workflow

Thanks for the lead on a fix.

Andrew

The fix is - add the following line to the MTL file.
In general, for Xfrog, the my_alpha_texture filename will be the diffuse map name followed by a "_a".

Paul