editor extensions
From Wiki
Holy Diver (talk | contribs) (Created page with "<onlyinclude> Extensions in this section deal exclusively with the editing tools which authors use to make new Sword of Moonlight games. For the most part other sections pertain ...") |
|||
| Line 4: | Line 4: | ||
====clip_volume_multiplier==== | ====clip_volume_multiplier==== | ||
| − | {{Ex/inival|1.1.1.3|real numbers|scales the clip volume in the windows where 3D graphics are on display. Scaling by values less than 1 will make objects appear larger, or closer, and scaling above 1 vice versa. 0.5 works very well in [[SOM_PRM]]}} | + | {{Ex/inival|1.1.1.3|real numbers|scales the clip volume in the windows where 3D graphics are on display. Scaling by values less than 1 will make objects appear larger, or closer, and scaling above 1 vice versa. 0.5 works very well in [[SOM_PRM]]|real}} |
'''Note: This extension is currently limited to SOM_PRM.''' | '''Note: This extension is currently limited to SOM_PRM.''' | ||
| Line 10: | Line 10: | ||
====default_pixel_value==== | ====default_pixel_value==== | ||
| − | {{Ex/inival|1.1.1.3|hexadecimal colour codes|effectively changes the background colour (normally black) in the windows where 3D graphics are on display}} | + | {{Ex/inival|1.1.1.3|hexadecimal colour codes|effectively changes the background colour (normally black) in the windows where 3D graphics are on display|color}} |
====do_hide_direct3d_hardware==== | ====do_hide_direct3d_hardware==== | ||
| Line 16: | Line 16: | ||
''previously do_hide_direct3d_hardware_devices prior to 1.1.1.5'' | ''previously do_hide_direct3d_hardware_devices prior to 1.1.1.5'' | ||
| − | {{Ex/inival|1.1.1.3|binary statements|will hide any hardware accelerated display devices from Sword of Moonlight tools. If there is no pure software device available then there will be a failure to acquire a device. Use this as a last resort when having compatibility problems}} | + | {{Ex/inival|1.1.1.3|binary statements|will hide any hardware accelerated display devices from Sword of Moonlight tools. If there is no pure software device available then there will be a failure to acquire a device. Use this as a last resort when having compatibility problems|do}} |
'''This extension is not intended to be necessary under any circumstances. It is a temporary fallback. If you find yourself relying upon it, please report the difficulties you are experiencing to someone who is in a position to resolve your issue.''' | '''This extension is not intended to be necessary under any circumstances. It is a temporary fallback. If you find yourself relying upon it, please report the difficulties you are experiencing to someone who is in a position to resolve your issue.''' | ||
| Line 22: | Line 22: | ||
====do_overwrite_project==== | ====do_overwrite_project==== | ||
| − | {{Ex/inival|1.1.1.4|binary statements|is nothing fancy. It will let you have Sword of Moonlight create a new [[project]] on top of an existing folder where a project may already be found. The normal project template will simply be written over whatever files and folders are in the target folder. Sword of Moonlight will not complain or refuse to do your bidding, neither will you be warned of the impending overwrite}} | + | {{Ex/inival|1.1.1.4|binary statements|is nothing fancy. It will let you have Sword of Moonlight create a new [[project]] on top of an existing folder where a project may already be found. The normal project template will simply be written over whatever files and folders are in the target folder. Sword of Moonlight will not complain or refuse to do your bidding, neither will you be warned of the impending overwrite|do}} |
====do_overwrite_runtime==== | ====do_overwrite_runtime==== | ||
| − | {{Ex/inival|1.1.1.4|binary statements|is nothing fancy. It will let you have Sword of Moonlight create a new [[runtime]] on top of an existing folder where a runtime may already be found. Your project will simply be converted and deposited on top of whatever files and folders are in the target folder. Sword of Moonlight will not complain or refuse to do your bidding, neither will you be warned of the impending overwrite}} | + | {{Ex/inival|1.1.1.4|binary statements|is nothing fancy. It will let you have Sword of Moonlight create a new [[runtime]] on top of an existing folder where a runtime may already be found. Your project will simply be converted and deposited on top of whatever files and folders are in the target folder. Sword of Moonlight will not complain or refuse to do your bidding, neither will you be warned of the impending overwrite|do}} |
====language_pack_to_use==== | ====language_pack_to_use==== | ||
| Line 36: | Line 36: | ||
====texture_subsamples==== | ====texture_subsamples==== | ||
| − | {{Ex/inival|1.1.1.3|whole numbers; 1, 2, 4|blows up textures, smoothing them out in the process. So if set to 2, a 256x256 texture will become a 512x512 texture in memory. Sword of Moonlight alone will try to blow textures up to the maximum size allowed by the display device. With modern hardware that is quite dangerous, since 8192x8192 or better is common, which is a 256MB texture. The Sword of Moonlight Extension Library by default uses 256x256 textures}} | + | {{Ex/inival|1.1.1.3|whole numbers; 1, 2, 4|blows up textures, smoothing them out in the process. So if set to 2, a 256x256 texture will become a 512x512 texture in memory. Sword of Moonlight alone will try to blow textures up to the maximum size allowed by the display device. With modern hardware that is quite dangerous, since 8192x8192 or better is common, which is a 256MB texture. The Sword of Moonlight Extension Library by default uses 256x256 textures|whole}} |
''It's not clear why Sword of Moonlight tools exhibit this behavior. One theory is the tools would in their day require software emulation under most circumstances to display graphics inside popup windows. Since filtering the texture on screen would be slower for a software rasterizer, blowing the texture up achieves the same effect while consuming considerably more memory.'' | ''It's not clear why Sword of Moonlight tools exhibit this behavior. One theory is the tools would in their day require software emulation under most circumstances to display graphics inside popup windows. Since filtering the texture on screen would be slower for a software rasterizer, blowing the texture up achieves the same effect while consuming considerably more memory.'' | ||
Revision as of 05:10, 18 January 2013
Extensions in this section deal exclusively with the editing tools which authors use to make new Sword of Moonlight games. For the most part other sections pertain to tools only in so far as if and when a tool includes previews of in game elements; extensions affecting the project should apply, however in practice this may not always be the case.
Contents
clip_volume_multiplier
Introduced around 1.1.1.3, this extension scales the clip volume in the windows where 3D graphics are on display. Scaling by values less than 1 will make objects appear larger, or closer, and scaling above 1 vice versa. 0.5 works very well in SOM_PRM. Values are limited to real numbers.[#]
Note: This extension is currently limited to SOM_PRM.
default_pixel_value
Introduced around 1.1.1.3, this extension effectively changes the background colour (normally black) in the windows where 3D graphics are on display. Values are limited to hexadecimal colour codes.[#]
do_hide_direct3d_hardware
previously do_hide_direct3d_hardware_devices prior to 1.1.1.5
Introduced around 1.1.1.3, this extension will hide any hardware accelerated display devices from Sword of Moonlight tools. If there is no pure software device available then there will be a failure to acquire a device. Use this as a last resort when having compatibility problems. Values are limited to binary statements.[#]
This extension is not intended to be necessary under any circumstances. It is a temporary fallback. If you find yourself relying upon it, please report the difficulties you are experiencing to someone who is in a position to resolve your issue.
do_overwrite_project
Introduced around 1.1.1.4, this extension is nothing fancy. It will let you have Sword of Moonlight create a new project on top of an existing folder where a project may already be found. The normal project template will simply be written over whatever files and folders are in the target folder. Sword of Moonlight will not complain or refuse to do your bidding, neither will you be warned of the impending overwrite. Values are limited to binary statements.[#]
do_overwrite_runtime
Introduced around 1.1.1.4, this extension is nothing fancy. It will let you have Sword of Moonlight create a new runtime on top of an existing folder where a runtime may already be found. Your project will simply be converted and deposited on top of whatever files and folders are in the target folder. Sword of Moonlight will not complain or refuse to do your bidding, neither will you be warned of the impending overwrite. Values are limited to binary statements.[#]
language_pack_to_use
Introduced around 1.0.0.1, this extension selects a language pack from the text folder; not the lang folder! A language pack in the text folder is normally a compressed .zip archive. It can also be a directory if uncompressed. You should specify the name of the language pack file, without the .zip extension. Values are limited to a legal NTFS file title.
A language pack is a translation (into another language) of the various editing tools which make up Sword of Moonlight. See #Locale for game translation extensions.
texture_subsamples
Introduced around 1.1.1.3, this extension blows up textures, smoothing them out in the process. So if set to 2, a 256x256 texture will become a 512x512 texture in memory. Sword of Moonlight alone will try to blow textures up to the maximum size allowed by the display device. With modern hardware that is quite dangerous, since 8192x8192 or better is common, which is a 256MB texture. The Sword of Moonlight Extension Library by default uses 256x256 textures. Values are limited to whole numbers; 1, 2, 4.[#]
It's not clear why Sword of Moonlight tools exhibit this behavior. One theory is the tools would in their day require software emulation under most circumstances to display graphics inside popup windows. Since filtering the texture on screen would be slower for a software rasterizer, blowing the texture up achieves the same effect while consuming considerably more memory.
The Extension Library ensures the texture is sampled in "halftone" mode. Sword of Moonlight neglects to do so and therefore where that is not the default behavior will likely consume about 16+ times the memory required without any positive effect.
+based on standard legacy software device numbers (1024x1024)
