Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
Dragonking (talk | contribs) No edit summary |
Verdite cat (talk | contribs) No edit summary |
||
(6 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
=="Test Play" Error== | |||
#'''Problem:''' Screen flickers while test playing a map. | |||
#*'''Cause:''' On some systems, when multiple programs are running (SoM + Wordpad etc) it causes this flickering effect. | |||
#*'''Solution:''' Close other programs. | |||
=="Create Runtime" Error== | =="Create Runtime" Error== | ||
#'''Problem:''' Create Runtime processing stops with a numbered error. | #'''Problem:''' Create Runtime processing stops with a numbered error. | ||
Line 8: | Line 13: | ||
#*'''Cause:''' No 'Starting Map' is selected in the System Editor. | #*'''Cause:''' No 'Starting Map' is selected in the System Editor. | ||
#*'''Solution:''' Select a map where the game will begin in the 'Other' tab in the system editor. The use 'Create Runtime' again. | #*'''Solution:''' Select a map where the game will begin in the 'Other' tab in the system editor. The use 'Create Runtime' again. | ||
#'''Problem:''' Movies included with Dark Destiny or the King's Field remake will not play. | |||
#*'''Cause:''' The required Indeo5 codec was not distributed with WinXP-SP2 and later Windows OS. | |||
#*'''Solution:''' Get the codec here [https://www.mediafire.com/?a0wmc5t8skr6k5x](32Bit only). Note that Vista onward changed how codecs are registered so other Indeo5 installers might not work. | |||
==Texture Problems== | ==Texture Problems== | ||
Line 13: | Line 21: | ||
#*'''Cause:''' This only occurs with fan-made parts. SoM expects a model (MDO) to have a single texture (TXR) with the same name as its model - for example "sword.mdo" and "sword.txr". If a model uses multiple textures or the texture is named differently than its model, it will not auto-transfer to built game's folders. | #*'''Cause:''' This only occurs with fan-made parts. SoM expects a model (MDO) to have a single texture (TXR) with the same name as its model - for example "sword.mdo" and "sword.txr". If a model uses multiple textures or the texture is named differently than its model, it will not auto-transfer to built game's folders. | ||
#*'''Solution:''' Manually transfer the missing textures (TXR) from SoM's folders to your game's folders. | #*'''Solution:''' Manually transfer the missing textures (TXR) from SoM's folders to your game's folders. | ||
[[Category:Sword of Moonlight]][[Category:Guides]] |
Latest revision as of 03:52, 14 September 2024
"Test Play" Error
- Problem: Screen flickers while test playing a map.
- Cause: On some systems, when multiple programs are running (SoM + Wordpad etc) it causes this flickering effect.
- Solution: Close other programs.
"Create Runtime" Error
- Problem: Create Runtime processing stops with a numbered error.
- Cause: Some part used in your project is missing. This is usually caused by a fan-made part whose PRF file names a model that doesn't exist, or if a part was used in the game was renamed or deleted.
- Solution: Figure out what file is missing and replace it or remove the part that needs the file from the game. A good way to narrow down the search is to make a copy of your project, then delete parts (Items Objects) from the editor until the project builds properly.
Compiled Game Play Problems
- Problem: When you select 'new game' in the title menu, the screen goes black and it quits-to-desktop.
- Cause: No 'Starting Map' is selected in the System Editor.
- Solution: Select a map where the game will begin in the 'Other' tab in the system editor. The use 'Create Runtime' again.
- Problem: Movies included with Dark Destiny or the King's Field remake will not play.
- Cause: The required Indeo5 codec was not distributed with WinXP-SP2 and later Windows OS.
- Solution: Get the codec here [1](32Bit only). Note that Vista onward changed how codecs are registered so other Indeo5 installers might not work.
Texture Problems
- Problem: Item or Object textures aren't showing up in a game built using "Create Runtime". Instead they look whitish.
- Cause: This only occurs with fan-made parts. SoM expects a model (MDO) to have a single texture (TXR) with the same name as its model - for example "sword.mdo" and "sword.txr". If a model uses multiple textures or the texture is named differently than its model, it will not auto-transfer to built game's folders.
- Solution: Manually transfer the missing textures (TXR) from SoM's folders to your game's folders.