DS got it down to 1,0.
I’ve heard something similar about people who seem to always be breaking things. “He could tear up an iron ball with a rubber mallet.”
“Break an anvil with a banana” is the phrase I’ve heard regularly.
Got some more 3DX success stories for y’all…
I’m on Day 4 with no cloud save capability, and the application engineer from my VAR admits to being stumped. The path we’re going down now involves me creating an entirely new SolidWorks ID and 3DX user profile because, and I’m quoting here, “I think your current credentials might be haunted.”
Additionally, today I get to dine on a full diet of SPAM courtesy of the 3DX license checker:
Screenshot (30).png
To add insult to injury, I got this in an email from Dassault this morning:
I’m beginning to think they’re doing this to me on purpose…
Ouch, I feel your pain.
I can only imagine the frustration it’s causing you, but please know your tales from the 3DX front line are at least really useful from an educational point of view!
Do you have any Attributes set to read only on platform for your SW files? If so, that may be why save is failing. There is a regression in FD01 that was just released over the weekend that causes save to fail if an attribute on platform is set to read only. To work around it you can remove read only for the attribute for now until a fix is deployed.
Sounds to me like they really need a total revamp on the quality control.
On the desktop version you can live with SP0, 1 and 2 might have a major bug that will stop you working. You have the option not to load it on until the early release bugs are ironed out at maybe SP3.
Negative. I finally got a response from DS over the weekend, apparently there’s a bug that prevents SLDASM files from saving properly if they contain components in Released maturity state…so you know, just another one of their much-vaunted PLM features that just stopped working and brought my workflow to a grinding halt for a week.
The fix was actually pretty easy once the root cause was found, a quick trip into RegEdit and now I’m back up and running, but damn it’s annoying to do beta testing for this thing…
See, in our environment we would’ve tested new changes in a test environment prior to rollout into production. So this type of issue would likely get caught…especially something that basic. This is my problem with a cloud systems where they upgrade everyone to the latest changes and you have no choice but to accept it.
They already loved to change default setting in SW and break everything.
Looks like they got it on the cloud too.
Why I can’t access anything?
Oh we have a new setting to lock user out. We set it on by default on last update.
Well quit releasing things for fabrication…Problem solved…
The fix was actually pretty easy once the root cause was found, a quick trip into RegEdit and now I’m back up and running, > but damn it’s annoying to do beta testing for this thing…
We were/are all doing that for SW Desktop. So, why would DS pay for that service for 3DXP?
Even with Ry-Guy/Ryan3DS singing the praises of the platform, we still don’t have anything resembling a “success story.”
Yeap, they did.
3DEX Lock-01.jpg
Wow… <()> I hadn’t seen this one pass along.
Okay today I have a 3DX success story that involves actual success!
We’re ramping up for a limited manufacturing run with our product version 1.1, and our CEO decides to save some pennies by recycling some leftover parts and pieces we have from our 1.0 run. Now, we’ve done a great deal of design work on 1.1 and still intend to use those part and assembly files for most of the 1.1 run, but now need to incorporate these 1.0 parts in. I made a new branch of our 1.1 files designated for the incorporation of the old 1.0 parts, which I was able to switch back to from our 1.1 versions with a few clicks. Now we’ve got parallel dev branches so we can both continue on primary 1.1 and make necessary edits to incorporate the 1.0 parts into the new branch without affecting anything we worked on in the primary branch. Whole process only took about fifteen minutes and I never had to leave my SolidWorks window.
When it works (and that’s a big “when”), 3DX can actually be a a pretty useful tool. It definitely has a steep learning curve, and I think doesn’t make sense AT ALL if a customer has existing SW data mgmt infrastructure (i.e., SW PDM), but if you need to build a CAD database from scratch (as we did), it can in fact be used for that purpose if the admin is willing to endure some personal pain and frustration learning the thing.
Make sure you mark all the 3DX update dates and don’t plan to work on that date and 2 days after.
LOL
I was trying to create a new 3DX account today (gosh why am i doing this…) and wondering why i could not get through
Apparently 3DX only allow specific symbol for their password and the password that i tried to use contained “/” which is prohibited.
HOWEVER
My other account which is created long ago contained “/” and has no issue login… (well.. most of the time)
<()>
image.png
So, the artist formerly known as Prince would be good to go.