Just had to switch over to SW 2022 due to horrible 2021 performance. Now Rhino won’t open SLDPRT files or even import them. This happened with SW2021 files when they first released it too, but McNeel got it fixed really quick. Time to do it again!!
Rhino says it imported or opened the file properly but no geometry appears. Have to go the extra step of saving the SLDPRT file out as a STEP, then import. Not the end of the world but really slows down work flow and adds more files.
Hi Tim! Thanks for your reply. Version 8 is the WIP, correct?
I’ve attached a sample file from SW 2022. 2021 was running extremely slow for some bizarre reason so I reluctantly switched to 2022 yesterday. That’s why I’m suddenly running into this importing issue.
Yes, version 8 is the WIP and I have confirmed that V7 is not using the same SDK as V8. Thanks for the file. No need to test V8 if it’s inconvenient, I can do that myself now that I have a file to use.
Holy smokes, that’s awesome!! Thanks! Any idea how long it will take to get this change implement in the next update?
I go back and forth between the programs very frequently. The work-around is to just save out the bodies as a STEP and then either open or import them into Rhino. And rotate 90-degrees since the X and Y axis are always flipped. When I import an SLDPRT file directly, the axis are correct. Again, just saves a few steps so not the end of the world for it to not function at the moment.
If it were an STP file I would say the issue is with the MDB functionality, specifically an STP 242. If the SW file has MDB specifics, I would say that is likely the source of the problem without any additional info.
We are potentially discussing MDB, SolidWorks has a specific module for MDB capability, and these files and native functionality may not be compatible.
If you would like to resolve the problem you should submit the SW to McNeel in private so that they may attempt to resolve the problem, or provide additional info.
As McNeel has indicated, V8 uses a different SDK than V7.
MDB may have nothing to do with the issue, so please submit the file to McNeel in private so that they can determine the issue, … I am just speculating.