Solidworks 2013 Crack Only
Lihue Barken
I am trying to determine if this is a Solidworks issue or a Windchill issue. We use Work Group Manager to manage our Solidworks files in PDMLink 10.2 m030 - randomly, when a Solidworks part file is placed into a workspace to check in to PDMLink, it becomes "Read only" and cannot be opened to modify
My drafter has saved a copy of the part on his desktop, unchecked the "Read only" box, filed - then placed part back in workspace overwriting the "Read only" part, closed out, reopened the part and it reverts back to "read only". We have checked everything on the solidworks side, making sure the part is configured properly to keep it from being "Read only", so inquiring if anyone else has seen this happen with PDMLink Work Group Manager... any suggestions?
Symbol looks like the part is being converted to a Toolbox. If you did a save as from an original toolbox part to create this custom part it will maintain Toolbox status. Here is a link to a video I found on youtube about how to separate a part from toolbox.
So I've pulled my hair out over this for months. I've looked up every "resolved" solution and tried it. I've rebuilt the part from scratch at least 5 times. STILL, every friggin' time I SEE a solid part, when I export it to the people on the other end using Solidworks ALWAYS get surfaces only!!
7-Rather than give me just thick walls, I end up with a full body extrusion. So I sketch on the new surface the area of the bodies center that I wish to cut and then extrude-cut backwards the center body back to the last plane/layer.
Sounds like it's a translation issue with Solidworks... I wouldn't worry too much about it, sometimes you, or someone else, just need to fix things on their end. You say your design is not open to sharing, can you make a generic part, see if you can recreate the issue and post that part?
well, I have had the reverse of this with Solidworks... they tried every option to export their info for me to use in IV, nothing worked... in the end, I just had to use what they sent, there was no way to fix it and make it useable in IV. it's not like he's saying that no information is being produced, it's just being produced as surfaces.... yes, I know not the best answer, but he can't sit there doing the same thing over and over until he retires, lol
Yes, I'm aware that IV will export a .sat file... but if "indeed" IV is causing translation issue, it would be better to try at least (1) example of exporting the data from a different program, plus I've used this method with .obj and .iges in the past to "fix" issues with exports. so it's worth a try.
Here's an example of my current issue. I have a C7.1 Teir 4 Acert Engine model from our sister company that was provider by the CAT engine reseller. The entire engine model is surfaces, containing over 6000 little surfaces. When opened in SW, these surfaces are grouped together in the browser by part #:
edit: the part I forgot to mention was that both SW and IV were exporting .iges / .step. and .obj files that were causing MODO to crash... but 3D Max created one that worked, that's why I mentioned the above workflow as a possibility.
Hi! Without seeing the actual files, it is almost impossible to determine who is at fault. Any translation issue can be due to issues at Importing end or Exporting end. It is possible SWX does not translate the geometry properly. It is also possible INV does not export it properly. INV can open SWX files directly. Did you try direct translation?
I built this open-file function in PowerShell for a GUI I wrote that lets you find and open various files on a server. I mainly use it for opening SolidWorks files as read-only, but also for PDF files and it should work for just about any other file if there is a file association for it.
The problem is that sometimes it doesn't work when opening the sldprt files. SolidWorks will either ignore the open file request or it wont open as read-only. I think this is mostly just a solidworks issue as sometimes it wont open files when double clicked on from windows explorer.
Anyway my solution is to set the file attribute to read-only. start a job that opens the file in SolidWorks, and then waits for the SolidWorks process to go idle before removing the read-only attribute. It does this through an event that watches for the job state to change. Since this is running through a GUI it has to be done in the background to prevent the GUI from locking up.
I know its a old question, but i was wondering if you ever managed to get a solution?If not, there is a few things you could try: first off, if your code is opening any other file just fine, it does not seem to be there the problem is.
File association with all SLD-files are working most of the time; but we do see it going bad from time to time (often related to updates), in that case, double-check that all SLD-file types are set to open with 'Solidworks-Launcher' (and not Solidworks directly).Using the launcher, will ensure Solidworks does not try to open a file, into an already running instance of Solidworks.
Also, try to check the following: Solidworks Options -> Collaboration ->'Enable Multi-user environments'... is this set?whatever state it is in; try changing is to the opposite.That checkmark is allowing multiple Solidworks-users to open the same file at the same time, and it does so by changing the read-state of the file, back and fourth.(it could be it is interfering with your code)
This can't be right?! You check out a file in SOLIDWORKS PDM then you open it in SOLIDWORKS. But, for some reason, it still shows as read-only in the title bar! What the heck is going on?
SOLIDWORKS PDM, of course, uses the check-out/check-in method to manage this situation. Occasionally, both mechanisms kick in at the same time, causing a file to be checked out by PDM but marked as read-only by SOLIDWORKS.
GoEngineer delivers software, technology and expertise that enable companies to unlock design innovation and deliver better products faster. With more than 35 years' experience and tens of thousands of customers in high tech, medical, machine design, energy and other industries, GoEngineer provides best-in-class design solutions from SOLIDWORKS CAD, Stratasys 3D printing, Creaform & Artec 3D scanning, CAMWorks, PLM, and more
Quite often I see SOLIDWORKS users struggle with the display of parts and subassemblies in a bill of materials (BOM). A common way is hiding the unwanted rows in a BOM, but this can lead to a lot of manual work and a high risk of errors. In this tech blog I want to show you different options to manage the display of components in the BOM. These options can all be applied at assembly level, so the BOM will use these settings.
You want subassemblies B and C to appear as dictated by the BOM Type (Top-level only, Parts only, or Indented) setting. But you want A to appear differently. In this case you can use the Child component display when used as a subassembly options to override the BOM Type setting.
As we have seen, you can greatly influence the display of subassemblies in a bill of materials with the help of the Child component display when used as a subassembly setting. This can be very useful when you add a subassembly of a buying component. Such a component should be listed as one item in the bill of materials. By hiding the child components of this subassembly, you can achieve this.
We also use third-party cookies that help us analyze how you use this website, store your preferences, and provide the content and advertisements that are relevant to you. These cookies will only be stored in your browser with your prior consent.
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
Are you importing a sldasm / sldprt models or did you do an export to udatasmith from solidworks?
Which version of the engine are you using?
Can we get a copy of the log file that is in the Saved>Logs folder of the project?
Current datasmith exporter for solidworks are for version 4.27 and above of unreal. I am thus expecting that if you export a datasmith scene from solidworks it will be partially to fully incompatible with UE 4.23.
image606878 24.1 KB
If you really need to use 4.23 you could try to import the sldasm file in UE instead, still with datasmith. Again, many things have changed on CAD import since 4.23 so I would switch to a newer version to get the newest perks of content import and everything else in the engine.
The first step to take to maximize your large assembly performance is to update your SOLIDWORKS software. I cannot understate how important it is to be using the most current version of SOLIDWORKS. With every major release, SOLIDWORKS spends a big chunk of resources on performance improvements which have a direct impact on large assemblies, or flashy new buttons and slick new features. Rather, the updated release just contains improved code that amounts to huge time savings.
Take a look at the image below which categorizes the enhancements to the latest release. For SOLIDWORKS 2021, more than 50 percent of the improvements were to improved quality and performance, while less than 25 percent were to enhancements. This sort of break down has been a common theme throughout the decades of SOLIDWORKS major releases. The latest release of SOLIDWORKS 2021 has some incredible time savings improvements that you unlock by just installing the latest version.
One example of how these improvements manifest themselves in an update is that the heavy lifting of performance (graphics) is improved so that the GPU is doing more of the heavy lifting instead of the CPU. This amounts to a quicker, more responsive and snappier experience when using SOLIDWORKS. Ask yourself, do you want better performance? The first, and arguably best step you could take is to update to the latest version.
7fc3f7cf58