eezstreet

Update (10/23/2024): This thread is out of date, to compile, you can either follow OpenJK's compilation guide or Flate's Ubuntu/Debian tutorial here. Prerequisites Currently JKGalaxies can be compiled on the following platforms: Win32 VS2014 and below Win32 VS2015 Win64 VS2015 It currently does NOT compile on the following platforms: Mac Linux Win64 VS2014 and below MinGW The following platforms will compile with some features omitted: Visual Studio 2015 In addition to one of the above platforms, you will need: CMake Git (for the `develop` branch) Compiling Guide You'll need to acquire the source code for JKGalaxies. This can be done on our Github page by either cloning the repository or downloading a zipped version of it. If you wish to contribute to the project, it is highly recommended that you create a fork of the project and clone your fork. When you have changes pushed to your fork, you can use a pull request. Currently, the directions for compilation are identical to the OpenJK Windows tutorial, located here: http://jkhub.org/tutorials/article/145-compiling-openjk-win32-must-read-for-new-coders/ Extra Steps for Visual Studio 2015 Visual Studio 2015 has a radically altered C runtime library (CRT) and as a result of this change, the game does not compile correctly because some of the libraries were compiled with older CRTs. To counter this, you'll need to disable the OpenSSL cryptography package (currently not used). Assuming you've loaded up the project in Visual Studio, right click on the MP Game Library in the Solution Explorer and select properties. Along the left hand side of the properties panel, do Configuration Properties > C/C++ > Preprocessor. On the line labelled Preprocessor Definitions, toggle the drop down and hit Edit. On a new line, add NO_CRYPTOGRAPHY. You'll also need to use a different version of SDL, the window, sound and input manager used by OpenJK and its derivatives. If you don't have the Properties panel open, right click on the MP Client project and hit Properties. If you still have the properties panel open, simply click on the MP Client project in the Solution Explorer. From here, do Configuration Properties > Linker > Input. On the line labelled Additional Dependencies, toggle the drop down and hit Edit. Find these lines: ..\..\codemp\libraries\SDL2\lib\x86\SDL2.lib ..\..\codemp\libraries\SDL2\lib\x86\SDL2main.lib and change it to this: ..\..\codemp\libraries\SDL2\lib\x86\vs2015\SDL2.lib ..\..\codemp\libraries\SDL2\lib\x86\vs2015\SDL2main.lib

Visual Studio 2015 will have issues compiling older code due to it using a completely new CRT (C runtime library). This means that any .libs that you have used will have to be recompiled from scratch. I strongly advise against using it unless you're an advanced user/OpenJK and co. release new windows libraries for it. That is all.

This thread has been moved to the new JKGalaxies subforum.

This thread has been moved to the new Jedi Knight Galaxies hosted mod forum.

Origins of Jedi Academy: ...somewhere in Los Angeles, California, in an Activision meeting room: Activision Exec: Ahahah! Excellent! JK2 was a top seller, and we have good review scores! Most excellent! Exec 2: Should we make another game? Exec 1: Of course! But we'll need Lucasarts to sign off on it. *phone ring at Lucas Ranch* Exec 1: Yes hello, Lucas? Can we make another JK game? Lucas: Yep sure mang. Exec 1: Excellent! So we're cool right? Lucas: Yeah - Exec 2: Thanks, bye! Lucas: but! Exec 1 & 2: *sigh* Lucas: It's gotta be like the prequels! Your game was dark and full of revenge and stuff. Exec 1: Okay okay. What do you want us to do? Lucas: It's gotta be about Jedis. And lightsabers. Kids fucking love lightsabers. Exec 2: The game already had lightsabers in it... Lucas: NO IT NEEDS MORE FUCKING LIGHTSABERS, YOU HEAR ME? MORE. Exec 1: How can it have more? Lucas: Did you not see Attack of the Clones? The Phantom Menace? Exec 2: Yeah, we saw them, but they were pretty awful- Exec 1: Awfully good, yes! *smacks Exec 2* Exec 2: We put in the double bladed lightsaber in JK2 though. Lucas: BUT IT WAS A CHEAT CODE! Exec 2: Okay, true. So you want double bladed lightsabers? We can work with that. Exec 1: Yeah. Shouldn't be too much of a problem. Lucas: AND TWO AT ONCE, JUST LIKE ATTACK OF THE CLONES. Exec 1: Okay sure, we can do that too. Can we get funded now? Lucas: Mmmmmm....hamburgers...I mean, YES. Make me a game. Exec 1: K, bye Lucas: Lol, bye. And no more puzzles! I fucking hate puzzles! *click* Madison WI, the next day: Exec: Okay boys! We're making another JK game! *collective cheers* Exec: But that last game took a little too much time. I mean, you started stuff in 2000 and it didn't come out until 2002? *murmurs* Exec: Alright, can we get it out in less than a year? Sounds good. Do us proud, guys.

