Circa

@ZanderNao the PK3 should be fixed now. It extracted fine with 7zip so I repackaged it. In the future I recommend reporting the file page for issues like that either with the report button or a DM to the author or the staff rather than a 1 star review.

Try this one, should be version 2.0 but with the hand fix. Again, if @Ruxith wants me to replace the main download with this one, let me know. I simply used this method.
https://files.jkhub.org/jka/playermodels/zzzZ_jedi_nm_FIX.pk3
 

This author hasn't been active in over 13 years, you probably won't get a response. Crediting should be sufficient and appreciated.

It's been awhile since I did that portion but I believe it was solved by using a skyportal?
{ "classname" "misc_skyportal" "origin" "2736 2416 1896" "angle" "90" } I went by this tutorial:
https://jkhub.org/tutorials/mapping/ent-modding-misc_bsp-fixing-blurred-hom-skybox-r122/
It works fine on basejka and ja+ from what I've seen, maybe Lugormod messes with that entity in the code or something.

Looks like it is meant to be played using the .bat file. Extract the zip to your Gamedata folder and double click the "launch_dragame0.bat" file.
If you're not on windows you can use "map dra_map_0" in the console

Thanks so much for the fix, Circa! Everything seems to work great in my testing. Appreciate your hard work on this

That issue should now be fixed in 2.1. So sorry for how long it took to fix it. 😅

This is a great experimental map! Utilizing Unreal Engine 4 opens up a lot of possibilities for maps in the future.
I was also getting a steady 120 fps with OpenJK and Rend2 enabled. I'm using a GTX1070 with an i7 7700k and 16Gb of RAM.
After testing the map, I looked at the pk3 file to see why the file size was so large. It looks like several of the textures are 20Mb+. Using the "om_bridge.jpg" as an example, sizing it down in Photoshop to 2048x2048 and saving it reduces the file size to about 1-3Mb. I don't think you would notice much of a loss in image fidelity at 2K and it would significantly reduce the amount of VRAM needed and likely have the map perform better on a greater range of devices. It may even allow the packaged pk3 file to be closer to ~200Mb or less.
Looking forward to see where you take this and other experimental maps in the future! I would be interested in seeing your workflow if you ever made any tutorials on the subject.

Linken told me this is not yet in Galactic Legacy so I'll allow it to be submitted to the contest since it hasn't technically released yet. Looks good!

JK2MV is multiplayer only. OpenJO's main function is general bug fixes and improvements to playing JK2 single player on modern hardware and operating systems. PK3 mods made for vanilla are compatible with OpenJO, yes.

Hopefully, someday, moders will replace sprites with OTF. 🙃

Thanks for posting it here! This looks so good, I'll have to try it on my next JK2 playthrough.

Thanks for posting it here! This looks so good, I'll have to try it on my next JK2 playthrough.

Linken told me this is not yet in Galactic Legacy so I'll allow it to be submitted to the contest since it hasn't technically released yet. Looks good!

Linken told me this is not yet in Galactic Legacy so I'll allow it to be submitted to the contest since it hasn't technically released yet. Looks good!

That was my fault, made a typo in the link.

Wow, big improvement from the first version. Nice work!

The vibes are really nice, I'm a sucker for dim lighting!

The vibes are really nice, I'm a sucker for dim lighting!

I love how simple yet elegant this map is. Nice work!

That bulge will put an eye out, watch out!

I've always believed those blue things to be terminals that officers stand at and use, so I'm really wondering if those that are at an angle are supposed to be used in anti-gravity or..... 😛 

Hey, thanks! I'm glad you liked it.
Well, the name of the map is 2Pits Warehouse because it's basically some kind of warehouse with 2 giant pits, that's the best name I could come up with. 2Pits is kind of inspired by 2fort from the game Team Fortress, so there's that.
The whole "dra_" stuff is basically for namespacing reasons, and is a habit that comes from programming in C and C++. Any code that I make, I always use dra:: or dra_ as namespaces, to make sure that any code that I write does not collide with code from other libraries, so that people who use what I make do not have to worry about having to fix it by renaming literally every single symbol in my code. I guess it does not make that much sense in modding for Jedi Academy, but it's still a habit that I've carried over just to be safe.
Also I initially did not really know what I was going to name the map, so dra_map_0 was the best I could come up with lol.
If you're curious as for what dra_ means, it's basically the initials of my name, inspired by the stb_ libraries, whose creator did the same to make sure that his code's symbols did not collide with other libraries. You can find the rationale explained here in one of his repositories on github https://github.com/nothings/stb?tab=readme-ov-file#why-stb-is-this-something-to-do-with-set-top-boxes