Measuring errors - Inventor 2018

[Anonymous]

I'm lost here. I have a sub assembly (made by a retired fella) adding trailing .9999.... to every measurement in the modeling window. For example, a part file measures 25". In the sub assembly, it measures 24.999 repeating. Then again in the master assembly, that same part measures correctly. Is there a scaling issue that can be changed or something?

[mcgyvr]

Not really..

You can derive/scale parts..

Can you post one of the parts here thats showing this issue?

Is the model tree still present for all parts? (if so good.. if not that would indicate they have been saved to a neutral format or imported files,etc..)

[Anonymous]

Mcgyvr, 

Thanks for the response. There are no apparent issues with anything in the model tree. This is occurring with various parts, both designed and imported purchase components, but not all. For example, there's an imported telescopic rail. Of the 2 components in that lower assembly, 1 reads correct at 1170mm, while the other is 1169.999. So this occurs with both standard and metric parts.

I've never come across this outside of this particular assembly.

[Anonymous]

Adding the working part file.

[kgilham]

WagnerBEP,

Can you also add your sub-assembly and top level assembly?  If I just add this part to a sub-assembly I don't see this issue.

Thanks,

[mcgyvr]

I'd bet you simply have "gaps" in your assembly and your picking the wrong lines,etc.. thus seeing that..

You are thinking you are picking the right line but you are picking the line next to it which is .0001" away from it..

[Anonymous]

I'm pretty sure that posting an entire machine on the internet would cost me my job, but I can give the SA. 

Appreciate your time.

[Anonymous]

I'm the 3rd ME to look at this. It'd be difficult for me to pick the same wrong line & planes in half a dozen different components in the SA several times each and then be perfect in the top level. The assembly is being successfully remade now, but I'm still really interested in the cause.

[mcgyvr]

FYI.. Posting an iam file without including all the ipt files and any sub iam files (and the ipt files it uses) is useless..

The iam file does not include those files in itself but only links to the associated files..

So all we can do with your iam is open it and get an error that all the parts are missing..

In the future you can use "pack and go" to quickly gather up all the files in one zip file or just manually grab them all and put them into a zip file..

I personally have NEVER seen Inventor give different dimensions for the same line or distance on identical parts nor have I ever seen it give "wrong" dimensions so without seeing your actual model or one showing the same issue (a sample dataset that shows the same problem for you) we really can't answer..

Unless the folks that actually work at Autodesk are aware of a know (known internally to them) bug.. I certainly don't know about it..

The measure tool is brand new for 2018 so its certainly possible there is a bug.. (everything else new released in 2018 has bugs so I won't say its not possible by any means.... )

edit.. forgot to include information about pack and go..

https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/2017/ENU/Inventor-Help/files/G...

Its also through the file menu..file..save as..pack and go

[kgilham]

WagnerBEP,

Like mcgyvr said attaching just the .iam won't give us the entire assembly.I am not aware of any known issues but I can check into that.  If you are not wanting to share the assembly publicly would you be willing to share it with the Inventor Development team to see if we can reproduce the problem on our end?  

Thanks,

[Anonymous]

Yeah, I'm brain's been stupid all day. I tried a .step and then imported back to inventor again and the problem was gone. Working on the pack and go, but it takes at least and hour to dig thru all the folders. When it's done, I'll test the pack & go to see if the problem still occurs or it resolves itself that way and pass along.

[johnsonshiue · Accepted solution]

Hi! This is a known issue on 2018. Essentially, the Measure tool is displaying numerical noise exceeding the display range. It is way beyond the model tolerance and the noise is meaningless. It has been corrected on an internal build targeting 2018 R1 update. For Beta program participant, they will be able to try the candidate build soon.

Many thanks!

[mcgyvr]

---

@johnsonshiue wrote:

Hi! This is a known issue on 2018.

---

@johnsonshiue 

Johnson.. Is there a way for end users (or those of us that like to help on these forums) to get in on the "known" bug list?

I've been spending time attempting to help people with quite a few issues lately and have come to find out they are ALL "known" bugs..

I would love to be able to check said "known list" before wasting more time attempting to help...

[Anonymous]

That answers it, thank you. I'm glad to know its a bug and its not going to cause further issues.

[johnsonshiue]

Hi Brian,

I am very sorry that you spent more time than necessary helping out users and it turns out some of the issues were known. It was not intended. On the other hand, these threads help validate that we are on top of these issues and we are actively working on the right issues.

Unfortunately, it is not possible to show you a list in public. It is because these issues are being actively worked on. They should be considered part of in-development items. The information is not suitable for public consumption, since they are not final yet. The ones that I commented on are the ones that I have high confidence which will be included in the update. Others are still work-in-progress and some don't even have a solution. Sometimes, we found out the fix was not safe and we had to pull out at last minute. The list would be wrong.

Many thanks!

[mcgyvr]

---

@johnsonshiue wrote:

Hi Brian,

I am very sorry that you spent more time than necessary helping out users and it turns out some of the issues were known. It was not intended. On the other hand, these threads help validate that we are on top of these issues and we are actively working on the right issues.

Unfortunately, it is not possible to show you a list in public. It is because these issues are being actively worked on. They should be considered part of in-development items. The information is not suitable for public consumption, since they are not final yet. The ones that I commented on are the ones that I have high confidence which will be included in the update. Others are still work-in-progress and some don't even have a solution. Sometimes, we found out the fix was not safe and we had to pull out at last minute. The list would be wrong.

Many thanks!

---

I personally would be happy with a list of what you can publicly state are "known bugs"..

Heck I guess I'll just keep checking your "accepted solutions" list as thats one big public list of known bugs right there..  

[Anonymous]

this happened to me recently with 2017, no know reason, model was perfect, the infinite .9999... decimal places were actually screwing with constraints.

I'm afraid to upgrade

[Anonymous]

In 2018, this issue was fixed months ago with an update. There was another problem after editing the drawing BOM, but a 2nd update fixed that as well.

[Anonymous]

good to know, thanks.

[bjoho]

.