Attach point cloud throws RTTI error and corrupts browser

[eucci]

I've been struggling with this file for a very long time.

Its been very difficult to narrow down the cause of the three cascading errors.

1. Access violation - no RTTI data!

2. Brower corruption (new features not in proper chronological order)

3. Persistent cyclical dependency error (when one does not exist)

I believe that the first error is thrown when attempting to insert or subsequently manipulate an attached point cloud. At which point I can continue to work in the file. However, this, in turn, leads to the other errors.

I have tried several different ways to export and attach the scan files to no avail.

I will attached the ipt file. However, the scan files are too large to included here. 

Please advise for best way provide the scan files. I'm assuming that a packngo to properly attach the scan files is in order.

This would appear to be a bug particular to 2021. I have been using this process for several years and have not encountered this until after I upgraded all my software to 2021

See attached files

[johnsonshiue]

Hi! The two .rcs files are not attached. Please attach them so forum experts can help take a look.

Many thanks!

[eucci]

As I previously mentioned, they are too large to attach.
80-90 MB ea
Please advise on the best way to get them to you

[eucci]

see dropbox link below

https://www.dropbox.com/sh/inmfdc9gomiwwks/AACavYAwDQ71djujBu7JwZRTa?dl=0

[johnsonshiue]

Hi! Many thanks for sharing the point cloud files! I do see the cyclic dependency error when moving EOP to the top. But, I am not sure if the corruption is related to point cloud (PC), since PC is more like a display. With or without PC, the issue should be reproducible.

The tricky thing here is that when the corruption already occurs, it is usually too late. We need to find out how to reproduce the corruption. Something is wrong for sure. You have posted this issue in several postings already.

[eucci]

I don't mean to hound you on this. I only posted multiple times because new
issues kept popping up the more I investigated.
Fortunately, last night, I finally got the file to a stable point where I
am able to progress and complete my work.
It does appear that you are correct about the PC being unrelated to the
other issues. I have been able to pull an earlier version from Vault
(before the browser corruption) and clear out the cyclical dependency and
while I'm still getting the RTTI error when handling the PC it does not
appear to prevent me from making progress.

This file was created in 2020 before it was migrated to 2021. My
understanding is that the RTTI error is related to files worked in multiple
versions. Perhaps most of these issues were exacerbated by this migration.

In all my years of working in Inventor, no file has given me the headache
with multiple errors that this one has.
Knowing what I know now it would have been smarter just to start again from
scratch in 2021.
However, my instinct with Inventor is to use existing assets whenever
possible and repair any errors to avoid the steps that led to the problem.

Regardless, I am no longer prevented from finishing this job.

Thank you

[johnsonshiue]

Hi! No worries! There is a bug for sure. The issue is that we need to find the workflows leading to the corruption. It is actually possible it may be a side-effect of fixing a crash. In the past, it may have crashed at one step. Then you can open the last saved file and keep working. But, now the corruption is tolerated and corruption stays with the file.

This is just a theory. Regardless, I don't have a clue how this particular corruption occurs. I suspect it might be related to feature reordering or rolling back.

Many thanks!