mrwonko

What do you mean, without coding? A config file is still a form of coding. The first step in adding such a feature is creating a precise requirement. How would new weapons be defined? I could see this happening, if we had enough manpower.

That's what the skeleton change dropdown menu in the importer is for - it changes the JKA bone hierarchy a little to fix those issues. A nice IK setup probably helps with animating; just import the skeleton and change it as necessary, I don't see why that would lead to any issues.

You'll want painscript, not fleescript; you can check HP in there and then spawn a new npc if it's below the threshold. Maybe show a cutscene to mask the exchange and make it clear.

sounds like you might've merged the animations the wrong way around?

OpenJK no longer stores config files in the game folder, to which a user may not have write access, but in his home folder; I'm not sure where there though, look for ~/.openjk or something like that.

OpenJK has autocomplete for map names - try pressing tab after entering map.

FWIW, as anyone who read the manual knows, if your basepath includes a GameData folder, the importer will be able to figure the rest out automatically.

This is either an issue with the shader, the texture or the model, although the latter is unlikely. Has the texture the right dimensions? How did you export the model, is it using relative paths? (I'm not sure if radiant would display absolute paths correctly though.) Are shaders involved?

As I said, roughly. 72" would be realistic, right?

In June I thought "jk3files is in a bad state... I better download everything." Turned out to be just in time. I have an online mirror and a torrent, although most torrent clients can't handle 40000 files (I downloaded the screenshots, too); I've had success with rtorrent on Linux and Tixati on Windows. I'm missing two dozen files or so, but most are there.

Seriously? Not even 3 hours and you become impatient? You should really give it at least a day. And you'll get better answers by asking more precise questions. Still, welcome.

Make sure they're not saved as progressive jpegs. If everything else loads perfectly, including shaders, it must be the textures. If you can't figure it out, share one of your textures on dropbox or somewhere like that where it doesn't get post processed, so we can take a look.

Make sure to use nodraw_solid (or is that just nodraw?) on the sides instead of caulk and ensure the force field Shader has the proper surfaceparms (look at common/env_glass for reference maybe). Also learn about the vis system; if you don't understand what's wrong here and didn't think to try making it a detail brush you probably need more of those in your map.

Well, you can put them in a different directory than the path you use in your shaders...

Just create your own skeleton.

You can really just use any skeleton, I think.

The xsi files are available here: http://mrwonko.de/jk3files/Jedi%20Academy/Utilities/Modding%20Tools/26624/ (there's also parts 2&3)

What Futuza said. And yes, it works with 2015.

I never tested any newer Blender than 2.69.

Me, maybe I can take a look tomorrow.

The UV issue is usually due to loose vertices, which can have UV coordinates in GLM files but those are lost upon import into blender, which only saves them per polygon. I think this can be fixed by selecting and hiding all faces in edit mode, which should leave the loose vertices visible for you to delete.

How are you trying to achieve this? I don't think it's possible with scripting, you probably need to edit the code.

Welcome aboard! In my experience, one unit is roughly one inch, give or take.

It would probably be a good deal easier if you just uploaded your file so we can take a look.

Hate all you want, I'm having fun