stepalibre
Alibre Super User
This mean my tools that use multiple Alibre Design.exe instances don't work!
Now single instance only?
- Thread starter stepalibre
- Start date
I also have this issue every day since the PDM version released. I understand from some e-mail from support team that they must be working on fixing that. A new release of the PDM version will be much appreciated. I fix by just cancelling alibre.exe process in window process administrator so that can restart again.
stepalibre
Alibre Super User
I’m not sure what you mean by window process administrator but only a single running instance is allowed in the latest version. PDM shouldn‘t have anything to do with it. Since PDM and Alibre Design is the same exe I’m starting to see issues affecting Alibre Design.
I have a problem with a script error stating something about repository which I’ve never seen before. This sounds like a PDM problem. Next year I’ll take a closer look at it.
@Max any information about API and scripting problems with PDM release?
I’m aware of this:
Working with PDM
The FilePath property returns null if the file is inside PDM. It's likely all methods and properties that touch the file system will break.
www.alibre.com
Last edited:
simonb65
Alibre Super User
I suspect it's so only one instance connects to PDM from each machine, so that you don't get into all kinds of sync and access issues (not only to PDM but other external resources like user profiles, log files, etc). Not sure why you would want to run multiple instances from your code (a bit of use case would be informational). A middle ground would be to allow multiple instances if there was no PDM configured, that would retain backwards compatibility!
Single instance can only make the application more robust ... and that's a good thing, isn't it!
On a side note, multiple instances could be abused against just a single seat license as you could essentially run a parallel 'server' farm of geometry generation using the API ... and I'm sure that goes against the 'good will and bounds' of a single seat license!
I am not sure if this replies to my comment. I never needed multiple instances. I can open several files with only one process instance. When PDM version released I get almost every this message
because for some reason when I close Alibre the instance is not closed and I am forced to manually close it and re-open Alibre again.
stepalibre
Alibre Super User
I have programs that are headless, they start AD.exe, code runs and then kill the instance. Some use Alibre in headless mode and start the GUI perform work and kill the GUI all while the program is still running in the background. These are async jobs, they don't wait for the other instances to die before a new one is started. This is how my software work with other software for automation. To fix this I'll need to wait until one close before starting a new one.
Modern software prevent the licensing issues, especially software that have COM automation or an API. They'll check if you have a license prior to any code running. Each process is using the same license on that machine.
I haven't recently but when scripting with Python I often use multiple instances one for working with the API and the others for testing code. This is useful when debugging addon code and when using Alibre Python Shell. Each instance has its own memory space where DLLs are loaded. I load and unload DLLs when developing. A long story short, I use MOI3D CLI and Rhino/Grasshoppers running headless programs in the background all with multiple instances running headless. I may open Rhino or MOI and work in their GUIs, the background programs are always running waiting for the next job.
I understand PDM is not managing properly refresh data and check-in check out with multiple instance but with no PDM usage it should be allowed. PDM is in an early version about that, but I understand will be fixed soon. I agree multiple instance should be allowed anyway, I use most engineering software for design and simulation with and without scripting and all allows multiple instance with a single windows user, no issues with licensing.
stepalibre
Alibre Super User
PDM is affecting Alibre Design workflows. My software has nothing to do with PDM.
One Job is, load an Alibre model, read and update parameters, exporting to STEP, then using MOI and Rhino/Grasshopper to further process the file.
The solution is v27.
One Job is, load an Alibre model, read and update parameters, exporting to STEP, then using MOI and Rhino/Grasshopper to further process the file.
The solution is v27.
stepalibre
Alibre Super User
v27 side by side with COM configured seem to be an Ok compromise.