Dynamo Revit 2025 Package not show

chuongmep commented 7 months ago

Dynamo Version

3.0

Revit Version

2025

Operating System

windows 11

What did you do?

Open Dynamo with package loaded

What did you expect to see?

See the tree package at the left side

What did you see instead?

Nothing

Stacktrace/logs

No response

Details

image

mjkkirschner commented 7 months ago

hi @chuongmep can you share your dynamo log?

chuongmep commented 7 months ago

hi @chuongmep can you share your dynamo log?

I saw some issue here :

Dynamo log started 2024-04-04 15:55:10Z
Python template set to default.
Dynamo -- Build 3.0.3.7597
System.InvalidOperationException:
There already exists an AlsoKnownAs mapping for DSCoreNodesUI.Logic.If.

System.InvalidOperationException:
There already exists an AlsoKnownAs mapping for If.

Duplicate migration type registered for SunPathDirection
launch darkly initalized
LD startup time: 302 
<<<<<InitDone>>>>>
feature flag exe starting
<<<<<Sod>>>>>
{"testFlag":false,"CER_v2":true,"graphics-primitive-instancing":false,"CER":false,"IsNewAppHomeEnabled":false,"IsTSplineNodesExperimentToggleVisible":false,"EasterEggIcon1":false,"NodeAutocompleteMachineLearningIsBeta":true,"EasterEggMessage1":"NA"}
<<<<<Eod>>>>>
The folder 'C:\Program Files\Autodesk\Revit 2025\AddIns\DynamoForRevit\Built-In Packages\Packages' does not exist
Dynamo will use the package manager server at : https://www.dynamopackages.com
The folder 'C:\Program Files\Autodesk\Revit 2025\AddIns\DynamoForRevit\Built-In Packages\Packages' does not exist
A package called DynamoPlayerExtension found at C:\ProgramData\Autodesk\RVT 2025\Dynamo\3.0\packages\DynamoPlayerExtension includes dll files but none are defined in node libraries in the package manifest.  Ignoring it.
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPRevit, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPUI, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPSandbox, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPCad, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPRevit, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPUI, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPSandbox, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPCad, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPRevit, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPUI, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPSandbox, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPCad, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPRevit, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPUI, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPSandbox, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPCad, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPRevit, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPUI, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPSandbox, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
Incorrectly formatted package node library encountered, this may result in a package assembly not being loaded!
This is the incorrectly formatted library name: OpenMEPCad, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null
The folder 'C:\Users\chuongho\AppData\Roaming\Dynamo\Dynamo Revit\3.0\packages\OpenMEP\dyf' does not exist
The folder 'C:\ProgramData\Autodesk\RVT 2025\Dynamo\3.0\packages\DynamoPlayerExtension\dyf' does not exist
Dynamo Player Extension (id: 3CD8E967-22D5-46C7-8E08-316BC53AEA1D) extension is added

chuongmep commented 7 months ago

This is end of section log :

