I have radeon hd 6870 running cat 10.10 at first and now 10.12. I simply renamed my jk2mp.exe to quake3.exe and i have no trouble.. all video settings work great. If you are having trouble with your video settings you must check your jk2mpconfig.cfg the one in the
C:\Program Files (x86)\LucasArts\Star Wars JK II Jedi Outcast\GameData\base
and the one in the
C:\Users\NAME\AppData\Local\VirtualStore\Program Files (x86)\LucasArts\Star Wars JK II Jedi Outcast\GameData\base
set r_mode "-1" set r_customwidth "1600" set r_customheight "1200"
this will get your screen size right.. dont worry about your actual screen size.. if you dont use a widescreen monitor change it to 1024 and 768 otherwise leave with those values.
set everything else to On and 32bit , trilinear you can run on high settings without issue with a card that has 10.9 or better obviously. make
after you fix all this do a /vid_restart in console then /write namehere.cfg to save it so you can exec it later or rename it to be your jk2mpconfig.cfg
also if if you want to use xfire with this you can easily alter the xfire_games.ini to recognize quake3.exe located
just right click "edit" and change all jk2mp.exe to quake3.exe and everything works normal again.
Good Luck! Good Gaming..
I created a little fix ( it's more a workaround ) for the crash on new versions of the ATI driver. Should work with all versions of JK2 and JKA.
JK2 and JKA crash on startup if you use it together with an ATI graphics card and driver version >= 10.5 It's because it trys to print all the OpenGL-Extensions on startup which are supported. This string became to big over the years and will result in a crash. This patch disables that message.
I'm a bit iffy about modifying the executable. I believe Xycaleth has a cleaner (in regards to legality) solution involving a proxy dll for OpenGL that only reports necessary extensions, but I can't confirm it works on all platforms as of yet. I'll leave the link there for now and sort it out in the morning in-case I'm being irrational.
EDIT: Xycaleth just mentioned your patch will also trigger the copy-protection, and I'm not going to let you bypass that =p
@Raz0r I don't know who Xycaleth is but it seems like he didn't even try it. Because i checked it and it doesn't, cuz it's only modding the string data inside the binary file...
I'm going to have the remove the link anyway, sorry. Binary modification is against the EULA, putting this file in a grey area, which GameFront will do its best to avoid. If you wish to challenge the decision, you'll have to speak to a network administrator such as Goody or Danny.
Also, interesting that the executable validation is only on the .code section o.o - I guess that means the 'checksum' is stored in the .text section? If so, do you happen to know where?
My apologies ouned. I've tried your fix and it does seem to work. The only problem is that it requires a direct modification of the jamp.exe binary, which is a violation of the EULA. The other problem is that the single player is still broken (though I'm sure you could easily come up with another patch for that). Just out of curiosity, does your fix work for Windows XP as well?
I just wanted to help... :rolleyes:
Yes it should work for Win XP, too. (But I only tested Windows 7 and Linux)
Why would raven or lucasarts care if we fix a bug^^
They don't care. Given a choice between using your fix (or any other fix that violates the almighty EULA) to play the game or not playing the game at all, they would prefer you not to play the game at all. Go against their wish and you could find yourself facing a legal prosecution.
I assume that LucasArts and/or Raven Software make some profit from every sold copy of the Steam version of the game, so by not allowing ATI users to fix this problem if the fix so much as scratches the surface of their precious EULA, they are actually doing damage to themselves since less people will spend their money on a game they won't be able to play anyway. Or maybe they have some deeper corporate strategy of making money that eludes me, some way that includes making more money by reducing the amount of potential customers (players). :clueless:
So AMD have apparently planned to fix support for JKA/JKO with the next driver release (11.1). Guess we'll find out if they hold true to their word. :P
Confirming that 11.1a includes a working OpenGL 4.1 fix. :D