mirror of
https://git.do.srb2.org/STJr/UltimateZoneBuilder.git
synced 2024-11-27 22:22:32 +00:00
518d3db5ae
TEXTURES parser: part of a TEXTURES filename is now used as a path in Image Browser. For example, textures from "textures.stuff" will be located in "[TEXTURES]/stuff" in the Image Browser. TEXTURES parser: added "//$GZDB_SKIP" special comment. Parsing of the file is stopped after this comment is encountered. Updated documentation.
42 lines
4 KiB
HTML
42 lines
4 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
|
|
<head>
|
|
|
|
<title>GZDoom Builder features</title>
|
|
|
|
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
|
|
<link rel="stylesheet" type="text/css" href="../default.css" media="screen" title="Default" />
|
|
<style type="text/css">
|
|
<!--
|
|
.style1 {
|
|
color: #990000;
|
|
font-weight: bold;
|
|
}
|
|
-->
|
|
</style>
|
|
</head>
|
|
<body>
|
|
|
|
<object type="application/x-oleobject" classid="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
|
|
<param name="keyword" value="faq">
|
|
</object>
|
|
|
|
<div id="gz_title"><h1>Frequently asked questions</h1></div>
|
|
|
|
<div id="contents">
|
|
<p><strong>Q:</strong> I'm getting a ton of "<strong>Unable to find the DECORATE class '[some actor]' to inherit from, while parsing '[some other actor]:[DoomEdNum]'</strong>" warnings. What's wrong?<br />
|
|
<strong>A:</strong> This happens when a DECORATE actor is inherited from another actor, which is not defined in game configuration and is not defined in any included resources. <br />
|
|
<span class="style1">If you are using (G)ZDoom:</span><br />
|
|
To fix this, add "<strong>(g)zdoom.pk3</strong>" as a map resource. Don't forget to check "<strong>Exclude from testing parameters</strong>" chekbox while adding it, otherwise (G)ZDoom won't load your map. "<strong>(g)zdoom.pk3</strong>" can be found in (G)ZDoom folder.<br />
|
|
<span class="style1">If you are using Zandronum:</span><br />
|
|
To fix this, add "<strong>zandronum.pk3</strong>" as a map resource. If you are using Skulltag monsters, you'll also need to add "<strong>skulltag_actors.pk3</strong>" and "<strong>skulltag_data.pk3</strong>". Don't forget to check "<strong>Exclude from testing parameters</strong>" chekbox while adding any of them, otherwise Zandronum won't load your map. "<strong>zandronum.pk3</strong>" and "<strong>skulltag_actors.pk3</strong>" can be found in Zandronum folder. You'll have to find <strong>"skulltag_data.pk3</strong>" on your own.</p><br />
|
|
<p><strong>Q: </strong>Dynamic lights defined in GLDEFS are not rendered in Visual mode / I'm getting a ton of "<strong>Light declaration not found for light '[light name]' ('[source]', line [n])</strong>" warnings. What's wrong?<br />
|
|
<strong>A:</strong> GZDoom Builder doesn't include GZDoom's/Zandronum's GLDEFS light definitions.<br />
|
|
<span class="style1">If you are using GZDoom:</span><br />
|
|
To get rid of these errors, add "<strong>lights.pk3</strong>" as a map resource. Don't forget to check "<strong>Exclude from testing parameters</strong>" chekbox while adding it, otherwise GZDoom won't load your map. "<strong>lights.pk3</strong>" can be found in GZDoom folder.<br />
|
|
<span class="style1">If you are using Zandronum:</span><br />
|
|
To get rid of these errors, add "<strong>zandronum.pk3</strong>" as a map resource. Don't forget to check "<strong>Exclude from testing parameters</strong>" chekbox while adding it, otherwise Zandronum won't load your map. "<strong>zandronum.pk3</strong>" can be found in Zandronum folder.</p><br />
|
|
<p><strong>Q:</strong> I don't like the "fake contrast" (<a href="http://zdoom.org/wiki/Fake_contrast">zdoom.org/wiki/Fake_contrast</a>) GZDB uses to render sector walls in Visual mode. How can I disable this?<br />
|
|
<strong>A:</strong> GZDB's Visual mode emulates (G)ZDoom's default rendering preferences (in (G)ZDoom, Options -> Display options -> Use fake contrast is "on" by default). You can change this behaviour by adding "evenlighting" or "smoothlighting" property to the "map" or "defaultmap" definition in the MAPINFO. More info about MAPINFO properties supported by GZDB can be found <a href="mapinfo.html">here</a>.</p>
|
|
</div>
|
|
</body>
|