u/TigerBarFly

Ever since we rolled out 2026 my firm has been plagued with C++ redistributable errors. It’s like playing wack a mole.

Randomly every day some user somewhere can’t launch Revit or C3D. It doesn’t just impact Revit. It impacts any Autodesk product. The fix is to go to Add/Remove programs and run a repair on the latest version of Microsoft visual C++ v14 Redistributable (x64). Sometimes this requires a restart sometimes it doesn’t.

But the fix never seem to stick and I’m losing my hair trying to identify what’s causing the issue. Is anyone else battling these gremlins? There seems to be a ton of documentation on it but no one seems to know precisely what is causing the issue (other than a firey print driver thing we don’t use).

We’re toying with applying Bh a blanket login script to apply this generic fix on login but that feels kludgy. Any suggestions?

My firm is looking at adjusting how we name and number projects in our various systems. We ultimately are trying to better align our various ecosystems so it’s easier to compile data from multiple locations.

The proposed naming convention everyone is set on is quite long. I’m worried about long file paths in ADC as that’s become everyone’s favorite way to access data on Forma.

I’ve flattened our folder structure as much as possible to combat long file paths but with a long project naming convention I’m concerned about how this will impact teams.

I personally just want the Forma project name to be a job number and the Forma project number field to be the name. Project names change sometimes but project numbers don’t. I think this is the most scalable solution long term.

In my research I’m getting mixed information. Some say long file paths are not a big deal at all, others say programs like Adobe, Bluebeam, and Enercalc do not play well with long file paths and some Revit C3D links break when paths are long. Overall half say long file paths are a drag on production others seem to believe it’s a nothingburger.

Can someone here help me get a better understanding of the technical risk profile of this decision? Am I being overly worried about file paths and how they impact production and project management? Or, is this a real productivity issue we’re about to unleash upon our masses?

Thanks y’all!

Just wanted to solicit feedback on a proposed change to our process. I am looking at a process for aggregating scope of work Sqft from many different projects across a large firm.

The proposed workflow is each project creates a Scope of Work Area Plan for each floor and we use the calculated area to determine the total SQFT for each project.

What I think we would need to do is leverage dynamo or C# addin to copy the total sqft from all the SOW area plan areas in the model to a project level (probably shared so I know it’s our parameter) parameter. Yes I know this could be scheduled but I don’t see how I can pull the calculated total sqft from a schedule grand total to a parameter.

Anyway the idea is as the work progresses changes to size of SoW are reflected in the updates to this SoW area plan areas. In theory this would be more reliable and accurate than the marketing data the team currently has. And we could use additional parameters to divvy up the SoW into types of work (lab, sleeping areas, k12, industrial, etc).

I foresee having issues aggregating this data somewhere accessible from models hosted in Forma, users updating this data (probably falls on the BIM team realistically), and parsing out “true project” Revit files from models copied forward to support future work. I’m confident parameter work for filtering sorting grouping etc on the reporting end (probably PBI or excel).

Anyway I’m just fishing for thoughts or recommendations.

Just wanted to solicit feedback on a proposed change to our process. I am looking at a process for aggregating scope of work Sqft from many different projects across a large firm.

The proposed workflow is each project creates a Scope of Work Area Plan for each floor and we use the calculated area to determine the total SQFT for each project.

What I think we would need to do is leverage dynamo or C# addin to copy the total sqft from all the SOW area plan areas in the model to a project level (probably shared so I know it’s our parameter) parameter. Yes I know this could be scheduled but I don’t see how I can pull the calculated total sqft from a schedule grand total to a parameter.

Anyway the idea is as the work progresses changes to size of SoW are reflected in the updates to this SoW area plan areas. In theory this would be more reliable and accurate than the marketing data the team currently has. And we could use additional parameters to divvy up the SoW into types of work (lab, sleeping areas, k12, industrial, etc).

I foresee having issues aggregating this data somewhere accessible from models hosted in Forma, users updating this data (probably falls on the BIM team realistically), and parsing out “true project” Revit files from models copied forward to support future work. I’m confident parameter work for filtering sorting grouping etc on the reporting end (probably PBI or excel).

Anyway I’m just fishing for thoughts or recommendations.