1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 2<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US"> 3<!-- InstanceBegin template="/Templates/default_template.dwt" codeOutsideHTMLIsLocked="false" --> 4<head> 5<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 6<meta http-equiv="Content-Style-Type" content="text/css" /> 7<!-- InstanceBeginEditable name="CSS の相対パス指定" --> 8<link href="../../../../common/manual.css" rel="stylesheet" type="text/css" /> 9<!-- InstanceEndEditable --> <!-- InstanceBeginEditable name="ページのタイトル" --> 10<title>Untitled Document</title> 11<!-- InstanceEndEditable --> 12</head> 13<body> 14<div> 15 <div class="body"> <!-- InstanceBeginEditable name="本文のタイトル" --> 16 <h1>Common Settings (For Application Programmers)</h1> 17 <!-- InstanceEndEditable --> <!-- InstanceBeginEditable name="本文" --> 18 <p>This section describes common settings that involve configuration of item settings for particles.</p> 19 <p>These settings are items of interest to application programmers.</p> 20 <h2>Enable</h2> 21 <p>The checkbox for Enable is marked by default.</p> 22 <img src="assets/particle_common_setting.png" alt="Enables the common features."/> 23 <p>Features are disabled (i.e., the Enable checkbox is cleared) so the programmer has control over features and initial values. So even if a designer is not using a feature, it may be applied to the actual data being exported.</p> 24 <p>For example, say that the gravity values A, B and C are attached to a set of data, and A is enabled while B and C are disabled. The programmer might be using value A for the initial state of gravity, planning to switch the state later from A to B to C.</p> 25 <h2>Copy Resource</h2> 26 <p>The checkbox for Copy Resource is cleared by default.</p> 27 <img src="assets/particle_common_setting_01.png" alt="Common feature: Copy resources at runtime"/> 28 <p>When the checkbox is marked, features are copied as resources when the data are exported.<br /> The application programmer can change the parameters of these copied features to make different variations.</p> 29 <p>For example, say that at game development time the programmer has created multiple copies of the same particle data. If <B>Copy Resource </B>is off, then the parameters of the feature will all change together. But if <B>Copy Resource </B>is on, then the parameters of the feature can be changed individually.</p> 30 <h2>Optimize (Always ON)</h2> 31 <p>At the current time, this setting can only be configured as a Color settings option in the particle Properties panel.</p> 32 <p>When this is enabled, which is the default setting, data are optimized when created to lighten the memory load.</p> 33 <img src="assets/particle_common_setting_02.png" alt="Common feature: Copy resources at runtime"/> 34 <p class="hint_warn">Caution:<br /> The programmer cannot control optimized data.<br /> If you want to have control over the data for a feature on the programmer side, clear the <B>Optimize </B> checkbox for that feature.</p> 35 <!-- InstanceEndEditable --> </div> 36 <div class="footer" /> 37</div> 38<hr><p>CONFIDENTIAL</p></body> 39<!-- InstanceEnd --> 40</html>
