Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not all of the terrain gets exported #92

Open
GerbSnail opened this issue Nov 5, 2022 · 0 comments
Open

Not all of the terrain gets exported #92

GerbSnail opened this issue Nov 5, 2022 · 0 comments

Comments

@GerbSnail
Copy link

It's what it says on the tin, a large portion of the terrain won't get extracted on certain maps.

This happened to me while extracting the Trostland load, and I assume it's because it's a very large map with ~90 individual parts. One thing to note is that Charm got very unstable and would crash 80% of the time while attempting to extract the map. I checked on three separate versions of the tool (1.2.4b, 1.3.0, and a custom one nblock sent me that I assume hasn't been built into a full release yet) and on all three versions it would not export the rest of the terrain. On all three versions it had a high likelihood of crashing and I assume even though that I'd wait until I got an extraction where it said it was complete, I assume just due to the high quantity of segments that it was extracting that it just couldn't keep up.

A few more things I should mention:

  • I was extracting on the "terrain only" mode
  • Most of the .cfg files were empty upon extraction

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant