This is a project about Blender's benchmark bundle and website. Both of this projects are highly under development, more information will be available once things are stabilized and ready for public tests.
Wed, Sep 16
Jun 25 2020
May 26 2020
I just wanted to express my appreciation of the edit mode crosshair. I even used the Speedflow addon mainly because it displays the current mode in fat letters in the corner of the viewport but the crosshair change is so much better. Now you can tell if you are in edit mode even with disabled overlays and header.
May 1 2020
There are systems in place to remove outliers, this is not considered a bug.
Apr 20 2020
Are there updates on this?
Mar 21 2020
Mar 3 2020
Feb 22 2020
Feb 17 2020
Please try again with the updated benchmark.
Feb 14 2020
I tried the Victor scene with an unrelated Windows laptop with 16GB ram and it had the same result.
Feb 13 2020
Hi @Sem Mulder (SemMulder), my apologies, I think I misunderstood what you said. I see the file now and yes, this works. Please accept my apologies for the inconvenience.
Feb 12 2020
Hi @Sem Mulder (SemMulder), I wouldn't call this resolved because the core issue is still a problem. I did use poetry per the instructions. Did you mean the readme.md (as opposed to txt)? There's no txt file anyway. I will try running the launcher in debug mode, but I think it failed the last time I'd tried that.
I believe @Ray molenkamp (LazyDodo) is correct here. We are currently still investigating how to detect this properly (detecting the amount of GPU memory available across all brands is a bit complicated). Closing this for now as this is not an issue with the launcher per se.
This issue occurs because you first need to download the Blender version. Please read the README.txt included in the archive downloaded from opendata.blender.org for details. We might improve that error message here though. Since this is not a bug I am closing this issue.
@Sem Mulder (SemMulder) any idea what I'm doing wrong here?
Also the 'import snapshot' instruction in the documentation fails with:
So, regarding this note:
Feb 11 2020
So I just tried running the test script (I didn't change the default values for the parameters mentioned above) and I get these errors:
How can I do this step:
Feb 6 2020
peak memory for victor on my box is 16774.97M that 16GB of ram may be just a little short there.
Feb 1 2020
You need to:
Um okay, how do I do that?
Are you running the benchmark client against your own development install of the Open Data platform (/website in the repo)?
In that case, make sure that you update the "Client" via the admin backend.
I just did a sync and rebuild of the launcher, and I'm seeing something odd. When I try to run it, I get:
Jan 27 2020
Jan 17 2020
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Nov 26 2019
probably fixed plz check if it happens in official 2.81 version if yes make new bug report
Sep 10 2019
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Aug 28 2019
Put some effort in the report.
@Abid Maqbool (cto.abid) Just a note: It's not the same triage system as BF Blender.
For Blender Benchmark there is no "Report an Issue" anywhere.
Currently only Blender Open Data has a blank forum for Report an Issue and that's it.
There are no guides or instructions on how to report a bug for the Benchmark client...
Tasks usually get assigned to Sybren.