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

Filenode tree doesn't create at initial import #40

Open
derplayer opened this issue Dec 20, 2018 · 3 comments
Open

Filenode tree doesn't create at initial import #40

derplayer opened this issue Dec 20, 2018 · 3 comments
Labels
question Further information is requested

Comments

@derplayer
Copy link
Owner

derplayer commented Dec 20, 2018

Filenode tree doesn't create at initial import and the tools simply crash

@derplayer derplayer changed the title Filenode tree dosent create at initial import Filenode tree doesn't create at initial import Dec 20, 2018
@philyeahz
Copy link
Collaborator

That is how it is intended for now so we can still make changes to the new cache filesystem and because it takes a long time.
For the crash you need to explain more.

@derplayer
Copy link
Owner Author

Just wrote it here before i forgot it
Well you try to open the tree with an mouseclick and then the software dies

@derplayer derplayer added the bug Something isn't working label Dec 28, 2018
@derplayer derplayer added this to the Release 1.3 (Modding Tools) milestone Dec 28, 2018
@derplayer derplayer added question Further information is requested and removed bug Something isn't working labels Dec 28, 2018
@philyeahz
Copy link
Collaborator

Current workflow:
Import -> Extract All -> Open ".cache" file

Write up a new workflow you want.

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

No branches or pull requests

2 participants