ensiform

cg_hudFiles 1 causes the simple HUD in MP (and also SP with OpenJK)  It won't be set to 1 because of too many menus, it has to be explicitly set and shouldn't be an error only a message.

Because you've not put it in the directory with the game.

It's under lib/SDL2/bin and select x86 if older than vs 2015 otherwise you want the x86 2015 one.

It's copied if configured to install. As the buildbot does include it for jka.

That means jk2 built just fine. The assets part for mp dlls didn't package is all.

Its not saying which executable was being used unfortunately so its difficult to say.  This can happen if the game is still running if you're launching from the build directory, or it could be one of the compiler tools, cmake, etc.

Did you turn on all 3 build jk2 things in cmake?  You must use the JK2SP Client, JK2SP Game, and JK2SP Vanilla Renderer for JK2.  There is no startup +set com_jk2 1 or anything like that.  You still need to copy the SDL 2 dll to your game directory of course as per usual which is prebuilt for you.

Serenity Jedi Engine source would be nice if the released version is going to remain online.

Capture point game modes don't work so nicely in Q3 engine unfortunately unless you have it be instant-trigger with a goal or something.  To have it be like TF2's where multiple players can capture etc, would not work so well.

These points look really nice.  They'd even fit for CTF too.

OpenJK's SP allows custom weapon.dat with damage entries but the defaults of course are not in the weapon.dat file so you'd have to still go through the code to find the right values for SP.

Sure but tf2 doesn't use the missile icon.

The disruptor doesn't have separate MOD_ types though afaik?

I think the weapon looks best for rocket.

I've tried saber only ctf and its not that fun.

The icons with the person in it look eerily like they come from Portal for some reason.

The alt fires are looking good.  Concussion is a little bit strange though.  I'd say use the sniper logo for the conc alt as the conc alt is an instant hit/hitscan laser like thing.

Also forgot about the turbo laser... misc_turretG2 idk if those are the hoth turrets or the hanging turrets though.  And I think the turret you're using is the player usable one.  Sadly the turret and emplaced etc are all kinda mixed and mashed as far as what uses what.  I think emplaced even uses the vehicle MOD :/

Don't bother with multiple saber icons though.  Its not separated as to what kind of saber or if you were kicked unfortunately, or even if it was a thrown saber.

The point behind using the different for some of the alt fires is that they are rapidly different kill types.  Such as the Repeater and Conc and flechette.  Or maybe the addition to the weapon icon could look different like how TF2 has the extra imagery after the weapon icon on some.

So I'm thinking we'd want:

• Stun Baton
• Melee
• Pistol (there is no distinguishing death MOD for jka vs jk2 pistol)
• Blaster
• Disruptor
• Bowcaster
• Repeater
• Repeater Alt
• DEMP2
• Flechette
• Flechette Alt
• Rocket
• Homing Rocket
• Thermal
• Trip Mine
• Detpack
• Generic Vehicle
• Concussion Rifle
• Concussion Rifle Alt Fire
• Force power kill (There is no way to distinguish this)
• Portable Sentry kill
• Drowned in water
• Dissolved in slime
• Burned to death in lava
• Crushed by object
• Telefragged
• Fell to death
• Suicide / unknown / trigger_hurt / generic?
• target_laser / turret
• Clean version of basic team color icons for flag and not sure what would be good for grab/drop/capture/return distinguishing icon wise could also be text next to icon as well

Well they would not be displayed in the console notify box if this was implemented.  You'd still see those cheesy messages in the console, though.

And every other game pretty much, yeah.

Thinking it could be a useful thing for like JA++ or such.  But the HUD is already so cluttered and disorganized as it is =/

And Raven decided to make the HUD code less functional than Q3:TA sadly.

Would anyone be willing to make a pack of icons for kill feed/action feed?

You'd want one for each type of weapon at least, and base death/kill types and probably at least some kind of default for the "unknown".

Other things possible: flag taken, flag capture, flag return.... Any others?  Some stuff is only printed to all clients and isn't an event of sorts so can't really handle those.

Adding the ability to add/remove commands from the UI module.  It will print warnings to console if attempted with jamp.exe since it is not part of the UI syscall interface at all.

The server shouldn't need to be updated unless that changed anywhere too.

I always remember the slash and * binds on the numpad mapping to the regular verisons in JAMP.  And this looks unchanged code wise.  It's treated as the same keynum value as * but only bind * works and bind / works.  I think the issue may have to do with the character value mapping to the incorrect character maybe?  It maps to the literal unicode multiplication × sign rather than * for KP_STAR U+00D7 isn't the same as the ASCII *.

https://github.com/jedis/jediacademy/blob/master/codemp/client/cl_keys.cpp#L245 claims to still be the case in base too.  So I'm not sure where the issue actually lies here or if behavior did actually change.  Could be SDL handling of characters too which may be externally blocked if this is a problem.

Mismatched UI_API_VERSION: expected 1, got 2

Means there's a conflict between engine and UI import/exports.  IE either old engine and new mod or something like that.  Probably affects all the mod "dlls"

The crash is... Not sure, might try without mods (particularly custom models) to see if that affects the crash from the first part.

Oh, the format of the folder path is just weird.

You can use brew install sdl2 to get it there. Per mazter instructions for now.

Does it by any chance have anything to do with the fact that you're essentially having the app within another app like that?  I have no clue how Apple libraries are loaded particularly SDL2.  Its not specifically in our codebase as loading it manually with dlopen.  It must be in the SDL code itself.

There's literally no useful debug information there though since its not a debug build.

Well "still crashes" with no information on the crash whereabouts isn't going to help get it fixed. =/