restdear.blogg.se - 3d benchmark

#3d benchmark pdf#
#3d benchmark zip file#
#3d benchmark upgrade#
#3d benchmark windows 10#
#3d benchmark software#

#3d benchmark software#

To use RFO Benchmark for meaningful comparisons you need to ensure consistent test conditions with no extra software running, identical screen sizes, etc.ĮDIT: BENCHMARK DOWNLOAD LINKS HAVE BEEN REPLACED, to temporarily point to my Sharefile site, since the download link was broken. It's worth the reminder, while comparisons of results reported here at RFO are interesting, and often entertaining, this is not appropriate data for purchasing decisions.

#3d benchmark zip file#

The bug related to unzipping with 7ZIP has been addressed, however, the best unarchiving approach remains simply right clicking the ZIP file and choosing Extract All, thus using the built in Windows UnZIP capability.

Various performance issues have been addressed, mostly related to how long the benchmark takes to run, not the actual Revit processing performance.

Test resources are now copied to a dedicated folder for processing, so multiple machines can be benchmarked from a network RFO benchmark folder.

Improved reporting of Revit build information.

Graphics without Hardware Acceleration has been moved to a standalone GPU only test.

The Simplified test does only includes standard views.

The Standard & Expanded GPU tests now compare Sketchy and non-Sketchy views for both the regen and view cube tests.

Additional GPU testing options now allow detailed heavy/large model testing.

This v3.1 benchmark changes a few things you should be aware of.

DPI Scale is now included in the report, so we can try to grok what settings and what hardware actually works.

It seems there is a problem with high DPI scaling and journal playback. If it crashes, especially in the middle of Model Creation, try setting your DPI Scaling lower.

If your DPI Scaling is above 150% you will get a warning, but the benchmark will proceed.A new Graphics_Comparison set compares standard graphics views, squiggled views and now 3D levels views.The Squiggly Lines graphics test has been removed from the Full_Standard set.Version 3.-2021 is, from a Tests standpoint, the same as v3.2. has a few changes compared to previous versions. As far as actual benchmarks, they have not changed. And of course Windows 8/8.1 isn't even supported for Revit any more. Hopefully not many are still in Windows 7.

#3d benchmark upgrade#

For Windows 7 users, you can download Windows Management Foundation 5.1 to upgrade your PowerShell. This is the default version of PowerShell in Windows 10, which is where the vast majority of us are now. Miscellaneous small bug fixes and refactoring.Note that Task Manager & Resource Monitor only work if the OS language is English due to the OS renaming these programs as the language changes. -foregroundMonitors switch added, to bring CPU-Z, GPU-Z, Task Manager & Resource Monitor to the foreground after Revit launches for each test, to facilitate monitoring resource use during the test.DPI scale warning functionality has been repaired.

#3d benchmark windows 10#

This is required by another change in the way PowerShell in Windows 10 works. Functionality of the -showStatus switch has been repaired.The way Wait is handled has been changed to mitigate this. This is a very odd interaction between Revit and the Start-Process cmdlet in PowerShell, specifically PowerShell 5.1, which is what is included by default in Windows 10. The main fix is the VERY long pause between individual tests.Perhaps if someone from Autodesk has the secret sauce I am missing that allows for this? I assume there must be some way, otherwise how would ADSK do regression testing on the new feature with multiple output locations?Īlso, thanks a TON Munkholm and Robin Deurloo, for the support getting the new download approach set up. The only option I had was to accept the default location, which would potentially leave output behind because I wouldn't know where to look to clean up, which I don't want to do. Not a relative path from the journal location, and not a variable with a calculated path. Neither of the approaches that I have used in other export tests to redirect output would work.

#3d benchmark pdf#

The combination of dealing with the new builds for my work and the benchmark has gotten more and more challenging, the last two years especially.Īlso, I should note that I was not able to include the new PDF Output as part of the benchmark, try as I might.