Highpowerd

That seems unlikely. Something that's set there isn't working right with the most recent Openjk or something (previous versions ran fine), or maybe a driver issue? Who knows... It's probably not Ja++ anyways, I'd imagine if you were to set one of these graphics settings manually to a higher value (that the default menus don't touch) just running Openjk it'd run bad too. This machine isn't the most powerful ever, but it's strong enough to run something like Skyrim with 30 gbs of graphics mods/enb and whatnot at 30-60+ fps lol. EDIT: Okay, found what it was. If r_depthbits is set to 32 (normally it's 24 I think if you max the game with default menus) kills it. Setting it back to 24 and it's fine. I honestly have no idea what this means, I'm sure somebody else can explain it, lol. Also r_stencilbits set to 32 kills volumetric shadows, 24 or lower and they're fine (old Openjk 32 if I recall was fine). Ja++ probably just needs it's menus updated to not allow bad values with latest Openjk or something lol. Or maybe there's some driver issues. Seems unlikely though if people with AMD and Nvidia are experiencing similar things. It would probably be good if several people put these values in console then do vid_restart and see what happens. And just for reference, I get these issues on this machine (with JKA installed on the SSD for some dumb reason...):

Ok I figured out what the issue was (for me anyways...). It seems that some option that's applied with Ja++'s renderer menu completely kills the FPS and whatnot. I started the game with defaults and the latest Openjk, but not Ja++, then I put the menu settings as high as they could go, and entered a custom resolution in the console and restarted, no issue. I then started up the game with Ja++ and maxed out the settings in the renderer menu there, and when those settings were applied, the game ran terrible again. So after deleting the Openjk.cfg (defaulting the game basically) again I just set up the video settings with only Openjk running, then when loading up Ja++ I didn't touch anything related to the renderer menu, and everything works perfectly fine now, lol.

Makes no difference. I had com_affinity manually set to 0 b4 anyways (which I think is the same as -1?)

@ post #39 & #42 (because I can't seem to quote anything here...) Similar issue, and attempts to fix the issue, here (although I didn't try SP). Except I have an Nvidia card. This has been the behavior with the most recent builds of openjk (either compiled myself, or from the builds.openjk.org page), or ever since the sdl2.dll is required in the gamedata folder. Any older builds work fine, latest ones though only give like 1-2 fps every OTHER second, and even a basic map like ffa3 takes minutes to load (normally I can load a huge map like Atlantica in under 20 seconds, and even on a map like that the fps would rarely go under the 125 cap...). Removing the Openjk folder from "Documents" and having everything reset didn't really work either, at least once I put in the custom resolution again (although at 800x600 the game was pretty much frozen saying "connection interrupted"...). This is on a win 8.1 64 bit machine as well, and never had any issues with openjk b4. Not really sure what's wrong now.