Hi, my name is Aaron, I am an independent 3D artist with 5-6 years experience has Blender user and about 2 years has a project administrator for a couple of Blender projects. Some of these projects include:
From a UX standpoint I think this makes sense.
This can now be committed
find is a standard bash command.
find is a standard bash command.
I would recommend also trying difference render settings for example disabling persistent data would help free up some render data that might not be needed for other frames.
Adding more video cards will only affects rendering time as each card can only access there own memory. You can use video cards with more video memory or more system memory. When rending cycles first uses the gpu memory as this is fastest, if that is not enough it starts using system memory at the cost of slower render times.
You must either optimize your scene by using lower resolution textures or upgrade your hardware. Even my machine with an 8gb bram and 32gb ram struggled with your scene.
Can you test with rendering blender from the command line. I could not reproduce with a 1050ti and a 2070.
I do not think that is true
The main advantage of this to apply looks on top of false-color maybe it makes sense to only make it a transform? But different transforms might give different luminance values so it is useful to see the false color before transform. I talked to @Troy Sobotka (sobotka) about this and said he was thinking about making false-color a transform in the official film config.
Not sure what you are expecting here this scene requires over 19gb of memory which for 4GB (VRAM) GPU is well over the limit and you start using shared GPU memory (RAM). If your laptop has 16gb of ram you are already hitting a physical limit. The reason why one frame will wor but not a second is that Blender needs to keep some of this data in memory such as for motion blur between frames.
Something is wrong with the transform.
@Tobias Heinke (TobiasH) can you better explain that, you have a double negative and I am not exactly sure what part of this task you are responding to.
Is this still an issue with blender 2.82?
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
This report does not contain all the requested information, which is required for us to investigate the issue.
Leaving as a todo to address the URL for 2.83
I have added a redirect so the initial report is fixed. In the future, now that we know can do this, hopefully, create an automated (maybe semi-manual) method to write redirects.
Glad to hear :)
To clarify on Trouble's comment, I meant to automatically adjust the version number from the addon side instead of the server-side.
I believe this broke loading the victor benchmark I get the following assert:
And we should definitely fix the add-ons docs links somehow including dev, it should contain the release number for official releases.
Personally, I would rather not adjust the naming, leaving things as they are even if they are broken.
In the future, we need to not do this, which has to do with implementing T68432.
The idea of D6546 and D6544 is to replace the current bright/contrast node. Before I get into fixing these patches how would this work as far as compatibility? The compatibility will likely be broken, the old node should be removed, it is broken and unfunctional and leaving it in the UI will confuse users.
The idea of D6546 and D6544 is to replace the current bright/contrast node. Before I get into fixing these patches how would this work as far as compatibility? The compatibility will likely be broken, the old node should be removed, it is broken and unfunctional and leaving it in the UI will confuse users.
This has been fixed in rB1e91d9d4dc49b09d53a1b544174ec245c4e8e684