Jump to content

ensiform

Members
  • Posts

    1,626
  • Joined

  • Last visited

Everything posted by ensiform

  1. Anything that prints from Com_Printf etc The Red box area is what I'm referring to. (Not using your HUD atm) It is not specific to MP either.
  2. The hugging is a bug too The fix long pre-dates OpenJK and is part of the mod code of course. It came from LucasForums bugfixes post (most of which were part of added to OpenJK via modbase merge)
  3. Just FYI, the notification box for regular prints (non-chat) is being blocked when using this HUD too. Could use some text indications of the values somewhere too tbh.
  4. It could be fixed more easily in something like MB2 of course. But any changes to the pmove in a compatibility manner or server-side mod manner are risky at best. Which is why that fix is used. Will just take some time to debug where its freezing and why? Presumably because the use item button stops processing of PM_Weapon thats my guess without looking as of yet.
  5. Huh? Which fix? which bug? Is it specific to MB2?
  6. Ammo text colors seem weird... Black for default, yellow for pickup, grey for busy/firing. Hmm not sure what else to try. May also want something behind the text so that its consistent with that background instead of whatever might be behind it otherwise. The ammo bar doesn't seem to work right now? (MP) That middle bar is in fact the armor bar not ammo bar.
  7. The difference is r_overBrightBits 1 and r_mapOverBrightBits 2 which aren't something in vanilla jka. And they are set in Q3A. So, serious tweaking to all of the lighting needs to be done. @@Boothand
  8. It has nothing to do with OpenJK though. The Steam Overlay controls hooking entirely to whatever program you tell it to.
  9. Menu editors don't help so much with JKA huds since the JKA hud code doesn't fully use the menu system at all. Only the information from it.
  10. No its a reference to the Movie It's in the trailer too in fact IIRC. @@DT85, I take it you've seen it.
  11. Slight movie spoilers, so don't click if you haven't seen.
  12. Well, its not a problem with the engine but within the mod. And switching to OpenJK (engine) won't fix this.
  13. Rich lost the source code to hydroball some years ago
  14. Added CMake installing guide to the wiki: https://github.com/JACoders/OpenJK/wiki/Installing-CMake-on-Windows
  15. To be fair FFA can be a dozen game modes with all the mods and the splinter communities turning it into many many other things.
  16. You could just try cg_thirdPersonAlpha cvar. 1.0 is fully opaque (default)
  17. OpenGL and VMs or RDP not the greatest idea. Like 5fps maybe.
  18. Most likely some Intel HD graphics doesn't have a large enough extension string to hit the crash or they have gotten better like nvidia to truncate before it gets to the game.
  19. Even if its just basic drop or grabbing ammo from player's ass, I wouldn't mind. I just don't want to see repeat of the bar graph showing player is reloading Use a +button or w/e or at least do most of the reloading in pmove.
  20. There is no actual patch for the regular games. However: You have several options, some of which you may not like . Are you intending to play Jedi Academy single player/ multiplayer? (If yes) Simplest is to just use an OpenJK build. See: http://jkhub.org/topic/2220-frequently-asked-questions/The others are: Downgrade to an older graphics card that doesn't have so many extensions.Switch graphics card vendors (ie: go from AMD to nVidia) as some nVidia drivers have a hack for jasp.exe and jamp.exe that works around the crash IIRC.Find a copy of the original Jedi Academy source GPL release that isn't modified like ours is, and fix the issue yourself.(If no, and you want Jedi Outcast) There is WIP support for Jedi Outcast Single Player, but you must build it yourself because we do not turn it on in the automated builds.No Multi Player support at all for OpenJK's JO yet.
×
×
  • Create New...