Node Revised.
Everything I've created from scratch (released under CC-BY), & everything Geartrooper & others have created is listed in the readme.
To my knowledge, I have not broken Geartrooper's CC-BY-NC licence, plus I have no way to contact him.

P.S. Could you specify exactly what's wrong with the packaging, if it's not your "what to fix" section? If so, I can't add anything to or change the package until next week.

He means to say that your folder should be inside another folder structure of packages/mapmodels first.

so pyccna/mapmodels/[models]?
I'll change that once I get access to fast internet again (most likely next week).

inside another folder structure of packages/mapmodels first.

It would be Packages/models/Pyccna/...

Okay, got it now, I'll fix it when I get good internet access.
For the time being, can we ignore the packaging issue & focus on the actual models for a minute?

You both packaged incorreclty actually. Package it as packages\models\mapmodels\pyccna as the models folder is very messy already and you`ve noted as mapmodels anyway.

Great job with the references, but now I'm still missing the links of where you actually got that stuff all from.

Okay, I'll break it down for you...

Wireframes I made: The wireframes for the FSS_Pyccna, Debris, Guard_Wood, Scribe_Wood, TC1S, all the guns in the Snoutx10k folder, and the sergeant_head
*Created by using the Cube 2 engine, and Blender.

Skins I made: skin for Debris, skin for FSS_Pycnna, skin for Snoutx10k (Warzone), skin for fsr1, skin for m390, skin for svd, skin for sergeant_head
*Created using Adobe Photoshop

Everything I did not make:
The Snoutx10k playermodel: I converted Geartrooper's playermodel to obj and posed it using Blender.

Wireframes for snowevergreen & snowevergreen_2d: the originals can be found under sauerbraten/packages/models/vegitation

Wireframe & animation for Fed_Door: the originals can be found under sauerbraten/packages/models/doors/door_03 (Created by Nieb)

Skin for the TC1S: tile4c, found under sauerbraten/packages/trak5

Skin for the Guard_Wood: ik_wood_planks_128b, found under sauerbraten/packages/ik2k

Skin for the Scribe_Wood: ik_wood_planks_128b, found under sauerbraten/packages/ik2k

Skin for the Fed_Door: the originals can be found under sauerbraten/packages/models/doors/door_03 (Created by Makke)

Skin for MG36: it is an edited png of Geartrooper's gl skin, the original can be found under Sauerbraten\packages\models\hudguns\gl

Skin for the HK36c: it is an edited png of Geartrooper's gl skin, the original can be found under Sauerbraten\packages\models\hudguns\gl

Skin for snowevergreen: edited using photoshop, original can be found under Sauerbraten\packages\models\vegetation

Skin for snowevergreen_2d: edited using photoshop, riginal can be found under Sauerbraten\packages\models\vegetation\tree03_sprite

Glad to see someone else sees a use for them.
(I think they're a good addition for anyone making an SP Map that needs a static secondary character)

Have a guess why; it's a playermodel which nowadays have more than 4000 vertices (don't even think how much faces that actually would be). Most mapmodels aren't even reaching 300 vertices (only trees do actually, yet they never are that expensive as a playermodel but often not advised to use in large numbers). They just aren't meant to be used as a mapmodel. You could better use the old ironsnout or monsters instead.

Doubtful; I'm not having problems with any of the ironsnout models, _{(plus since the original model is now split into legs, body, & arms, it cuts down on how much is actually displayed per model)} it's the FSS_PYCCNA models because that model has 50x the vertices than the snoutx10k's and is 20x more complex.

you do realize most games playermodels are between 5000 - 15000 verts ;p they just use loding... some times there even 20,000+ ;p mostly sp games

i dont think your gonna have any problems with a few thousand more verts on your map most games don't use a marching cube algorithm (which is not very graphically intense) they use models, lots of models, some of which are pretty large ;p

as far as the error i dont think it due to to many verts (faces, tris etc) that would just cause a performance problem (like getting 2 fps). Run time errors (9/10) are due to null pointers, my bet it is its something in your config 0.0 ;p

chasester

Well put it this way, if FSS_PYCCNA is spammed on the map like over 100 times, Sauer crashes.
Even with the original FSS_PYCCNA model it was too large for the engine to handle & wasn't displaying half the vertices, or it was skewing them to where the model became a giant spiky cube. I don't know why it does that, either way, back to the main point; just don't use FSS_PYCCNA too much on one map & if using it as a platform or elevator, don't put volumes (except for clip, alpha, & glass) in its path.

I`ve noticed the weapons have been made roughly with Saurbraten itself and you`ve forgotten to calclight or even remip before exporting. This gives them a lot of unnecasary triangles/vertices.

lights cannot be preserved when exporting from sauerbraten i thought

The command calclight does more than just the lighting you know.

I'll bear remip in mind as I put the finishing touches on Warzone Ch2.