![]() The issue is caused by Windows Explorer hiding files and folders. However, that suggestion is not the case as doing this does not correct the issue. The specified path is too long", which would make you think the installation file location needs to be shortened. When installing DraftSight you might encounter the "Error 1320. The screenshots you show are bread and butter stuff for most 3D CAD systems.This article explains how to correct the problem with "Error 1320: The specified path is too long" when installing DraftSight. 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. Typically we have assemblies with maybe 200 unique parts and thousands overall, with linked drawings with 20-30 sheets. Creo has crashed 2 times in 6 months and one of them was when the license server failed. SolidWorks is used more often but we get maybe 1 crash every few days over 2 licenses. I've used SolidWorks for over 20 years and never seen problems as bad as that. 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. 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. I was a (very) early alpha/beta tester of Onshape but chose not to go down this route as the pace of development (or rather the path) did not suite our needs (complex surfaces needed), and the cost did not offer any benefits to existing license holders (compared to functionality and hassle of changing). We actually jumped onto Creo when that went subs only as well as Fusion. ![]() In my experience no single system does it all sufficiently well to make us most efficient.for us that rules out Onshape as we always need some off line capability. The issues are at their peak right now with Solidworks at our company, 2016 was mostly good.Ģ017 all hell broke loose. By the time we really knew how bad it was, we had a few projects done and was relatively too late to abandon and go back to 2016. ![]() We skipped over 2018 in fear of further problems (as has been the case with every release so far starting around 2016)Ībout a year or so ago I heard on Onshape and was not serious about it. I'm still in a forum thread in solidworks that has been un-resolved from 2015) I finaly gave up on that thread a couple days ago with a simple: But I stated paying attention to the updates, and the very non-toxic community on the forum (People actually know what they are talking about most of the time. I mean look at how terrible that work around is. Onshape has the advantage that we can share our documents directly with the forum, or support. Which doesn't required copies of the file, or having to repeat the Fix into your main project. Onshape has it's problems, but most of the ones that really bite me with SW are inherent in the fact that it is a piece of software on a computer. Each computer could be slightly different in setup/configuration. Each File is "locked" if someone has it open (even with eDrawings in the shop) So if you open a file and it says read only, it may be a 5 minute adventure as you check everyone's computer for eDrawings being open. When you have a couple people working on the same area of a project, it becomes a game of hot potato with each file as you swap around between readonly and write access. Some bugs are only on one person's machine, some are on all. Some are so bazaar there is no telling what the cause was. With a cloud based system, it comes down to "Was this on firefox, chrome, etc" otherwise we all see the same bugs and (I'm sure) that makes it much easier to chase down the bugs on Onshape's end. These reasons are the main reasons Onshape was founded, and they have certainly addressed most of these issues flawlessly. In my experience with SW the issues come in waves. #Draftsight 2016 not responding windowsĮither with releases, SPs, Windows updates and so on. So yes, most of the time the instability is more of an "ecosystem" no just the software, but once you experience not having to deal with that crap, it's hard to go back.Microsoft Excel is utilized in SOLIDWORKS by embedding or linking an Excel-based table. #Draftsight 2016 not responding windows.#Draftsight 2016 not responding license.#Draftsight 2016 not responding software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |