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

Can't get the module to work properly. #252

Closed
themaskedcoyote opened this issue Aug 6, 2019 · 3 comments
Closed

Can't get the module to work properly. #252

themaskedcoyote opened this issue Aug 6, 2019 · 3 comments

Comments

@themaskedcoyote
Copy link

HI MuOn,
At a bit of a loss here. Scanned through all previous issues to see if I could solve my issue but no luck.
I uninstalled all previous Vassal files (engine and modules) and started fresh. Everything in in C:\XWingVassal\ as I saw that was an issue for someone. Basically I get this message as soon as I load the module:

Error: can't connect online to verify the module's integrity with xwing-data2 - will attempt to use local files instead.
--- File not found 'manifest.json' not found in C:\XWingVassal\xwd2.zip
XWS2Upgrades line 343 - couldn't load the manifest for upgrades
XWS2Upgrades line 343 - couldn't load the manifest for conditions
XWS2Upgrades line 323 - couldn't load the manifest for conditions

  • Star Wars X-Wing Miniatures Game version 8.7.1

If I create a game and attempt to hit the 2.0 Squad Spawn button, I get the following:

--- File not found 'manifest.json' not found in C:\XWingVassal\xwd2.zip
XWS2Upgrades line 343 - couldn't load the manifest for upgrades
XWS2Upgrades line 343 - couldn't load the manifest for conditions
XWS2Upgrades line 323 - couldn't load the manifest for conditions

Any insight would be helpful. Thank you

@Mu0n
Copy link
Owner

Mu0n commented Aug 7, 2019

This issue is known, as per your copied text lines in the chat window. Starting in 8.7.1, the module is supposed to give you one extra annoying popup that tells you how to resolve the issue. Did you see it?

The problem: you put the module file in a folder where the vassal client has no writing access. The module wants to download data and create local cached files where it resides. A known bad folder is something like /program files/vassal/, where the client program of vassal resides. You have to put the module elsewhere and you'll know it works when you see some cached files pop there after loading the module, and you'll stop getting those warnings in the chat window.

@tdhtim
Copy link

tdhtim commented Aug 17, 2019

I have had the same issue but on mac. I've tried moving the module to different folders without success. Got any insights? Also, I haven't seen an "extra annoying popup" telling me how to fix it.

@Mu0n
Copy link
Owner

Mu0n commented Aug 18, 2019

I assume you can edit the rights of the vassal client software to allow it to write files? I don't own a modern mac but that's what I'd investigate.

@Mu0n Mu0n closed this as completed Mar 19, 2020
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