First is: My munging process says it can't access the file (s) because it is being used by another process.
2nd: When it isn't giving me the bull up above, when the munging process is at the part where it says something about creating a mesh it freezes up for 2 hours.

#1 is caused by stoping a munge, Never do this. a part of the munge still runs, and is accessing the files, so the next time you try to munge, it can't access them.

#2 let it go, Do Not stop it.
It may take 10 hours, just let it do it's thing.

is it about a created mesh or creating?

I'm sure he means CreatingLODmesh, or MergingShadowmesh.
Not that it makes alot of difference.

Sorry, but you lost me in that last post.
And what do you mean it wouldn't make any difference? Everything does.

SilvaDalek wrote:Sorry, but you lost me in that last post.
And what do you mean it wouldn't make any difference? Everything does.

Its cause they both mean about the same thing, and have the same effect, making the munge take forever.

Oh, the shadow mesh takes so long I don't use it.
And is canceling a munge that bad?

It can be very bad, its just well advised not to.
If you absolutely MUST, I guess you could.

And if you just changed the texture or added objects to a map what are you supposed to munge?

some single objects take 7 hours (mine from this morning just got done . . .)

One common Munge misconception is the "Everything" selection from the drop down menu, that is only ever needed if you've mad changes to multipliable of your custom sides.

If you have no custom sides, all you'd ever really need is to have common and localize checked, Load, if your making a load screen.

It says it's being used by another process due to the munge being stopped. VisualMunge.exe stops, but whatever background program is running keeps going until it's done. In this case probably pc_modelmunge.exe (if you open task manager and go to processes you'll probably see it there). The best thing to do is restart your computer, go in and manually clean (see the tutorial at the top of this forum) and then munge again, walking away from the computer until it's done. Even if it takes 10 hours. If I'm munging custom models I usually leave the computer on overnight and start the munge before going to bed.

To be more specific on the freezing part this is the line: _CreateShadowMesh(lod:0): created hires shadow (226 verts 1322 edges).

It's not frozen, it just takes forever to optimize the model. Did you even read what people posted?

some single objects take 7 hours (mine from this morning just got done . . .)

It may take 10 hours, just let it do it's thing.

The best thing to do is . . . [walk] away from the computer until it's done. Even if it takes 10 hours.

If you're not gonna read the answers, why should we post?