![]() To be frank I would be getting my VAR on this with a fraction of these problems, and getting SW to dial in to look at the environment. Perhaps your environment is the issue or a big factor? What does the VAR say?īefore anyone jumps in I am not doubting your issues just surprised they are as severe as you say. I've used SolidWorks for over 20 years and never seen problems as bad as that. SolidWorks is used more often but we get maybe 1 crash every few days over 2 licenses. Creo has crashed 2 times in 6 months and one of them was when the license server failed. Typically we have assemblies with maybe 200 unique parts and thousands overall, with linked drawings with 20-30 sheets. ![]() We use SolidWorks, Creo and Fusion360 and Rhino here primarily with in context top down assembly or complex surfacing and master parts linked to assemblies and drawings. The screenshots you show are bread and butter stuff for most 3D CAD systems. Regardless of whether you are able to elaborate further or not on the cause of the crash, please accept my sincere thanks and I appreciate the prompt response and assistance for this matter very much.Im genuinely curious here. Would you be able to share and elaborate further on what is exactly causing the issue though? Because while this is a workaround, I am sure my users would like to know the cause of it and to see if we can do anything to the dwg file so that they do not need to use this workaround for every dwg file that might be having the same issues. i will get the user to try other files and to see if there are any other further issues with it or not. I tried using the above method ( open with Draftsight, using the explode command and then saving the file in 2010 format) and it did manage to resolve the issue ont the file which I sent you. Please check whether you are able to import the new DWG into DIALux 4.13.0.2. We have sent you the modified DWG file via email. Then it was possible to import the DWG into DIALux. We resolved the DWG file in DraftSight with the command "Explode" and saved it in 2010 format. So, we decided to open the DWG in DraftSight (DWG viewer from Autodesk). We are able to reproduce the crash in DIALux during the import process when using the original DWG drawing. Thank you very much for sending us your DWG file. I will appreciate if someone can assist me with the problem and show me how to resolve this. Hence after trying all these, I am still unable to resolve this though at least I can confirm that this isn't a workstation specific issue or OS specific issue since I tried it on various OS and workstations. Below are some of the things I have tried so far.ġ) Reinstalling Dialux 4.13 on the workstation which is running on Wins 10 OS.Ģ) Downgrading the DWG to autocad 2010 version.ģ) Installing Dialux 4.13.02 on other workstations that are running on different OS such as Windows 7 and Windows Server 2016Ĥ) Copying out the files and putting the files on local desktop and loading the file from local instead from the shared folders.Ħ) updating the graphic card drivers to the latest.ħ) Ensuring there is no "dell recovery software" on the workstation. I have tried a few things to troubleshoot this but as of now, i wasn't able to successfully load the DWG file. Are there any known issues regarding the loading of DWG and if yes, how can we resolve it?ģ) On the "guide" interface which is on the right, click on the "Load DWG or DXF File"ĥ) Browse to the location and select the "DWG" to load inside.Ħ) Once we click open, the popup will then freeze and not load anything. I installed Dialux 4.13 on one my users' workstation and everytime she try to use the load DWG or DXF file function, the screen will just freeze there and then there will be a "No responding message" for very long and the only thing she can do is to force shutdown the program. I hope this is the correct place and I hope I can get some help for it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |