OTOY Forums

Thank you, mementomori000, for your investigations.

Unfortunately, your solution doesn't work for me. I would be very happy if it work.
So actually Octane and bunch of stuff that I've bought for it are simply useless.

Not working for me too anybody found a solution yet?

HEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEELLLLP!!!!

I HAVE A HUGELY TIGHT DEADLINE AND NEED TO KNOW IF THIS PROBLEM CAN BE RESOLVED SOOON!!????

I get the same error message

this is what my Maya log says

"1/6/2013

Starting "C:\Program Files\Autodesk\Maya2012\bin\mayabatch.exe"
Info: Loaded DMM plugin
mental ray for Maya 2012
mental ray: version 3.9.1.48, Dec 7 2011, revision 162457
Hardware Renderer : vendor(NVIDIA Corporation), renderer(GeForce GTX 690/PCIe/SSE2), version(4.2.0)
fragment API(NVIDIA Cg)
vertex API(Cg vertex programs)
Cg fragment profile(fp30), vertex profile(arbvp1)
Error: }
Error: Syntax error
File read in 1 seconds.
Result: D:/Project_ZX887/Virgin_Media/3D/LightBulbs__7032.mb
Error: OctaneRender is not activated!
Warning: Renderer returned an error while rendering 'defaultRenderLayer', please verify the output image.
Scene D:/Project_ZX887/Virgin_Media/3D/LightBulbs__7032.mb completed."

HEEEEEEEEEEEEEEEEEEEEEEEELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

The only way I found to solve this problem was to change computer.

BTW, I haven't seen before those syntax error in your log. I wonder if that is due to using a GPU from the 600 family (new CUDA). If you have a machine with a 5X0 GPU , try with it.

SamQior wrote:Hardware Renderer : vendor(NVIDIA Corporation), renderer(GeForce GTX 690/PCIe/SSE2), version(4.2.0)
fragment API(NVIDIA Cg)
vertex API(Cg vertex programs)
Cg fragment profile(fp30), vertex profile(arbvp1)
Error: }
Error: Syntax error

This is not Octane error. Some of scripts loaded at startup gives this error...

SamQior wrote:File read in 1 seconds.
Result: D:/Project_ZX887/Virgin_Media/3D/LightBulbs__7032.mb
Error: OctaneRender is not activated!

This is not full log as it does not contain the reason of "not activated". To see all Octane startup messages just disable auto-loading of Octane plugin in Maya, and then start the batchrender - in this case Octane will be loaded after mayabatch.exe will open the scene file, and you will see all Octane startup messages.

JimStar wrote:
BUG FIXES SINCE LAST RELEASE:

• Fixed the bug that crashed the particles render in some cases.
• The national symbols in image textures paths work OK now.
• The min value of Aperture in Octane camera is now "0".
• A few minor fixes...

I not doubt that it's important that the national symbols work ok, but instead of all this, IS IT really difficult to fix Maya batch problem?
I have an impression that with exception of some sings of attention, you, JimStar, are simply ignoring this issue, because until now you've not proposed any solution. only bla bla bla.

Sorry, but could you explain for all customers having this problem which DATE you plan to fix it? May 2013? September 2013?
Hope to hear an adequate reply.

Thanks

Is there any chance that we can get the last version of octane before this issues started? 1.0RC2 I believe. I don't think I still have it, and it might relieve some of the frustration other users are having until a solution is found.

Working now!!! WOOOOHOOO

Just downloaded the latest version - (v1.02b) and it works!!

Thanks!!



On a smaller note - the plugin version seems to render slower than the stand alone has anybody else noticed this or is it just an issue with my setup

focus wrote:I have an impression that with exception of some sings of attention, you, JimStar, are simply ignoring this issue, because until now you've not proposed any solution. only bla bla bla.

I think that if someone can't read clearly stated things such as e.g.:

JimStar wrote:It looks like the engine activation issue...
I will ask the engine-team about it, thank you for info.

JimStar wrote:PS. I have said about it to engine developers...

JimStar wrote:I have not yet got any news from engine-team regarding this...

and just starts to lout instead of reading - this is the true blah blah blah.

focus wrote:Sorry, but could you explain for all customers having this problem which DATE you plan to fix it? May 2013? September 2013?
Hope to hear an adequate reply.

You are planning to hear the adequate reply after starting to abuse me here. Funny.
I do not plan to fix it, if you still have not read the simple english posts here (and even did not read the status on my avatar - "Licensed Customer"). From the point of view of Maya's plugin - I'm the same user of Octane engine as you or any other user here, I bought Octane licenses for my own money as all others here. I do not have the access to Octane engine sources or licensing server or its algorythms. I only get the closed-sourced SDK from Octane team and develop the cheap plugin for Maya users in my spare from main work time, having just a little penny for this hobby (and you bought the beta version, remember?).
So, I repeat the last time, specially for you: I develop the plugin, not the Octane engine, I take no responsibility for autorisation algorythms inside the engine. I can't even debug it by myself or analyse the source of problem, as I don't have the engine sources.

focus wrote:I not doubt that it's important that the national symbols work ok, but instead of all this, IS IT really difficult to fix Maya batch problem?

OK, I can just stop all Maya's beta-plugin bug fixing and improving before I will get from Octane engine team the SDK that fixes this issue, no problem. Let's make users who have no autorisation problem and had the problems using textures laying in national-symbols paths wait together with you. I'm apologize to all users who had suffered from these bugs for fixing them so quickly, I will never do such stupid thing again.

SamQior wrote:Working now!!! WOOOOHOOO

Just downloaded the latest version - (v1.02b) and it works!!

Thanks!!

I think it is some other reason why it started to work on your system, as I did not changed anything beside is stated in the changelog... The engine it the same too. And for focus it still does not work...
It maybe something in your system was changed, or maybe something was fixed on the licensing server by Octane team... Very strange...
Besides not having the sources, it's even harder to catch the reason as I can't find the machine here on which this authorisation problem pops up, no computers where I can reproduce it - all is OK on all of them.