Jump to content

Autodesk Autocad 2022 AMD fix


fabiosun

Recommended Posts

  • Supervisor

As in Maya 2022 two libs need a simple fix:

 

put patched libtbb.dylib in

/Applications/Autodesk/AutoCAD 2022/AutoCAD 2022.app/Contents/Frameworks

 

and patched libtbbmalloc.dylib in the same

/Applications/Autodesk/AutoCAD 2022/AutoCAD 2022.app/Contents/Frameworks

 

You need to overwrite the files already present there.

 

If you have SIP enabled you may need to re-sign them:

 

sudo codesign --force --deep --sign - /Applications/Autodesk/AutoCAD\ 2022/AutoCAD\ 2022.app/Contents/Frameworks/libtbbmalloc.dylib

 

sudo codesign --force --deep --sign - /Applications/Autodesk/AutoCAD\ 2022/AutoCAD\ 2022.app/Contents/Frameworks/libtbb.dylib

 

 

900997649_Screenshot2021-12-01at3_10_21PM.png.2e8e0c2896cc4cc3862c7379b51bb017.png

Archive 2.zip

  • Like 3
  • +1 1
Link to comment
Share on other sites

  • fabiosun changed the title to Autodesk Autocad 2022 AMD fix
1 ora fa, fabiosun ha scritto:

As in Maya 2022 two libs need a simple fix:

 

put patched libtbb.dylib in

/Applications/Autodesk/AutoCAD 2022/AutoCAD 2022.app/Contents/Frameworks

 

and patched libtbbmalloc.dylib in the same

/Applications/Autodesk/AutoCAD 2022/AutoCAD 2022.app/Contents/Frameworks

 

You need to overwrite the files already present there.

 

If you have SIP enabled you may need to re-sign them:

 

sudo codesign --force --deep --sign - /Applications/Autodesk/AutoCAD\ 2022/AutoCAD\ 2022.app/Contents/Frameworks/libtbbmalloc.dylib

 

sudo codesign --force --deep --sign - /Applications/Autodesk/AutoCAD\ 2022/AutoCAD\ 2022.app/Contents/Frameworks/libtbb.dylib

 

 

900997649_Screenshot2021-12-01at3_10_21PM.png.2e8e0c2896cc4cc3862c7379b51bb017.png

Archive 2.zip 332 kB · 0 download

Thank you!

  • Thanks 1
Link to comment
Share on other sites

  • 1 year later...

Hi Fabiosun, 

 

I run into similar issue with fusion 360 as of the latest release, I used to just copy over the libtbb@2020 version into the app but that no longer works. I see an error about code signing of these libraries but if I force sign the error changes in "libtbb.dylib' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)"

 

Trying to code sign with my personal developer cert throws another error in codesign:  Warning: unable to build chain to self-signed root for signer "Apple Development: xxxxxxx"

 

Any clue?

Link to comment
Share on other sites

Ok, solved the code signing issue but now I get this: "libtbb.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs)"

 

Original:

 

codesign -d -v libtbb.dylib

Executable=/Users/xxxxxxxx/Library/Application Support/Autodesk/webdeploy/production/091ac024abfbd3b18cc71f4f8bebd0095c5b58c6/Autodesk Fusion 360.app/Contents/Frameworks/AIRMAX/libtbb.dylib

Identifier=libtbb

Format=Mach-O universal (x86_64 arm64)

CodeDirectory v=20500 size=5490 flags=0x10000(runtime) hashes=166+2 location=embedded

Signature size=9048

Timestamp=6 Apr 2023 at 11:44:38

Info.plist=not bound

TeamIdentifier=XXKJ396S2Y

Runtime Version=10.12.0

Sealed Resources=none

Internal requirements count=1 size=168

 

 

Link to comment
Share on other sites

Ok, one step further again. If I force code sign the entire AIRMAX library folder with my own identity fusion starts up and I was able to open one of my files but after a few seconds crashes...

 

After some more tries this seems to be working... 😀

Edited by Rox67er
  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.