Topic split from viewtopic.php?f=4&t=1935
Have the same issue with 2.4 master on viewport RT cpu.
Pretty simple scene. Cpu stay at 100% without loading viewport render.
After a long 5mn wait viewport switch from solid to render mode.
Slow pointiness shape computation
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Re: Luxcore is very slow and freezes
Sounds like first-time kernel compilation for OpenCL viewport, but you say you are using CPU as device?
Can you upload a scene that shows the issue?
Is it only the startup time that's long, or is the interface sluggish even after the render has started, as reported in the first post?
Can you upload a scene that shows the issue?
Re: Luxcore is very slow and freezes
Here is the scene. i know why it is like that. if you reduce subsurf to 3 or 4 you can work. but at 6 it Bye bye
Re: Luxcore is very slow and freezes
It uses the Pointiness shape, is it intended ? Indeed, it is very slow, it has to recompute pointiness each time.
Re: Luxcore is very slow and freezes
Yes i'm in process to make a new tutorial with it. And cycles is working fine with it even at 6 level subsurf.It uses the Pointiness shape, is it intended ? Indeed, it is very slow, it has to recompute pointiness each time.
Re: Luxcore is very slow and freezes
Are you using pointiness also with Cycles?
I have accelerated the pointiness computation quite a bit in the latest builds, not sure if you're using that.
However, the Cycles implementation is still faster, which might become noticeable on very heavy meshes.
(The reason being, from what I can see, that LuxCore needs to build edge information, while Cycles uses the raw Blender mesh which still has edge information).
I have accelerated the pointiness computation quite a bit in the latest builds, not sure if you're using that.
However, the Cycles implementation is still faster, which might become noticeable on very heavy meshes.
(The reason being, from what I can see, that LuxCore needs to build edge information, while Cycles uses the raw Blender mesh which still has edge information).
Re: Luxcore is very slow and freezes
Yes of course.Are you using pointiness also with Cycles?
why can't we do the same ? any blender API limitation.(The reason being, from what I can see, that LuxCore needs to build edge information, while Cycles uses the raw Blender mesh which still has edge information).
Re: Luxcore is very slow and freezes
It is the same for any geometry transformation (i.e. pointiness, displacement, etc.) and it always been like this.
P.S. It is likely to be not the topic of this thread, I have the feeling people were talking of a different type of problem.
P.S. It is likely to be not the topic of this thread, I have the feeling people were talking of a different type of problem.
Re: Luxcore is very slow and freezes
Great job mate just instal the last build from both Luxcore and blendluxcore. it work great thank you thank youI have accelerated the pointiness computation quite a bit in the latest builds, not sure if you're using that.
However, the Cycles implementation is still faster, which might become noticeable on very heavy meshes.
Re: Luxcore is very slow and freezes
Editing that mesh in Cycles (or even in the OpenGL viewport) is just as sluggish as in a Lux viewport render. This is simply due to the very high subdivisions and the time needed to compute them. The pointiness is just the icing on the cake.
It would require a special pointiness precomputation just for Blender inside the Blender mesh transfer code. It's possible, but it would add a lot of complication and code duplication, which is why I'd like to avoid it (especially because the performance gain will be small).