V6 and SolidWorks 2018


#1

Hi is there a time-line for V6 to be updated to import SolidWorks 2018?

Thanks,
Eric


(Pascal Golay) #2

Hi Eric - I think that is in the works - not that that answers your question very well…

(@lowell, am I correct about that?)

-Pascal


(Lowell Walmsley) #3

I think so. @tim did the update


#4

Great, thanks for that.

Eric


(Tim Hemmelman) #5

Hi Eric,

Yes, it is in the works (both Windows and Mac platforms). I have it all hooked up at this point (on Windows) but I get repeated crashes opening some files. I have inquired with the company that develops the library we use but have not yet had a chance to implement their suggestion. It will not be included in V6 until I can get the crashing problem resolved.

Cheers,
Tim


(Kyle Houchens) #6

@tim any updates here? I’ve received several requests from users on this subject-


(Tim Hemmelman) #7

Hi @theoutside,

The DataKit people have not fixed the crash yet, I’ve sent them some files. However, in the midst of trying to figure it all out I determined that the crash only occurs in debug builds on Windows. Even more interesting is I tried to see what was different with previous library and found it had the same crash. So, I asked Lowell about it and we decided it was OK to go ahead and merge it in. See https://mcneel.myjetbrains.com/youtrack/issue/RH-43442 for details.

Tim


(Pascal Golay) #8

@theoutside - 6.2 builds open SW 2018 parts.

-Pascal


#9

Thanks Tim.

The other recurrent issue with SW import is that it seemingly randomly ignores the color of SW bodies and parts. Not too surprising considering how complicated applying appearance is in SW; it can be applied at face, body, part and assembly level. But it was better for a while back with the 2016 version it seems like.

Eric


(Tim Hemmelman) #10

HI Eric,

You can send in a simple file (the simpler the better) that demonstrates the errant behavior. All I’ve done to the plugin recently is hook up the new library. How long ago was it “better”? I can look through the change logs and see if I can pinpoint some change (of our own) that might account for it. If it was a change in the library we use it will be complicated. Now that I think about it, it would be handy if the file you send I can pass along to them in the event I need to.

Tim


#11

Hi Pascal, any idea when 6.2 build will be available?

Thanks,
Eric


(Pascal Golay) #12

Hi Eric - it is the current release candidate, so you can get it by setting you updates (Options > Updates and statistics) to look for ‘Service Release candidates’.

-Pascal