mrwonko

FYI: They've rebranded to gog.com, which no longer means anything. Because that's not confusing at all.

Are you sure there are already cuts in the geometry where there are cuts in the texture? Select an adjacent face and move it to see if there is indeed a cut.

You do have to create splits, nothing changed if you're using my Blender plugins. It sucks, but it's that way. What you don't need to do is separate every single triangle, which I assume is what you did leading to that explosion in vertex count. Don't do that. Only create cuts where necessary - in places where the texture has cuts. You can use a UV Test Grid texture to see the cuts in the 3d view.

I started creating a video tutorial on playermodel creation but got stuck when I had trouble modelling hands - I'll try to give that another try soon, maybe I'll get further this time.

There's a UV seam, you need to split the meshes at UV seams. It's something the exporter should ideally do automatically, but it can't.

My crawler was made specifically for the jk3files page and I have no interest in adapting it to anything else. I used Scrapy, which made it fairly easy; here's my source code in case anybody wants to study that instead of the docs.

There were a couple of Iron Man skins on JK3Files, but this is the best looking imo.

The XL Engine can load the levels, maybe contact the author for information about the format.

I gave it a try and yeah, while held the blade is invisible but the hilt is not. I vaguely remember having seen this before, but I don't remember what causes it.

Is there a place for documentation? I suppose there isn't much available yet, but if there's a wiki page somewhere you don't need to write it all yourself. I'd be interested in playing around with this a bit, and I might as well document it while I'm learning it.

What do you mean by fix? Make the lightsaber visible when holding it? That would probably require a proper hand tag on the player model. Or make it invisible even when thrown? Then you'd probably need a custom saber with invisible blade & model.

I can't imagine there being LOD. Typically you'd handle vis by placing antiportals, not sure if that happened here, far too few people know about proper vis setup.

That's pretty neat, though yes, very tedious. Ideally you'd still place light_junior throughout the map to create a proper lightgrid so the "dynamic" lighting works (on playermodels, first-person weapons etc.), but the amount of work gets pretty obscene. I suppose with a plugin they could be exported as well? They're basically evenly spaced light probes.

What you're talking about sounds highly exaggerated to me, but I totally get not being active any more - I haven't produced much in the last years either. Still sad to see you go. And everybody else please shut up about not wanting women in your Star Wars. If you need to share your bigoted views, create a separate topic in nonsense; I don't feel that's a productive discussion in this thread.

This does sound like a bug in the code, if I find some time I'll look into it.

The argument is that without some form of updater/version check people will never update, so that's kind of important to have asap.

That looks useful, though it's only a plugin, and I'd probably need to update my plugin to take advantage of this.

Plenty, I imagine, though I can't remember what I used 10 years ago and it wouldn't be quite the same anyway. Maybe start with the Blender manual?

It doesn't need to be a separate folder, simply extracting the files into base works as well. But you will have to unpack the .gla file as well as the .glm you're importing, keeping the directory structures intact.

You'll have to re-weight it to the skeleton.

Fair point. For your ordinary Mac user we should really just work - it must be possible to include libraries in an app bundle since everything else works, so let's just do that.

I'm not saying it doesn't work, and after 10 years I'm used to it, but it's not intuitive for beginners.

Homebrew is pretty much the go-to package manager on Mac, yes.

Off the top of my head, a mix of both common criticism and my own experience: The whole UI has a steep learning curve; being fully customizable has its drawbacks.When in object mode, one undo erases all the changes made in edit mode. From a programmer's point of view I can see why this is, and I occasionally use it to my advantage, but it makes it really easy to lose work.The reference counting resource user system is really weird to non-programmers as well.Right click to selectCan't edit vertex normalsCan't weight emptiesCan't display vertex indices let alone set themMore stuff I'm forgetting

You're wrong. That's what animation.cfg is for: defining how long each animation is.