.obj import failed in 2.01

Generic forum to discuss Octane Render, post ideas and suggest improvements.
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Post Reply
Vue2Octane
Licensed Customer
Posts: 88
Joined: Thu Jun 26, 2014 8:16 am

I purchased Octane 2.01 for Win8 64bit 10 min ago.

I tested the demo version Octane 2.0 before purchasing the full 2.01 version and .obj import in 2.0 demo version worked well.

Right after installing/activating (all zero propblems) 2.01 I wanted to import the exact same .obj that I successfully imported in 2.0 demo version before and my graphics card gives an error. (the font turns red and '(failed)' is written next to the graphics card name just above the node graph)
Import in 2.0 demo version still works.

This happened all within 10min - tested demo on more time, decided to purchase, installed/activated, tested 2.01-> Failed message.
Nothing else changed. I just wanted to import the same .obj right after purchasing the full version 2.01.

Has anyone advice?

Config:
Nvidia Gforce GTX760M
Win8 64 bit
Intel(R) Core(TM) i5-4200M 2.5GHz
Vue2Octane
Licensed Customer
Posts: 88
Joined: Thu Jun 26, 2014 8:16 am

Update:
just re-installed Nvidia drivers - did not work
uninstalled demo version and re-installed v2.01 again to have v2.01 as the only version on my cpu - did not work
installed demo again and repeated .obj import ->>> works fine in demo version v2.0, does not work in licensed v2.01 and gives my 'fail' next to graphics card name

.obj is mesh, colour bmp, alpha bmp, bump bmp. Exported from VUE Software


A bit disappointed really. You test the demo, all ok. Then you pay 300Euros for the stand alone version and instantly run into trouble...

Is there some technical support available for OctaneRender?
Vue2Octane
Licensed Customer
Posts: 88
Joined: Thu Jun 26, 2014 8:16 am

I just downloaded licensed v1.55 and the obj import works fine there as well.

I really seems to be an issue with v2.01
Vue2Octane
Licensed Customer
Posts: 88
Joined: Thu Jun 26, 2014 8:16 am

Sorry for talking to myself so much.
Appearently in v2.01 the opacity map makes trouble for obj imports.

For an obj that works fine in v1.55 and v2.0, I have to tick 'invert' in opacity to get it running. If I do not do it, then the object disappears completely or I get the 'failed' as mentioned above.

Does anyone else have trouble with .obj import and v2.01?


edit: had to switch to RGB image for opacity. Default after import is greyscale, which worked for v1.55 and v2.0, but not for v2.1 apparently. With RGB image it works fine and applies my opacity map correctly.
abreukers
OctaneRender Team
Posts: 500
Joined: Thu Aug 18, 2011 12:28 am

hi Vue2Octane,
thanks for posting. This may be a bug... or not.
It would be best to post this on the related forum for the respective release, it's found under Board index ‹ Octane Licensed Customer Forums ‹ Commercial Product News & Releases (Download here), topic: OctaneRender™ Standalone 2.01 - updated

and perhaps attach the scene along with your post so the case can be checked more thoroughly by our devs. Nonetheless, a newer update has been released since.

v2.02 can be found here: http://render.otoy.com/forum/viewtopic.php?f=24&t=40909 please try it out. cheers...
i72630QM @ 2.00GHz | 6GB RAM | 2GB GeForce GT 540M | Win7 64bit
Vue2Octane
Licensed Customer
Posts: 88
Joined: Thu Jun 26, 2014 8:16 am

Thanks for the reply.

The opacity map issue is due to the default grey color image when you import. Changing manually to RGB image and reloading the opacity map helps.

They have it on the list for the next few updates.
Post Reply

Return to “General Discussion”