OTOY Forums

Hubby72 wrote:Hi AlfaseeD,


check these forum posts and you can make yourself a picture of the answer to your question :

viewtopic.php?f=44&t=57829
viewtopic.php?f=44&t=57905

I saw the first thread but not the second !
Thanks a lot, this help me a lot

Hi Paul,
I just noticed that most of the latest product on Daz support iRay and their material most of the time use the metallicity/roughness maps.
Usually there are a few maps: metallicity map, diffuse, glossy, roughness and normal.

Now, the Octane plug-in doesn't seems able to convert this kind of shader and this is a really huge problem since I need to do it all by hand and yeah, it's super time consuming.

Do you plan to improve the material/shader conversion in order to get a good results in octane without the need to do it all by hand?

If you can send me a simple .duf scene which demonstrates the above issues, I will take a look.

Live DB material materials can not be partially loaded!
Some materials can not be loaded from the LiveServer, then the load window remains open and you can do nothing more - neither close the window nor save the scene. The only way to strangle the program in the task manager. If you have not stored there before all work is gone!
It would be great if you could close this window or fix the defective materials. ("Metal Dirt" is a material that does not work, but there are several)

Metal Dirt loaded fine for me.

Paul

In relation to LiveDB Shaders stalling the application this is happening a lot to me.

I actually created some of my own shaders through Octane Standalone and uploaded to the Database which happened seamlessly but when I try to use them via the DS plugin the system stalls.

LI Concrete Displacement ( I idid use 4k JPEG for this so I thought it was load time but no luck as yet )
LI Concrete Grain

This has also happened with other shaders not self created.

As a side note they are loading and rendering fine in the Standalone Version.

Also seem to be having issues with loaded objects not showing up in the scene. ( As attached ) Camera also not matching scene.

Current solution close and reload scene. ( Reload Force / Rebuild Scene ineffective )

Wondering, remember seeing something about this a while back, is there any chance we will get DS Instances rendering in the future ?

Hey mate, did you get the most recent TEST version of the plug-in here? viewtopic.php?f=44&t=55214
The most recent one supports instances and instancing groups.

Camera also not matching scene.

Current solution close and reload scene. ( Reload Force / Rebuild Scene ineffective )

Wondering, remember seeing something about this a while back, is there any chance we will get DS Instances rendering in the future ?

I am aware of these issues and have a partial fix in the next release, however there is still more work to be done. I hope to have the next release out just after New Year.

Paul

Cool, thanks for the heads up.

face_off wrote:

Live DB material materials can not be partially loaded!
Some materials can not be loaded from the LiveServer, then the load window remains open and you can do nothing more - neither close the window nor save the scene. The only way to strangle the program in the task manager. If you have not stored there before all work is gone!
It would be great if you could close this window or fix the defective materials. ("Metal Dirt" is a material that does not work, but there are several)

Metal Dirt loaded fine for me.

Paul

Maybe New Zealand is too far from Austria and therefore the DB material does not come to me.
But it is really annoying when I spend hours at a work and then I must throw away everything because the DB window blocks everything!
I do not dare to load anything from the DB server since this problem occurs very often.
The function "close the window" would be very helpful.
Greetings Thomas

Fanthomas wrote:

face_off wrote:

Live DB material materials can not be partially loaded!
Some materials can not be loaded from the LiveServer, then the load window remains open and you can do nothing more - neither close the window nor save the scene. The only way to strangle the program in the task manager. If you have not stored there before all work is gone!
It would be great if you could close this window or fix the defective materials. ("Metal Dirt" is a material that does not work, but there are several)

Metal Dirt loaded fine for me.

Paul

Maybe New Zealand is too far from Austria and therefore the DB material does not come to me.
But it is really annoying when I spend hours at a work and then I must throw away everything because the DB window blocks everything!
I do not dare to load anything from the DB server since this problem occurs very often.
The function "close the window" would be very helpful.
Greetings Thomas

Yes I too get this message from time to time, the only way out is to end task and re-construct the scene or reload the scene from disk if I remember to save every now and then.

Maybe New Zealand is too far from Austria and therefore the DB material does not come to me.
But it is really annoying when I spend hours at a work and then I must throw away everything because the DB window blocks everything!
I do not dare to load anything from the DB server since this problem occurs very often.
The function "close the window" would be very helpful.
Greetings Thomas

Yes I too get this message from time to time, the only way out is to end task and re-construct the scene or reload the scene from disk if I remember to save every now and then.

This is becoming more and more of a concern to me as well because it seems to be becoming random which LiveDB Mats are affected by the endless loading issue. I'm apprehensive now every time I want to load a material from liveDB so I always save my work first before doing that.
Sure, saving your work before loading liveDB mats helps, but it is annoying nonetheless having to go to Task Manager in order to close DS, restart then reload the scene, especially when you have a big scene that takes minutes to load.
So yes, a function to cancel would be great... or perhaps OTOY should check if there's anything wrong with the liveDB library lately.