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

Install guide #627

Open
xycaleth opened this issue Feb 10, 2015 · 14 comments
Open

Install guide #627

xycaleth opened this issue Feb 10, 2015 · 14 comments

Comments

@xycaleth
Copy link
Member

I don't know how an install guide hasn't been created yet, but we need one for the first release. It should be aimed at a novice user and preferably with screenshots. Make sure to explain for Steam variants as well!

@Yberion
Copy link
Contributor

Yberion commented Feb 11, 2015

Made an unofficial video long time ago to explain how to install openjk and where to find the lastest builds but it's pretty old now.

https://www.youtube.com/watch?v=DCEVwh5xDQ0

@ensiform
Copy link
Member

That won't be relevant for an actual install.

@eternalcodes
Copy link

  1. Download
  2. Extract to GameData
  3. Create shortcut to desktop

@Katana-Steel
Copy link

Might need something for non-Windows users as well I think
On Sep 21, 2015 11:52 AM, "dan2077" notifications@github.com wrote:

  1. Download
  2. Extract to GameData
  3. Create shortcut to desktop


Reply to this email directly or view it on GitHub
#627 (comment).

@eternalcodes
Copy link

I can confirm that the same instructions work for Linux.

@Razish
Copy link
Member

Razish commented Sep 21, 2015

We'll also need to correct some myths/misconceptions:
jampconfig.cfg is now openjk.cfg
Clarify that openjk.x86.exe (or equivalent) replaces jamp.exe and may be used the same way with launch arguments etc
Screenshots, configs and other game-produced data is now saved to fs_homepath, e.g. Documents/My Games/OpenJK
DLLs are no longer extracted from PK3s to JA's directory, and any residual DLLs should be removed (this has caused much troubleshooting pain)

@eternalcodes
Copy link

It's an install guide; it needs to be as simple as possible.

@Razish
Copy link
Member

Razish commented Sep 24, 2015

Unfortunately that's going to bring a lot of painful troubleshooting in the future, which we're already getting because the issues mentioned above aren't dealt with.
Some of these people have been playing for 12 years without those changes.

@mrwonko
Copy link
Contributor

mrwonko commented Nov 23, 2015

and any residual DLLs should be removed (this has caused much troubleshooting pain)

We should have an installer that takes care of that; or simply not load any loose dlls from the game folder.

@Razish
Copy link
Member

Razish commented Nov 23, 2015

or simply not load any loose dlls from the game folder

That would make development a nightmare, not to mention it's the only supported behaviour on unix backends

@ensiform
Copy link
Member

With the current implementation debugging mods doesn't work as it is on windows.

@mrwonko
Copy link
Contributor

mrwonko commented Nov 23, 2015

Well, you can always attach to the process, works just fine.

@Yberion
Copy link
Contributor

Yberion commented Nov 27, 2015

Maybe offer the possibility to choose between installer and .zip, I will always prefer a .zip personally.

@mrwonko
Copy link
Contributor

mrwonko commented Nov 27, 2015

I get that; but it should be somewhat hidden so only advanced users who know what they're doing use the zip.

@mrwonko mrwonko mentioned this issue Mar 25, 2016
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants