quick/netradiant-custom
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

misc_model _skin/skin key: handle both DP and Q3 naming conventions

Browse Source 
disable trying skin 0 by default
not that it does much atm, as assimp md3 loader handles .skin and shader name substitution alters non path names
handle \r\n endlines in .skin
This commit is contained in:
Garux
2021-11-10 22:25:45 +03:00
parent 76017a8ce3
commit b474073ebe
6 changed files with 22 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/Complete_list_of_entity_keys.htm
View File

@@ -211,7 +211,7 @@ td.formatted_questions ol { margin-top: 0px; margin-bottom: 0px; }
<li><strong><code>_clipdepth</code>:</strong> thickness of autoclip brushes</li>
<li><strong><code>_frame</code>, <code>frame</code>:</strong> frame of model to load (doesn't work)</li>
<li><strong><code>_remapXXX</code>:</strong> <code>XXX</code> can be any string to allow multiple keys for this; contains a string of the form <code>from;to</code>, and any shader <code>from</code> in the model will be replaced by <code>to</code>; the special value <code>*</code> in <code>from</code> matches all shader names</li>
<li><strong><code>_skin</code>, <code>skin</code>:</strong> skin number to use</li>
<li><strong><code>_skin</code>, <code>skin</code>:</strong> skin number (DarkPlaces convention) or name (Quake3 convention) to use</li>
<!-- <li><strong><code>model2</code>:</strong> path name of second model to load</li> light code reads this for brush entities-->
<li><strong><code>model</code>:</strong> path name of model to load</li>
<li><strong><code>modelscale</code>:</strong> scaling factor for the model to include</li>

2
docs/shaderManual/quake-editor-radiant-directives.html
View File

@@ -88,7 +88,7 @@ textures/liquids/lavahell2 //path and name of new texture
-->
<h2 id="trans">qer_trans N.N</h2>
<p>This directive makes brush transparent when seen in the editor (no effect on game rendering at all). It can have a positive value between 0 and 1. The higher the value, the less transparent the texture. Example: qer_trans 0.2 means the brush is 20% opaque and nearly invisible.</p>
<p>This directive makes brush transparent when seen in the editor and filterable by 'translucent' filter (no effect on game rendering at all). It can have a positive value between 0 and 1. The higher the value, the less transparent the texture. Example: qer_trans 0.2 means the brush is 20% opaque and nearly invisible.</p>
<blockquote>
<h4>Design Notes:</h4>
<p>On GtkRadiant 1.4 and earlier, if the shader uses qer_trans and a qer_editorImage with an alpha channel, the transparent areas of the editorImage will be 100% transparent. To keep the solid areas of the editorImage opaque, use a near 1 value for qer_trans (eg. 0.9999). This is useful for grates, windows, fences, etc. If using GtkRadiant 1.5 or later, use qer_alphaFunc for editorImage masking instead.</p>