-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
Unable to find files after going through compile and extraction steps #285
Comments
If you followed the directions exactly, you should have a Also, it looks like the game is looking for the data files in /usr/local/share/nxengine. Is that what you want? If so, you need to run git clone https://github.com/nxengine/nxengine-evo
cd nxengine-evo
mkdir build
cd build
- cmake -DCMAKE_BUILD_TYPE=Release ..
+ cmake -DCMAKE_BUILD_TYPE=Release -DPORTABLE=ON ..
make |
Other resources if you're still stuck:
|
Yes there is where I want it for example and yeah I think you should add that in the documentation also as I do know about that cmake option from another issue which I have replied on :) Do you know why I have missing files at all? |
Done: https://github.com/nxengine/nxengine-evo/wiki/Building-on-Linux
Oops, you're right, there is no nxengine-evo root
I'm not sure I understand the state your build is in, but it sounds like
The part I'm not clear about is data files. Start by rechecking those steps. Did you copy |
Here is my layout
inside build
After extracting the files from Doukutsu.exe I first try portable mode but ran into the same issue of it being unable to find the files and I used the [Aeon Genesis (pre-patched) version, I than did the non portable compiling mode and as a test I manually put the files in /usr/local/share/nxengine to see if it would work but sadly no dice. I copied the files in data into the nxengine-evo data folder but that created more errors
I tried again with portable mode and extracted but it's looking for font_1.fnt which doesn't even exist. If I copy the files from inside the data folder into the nxengine evo and run it from /build it will think that the data folder and when I put the data folder from cavestory I run into the same issue.
Here is the log when I extract it
|
I'll add more explicit instructions for getting the data files from Cave Story. Hopefully that will make this part more clear. |
Ohhh ok now I get it, you move the data folder,nxengine-evo and nxextract from nxengine-evo into the cavestory folder replacing and adding everything then you run nxextract and it should work because now it works. I think the instructions need to be a bit more clear also remove |
I'm glad you got it working!
This is not quite right. You take the data/ and Doukutsu.exe files from Cave Story and put them in the nxengine-evo repository root, like this (I added this to the instructions):
After that, data/ contains a combination of 3 things:
Fair; I removed that. |
Right I see but if I wanted to make a game folder for the game and compiled it as a portable binary I could do it that way and not have the rest of nxengine-evo files there that are no longer needed if I wanted a smaller folder and zip it up correct? also do I need to worry about these warnings?
|
Oh and for build instructions you should do |
Yes, and that's why in the docs I added the section about moving the data files and binary to a separate directory:
Yeah, that's fine. I always have those as well. If I understand the code correctly, it tries to load all sound files from fx00.pxt to fx75.pxt even though some of the files in that range don't exist in Cave Story. |
Hey I am having a issue where I have gone through the setup steps for compiling and extracting for Linux and it is unable to find the files
Just wondering if I did something wrong or not as I found the instructions a little confusing since it also didn't work. Where it says "Look in the /bin folder for the compiled binaries, and the /data folder for additional data files." where is this referring to exactly because there is no bin folder in nxengine-evo
The text was updated successfully, but these errors were encountered: