The theme is present on github:
https://github.com/LuxCoreRender/BlendL ... issues/621
Performance issues
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: Performance issues
Linux Plasma | Ryzen 5, 32Gb, SSD M2, GT 590 RX | BenQ 27 | Wacom One | Microsoft Ergo | Tie Guan Yin tea
http://dezigner.tilda.ws/
http://dezigner.tilda.ws/
Re: Performance issues
How much money does it take to get this issue resolved?
Linux Plasma | Ryzen 5, 32Gb, SSD M2, GT 590 RX | BenQ 27 | Wacom One | Microsoft Ergo | Tie Guan Yin tea
http://dezigner.tilda.ws/
http://dezigner.tilda.ws/
Re: Performance issues
You can solve it for free by pressing z and choose Solid mode, make your scene update, press z and choose Rendered mode. You really don't have to do everything in rendered mode.
We are subject to the limitations of interacting with Blender through its Python API, and its associated architecture and constraints. You can't compare it to latency in Cycles or Octane, because they integrate directly with the C++ core, and have direct access to the data needed for rendering.
And also, chill out dude. Your attitude is coming across as pretty entitled. There are very very small number of developers on this project, and whatever they work on means everything else stops. Also what they work on will be prioritised by them.
AMD Ryzen Threadripper PRO 5995WX 64-Cores | 2x Gigabyte RTX 4090 Gaming OC
ASUS Pro WS WRX80E-SAGE SE WIFI | 256GB Kingston Server Premier ECC Unbuffered DDR4
ASUS Pro WS WRX80E-SAGE SE WIFI | 256GB Kingston Server Premier ECC Unbuffered DDR4
Re: Performance issues
This is ridiculous. That's how our grandmothers used to set up the lights. Today it is too slow a process.
To understand this, you have to try and set the light for the product yourself.
It's a fine-tuning of the many luminaires interacting with each other to create a light and shade pattern of an object, emphasizing its shape.
https://i.imgur.com/J2Rckp7.png
https://i.imgur.com/vH7Ago9.png
So you're wrong. When rendering merchandise you really have to do a lot in rendering mode.
And you're wrong, I'm not comparing it to Cycles or Octane.
I'm comparing with ProRender and AppleSeed which also work through API and have a much more responsive viewport.
Here's how the AppleSeed viewport works: https://youtu.be/KhD8Row_IOs
During scene modification, rendering pauses.
This is an idea I've suggested before.
The ProRender viewport works without pausing, almost like Cycles, very nice to work with.
So you are wrong again. Through the API others have been able to. I'm sure our developers can do it too, they are extraordinary specialists.
Advising me to relax is also ridiculous. I can advise you so much myself - enough to make sense of it for a lifetime.
I know about the number of developers and how busy they are.
I'm talking about the priority on the speed of the viewport should be taken.
Without a fast viewport, there is a very big waste of time for everyone involved in making quality adjustments to light and the scene as a whole.
Quality, excellence, exclusivity is what people come to Luxcore for.
But they run into a wall of insurmountable brakes.
And they turn around and leave.
So, man, you're just not in the loop, so you can't advise me.
To understand this, you have to try and set the light for the product yourself.
It's a fine-tuning of the many luminaires interacting with each other to create a light and shade pattern of an object, emphasizing its shape.
https://i.imgur.com/J2Rckp7.png
https://i.imgur.com/vH7Ago9.png
So you're wrong. When rendering merchandise you really have to do a lot in rendering mode.
And you're wrong, I'm not comparing it to Cycles or Octane.
I'm comparing with ProRender and AppleSeed which also work through API and have a much more responsive viewport.
Here's how the AppleSeed viewport works: https://youtu.be/KhD8Row_IOs
During scene modification, rendering pauses.
This is an idea I've suggested before.
The ProRender viewport works without pausing, almost like Cycles, very nice to work with.
So you are wrong again. Through the API others have been able to. I'm sure our developers can do it too, they are extraordinary specialists.
Advising me to relax is also ridiculous. I can advise you so much myself - enough to make sense of it for a lifetime.
I know about the number of developers and how busy they are.
I'm talking about the priority on the speed of the viewport should be taken.
Without a fast viewport, there is a very big waste of time for everyone involved in making quality adjustments to light and the scene as a whole.
Quality, excellence, exclusivity is what people come to Luxcore for.
But they run into a wall of insurmountable brakes.
And they turn around and leave.
So, man, you're just not in the loop, so you can't advise me.
Linux Plasma | Ryzen 5, 32Gb, SSD M2, GT 590 RX | BenQ 27 | Wacom One | Microsoft Ergo | Tie Guan Yin tea
http://dezigner.tilda.ws/
http://dezigner.tilda.ws/
Re: Performance issues
I can confirm this issue too at my big suprise : https://youtu.be/PpBVFQOjojMI'm comparing with ProRender and AppleSeed which also work through API and have a much more responsive viewport.
Here's how the AppleSeed viewport works: https://youtu.be/KhD8Row_IOs
During scene modification, rendering pauses.
This is an idea I've suggested before.
The ProRender viewport works without pausing, almost like Cycles, very nice to work with.
I posted here also : viewtopic.php?f=10&p=30804#p30804
Re: Performance issues
Most of the problem is coming from the slow conversion of the scene especially with too many objects or maps. more explain in:Sharlybg wrote: ↑Thu Jun 10, 2021 4:15 pmI can confirm this issue too at my big suprise : https://youtu.be/PpBVFQOjojMI'm comparing with ProRender and AppleSeed which also work through API and have a much more responsive viewport.
Here's how the AppleSeed viewport works: https://youtu.be/KhD8Row_IOs
During scene modification, rendering pauses.
This is an idea I've suggested before.
The ProRender viewport works without pausing, almost like Cycles, very nice to work with.
I posted here also : viewtopic.php?f=10&p=30804#p30804
viewtopic.php?f=10&p=30806#p30806
Omid Ghotbi (TAO)
Last update information
viewtopic.php?p=34390#p34390
My Artstation https://www.artstation.com/omidghotbi
My Instagram https://www.instagram.com/omid.ghotbi
Last update information
viewtopic.php?p=34390#p34390
My Artstation https://www.artstation.com/omidghotbi
My Instagram https://www.instagram.com/omid.ghotbi
Re: Performance issues
I tested with cycles and it seem to stop the render and only update after the user stop editing.
So why we don't follow the same strategy ?
So why we don't follow the same strategy ?
Last edited by Sharlybg on Thu Jun 10, 2021 4:45 pm, edited 1 time in total.
Re: Performance issues
that is a good solution aside from a more convenient way of conversion in an async multi-thread way.
Omid Ghotbi (TAO)
Last update information
viewtopic.php?p=34390#p34390
My Artstation https://www.artstation.com/omidghotbi
My Instagram https://www.instagram.com/omid.ghotbi
Last update information
viewtopic.php?p=34390#p34390
My Artstation https://www.artstation.com/omidghotbi
My Instagram https://www.instagram.com/omid.ghotbi
Re: Performance issues
I feel really bad. Like we are uselesslly slowing people adoption. it should be a top list priority as it is easy for some people to face it while testing.that is a good solution aside from a more convenient way of conversion in an async multi-thread way.
in my previous test i couldn't notice it so it was barelly visible for me :
https://youtu.be/2INyFqIP3X8
Re: Performance issues
that is exactly what I was talking about in the past you see it now. with the scene, you test if the HDRi is enough big just try to change the Gamma of it below the gain. It will take time because the HDRi should convert again with every different Gamma setting.Sharlybg wrote: ↑Thu Jun 10, 2021 4:50 pmI feel really bad. Like we are uselesslly slowing people adoption. it should be a top list priority as it is easy for some people to face it while testing.that is a good solution aside from a more convenient way of conversion in an async multi-thread way.
in my previous test i couldn't notice it so it was barelly visible for me :
https://youtu.be/2INyFqIP3X8
I'm just telling this because it shows how can conversion especially in PNG can be a big part of the problem.
By the way I do not know the reason behind convert all textures to PNGs? maybe there is a particular reason behind this.
Last edited by TAO on Thu Jun 10, 2021 6:44 pm, edited 2 times in total.
Omid Ghotbi (TAO)
Last update information
viewtopic.php?p=34390#p34390
My Artstation https://www.artstation.com/omidghotbi
My Instagram https://www.instagram.com/omid.ghotbi
Last update information
viewtopic.php?p=34390#p34390
My Artstation https://www.artstation.com/omidghotbi
My Instagram https://www.instagram.com/omid.ghotbi