Bimbeats Release v1.1.35.0

Team,

I would like to announce a new release of Bimbeats. As always, we have been working pretty hard behind the scenes not only to fix bugs (v34 😩), but also to open up more possibilities. This release of Bimbeats should do just that. Here’s a few highlights:

  • First and foremost we are now supporting all Autodesk 2023 products that we previously had support for. That includes Revit/Dynamo, AutoCAD and Navisworks.
  • For those of you using our floating license server solution (TurboFloat), we added the ability to monitor our/your own license server and keep track of your Bimbeats licenses. Check out this article for setup instructions: https://bimbeats.freshdesk.com/support/solutions/articles/47001162778-4a-deploy-logstash-bim-360-flexlm-turbofloat-to-a-windows-server
  • Couple of smaller, Revit related improvements that should make a few workflows easier:
    • We added a field called “document.changed” to “View” and “Sheet” actions. The intent behind that addition is to count how many elements were changed (added, deleted, updated) in a view for the duration of that view being open. This should help to improve your ability to look at work done across various types of views - typical details, plans, sections etc. - and gauge how much work and effort actually goes into them. We previously offered that via just measuring the time that users spend in a view, but now we can better gauge “work” by looking at a ratio of “time over changes” to more accurately measure work effort. This should help you identify whether Typical Details that your company starts every project with, are actually typical, or do they get reworked on every project. This is just one of the potential use cases.
    • We also fixed an issue with a field called “view.instances.hidden.count”. Why does that matter? Because that field gets published for every View action, and should tell you how many elements were hidden in that view via Right-Click > Hide In View method. We, BIM Managers, preach that this should never be done, so now you can keep track of how much that method is being utilized on your project. If that ever becomes an issue, you can easily use that data to organize training sessions or better target your cleanup efforts.
    • We also added an API_ERROR logs to revit-user index. These should help your development team identify conflicts between various plugin dependencies. Normally, these rarely cause issues, but in some extreme cases, these conflicts can cause crashes. As funny as that sounds, this was actually a request from Autodesk folks. 😅

We have also recently published a study on the impact of compacting on your files and potential savings that it can have for your company. You can read about it here: https://archi-lab.net/the-case-for-compacting-revit-files/

Full changelog between versions can be found on our Knowledgebase. We would love to show you around the features noted above or are here to help you deploy this latest version of Bimbeats to your teams, so please get in contact with us via our support desk or find a slot in my calendar. Finally, if you are going to deploy this latest update on your own, please review our deployment instructions first.

Please find attached a link to the latest installers for Bimbeats version 1.1.35.0.