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

Starts to open then Closes #176

Closed
elmic11111 opened this issue Oct 1, 2014 · 3 comments
Closed

Starts to open then Closes #176

elmic11111 opened this issue Oct 1, 2014 · 3 comments

Comments

@elmic11111
Copy link

Pyfa failed to load after installing the 1.5. After checking a couple things I found that when watching task manager I can see the program start to load and a second later close.

@Dekadara
Copy link

Dekadara commented Oct 1, 2014

Win 8.1
Pyfa crashes when trying to load saveddata.db created in version 1.4 (in folder %USERPROFILE%/.pyfa)
If delete this file, the Pyfa is loaded, with the loss of all fits and API. A temporary solution - Make a backup xml copy fits in 1.4 and import to 1.5

@blitzmann
Copy link
Collaborator

Can you guys send me the saveddata.db file and any saveddata_migration backups you may have in your .pyfa directory? If you're worried about security, evemail me a link at Sable Blitzmann

I'm looking into this now while on lunch break, and will look into it further after work. Temporary solution of importing backups works for now, but doesn't keep APIs, projections, fleet boosters, etc, and is not ideal.

@blitzmann
Copy link
Collaborator

So, basically, this is because I failed to realized that the windows skeleton (and possibly mac?) need to be rebuilt whenever the root file changes (root file being pyfa.py). Apparently when these skeletons are generated they take that file and integrate it into an executable, so any changes to the file need to be mirrored with a new skel.

I was under the impression that it was like all other python files in that if you change it, it will work regardless.

Anyway, the changes that I made to pyfa.py was the actual data migration procedure. Since it didn't happen, pyfa was crashing on a column that it thought was there but really wasn't.

Fix is coming out tonight, closing issue.

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

3 participants