The folder 'C:\ProgramData\Autodesk\RVT 2025\Dynamo\3.0\packages\GenerativeDesign\dyf' does not exist
The folder 'C:\ProgramData\Autodesk\RVT 2025\Dynamo\3.0\packages\GenerativeDesign.Extension\dyf' does not exist
Generative Design (id: DFBD9CC0-DB40-457A-939E-8C8555555A9D) extension is added
The folder 'C:\ProgramData\Autodesk\RVT 2025\Dynamo\3.0\packages\GenerativeDesign.Revit\dyf' does not exist
DynamoPackageManager (id: FCABC211-D56B-4109-AF18-F434DFE48139) extension is added
Backup files timer is started with an interval of 60000 milliseconds
SYSTEM:Environment Path:C:\Program Files\Autodesk\Revit 2025\en-US;C:\Program Files\Autodesk\Revit 2025;C:\Program Files\Common Files\Autodesk Shared\RealDWG Shared 2025;C:\Program Files\Microsoft MPI\Bin\;C:\Program Files\Microsoft\jdk-11.0.16.101-hotspot\bin;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\compiler;C:\Python311\Scripts\;C:\Python311\;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.2\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.2\libnvvp;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\ProgramData\chocolatey\bin;C:\Program Files\Git\cmd;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\dotnet\;C:\Program Files\Common Files\Autodesk Shared\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\NVIDIA Corporation\Nsight Compute 2023.2.1\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\ProgramData\nvm;C:\Program Files\nodejs;C:\Program Files\Common Files\Autodesk Shared\Advance\;C:\Program Files (x86)\Common Files\Autodesk Shared\Advance\;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Cloudflare\Cloudflare WARP\;C:\Users\chuongho\anaconda3;C:\Users\chuongho\anaconda3\Library\mingw-w64\bin;C:\Users\chuongho\anaconda3\Library\usr\bin;C:\Users\chuongho\anaconda3\Library\bin;C:\Users\chuongho\anaconda3\Scripts;C:\Users\chuongho\AppData\Local\Microsoft\WindowsApps;C:\Users\chuongho\AppData\Local\GitHubDesktop\bin;C:\Users\chuongho\AppData\Local\JetBrains\Toolbox\scripts;C:\Users\chuongho\.dotnet\tools;C:\Users\chuongho\AppData\Roaming\npm;C:\ProgramData\nvm;C:\Program Files\nodejs;C:\Program Files\Autodesk\Revit 2025\AddIns\SteelConnections;
RENDER : Rendering Tier: 2
RENDER : Pixel Shader 3 Supported: True
RENDER : Pixel Shader 4 Supported: False
RENDER : Software Effect Rendering Supported: True
RENDER : Maximum hardware texture size: 16384,16384
RENDER : ProcessRenderMode: Software
RENDER : Rendering Tier: 2
RENDER : Pixel Shader 3 Supported: True
RENDER : Pixel Shader 4 Supported: False
RENDER : Software Effect Rendering Supported: True
RENDER : Maximum hardware texture size: 16384,16384
RENDER : ProcessRenderMode: Software
Documentation Browser (id: 68B45FC0-0BD1-435C-BF28-B97CB03C71C8) view extension is added
DynamoManipulationExtension (id: 58B0496A-E3F8-43D9-86D2-94823D1D0F98) view extension is added
Properties (id: 28992e1d-abb9-417f-8b1b-05e053bee670) view extension is added
Graph Node Manager (id: F76F4274-537D-4782-B1E9-27E8FDE2186F) view extension is added
LibraryUI - WebView2 (id: 8b093acd-5656-4914-b6b0-c54b26ca6d0e) view extension is added
Graph Status (id: 3467481b-d20d-4918-a454-bf19fc5c25d7) view extension is added
Notifications (id: ef6cd025-514f-44cd-b6b1-69d9f5cce004) view extension is added
Package Details (id: C71CA1B9-BF9F-425A-A12C-53DF56770406) view extension is added
Open MEP View Extension (id: 4811E3B2-1B98-4E9E-B34F-BD62AAFFF367) view extension is added
Generative Design Tools (id: DFBD9CC0-DB40-457A-939E-8C8555555A9D) view extension is added
PackageManagerViewExtension (id: 100f5ec3-fde7-4205-80a7-c968b3a5a27b) view extension is added
Python Migration (id: 1f8146d0-58b1-4b3c-82b7-34a3fab5ac5d) view extension is added
Workspace References (id: A6706BF5-11C2-458F-B7C8-B745A77EF7FD) view extension is added

Welcome to Dynamo!

mjkkirschner commented 7 months ago

look here: https://github.com/DynamoDS/Dynamo/blob/bbc17790b6afd1df0a6e82b6a038737f93cdb513/src/DynamoPackages/Package.cs#L454

I guess OpenMEP is your package? The library names in the nodeLibraries entry are not valid assembly names in net8.

chuongmep commented 7 months ago

@mjkkirschner yes, that is libary I'm maintaining, so it is news in 3.0 ? I don't have any issue with Dynamo Revit 2024. I don't know what exact meaning incorrectly formatted library name, do I need follow any new standard ?

mjkkirschner commented 7 months ago

very likely because of changes in .net48 and .net8 - you can see that the old assembly name constructor did not pre parse the value:

net48 https://referencesource.microsoft.com/#mscorlib/system/reflection/assemblyname.cs,385

vs

https://github.com/dotnet/runtime/blob/5535e31a712343a63f5d7d796cd874e563e5ac14/src/libraries/System.Private.CoreLib/src/System/Reflection/AssemblyName.cs#L36

chuongmep commented 7 months ago

Thank you @mjkkirschner , I will try expand more time to fix that.

avidit commented 6 months ago

@chuongmep please keep us updated

chuongmep commented 6 months ago

Hi @mjkkirschner @avidit , this is problem I resolved recenlly but it make so anoy to moidify all the Assembly, I will share way how I resolve the problem :

First at all, I need to change to correct version assembly match:

<AssemblyVersion>2.0.0.*</AssemblyVersion>

to

<AssemblyVersion>2.0.1.0</AssemblyVersion>

And then In config of file pkg.json I'm also set correct version of assembly 👍

"node_libraries": [
"OpenMEPRevit, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null",
"OpenMEPUI, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null",
"OpenMEPSandbox, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null",
"OpenMEPCad, Version=2.0.0.*, Culture=neutral, PublicKeyToken=null"
]

Now

"node_libraries": [
"OpenMEPRevit, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null",
"OpenMEPUI, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null",
"OpenMEPSandbox, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null",
"OpenMEPCad, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null"
]

The main reason I'm still using the assembly version * because I want it automation update number without modify assembly version.

emru-y commented 6 months ago

Hi @chuongmep,

There was a similar discussion here regarding the assembly update automation: https://forums.autodesk.com/t5/vault-forum/how-to-update-automatically-parent-assemblies/td-p/10819689.

DynamoDS / DynamoRevit