Txamo wrote: Mon Nov 16, 2020 10:08 pm
Yes, but it happens to me with all the scenes, are they all wrong? In addition to this, if the scene was wrong, it would be wrong when rendering with 2 GPUs and when rendering with 4 GPUs, it does not seem to me that it makes much sense, the pattern is clear, render with 2 GPUs well, more than 2 Blender closes as you see in The videos.
I have put the example in those videos with that scene, but it happens with the other scenes.
Yes it can be an internal hidden bug.Because this type of configuration aren't common Devs maybe never have to deal with. Can't reproduce it here as i have a single 2060S wich is far from your Rig
Support LuxCoreRender project with salts and bounties
Well, it's a shame, we had the configuration created to render animations (no mr it seems crazy to have a render farm to render animations with 4 GPUs), it is the first time that I have heard of such a limitation in an engine and look that I have used almost all rendering engines, but a limitation of this type never, I said, a shame I will have to continue with Cycles or Octane.
It would be good, as a recommendation I mean, that in the specifications of the program, as well as the minimum requirements, it is noticed in some way that from 2 GPUs the program is not compatible or something similar, because it is clearly a limitation that now you have the software and I think it is a very important limitation, regardless of how many people have 2 or 3 Gpus.
This is a bug and not an intended limitation.
Also, as far as I know, the only report of this problem came from you. No one else seems to have the same problem.
No, I have explained myself wrongly, I am not wanting to say that it is an imposed limitation and that is why it must be mentioned. I mean, it would be nice to mention that there is a limitation with configurations beyond 2 GPUs. We have two equal teams in the study and the problem is in both.
Even so, I do not believe and it is clear that it is a personal opinion what I will say, the fact that this is reported only I do not think it is something that should be lost track, seeing that the problem exists, I understand that If this was reported by 250 people, it would be more case than if I only do it, but it is still a problem, although at the moment it only affects one person in two teams.
If my comment bothered you, I beg your pardon, maybe I didn't know how to explain myself in the last message.
Txamo wrote: Tue Nov 17, 2020 10:45 am
No, I have explained myself wrongly, I am not wanting to say that it is an imposed limitation and that is why it must be mentioned. I mean, it would be nice to mention that there is a limitation with configurations beyond 2 GPUs. We have two equal teams in the study and the problem is in both.
Even so, I do not believe and it is clear that it is a personal opinion what I will say, the fact that this is reported only I do not think it is something that should be lost track, seeing that the problem exists, I understand that If this was reported by 250 people, it would be more case than if I only do it, but it is still a problem, although at the moment it only affects one person in two teams.
If my comment bothered you, I beg your pardon, maybe I didn't know how to explain myself in the last message.
I apologize.
It is a Bug so why should we writte that there is a limitation caused by a bug. you are the first to find it and the solution is to correct it as it isn't mean to stay like that.
In the past we had a probleme with very high core count CPUs the bug was reported and solved. So it is going to be the normal procedure :
User report
Devs Fix
User test and Confirm
We move on
Support LuxCoreRender project with salts and bounties
No harm done
I just wanted to say why I think it wouldn't make sense to include it in the documentation. It would fit better into the "known problems" category of the release notes, if we can reproduce it but cannot fix it.
Well, as I was saying and apologizing, I did not want to say that it was put as a limitation, I repeat, I have expressed myself wrong, what I wanted to express was, that it would be good to know about this "LIMITING BUG" in case of configuring a team with 3-4 GPUs would be limited to people who can create an environment with the render engine, in my case we have made the change to Blender with Luxecore and made this configuration to make it viable, because we never expected that this problem could occur, it was not something that We believed it was going to happen.
It was just a way to help other people. I understand that you cannot solve it because you do not have the necessary hardware for it, even so I appreciate your effort.
If you need help with this bug, I am at your entire disposal with what you need.
The thing is, there's the LuxMark database where people have submitted results of running LuxMark, which is essentially an older version of LuxCoreRender.
For example, here's the top results for the "complex" benchmark on GPUs: http://luxmark.info/top_results/Hotel/OpenCL/GPU
There are hundreds of entries there that were created with more than 2 GPUs.
Txamo wrote: Tue Nov 17, 2020 12:07 pm
If you need help with this bug, I am at your entire disposal with what you need.
Some kind of stacktrace or other debug logs would be good as a start.
You could run LuxCore in a debugger like gdb, trigger the crash, and extract a stacktrace.
If you explain to me how to do all that you ask me, I will do all the tests you need, I am a blender user but I don't have the knowledge that you ask me to be able to carry out those tests.
If you guide me please, I will be happy to throw the tests that are to be able to solve it.
