mrwonko

It should just be a matter of moving the bespin cop's model.glm and model_default.skin into kyle's folder in models/players, I believe.

Wrong, there are even two representations: -0 and +0. Bruce Dawson has a nice series of blog posts on floating point numbers.

The whole point of having the origin texture is for defining origins. If it were a matter of order you could just use nodraw. But you can't, because that's what origin is there for. I would very much like to get a step-by-step reproduction or a video for the problem you're having... The only problem related to selection I'm aware of is with copying - if you clone an entity, pressing N will edit the original's properties, not those of the selected copy. Anyway, as for wobblyness, that may be due to patches being hard to make perfectly round due to math.

Maybe you confused blocksize and gridsize... The former is for vis, the latter for the light grid. What had you set it to?

No. You can only hard code different times for different states, i.e. save the current location and execute different moves depending on that.

I thought it was just a matter of using a water shader (such as the ones in common)? There may be more effects in SP than in MP.

Besides your current troubles, keep in mind that you can only have one portal in view at any time. If you have multiple (e.g. 6) only one will be displayed.

To what end? Planning to redistribute your map via floppy disk?

Q3Map2 can handle misc_model with either of those formats, as well as .ase (and possibly more?).

Surely Maya can export lwo, obj or 3ds? Those all work.

Okay. Or do you need some specific bone and animation names? Or some tags? Tags are a pain...

That's done with a shader. There's a bunch of transparent gradients in common.

How so?

May or may not work, depending on whether the format has changed since...

You mean the weapons used in first person, which are usually MD3 files? You'd rather use GLM?

Take a misc_model, give it a _remap old/shader/path;new/shader/path property.

Why misc_model_static? Go for misc_model, I'm not aware of any big limitations regarding them (unlike misc_model_static, which should for one count towards the entity limit of 1024) though I never stress tested them. And yes, I too think that you should just use brushes for visibility and physics and go for models otherwise. I'd have to do some research on lightmapped models, but I don't think they're particularly problematic.

https://jkhub.org/files/file/1413-blender-264-jedi-academy-plugin-suite/ There are a lot of things you have to do correctly for it to work. Take a look at the pdf in the archive and at the vehicle modelling tutorial, which covers most things as well: [sharedmedia=tutorials:tutorials:127]

But that's actually one of the main things your importer should handle, it's bound to happen a lot.

No I wouldn't be.

I have no idea what and SBD gun is, but replacing weapon models isn't all that difficult, provided you can model.

How about upgrading to 1.04?

Could you elaborate on this? Are you thinking about an extra file per face state? Maybe you can ignore the depth? The only thing that causes outward movement on your faces is blowing out one's cheeks, right?

You rarely need more than one waypoint_navgoal. Just have a proper waypoint net. And the only thing that needs to go into a dowait task is SET_NAVGOAL, since that's the only way to wait for him to finish. But since you don't want to wait for that anyway you don't need a task at all.

Since Jedi Academy itself is Open Source, OpenJK is no less insecure. To the contrary, exploits are actively being fixed while nobody patches Jedi Academy itself anymore. Find out how your server got crashed (e.g. by running a packet sniffer) and relay that information to the OpenJK team and I'm sure they'll fix it.