No Message Maker wizard in LV25

[Jonzarwal]

Hello,
I have this problem since I upgraded to LabVIEW 2025 (from LV20). Impossible to see the create message wizard when right clicking a method. It works well with actors inheriting from the vi.lib, but not when it's from my own AF ppl.

Something fun is that the right click / New / Actor from "My Computer" works and create a child of my AF PPL lib.

To sum up, when using a ppl, Create Actor works, Create Message does not.

Anybody has the same behaviour?
I let attached a simple project to reproduce.
Thanks!

[justACS]

Thanks for posting.  We'll take a look.

[justACS]

Also, I assume it worked in the prior version you were using?  Which version was that?  And you moved to 2025 Q3?

[Jonzarwal]

Indeed. I used LabVIEW 2020 and move to 2025 Q3. I decided to move all my libs to 2025 to start my new projects with the latest LV. Rebuild the AF PPL from scratch, and then my child libs from this new AF. Everything runs fine, but the wizard is dead.

[justACS · Accepted solution]

I'd like you to try one more thing for me, if you can.  When R&D pulled the latest open source AF into 2025 Q3, they missed the AF Debug folder that resides in the Resources folder.  We've had a few issues crop up around debugging, and I'd like to make sure this isn't an expression of the same problem before we do a deep dive on cause.

Can you please install the package Actor Framework 2024 for 2020 on your machine, rebuild your PPL, and let me know if the problem persists?  This package is the complete AF that was supposed to ship, and uninstalling it restores the version that did ship.

[cbutcher · Accepted solution]

If that doesn't work, can you describe how you build your PPL? (Or perhaps, from where?)

AF checks a partial path to determine when something is an Actor, for the purposes of the MM - when I build my AF PPL, I do so from a copy of sources that are not in vi.lib (and perhaps have a different parent folder name, ActorFramework Vs Actor Framework, or something?), and so I have to update a VI in the frameworks folder to shorten the path to match.

If you're doing something similar, you may need to change the same VI (I'll check where it is if that sounds plausible, or you may be able to find me mentioning it somewhere else in this forum).

[Jonzarwal]

Hi everyone, thank you for your help. The issue is now resolved.

I was already using Actor Framework 2024 for LabVIEW 2020, but it had been built from a GitHub download and installed in a location other than vi.lib. Like cbutcher, I believe the issue was caused by that installation path.

What I did:

- Installed the latest versions of Actor Framework and the Actor Framework Project Provider on my LabVIEW 2025 machine using VIPM (just to be safe).

- Rebuilt my Actor Framework PPL, this time pointing to the lvlib in vi.lib, without changing anything else (thanks to this new version!).

- Tested it in my project — it works. I still get a warning when opening the project, so I may need to rebuild some intermediate classes.

I still need to verify that everything also works correctly for my Linux RT–based project, but I’m confident it will. I’ll keep you posted with the results.

[Jonzarwal]

It’s also working on my cRIO project.
So, here’s what I’ll note for the future:

• Use the latest version of Actor Framework available on VIPM.

• Build the PPL by targeting the lvlib located in vi.lib, without making any modifications.

Again thank you for your help.

[justACS]

I'm glad it was that easy.

BTW, it's worth noting that, even if you are using a PPL, you need to keep the source AF code in vi.lib.  The tools make use of templates that source code, and they won't work if you remove them.