You're referring to the game, not the mod. Huge difference. Game = Star Wars Galaxies Mod = Jedi Knight Galaxies

I said it was a great model for a beginner. This is your first model, yes? That would definitely put you in the category of a beginner, and objectively it's a pretty great model for a beginner. If someone with experience like Ashura, Chalk, minilogoguy, Gir, etc put out something like this, I would naturally be a bit confused. I'm not sure I understand the offense? :? I always critique people's models based on polyflow- I don't know a damned thing about working with the tools to sculpt or producing a good texture - those are a bit beyond me. But if I see a nasty set of triangles, then that's easy for me to recognize. I mentioned quads because they're easier to work with in a lot of ways since you have fewer edges and faces to work with. Some things are just easier to represent via quads anyway, like the upper lip. Part of the learning process is making mistakes and then learning from them. In this case you've made a rather common mistake: Getting it ingame before getting the mesh critiqued. Have a look at the resources that the others have provided, they'll give you some pointers.

Your polyflow looks pretty jacked up, especially around the nose and upper lip / "stache" area. I think modelling in tris is a bad idea, you should probably stick to quads as they are easier to work with and you'll get nicer results. But for a beginner model, this is pretty great work.

Yes. I just need to install VS2013/14 on my desktop and that'll be good to go.

hype

Can we get a wireframe, perhaps? I'm rather curious how the shoulder deformations will play out.

hype hype hype

No, those are the development files. I need the stuff to actually run the game. EDIT: Nevermind, Stoiss lent me a hand and I've got everything I've need to set up a small workstation.

But no, srsly. I need those assets. The direct link on the website doesn't work and there's other broken stuff too on the Moddb page.

Here you go: https://github.com/JKGDevs/JediKnightGalaxies/releases/tag/HEAD

GLM/NPC will not work. They have a bounding box.

Will do, later today.

I see you found Ste's rant.

If you read the article, I'm pretty sure you would be convinced that it was totally a joke.

At least they aren't as bad as fscking Paramount.

Really the only thing that's the problem is the assets. Once you download them, all you need to do is continually update your DLLs and maybe a PK3 or two that I decide to change. @@Darth Futuza: if you'd be a peach and upload the assets here, I can write proper installation, compilation, etc instructions as well as basic information on how to host. I'm also kinda stuck since I don't have the most recent copy of the assets, otherwise I'd be chipping away at some code.

ohai

Pff, I've stopped giving a shit about everything really and have a newfound apathetic view on life. I just don't want people harassing me about it.

It's totally not dead! See! I fixed something! https://github.com/JKGDevs/JediKnightGalaxies/commit/5eef5880a8a0512e1cefe5757e6cc3621049eb11 ...

In the base game, yes. Most other values excluding missile velocity are controlled in one file: ext_data/weapons.dat. I implemented an override to OpenJK that allows people to modify the damage and alt damage of weapons there too.