Cerez

It doesn't look like this anymore? Good. Keep it clean, boy!

I won't give you a cookie until you clean that GameData folder up.

Nope, that theory goes out the window... at least until the usability issue is fixed. The reason it's confusing is because there are too many locations the game is placing stuff into, and it's not clear to the user what order the game is prioritising these locations in loading sequence, and what it's overwriting, and whatnot.

Mark my words: clean that GameData up so that it matches a factory default JKA installation, and you'll get rid of the problem. Something went wrong in that mess -- something is interfering with the reading of the base assets or overwriting them... Start clean (in your base and GameData, too!), and add your JA+ in only after it works, and see if you get the issue again. That will help you find the cause. @@Xycaleth, could the source being in GameData also be interfering with JKA's workings?

Okay, now we're getting there! So jampgamex86.dll, cgamex86.dll and uix86.dll need to be packaged into a PK3 and placed in "Documents/My Games/OpenJK/base" for this to work! If you do the same for "GameData/base", the game craps on you and does what it feels like. Also, if you don't package the files into a PK3, the game craps on you and does what it feels like (when joining a pure server). So that leaves you with a lot of choice. (Documentation, anyone?)

I'm not following... It was happening in GameData? What? The copying? They're not, currently. If I were to put them in a PK3, would they still need to be in "GameData/base" for this to work? Or should I put the PK3 in "Documents/My Games/OpenJK/base"? This is so confusing...

What about faulty or lacking OpenGL implementations with the card? That GameData looks awfully messy to me... What if you made a clean start with a new installation and didn't mix the source and JAplus and god-knows-what in there... Might be easier to figure it out when things go wrong. Sorry, I'm not picking on you -- just trying to be practical. This looks like a debugging nightmare (and could very well be the cause of your problem).

No, I mean it literally copies the DLLs from the base assets into "Documents/My Games/OpenJK/base", replacing my OpenJK ones. After I join a pure basejka server, the whole thing reverts to the basejka game engine permanently. I need to do the manual replacement on the DLLs again. Edit: That gives me an idea: what if I revoked writing permissions for the game on these DLLs?

That's just JA+ telling you that you don't have the full release of JA+ installed, and the game telling you that what you have in your base folder is different to what the server has. All expected and normal. Those are perfectly fine except for the ui/hud.menu errors.

An update on this: If you are running a customised build of OpenJK MP, edit the following in the source code to eliminate the need for cheats to be enabled while using the first person view: XCVAR_DEF( cg_thirdPersonAlpha, "1.0", NULL, CVAR_ARCHIVE ) In "codemp/cgame/cg_xcvar.h" change CVAR_CHEAT to CVAR_ARCHIVE on cg_thirdPersonAlpha. This allows you to use the first person view without problems even on public servers. Thanks to Tr!Force for helping me with this one. That's fine, and you're right, but you also need cg_thirdpersonalpha to be 0 if you don't want the character model's head to get in the way of your view.

Definitely smells like corrupted assets0-3. *nods* Either by a custom mod or by themselves. Edit: OR it could be a serious rendering issue with the graphics card (rendering methods not supported).

In that case all that's left for you to try is to reinstall JKA, and see if the visual issue goes away. Otherwise your graphics card and driver may be outdated and/or not compatible with OpenJK. @@Xycaleth, is there any option to switch the blade rendering to a different method through settings?

Oh good. There is one drawback to my manual fix method: when I join a pure basejka server, the DLLs are reverted, and I have to copy and replace them all over again.

It is more likely that it is the driver.

It seems point 2 is the culprit then. That would explain bot the lightsaber blade visual glitch and the unusual shader rendering errors. The lightsaber blades are using OpenGL to render. Update your graphics drivers, @, and switch to the latest version of OpenJK, as @@Xycaleth recommends. You may also need to remove/disable GLDirect. Edit: Sorry, I missed the last page of the convo, but yeah, try updating the graphics drivers, and see if that helps with the rendering. I have 8.1 as well, and it runs perfectly fine here without DirectGL. It definitely has to do with your graphics card. Driver updates!

@@Xycaleth @@mrwonko Thanks guys. Finally managed to track it down, but this is really strange... Despite the fact that I have the OpenJK DLLs placed in my "GameData/base", the game is copying the basejka DLLs to "Documents/My Games/OpenJK/base" (even after a delete), and overriding what's in my "GameData/base" that way for some reason... What I did to fix this was to manually replace these DLLs (in "Documents/My Games/OpenJK/base") with the OpenJK ones.

Gave this a go, and it worked superbly, Tr!Force! Thank you. Not sure if this is OpenJK version dependent, but the actual CVAR settings were in "codemp/cgame/cg_xcvar.h" for me.

Found it: http://jkhub.org/tutorials/article/50-adding-entities-to-maps-after-compiling-editing-base-maps/ Thanks everyone.

This thing's killing me! My Mac build does what it's supposed to, and my Windows build ignores my changes. WTH?! I really need help from an OpenJK expert. @@Xycaleth, @@eezstreet, @@ensiform, @@redsaurus, @@mrwonko, ..?

It's not the script errors that are breaking it after all. Honestly, I think the game assets have somehow been corrupted. It's the last thing one wants to believe, but it sure is drawing to that conclusion. You are getting this error even with a clean directory and no problems/errors detected on initial loading. I can think of three possible reasons this is happening: 1. The assets are damaged and you need to reinstall Jedi Academy. 2. Your graphics card driver has problems with the shader implementations. The fix for this would be to update your graphics card driver. 3. Either your current release OpenJK binary is buggy or relies on "jagamex86.dll" for those shaders. Maybe try a different version/release of OpenJK?

Could you paste the log from the main menu while your base is clean? Thanks.

I've found something that may be a clue: The "gamename" when I load up OpenJK MP Solo mode is "basejka", not "OpenJK", and that exactly how it seems to be behaving. For some reason it's still running the base engine, and not my custom build of OpenJK. ... Why? The OpenJK cgamex86.dll and uix86.dll are in GameData/base, along with jagamex86.dll and jampgamex86.dll. The OpenJK binaries are in GameData, along with rd-vanilla_x86.dll and rdsp-vanilla_x86.dll. Is this a setting (at compile-time) I'm not aware of? What gives??

That's okay, "jagamex86.dll" is for the SP game. That's all you should have in "Program Files (x86)/LucasArts/Jedi Knight Jedi Academy/GameData/base", nothing else. Then run OpenJK (MP) and start a Solo game, and see if you still have the error messages.

I can see quite a few script errors... When you moved the custom PK3s out, did you move your custom scripts out, too? There should have been nothing but these files in your GameData/base: assets0.pk3 assets1.pk3 assets2.pk3 assets3.pk3 uix86.dll jagamex86.dll jampgamex86.dll cgamex86.dll