Hello guys

You know, when you made a new teleport door in Tamriel world, CK will save tons of navmesh triangles as Identical To Master (ITM) in the cell where the door is located and in the boundary cells too.

To clean these ITM I used TES5Edit. However is there a way to do this without TES5Edit?

Thanks.

Yes, the pre-TES5Edit caveman approach of flagging records with Ignore in the CK's data viewer. Just keep using TES5Edit, though.

Flagging NAVM of exterior cell as ignore, will revert back the whole navmesh cell and removes the new teleport door.

I got several issues cleaning my Silverfish Grotto with TES5Edit.

For istance I've a formlist with a list of custom NPC. One of the custom NPC was gone (the actorbase) and replaced with Katla (a vanilla NPC).

Another: A objectreference property of a scripted book item that was pointing to an xmarker, was replaced with a chair in the Thalmors' justiciars headquarters...

I edited nothing by hand with TES5Edit, just cleaning the ITMs.

I want to use TES5Edit as checking utility but I want to use CK to remove ITMs.

wow... so this is still were quest and dungeon modders are left as Bethesda moves on?

ok, so just wondering but...well how did Bethesda do it?

I really do not think they are using Tes5edit no matter how good a program Tes5edit is.

Or did they just leave in the "dirty" edits?

If you are running into TES5Edit doing things you aren't expecting, you should bring it up in the TES5Edit thread so Zilav can find out what is wrong and fix them.

Regardless, unless something is very wrong, cleaning a mod with TES5Edit cannot do what you described. Not to mention you are just making a huge amount of extra work for yourself for no real good reason.

I'm confused about the teleport door issue. I've set up a number of teleport doors in the world, without needing to change any navmesh info, and have never created a load of ITM records to the cell's navmesh triangles. Is either you or I doing something wrong?

Unfortunately I got these issues after cleaning the mod and I don't want to flame anyone, including TES5Edit. Probably I did something wrong, but I just cleaned the mod. This is my experience.

Staying on topic I need just to know if I can clean ITM navmesh triangles via CK.

Well... I missed to say the words "finalizing the exterior navmesh" to add the new teleport record. Sorry.

What is your procedure? Can you elaborate to how not get tons of ITMs?

With the door doors I placed that required finalising the navmesh, I'd already edited the navmesh itself. But even then, it didn't create ITMs in the adjacent cells.

You did something wrong, or if you didn't, then TES5Edit did something wrong.

The solution to this is not to completely abandon the proper way of doing what you want. It is to determine whether the fault was yours or the program. If it was yours, you need to learn to do it correctly. If its the program's, you need to report it to the developers so it can be fixed.

There is no "flaming" going on here. Reporting a bug, or even asking for assistance in case you made the mistake is not "flaming" it is doing things the way you are supposed to. So instead of doing this in an incredibly ass-backwards way, do it properly!

Keep calm please! Don't automatically think I'm doing wrong and TES5Edit is the perfection, end of discussion about TES5Edit!

Just reply to #1 if you can. Thanks.

Very curious O.o

Everytime I refinalize exterior vanilla navmesh, I have ITMs in boundary cells!

Are you positioning the camera in adjacent cells by mistake at all?

No, I'm very close to the teleport marker and the triangle is fully inside the cell.

I'm not automatically thinking you are wrong, I'm saying you got a highly unexpected result, which is either the result of user error or an error in the program. One way or the other, you should report it in the TES5Edit thread.

I don't care if you want to make extra effort for yourself, I however do care that *Edit is a bug-free and smoothly functioning program. So if you have found a possible bug, you should report it.

Actually I can't report that because is very generic and it happened in 2 or more different causes. I should try to know what exactly happened before writing a bug report.

Set up a test esp file, and just create load doors into interiors, a fair amount of them, finalize each navmesh, maybe one at a time, save test etc. See if you can faithfully reproduce it.

I'll do. Thanks.