Thanks David. I tried this on my laptop and it didn't make any difference in speed regardless of which processor I assigned. Again, this all started with V25.Andy - have you followed instructions in Help regarding graphics adapters?
Articles
help.alibre.com
Also just as an experiment - in Alibre System options, try different graphics adapter settings. A couple of users have found that they need to set the integrated graphics there to allow Windows to actually use the high performance adapter. Not really sure why, but in modern laptop the integrated graphics adapter is always the one connected to the screen - in high performance mode it acts as a frame buffer for the other adapter.
I can also confirm that this method works for me.option 2: follow the procedure below (which is what I do because it only takes a few seconds)
- Right click Edit Here on the part you JUST EDITED (the second you do this you will see your part snap back to its constrained position if you moved it after editing)
-Then, immediately back out of this operation by going to the design explorer, then right click on the part name you are editing, then select the top most menu item (Edit Part/Subassembly). This will return you to your assembly file and let you continue to work. Hit save if you want, no need to though.
Almost as if the top level assembly display isn't updating when you leave the separate window. Does pressing F5 correct things?
How do you leave the separate window after doing edits? You should only need to close the separate window, you should not hit Save for example.
Hi All. I work with a number of different assembly files and all of them suffer from the same loss of constraints once the part counts get higher than a few dozen, and sometimes as few as a dozen parts. I was able to recreate the issue while on a zoom call with support, so they saw first hand how re-editing the just edited part magically snapped it back into position. Unfortunately, rotating the models, changing views, F5, or Regen doesn't restore the loss. The only thing that does is doing what was already described earlier. Look, not everyone edits a part and then moves it after editing it. I can imagine a lot of users editing the part, returning to the assembly, then working on some other part, and then saving the assembly and leaving. Upon opening the file the next time all constraints will work and you'll never be the wiser that a loss of constraint had even occurred. It just seems I'm always grabbing the part I just edited to move and rotate, etc. This was not a problem before V24.