TestExec build exe pops up many "Loading:" messages when running custom Operator Interface build

[DLMC]

My specifics

Windows 10 Enterprise

Labview 2022 Q3

I have a TestExec build .exe that uses TestStand and Labvew parts in a custom Operator Interface that is running fine, mostly.

I built all of this with teststand configured in developer mode.

I did a mass compile with no problems and built my lvproj again with no errors.

BUT

I keep getting these windows with a bazillion "Loading" messages while the program is running.  How do I turn those "Loading" messages off?, or get all the loads to be done up-front instead of along the way?  If that is what is happening.

Any clues appreciated!

Be well,

DLC

[Kyle97330]

It's been a while since I used TestStand but I remember there being settings that control whether files needed to run steps are preloaded, or only loaded at run time.

This is the only page online I could find referencing it:

https://www.ni.com/docs/en-US/bundle/teststand-api-reference/page/teststand-api-ref/db_preload_progr...

Have you looked into those settings at all?  I haven't used TestStand in 5ish years, so any specifics beyond that escape me at the moment...

[DLMC]

That kinda sorta looks like what I am referring to.  I don't get a progress bar though.  I left the TestStand settings as they came default.  I note that all my Load options are "Preload when execution begins" rather than on-the-fly.

There are a ton of things I don't fully understand with this (I inherited the code and am porting it to a MUCH newer LV and TS version.)

The LV stuff I pretty well get by now after a couple of months, but TestStand is still about 50% a mystery and getting a custom OI to work like I want it is a challenge.  Every "fix" I make tends to break something else, not uncommon with programming, and debugging callback code is not fun, but still...

A voyage of discovery this is.

On a related topic, does it matter to a built exe if it is created in run-time or developer mode in TestStand?

Thanks for the pointer, I will go down that path and see what I find.

be well,

DLC