mrwonko

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

Sounds like a shader issue to me - what do the hood texture and its shader look like?

Only if you don't have a proper waypoint network! Although the visibility rule still applies between waypoints, i.e. there must be line of sight for waypoints to connect.

Well one issue I see with BS_WANDER is that given a proper waypoint network the npc will wander the whole map; if you only want it to wander in one area, you'll need a script.

Dunno, but I think the limit may be 512. I can take a look later.

Took a little longer than 3h but whatevs. Have a screenshot. Waypoints that don't appear to be connected use target2 etc., which (my version of) radiant does not visualize properly.

I never investigated this, but I always assumed navgoals were not part of the network... I'll supply a screenshot once I'm home (give me 3h or so).

Complain to someone else, idgaf. I've never had issues with the system and it yields good results; connecting waypoints automatically is done ingame during loading, so connecting arbitrary distant waypoints would be O(n^2), hence the limit.

Did you connect the waypoints? They won't automatically connect beyond some distance (512 units?) so you need to use target[2-4]/targetname.

Just take a look at the sp example maps to get an idea for how to do it properly; there's no need for a waypoint every 5 meters. Or I can create an example map in 10h.

You'd need to place a navgoal at every corner anyway; just make it a normal waypoint, which can be connected at any distance and can also be used for path finding outside of navgoals (e.g. when an enemy tries to chase the player). You can send an enemy to the opposite site of the map if you have a proper waypoint network. Generally needing some kind of pathfinding network - be it waypoints, a navmesh or whatever - is super common, as is having to create it manually, especially in older games. (And even in modern games like Skyrim, where a first approximation can be automatically generated, you still need a lot of manual adjusting.) No.

Wrong.

Multiple waypoint entities connected via target, target2 etc. Use "nav show all" to check them ingame. Only works in SP.

You almost never need more than one navgoal; it's just a matter of having a proper waypoint network. That's what the ordinary waypoint entity (without navgoal) is for.

Customization might not have a proper default skin; usually most surfaces will be *off. Try selecting a skin in the outliner on the left.

I think it probably has nothing to do with your resolution, but I can't tell what causes it. Are your drivers up to date?

Here, have some money.

It's a Q3Map2 feature; compile-time projection of decals onto surfaces. See the q3map2 manual.

I had some other issues, but those were obvious enough that I caught them.

I was afraid I might break something, rewriting all of the effects parsing... Thanks for the heads up, effects with the useAlpha flag should now work again.