Community Forums for OTOY Customers
https://render.otoy.com/forum/
Well thanks! What's your question?divasoft wrote:All scattered cubes in viewport are gray and scatter use only first object for scattering when i use cinema effectors with octane scatter.
For what its worth, I'm noticing something similar on my end. Hope we can figure out what is going, would be greatly appreciateddivasoft wrote:Standalone works fine even 16k textures without freezing. 3ds max works fine even 8k textures without freezing.desire wrote:don't need to use 8k map and displacement to get very long time response.divasoft wrote:Only one 8k displacement freeze cinema as hell. How i can work?
https://drive.google.com/open?id=1Jfets ... Lu-XGGX6ZO
Even in a quite simple scene there is enough start working with mat that have 4k tex to get response around 4-5 sec after changing any parameter.
If a mat has several 4k tex - response time is about 10-12 sec after any changing. (ANY!)
8K tex I'm using at the moment ONLY for the final render. To work with a scene without hangs I used a bunch of needed textures in a 2K resolution ((
I am glad for you that you use 2k textures, but this is not the right way. The fact that you are used to performing numerous unnecessary actions does not mean that this is correct.
The developer should optimize the software, and not force the user to do tricks
It's not a question. This is what needs to be fixed.aoktar wrote:Well thanks! What's your question?divasoft wrote:All scattered cubes in viewport are gray and scatter use only first object for scattering when i use cinema effectors with octane scatter.
There's not any problem for rendering, just viewport issue. I don't have any plans to update the scatter objectdivasoft wrote:It's not a question. This is what needs to be fixed.aoktar wrote:Well thanks! What's your question?divasoft wrote:All scattered cubes in viewport are gray and scatter use only first object for scattering when i use cinema effectors with octane scatter.
You are a moron and a child. If you were competent you wouldn't waste the devs time with nonsense requests like this. Your unending wave of brainless requests and attacks are hurting other users. The devs need time and energy to do their jobs.divasoft wrote:It's not a question. This is what needs to be fixed.aoktar wrote:Well thanks! What's your question?divasoft wrote:All scattered cubes in viewport are gray and scatter use only first object for scattering when i use cinema effectors with octane scatter.
I don't see any CRASHES here. It's just waiting the calculation in the renderer. Green "UPDATING...." text on top of LV that shows it's waiting some calculation on the RENDERER. Try to decrease subdivisions and displacement resolution and try to don't use PNG/JPG for images. Also disable material/opengl previews for faster editing. Or BE SURE that "Texture caching" option is ENABLED in settings.divasoft wrote:Hi. I work with displacement. And octane is constantly crashes. Every now and again. I have to restart cinema about 30-40 times per hour. Failure occurs at random times. It's not a problem with devices, same things happens on different hardware configurations. Sometimes just moving a node in the node editor is enough. A little bit more stable displacement in 4.05, where failure occurs about 10 times per hour. Despite the fact that everything works perfectly in the standalone. I think that you, Aoktar, need to completely rework the part of code related to displacement. This part makes the application extremely unstable. Work becomes almost impossible.
Please do not need to ask me for test scenes. If you try to test at least a little yourself what you created, you will immediately see how unstable the displacement works. A year ago, I told you that it was necessary to hire a tester on the staff.
https://drive.google.com/open?id=1Xc1Db ... fj7clAtS5a
Yes, error popup not appear, but if i will waiting for calculation i will be wait infinite. I was try to wait 2 times for 10 min and nothing happened. In standalone this operations works on the fly.aoktar wrote:I don't see any CRASHES here. It's just waiting the calculation in the renderer. Green "UPDATING...." text on top of LV that shows it's waiting some calculation on the RENDERER. Try to decrease subdivisions and displacement resolution and try to don't use PNG/JPG for images. Also disable material/opengl previews for faster editing. Or BE SURE that "Texture caching" option is ENABLED in settings.divasoft wrote:Hi. I work with displacement. And octane is constantly crashes. Every now and again. I have to restart cinema about 30-40 times per hour. Failure occurs at random times. It's not a problem with devices, same things happens on different hardware configurations. Sometimes just moving a node in the node editor is enough. A little bit more stable displacement in 4.05, where failure occurs about 10 times per hour. Despite the fact that everything works perfectly in the standalone. I think that you, Aoktar, need to completely rework the part of code related to displacement. This part makes the application extremely unstable. Work becomes almost impossible.
Please do not need to ask me for test scenes. If you try to test at least a little yourself what you created, you will immediately see how unstable the displacement works. A year ago, I told you that it was necessary to hire a tester on the staff.
https://drive.google.com/open?id=1Xc1Db ... fj7clAtS5a
I don't think so! Send us your comparison scenes and lets check what you do. Standalone has not to generate previews on every operations, don't forget that. It's a big task for plugins.divasoft wrote: Yes, error popup not appear, but if i will waiting for calculation i will be wait infinite. I was try to wait 2 times for 10 min and nothing happened. In standalone this operations works on the fly.
Png is good for storage with small size but decompression time is longer than tiff/psd/etc...jayroth wrote:Hi Ahmet,
I use PNG files all the time. Is there a link to explain why that is not a good idea?
Thanks.