If I star an optimization study, the log reports that Creo2 is being started in the background.
The command shell opens, xstop is listed in the active processes, bu then nothing happens.
The model is really simple, resources are not a problem, but Creo does not seem to update the features selected for the optimization.
Does the log report that Simulate is trying to recover from an invalid parameter update?
You can create a Sensitvity Study, with the same variables and bounds as the optimization, and Shape Animate the model. If the model updates successfully while stepping through the different Shape Animate values, then there is a much better chance that the model will update successfully when it is running an Optimization study
I opened a case over 1 month ago with PTC regarding this same issue where the run appears to start but never completes. So far, I haven't recieved an answer from PTC. Sorry for the bad news. I have a call into PTC today to inquire on the status. Once I find out something, I'll let you know.
Last Friday I also experienced this issue. Same thing. Simple model with some forces, some shell elements and some simple displacement constraints. The standard static structural analysis ran beautifully. But when I tried to run either a sensitivity or design optimization study, both got stuck in this endless loop trying to open up "Creo in the Background". I've also seen several other users have this issue but have not had an answer just yet.
I have issued a case, talked to them on the phone for about a half-hour and then eventually uploaded the part file with the simulation definitions. They said they would have to get back to me. Not very hopeful they'll have a solution.
You guys have any ideas?
Exact same problem happening to me today. Ran many modal optimizations yesterday without problems. Can't have anything running today.
Well PTC couldn't recreate the issue after uploading my model to them.Of course they suggested updating to the latest datecode which currently is M120 (M130 is available after 4/21/17).
After upgrading to the latest datecode I do not have this issue anymore. Perhaps they have patched it?