Constant crashes. How to workaround crashes ?

[oguzbir]

Hey,

We can squash more bugs for the upcoming release, so if anyone can provide a step-by-step procedure to reproduce the crash(es) in question,
we will investigate and fix.

The procedure should be detailed enough to allow us to reproduce the crash.
The given information is a bit vague, i can't seem to reproduce it.

Radiance

I'd really try to re-create procedures but mostly are random. All of a sudden.
All I can say and sense is. It's not about the scene heavyness or overdriven attributes.
panning, nodelinking, de-linking. All I can say is besides panning stalls, with out obj importing dealing with material only scene does not crash. Could it be related with the max2Octane issue? Im using v5 x64 maybe x32 will do the trick that's something I didn't test...

I reduce max samples to 25 or 50 even though it crashes.
some kind of a auto saving could save me from giving up R&D. That's why I cant get octane in my workflow.
By the way I realy get astonished with the way people create such nice images.
I repeat my question to all users, especially the ones that create and manage to finish nice interiors .
Do you have these issues also.
This is not a scream out. But a question to understand if these are my issues only.
I think If I was to create an interior type of image with lots of materials. I would come up with about 50-70 lockups, and more crashes than these..

Waiting paitiently for stable called versions.

Cheers..

[oguzbir]

I create material nodes next to the the obj node. Then I try to connect the nodes one by one.
But after some time connecting a simple diffuse material as is - without any texture applied-
Octane crashes.

I often have this problem too (with a new material node or with a material node from the LiveDb). This is how I avoid it.
I create the new material node (or I drop it from the LiveDB) and, BEFORE CONNECTING IT TO THE OBJ NODE, I double click on it, so I switch on preview mode (you know, with the sample ball ...).
And then, I connect this material node to the obj node. And so on ... FIRST double click on a material node and AFTER, connect it ...

Sorry for my english , I hope you'll understand what i'm triyng to explain and also that this will help you ...

I generally close the preview option.
That's what avoid in order to see what I 'm linking directly on the object it self.
May be your way is indeed a workaround, using the preview option.
Will try that..
Thanks

[oguzbir]

Would it help octane if we triangulate our objects not quads ?
I remmember one saying that octane does not like quads?

Radiance,

Here is a testing scene. And it just crashed.
While dealing with the bulky rectangle object ( connecting a diffuse mat. and than adding a RGB color to have translucency) it crashed .. Gave assertion failed message line 43 nodepin.cpp..
I pressed ignore. I continued. But the diffuse material has lost its input nodes. Only 3 input was left.
You can see the capture image.
I saved the file as aftercrash.
exited octane. Re run. load aftercrash file. and another silly material mix both having transluceny in order to exploit the so called reason. none happened. saved file as suffix to previous one ..afterthat.ocs
But after few minutes. panning the scene gave a lockup....
killed octane. Said Pufff.


Hope it helps.
This is not a spesicif file that crashes this the way octane runs on my pc.
Hope you solve some issues.

Thanks,

[abstrax]

Would it help octane if we triangulate our objects not quads ?
I remmember one saying that octane does not like quads?

Radiance,

Here is a testing scene. And it just crashed.
While dealing with the bulky rectangle object ( connecting a diffuse mat. and than adding a RGB color to have translucency) it crashed .. Gave assertion failed message line 43 nodepin.cpp..
I pressed ignore. I continued. But the diffuse material has lost its input nodes. Only 3 input was left.
You can see the capture image.
I saved the file as aftercrash.
exited octane. Re run. load aftercrash file. and another silly material mix both having transluceny in order to exploit the so called reason. none happened. saved file as suffix to previous one ..afterthat.ocs
But after few minutes. panning the scene gave a lockup....
killed octane. Said Pufff.


Hope it helps.
This is not a spesicif file that crashes this the way octane runs on my pc.
Hope you solve some issues.

Thanks,

Thanks for the information. I will have a look at it next week. Hopefully I can find something wrong here. It seems that at some point there have been more than 1 connection to a material node pin. Which caused the assert.

I will try to reproduce it and see what happens.

Thanks again,
Marcus

[matej]

It seems that at some point there have been more than 1 connection to a material node pin. Which caused the assert.

This (multiple connections) happens to me when I change material names in Blender, and then re-export to an existing .ocs (which has the old names). Some pins have two materials attached and some nodes won't disconnect (they re-attach automatically back to the mesh).

This doesn't cause any errors or crashes, and is resolved after I disconnect everything that is possible and save/reload the .ocs (a few times).

Just to point out.

[face]

The workaround for changing scenes is, that you should use the overwrite function.
Octane isn´t ready to handle it currently. That should be known.
I don´t know why some people use functions that aren´t integrated...

face

[abstrax]

The workaround for changing scenes is, that you should use the overwrite function.
Octane isn´t ready to handle it currently. That should be known.
I don´t know why some people use functions that aren´t integrated...

face

I'm actually not sure, that it's the relink problem. It might be something else, that happens while you work in the node graph editor. I will give it a try on Monday. The report of oguzbir was definitely interesting and heopefully it helps finding the actual problem.

Cheers,
Marcus

[oguzbir]

Thanks for the information. I will have a look at it next week. Hopefully I can find something wrong here. It seems that at some point there have been more than 1 connection to a material node pin. Which caused the assert.
I will try to reproduce it and see what happens.
Thanks again,
Marcus

Ehhm. I generally make 2-3 copies of the same material in order to try the differences I have made. This is because there is no undo.
As I use other node based applications like fusion. I tend to overlap the new materials output node to the older one's connected node to change the connection.
Could that cause the problem?

What ever the the problem would be I'd really love to have a autosave function. like Realflow or max.
Maybe project based saves under different folder. thus, keeping the directory tidy.
And previous folder remembering type of thing. And Ctrl-O like shortcuts to open and save is a must anyway..


Thanks that you'll inspect my file.

[oguzbir]

Another thing about the freezing because of panning I think I might give clues of my habbits.

Due to crashes when altering material properties I tend to change the material in the object node itself. I try to avoid to link material nodes as if it will crash.

So I generally hold the material picker tool and navigate with it. Maybe that kind of navigating where clicking to an object wrongfully and repeatedly could or would create a problem and cause freezing.

If this is the case you might have to assign a keyboard shortcut key to help us change the cursor speaciality to overcome this issue.

Thanks.

[face]

The workaround for changing scenes is, that you should use the overwrite function.
Octane isn´t ready to handle it currently. That should be known.
I don´t know why some people use functions that aren´t integrated...

face

I'm actually not sure, that it's the relink problem. It might be something else, that happens while you work in the node graph editor. I will give it a try on Monday. The report of oguzbir was definitely interesting and heopefully it helps finding the actual problem.

Cheers,
Marcus

Sorry, correct is, that Octane can´t handle new materials on existing projects when the new material is´t at the end of the mtl-file.
For that it is required to use the overwrite function...

In Softimage, objects will be exported in the order of the meshname.
If you want to use only one Octane material and let the others as in the mtl-file, then you should rename the object to 0xxx, so that it stay in the first place.
For this Material you can now create a material macro.
After export a scene, Octane use the macro for the first material and the others will become the definition from the mtl-file.
You can do that for 2, 3, 4 materials, but they must be in the first places.

I think the other exporters will use the same technique...

face