stock model goes dirty when saving

Started by Programinator, December 19, 2022, 05:15 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Programinator

on 2022.  why does stock model randomly dirty stock model when saving file?  anyone else see this?
Mastercam 2022 update 3.1
Dell Precision 7530
Intel i7-8850H, Six Core 2.6GHz, 4.3GHz Turbo, 9MB Processor
32GB NECC RAM 2666MHz
4GB NVIDIA Quadro P2000 Video Card


JakeL

I'm also seeing this.

Sometimes the stock model will be displaying wrong, but it won't be dirty. For example sometimes it will show 2 separate pieces of stock. Or after updating one of the stock dimensions it will regenerate and not show the update.

Whenever I see this issue I save and that causes the stock model to go dirty. When I regenerate, the stock model displays correctly.

Jeff

I don't use linked planes, but I swear I've seen this happen once or twice.

Wait, If you count creating planes relative to another user created plane then I do use linked planes often.

crazy^millman

Quote from: Jeff on December 20, 2022, 07:44 AMI don't use linked planes, but I swear I've seen this happen once or twice.

Wait, If you count creating planes relative to another user created plane then I do use linked planes often.

Ding Ding Ding we have a winner. Why Linked planes came about since they were already linked and we were not aware they were when using relative to for plane creation.

svnmlkdmf

I never created a relative plane, I always felt like that was asking for trouble, I actually try to avoid making them at all for operations unless i really need to, then i lock them

svnmlkdmf

I haven't ever had those issues, but i haven't worked on parts as complex as the ones all y'all do

svnmlkdmf

If you guys can duplicate this in a file, I can probably make a patch for it and send that to CNC to look at, but i dont see the problems you have been talking about for years

crazy^millman

Quote from: svnmlkdmf on December 20, 2022, 09:07 AMIf you guys can duplicate this in a file, I can probably make a patch for it and send that to CNC to look at, but i dont see the problems you have been talking about for years

They are aware of my issues and they have the ITAR files to review them to get to the bottom of it. I have about 6 numbers all related to different things I have found in the last couple of months. Thanks for offering to help. I also found out about the 200 solid limits and the issues that creates in Mastercam.

Dylan Gondyke

We got a file for this a few days ago and we're on the hunt. I think we have a good idea of the cause...

The linked planes dirtying stock is a separate workflow issue that should be more visible in 2022 onwards, but is not what I'm referring to here.
Toolpath Systems Product Owner- Mastercam

Programinator

I dont use linked planes.  At least I don't think I do.  If linking a plane is telling the stock model to reference a plane is linking a plane then yes I do link a plane.
Funny Funny x 2 View List
Mastercam 2022 update 3.1
Dell Precision 7530
Intel i7-8850H, Six Core 2.6GHz, 4.3GHz Turbo, 9MB Processor
32GB NECC RAM 2666MHz
4GB NVIDIA Quadro P2000 Video Card

crazy^millman

Quote from: Dylan Gondyke on December 20, 2022, 02:14 PMWe got a file for this a few days ago and we're on the hunt. I think we have a good idea of the cause...

The linked planes dirtying stock is a separate workflow issue that should be more visible in 2022 onwards, but is not what I'm referring to here.

Dylan the fact it is a known issue is more of the idea than anything. Nothing worse than fighting something and submitting it and not getting a response or we have never seen that before it must be you as the only person in the Mastercam Community seeing it.

Dylan Gondyke

Quote from: crazy^millman on December 21, 2022, 05:59 AMDylan the fact it is a known issue is more of the idea than anything. Nothing worse than fighting something and submitting it and not getting a response or we have never seen that before it must be you as the only person in the Mastercam Community seeing it.

I just had a chat on the 200 limit item with the Product owner because it wasn't a known issue. It's an active area right now and they're looking at options- even for 2023. I like to review tech support items where I can, as oftentimes they aren't armed with the same broad spectrum of information as QC, or higher, say. This isn't an excuse, but a tech support person is expected to be an expert at anything and everything they can possibly touch in Mastercam, and that's just impossible if, say, they get a question from a user that's been using 4 axis HMC's for 30 years and is at the highest level in terms of process knowledge for that specific area. Even I can't do that. I don't know the ins and outs of setup sheets, for example, and if you showed me a setup sheet bug and I couldn't immediately match it up with an existing request, it'd certainly be new to me.

It's easier if it's NOT new, as that means there's an existing R # and it doesn't have to be tested and written up from scratch, but information and test cases simply appended. You and I have talked about communication and response in the past Ron, and I'm certainly not defending some of the Tech Support response times or effort, but I can promise that things don't just fall on deaf ears or get ignored.

Like Like x 3 View List
Toolpath Systems Product Owner- Mastercam

crazy^millman

Quote from: Dylan Gondyke on December 21, 2022, 11:26 AMI just had a chat on the 200 limit item with the Product owner because it wasn't a known issue. It's an active area right now and they're looking at options- even for 2023. I like to review tech support items where I can, as oftentimes they aren't armed with the same broad spectrum of information as QC, or higher, say. This isn't an excuse, but a tech support person is expected to be an expert at anything and everything they can possibly touch in Mastercam, and that's just impossible if, say, they get a question from a user that's been using 4 axis HMC's for 30 years and is at the highest level in terms of process knowledge for that specific area. Even I can't do that. I don't know the ins and outs of setup sheets, for example, and if you showed me a setup sheet bug and I couldn't immediately match it up with an existing request, it'd certainly be new to me.

It's easier if it's NOT new, as that means there's an existing R # and it doesn't have to be tested and written up from scratch, but information and test cases simply appended. You and I have talked about communication and response in the past Ron, and I'm certainly not defending some of the Tech Support response times or effort, but I can promise that things don't just fall on deaf ears or get ignored.



I don't think they do and don't mean to come across that way, but I am extremely anal and have many years of communication with D-R-S numbers that I reference and ask about from time to time. If I only had a dozen ore so of them then might not be a big deal. I have well over a 100 of these numbers over the years. My experience is probably a lot different than a majority of users. 

CNCAppsJames

I stopped keeping track of requests and bug reports in the early 2000's IIRC. I really didn't have/couldn't come up with an effective way to track them myself so it really just didn't make sense for me.
"That bill for your 80's experience...yeah, it's coming due. Soon." Author Unknown

Inventor Pro 2026 - CAD
CAMplete TruePath 2026 - CAV and Post Processing
Fusion360 and Mastercam 2026 - CAM