eezstreet

If you make a "People" tab over a "Modders" tab, that might entice clan leaders and such to make up their own page. Thus, more clan/community-oriented over mod oriented

Good. Now the site will be more leaned towards clans and things of that nature, I hope. Now then. I used a teleporter to visit Australia, and it's the 24th. Where's my news update, Cael?

That's all well and good, but pretty irrelevant. The issue is raised on the client whenever it tries to draw the refEntity (the renderer version of the ent in a sense), and it crashes on the engine. So there's no real accurate way of determining where exactly it happens. However I'm like 90% certain that if you assigned Ragnos/Saber Droid a different GLA/GLM, they wouldn't crash at all. It's likely just another stupid inconsistency between SP and MP though. I frankly can't understand why the saber droids weren't on the humanoid skeleton to begin with. They could have been just fine on the humanoid skeleton with modified animations. But I digress.

If that's how FM3 fixed it, that's not fixing the actual issue behind it, that's just dressing up the issue. I highly doubt that FM3 actually RE'd the game and fixed the issue itself, otherwise it would have been a pretty large headline. Like I said, it might be worth checking to see if there's any key differences between the saber droid/ragnos and say a rancor in terms of hierarchy etc, bones aside. There's something in the skeleton of Ragnos (I think) that the game doesn't like.

Ragnos / saber droid are broken at an engine level, and nobody really has any idea as to why (my guess is that it's in the engine code handling GLAs - might want to look at their skeletons and see if anything is out-of-the-ordinary)

slaves illegal in murrca fgt

Old news.

I'd ask Rich if I were you. He's always behind the scenes coding weird things into JA (SOF2's RMG port works, with a little bit of maintenance, Siege was in JK2, etc)

edit: wasn't ever "broken", it's just leftover code from Quake 3

give it better graphics, everyone will be none the wiser.

>> implying that raz0r employs slaves to help him do work

I like JK2. But I don't know if a lot of people play it anymore outside of the "chat and duel" scene.

Hello there

gah fff, turn cg_shadows to 1 or something where it won't ruin the screenshots of your model

As long as your hit detection code isn't nearly as derp as MB2 (8 similtaneous hits in same map = 9th collision never happens, hits rely on oft-inaccurate hit box data, et al). That said, I think the droid classes in MB2 probably should have been combined into a megaclass, since they're quite novelty in all reality I've found. I do think that there is some room for improvement with semi open mode as well. But I hope your team situation pans out a lot better, and I hope you aren't silently knocked out of your team for someone else throwing a fit. As everyone knows, if you're going to kick someone out for someone throwing a temper tantrum, you should probably talk within your team to let them know that they're gone. Probably doesn't hurt to make sure their Mercurial account isn't still running after two weeks or so either. Oh, and by the way, just a tip, if you're making MB3 cross-platform, best to release a launcher for it under Qt, not C#, as that probably, you know, makes a lick of sense. Oh, should stop derailing my thread with pointless banter as well. My gripe isn't with modellers, it's with angsty programmers that have an overly cautious attitude with the code, and treat their community badly. I think I've sufficiently made my gripes clear though, so no need to pinpoint which MB team members set me off @@Jango40: try turning off or down the SSAO or DOF settings. Those are fairly intensive.

what do your changes entail, and what is your PK3 named?

Protect - gfx/misc/forceprotect Absorb - gfx/misc/personalshield Team Heal/Energize - powerups/ysalimarishell (?) Unknown what each file is in for these.

Probably needs coding in order to render things in fullbright while in sight (might be able to get away with using a shader though). But the rest of what you mentioned should work fine. All of what you mentioned is done with shaders.

Not sure. I do know that the major size discrepancies occur because JK2 used videos instead of ingame cinematics though. I haven't actually cracked open the JKA XBOX disc yet though. Expect it to be teeeeeny tiny though, like 640x480.

Replace the .bhc and use a different script compiler. Done.

Especially since they managed to worsen the saber hit detection in the worst way possible.