Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I tried attaching the nameplate file that takes forever to update if you edit "Sketch 11" then close it to see how long it takes to regenerate and watch your CPU in the Task Manager it putters along and at the very last it will increase the Utilization. It is 11 meg so it wasn't accepted by your email server.
I haven't tried using the new Mark command to mark the Nameplates yet because we send a pdf of this out for laser etching. I think Mark will only do the outline of the letters but I'll try one and see.
[image: image.png]
Also I know I'm starting to sound like a broken record to the crash dummies but we really need to come up with a way to have IV save everything in the state it is when it crashes. That is the most frustrating thing I keep dealing with. At least let it not perform the offending command or function and send up a white flag telling us to save the current state. Rather than dump everything! I don't know how most users use IV but I'll have 5 to 20 processes going at the same time and when it crashes and shuts everything down it takes a while to remember what I was doing in each window.
I know the code is using error reporting internally so it should be able to flag a potential forthcoming crash and start a dump routine that would save all the model states of open files.
Thanks for sending me the problem part file - we'll do some performance profiling to see what the root cause issue is & follow up with you more through the Feedback Community.
File > Save- multithreading is used during the save process. A more advanced compression method is employed for packing data, which results in a reduction of file size.
Assembly Mirror- Multithreading is used for computing reused components and previewing assembly Mirror
Already tested locally - Assembly mirror can use ALL CPU cores in some cases. Mainly reuse for big assemblies.