mrwonko

Could somebody write a script for Blender that splits the selected mesh(es) at the UV seams? I'd do it myself but I'm probably busy until mid-July. You can take a look at the 3ds exporter, which does this. (Alternatively, add this functionality to the GLM exporter in addition to applying all modifiers besides armatures and triangulating it.)

Short answer: Bascially no. Long answer: You can import premade geometry ("prefabs") in Radiant, but there isn't much available. You can place the models that come with the game using misc_model, but you'll still have to manually add clip brushes to prevent players from moving through them. Either way you'll still end up having to put a lot of work in.

There's EasyGen for creating terrains, and geometry can also be modeled (e.g. in Blender, which isn't really any easier if you're new to it), but in the end you'll always have to use the Radiant to make it playable.

" error is a known bug/issue with Blender, and there's an easy fix for it. I wouldn't call it a bug, it's just a missing feature. Ghoul 2 models are split at the seams, and since the exporter can't do that automatically, you have to do it manually.

Not really, you just need to fix the weights if you move stuff around. Unless having to put in some work means being screwed to you.

It's probably a matter of weighting, actually. Without reweigthing, a moved mesh will transform weirdly when bones are moved.

Ideally put it in the JK2 folder; or at least replace JKA's _humanoid.gla with that of JK2 while importing.

Yeah, the UV stuff is quite annoying... I should write a script to do all the necessary preparation (or better yet adjust the exporter to do it) but I really don't have the time or motivation. In GLM, every vertex can have only 1 UV coordinate. Blender does not have this limitation, but a model that doesn't meet it will not export. One way to find seams is to use a gradient (like this one) as the texture. Wherever there's a seam in the texture, the model has to be cut, too. (Too late, eez, I was already here.)

Take a look at the source code, I bet some of the non-existent paths are defined there. You can just do a text search for the paths in question. Chances are the layout is defined there as well, if there's no .menu file for it.

Are you talking about GLM for player models? In that case something like 32 bones and 1000 vertices and one texture per mesh (though you can have multiple meshes per model), 4 or so bones per vertex (though my exporter will drop the least influential bones if there are too many), 3 sides to a face, very importantly 1 UV coordinate to a vertex (meaning you have to split the mesh at the seams (which to be honest the exporter should be capable of doing)) and normals are exported on a per-vertex level, so enabling smooth shading gives an accurate representation of the ingame look. Or is this about animated md3 models? In that case I'm not entirely sure, size limitations (range [-512, 512)) aside. Or do you want non-animated (misc_model) map models? Those are baked into the BSP by Q3Map2 and thus have very few limitations.

The tutorial mentions a rgoer template that's supposedly required... Download on there is broken though.

Do non-terrain textures show up fine? Which shader templates are you using when exporting from easygen?

Instead of `multiple lines` `of code`you should write ``` multiple lines of code ```in the wiki. That way you don't get a separate code box for each line.

In the case of my exporter, 1 Blender Unit = <export scale setting> * 1 Game Unit. There's probably an md3 exporter around somewhere, or you could try converting it to glm with MD3View and import that.

Well you can always do it using shaders... I don't know about entity flags.

No. They're fixed movies, like an .avi, so they can't be adjusted to contain the current playermodel. Use cutscenes for that.

what about //(BHVD) set ( /*@SET_TYPES*/ "SET_FORCE_INVINCIBLE", /*@BOOL_TYPES*/ "true" );

In Blender? I don't think it matters there.

Plugins > bkgrnd2d

Tags. Looks like they need to be adjusted/added. Take a look at the mark1 model - what's the name of its muzzle tag? You need to change the Droideka model, adding the missing tag.

You have three options: Roff. Animated Rigid Bodies. Hardly what you want here, but for the record: I think there's a limit on how many of them you can have, but the objects animated this way can have collision detection. MD3. Per Vertex Animation. Size limited to [-512, 512). Take a look at e.g. the button scripts to see how this works. Ghoul2. Bone animation. Need an NPC, or possibly that misc_ghoul2 or whatever it's called, I never tried that. What exactly are you having trouble with?

It's tested up to 2.69, but new Blender versions can load older saves just fine (and mostly vice versa, too) so you can just save as a .blend and load it in a 2.7+

Have vertices in roughly the same places, I suppose. How do you weigh that it becomes a problem?

Oh, I see. GLM only support one UV coordinate per vertex. So you'll have to split the mesh at the UV seams. One way of doing this is to mark those edges as sharp and use the edge split modifier to split sharp edges.

It would appear so, yes. Thanks a lot.