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.
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. 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. You might see the results come back a few seconds faster. If you downloaded the 2023 or 2024 benchmarks between April 3rd and April 6th, you will want to delete them and redownload, and rerun. As of 8am CST on 2023.04.07, its been corrected. Important Note: I had a minor mistake in the 2023/2024 benchmarks, when originally posted.
0 kommentar(er)
