Model Prefabrication Guide

Suicizer | 2011-06-30 08:32

[

points ]

(1 vote)

Blurb A prefab for mapmodels, with some side note of the existence of the ingame mapmodel gui.

Detailed description

Informations
This node once had a different plan but has been changed to a model prefabrication guide, as extension for the Texture Prefabrication Guide (so new beings can also understand the commands and their values of (map)models).
Why this decision?
Because I fail at scripting and I won't be able to create a script which let players define commands for models in-game...
Unlike in the Texture Prefabrication, models won't be loaded as an example. This is just because models have a larger amount of commands which most of them have a different way to specify (like md3spec mesh 30 for example. Where the mesh still has to be specified, while such thing happens directly for textures, as long as the diffuse texture is under the line of specscale).

Notifications
The commands and their parameters are shown in the guide like the next image:

Beware! This is not how you should actually write the commands and their parameters into a real .cfg-file!
It's only positioned like that so every parameter can be explained individually. This should make it easier to understand all parameters of certain commands as several of them have parameters with completely different purposes or cases which should be explained.

Cube Engine 2 supports more formats than the guide offers. Those have equal options to the .md5-format or .md3-format. These are;

.iqm (Inter-Quake Model), equal to the .md5-format.
.smd (Studiomdl Data), equal to the .md5-format.
.obj, equal to .md3-format (objlink and objanim are not supported).

Just replace the md3* or md5* to execute the commands.

Improvements
28th of June 2011
Reviewed the prefabs and added "unknown" commands.

17th of November 2011
Rewrote the prefabs to get a cleaner result for explaining every parameter of every command.
Deleted the prefabs of the "iqm", "smd" and "obj" formats, as they are identical to the "md3" and "md5" prefab.

18th of November 2011
Wiped out some typos and added more information about commands which affect the lighting of the model.

22th of October 2012
Fixed some small mistake which I've overseen.

Config file config_prefab_19july13.zip (11.17 KB)

Rating

points

(1 vote)

Comments

RaZgRiZ | 2011-06-30 10:33

first thing i noticed:

guiradio "on" "modelcollide 1"
guiradio "of" "modelcollide 0"

seriously? :P

guicheckbox "Model Collisions" modelcollide

Suicizer | 2011-11-18 00:59

Thanks a lot razgriz! I wasn't sure of that would do the trick. I'm still not sure anyways, because all settings needs to get saved in a notepad file after all (so like setting up a map-cfg ingame).
I'll just read "menus.cfg" another time, to find out how that works.

Edit:
I hope people like this prefab also...

unixfreak | 2011-11-18 12:14

Very useful, thanks again.

One question... i have an md3 model of a flying saucer i made in blender, and seem to have problems with the textures appearing very dark (i think there is no lighting at all).

I can't try this right now but after skimming through your prefab, i'm guessing if i set 'md3ambient' to a higher value this will make fix the dark textures on my model? Or do i need to adjust the light from somewhere else (maybe before exporting the model from blender?).

Screenshot for reference:

Suicizer | 2011-11-18 12:47

There are different ways to specify the "darkness" of how the skin of the model should be rendered, like:

The command "md3ambient" (or "mdlambient") is about how dark the model will be in a shadow only (so unlighted or lighted with a very low intensity).
The command "md3glow" (or "mdlglow") is about how bright the model will appear (at all times) excluding the result when the model would be in a dark area. This means it still appear darker when it's unlighted or lighted with a low intensity.
The command "md3fullbright" (or "mdlfullbright") is about how bright the model will appear (at all times), included the result when the model would be in a dark area. So any lighting has no effect on the model at all.
I hopes that helps (I'll probably included it in de prefab either).

If you just have a certain light-entity which lights the model, I would recommend to use "md3glow" (or "mdlglow"), as this preserves the atmosphere which the model emits (something which "md3fullbright" or "mdlfullbright" lacks and "md3ambient" or "mdlambient" breaks).

User login

Navigation

Users on Quadropolis