hpl3:community:editors:troubleshooting
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hpl3:community:editors:troubleshooting [2015/10/09 22:48] romulator [When testing my level, my model appears at XYZ = 0.] |
hpl3:community:editors:troubleshooting [2018/01/04 04:27] (current) cadely Added solution to Level Editor hanging on load |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| {{http://puu.sh/kDNWk/0629817d2b.png?direct&}} | {{http://puu.sh/kDNWk/0629817d2b.png?direct&}} | ||
| - | |||
| - | Some of the errors which come up include: | ||
| - | |||
| - | <TO-DO: A list of errors. Template: **errorType ** Description. //How to fix>// | ||
| To fix these particular errors, note down the location of the error. Here we can see the error is in base_map.hps, Row 14, Column 25. Therefore, there is a problem either on or before Row 14. Inspect the code and figure out if you can pinpoint the error. Feel free to post in the [[https://www.frictionalgames.com/forum/forum-80.html|SOMA Development]] section of the forum if you're having issues figuring out your error. | To fix these particular errors, note down the location of the error. Here we can see the error is in base_map.hps, Row 14, Column 25. Therefore, there is a problem either on or before Row 14. Inspect the code and figure out if you can pinpoint the error. Feel free to post in the [[https://www.frictionalgames.com/forum/forum-80.html|SOMA Development]] section of the forum if you're having issues figuring out your error. | ||
| Line 44: | Line 40: | ||
| This will generically be caused by one of two things: | This will generically be caused by one of two things: | ||
| - | - **The model cannot find all connected submeshes.** \\ This means that there is a model or .dae file missing. You will know this is the case if when you place down a model and it does not appear in the editor (see the image above), and upon clicking where it is placed, does not actually select the model. To fix this, you'll need to open the model in the HPL2 Model Editor and locate where the referenced models are located in The Dark Descent or in Machine For Pigs. Make sure you copy all of them over into your SOMA directory, and it would be a good idea to try and keep them as close to the original directory as possible. | + | - **The model cannot find all connected submeshes.** \\ This means that there is a model or .dae file missing. You will know this is the case if when you place down a model and it does not appear in the editor (see the image above), and upon clicking where it is placed, does not actually select the model. To fix this, you'll need to open the model in the HPL2 Model Editor and locate where the referenced models are located in The Dark Descent or in Machine For Pigs. Make sure you copy all of them over into your SOMA directory, and it would be a good idea to try and keep them as close to the original directory as possible. |
| - | - **The model has all of its components but not its material (or all of its textures).** \\ This means you do not have the material or the textures (or even just the diffuse texture) in a recognisable location for your entity or static object. An example that comes to mind is the towels in A Machine For Pigs, as they base their texture off a carpet material file. To check what material it uses, you can open up the model in the HPL2 Model Editor and press the [+] button next to the mesh. It should show you the name of the .dds textures. Most of the time, all the materials and .dds files will appear there, but you can get all of them. | + | - **The model has all of its components but not its material (or all of its textures).** \\ This means you do not have the material or the textures (or even just the diffuse texture) in a recognisable location for your entity or static object. An example that comes to mind is the towels in A Machine For Pigs, as they base their texture off a carpet material file. To check what material it uses, you can open up the model in the HPL2 Model Editor and press the [+] button next to the mesh. It should show you the name of the .dds textures. Most of the time, all the materials and .dds files will appear there, but you can get all of them. |
| ==== When testing my level, my model appears at XYZ = 0. ==== | ==== When testing my level, my model appears at XYZ = 0. ==== | ||
| This is a problem caused by the meshes of some Amnesia: A Machine For Pigs models. I do not know if these problems will persist in HPL3, but if it does, the simplest way is to delete the .msh and the .anm files if there are any included with that particular model. That will generate a new .msh file which HPL3 can recognise. | This is a problem caused by the meshes of some Amnesia: A Machine For Pigs models. I do not know if these problems will persist in HPL3, but if it does, the simplest way is to delete the .msh and the .anm files if there are any included with that particular model. That will generate a new .msh file which HPL3 can recognise. | ||
| + | |||
| + | ==== Loading my map causes the editor to hang infinitely ==== | ||
| + | |||
| + | If your map uses .dae models from your mod directory that are not part of SOMA, try deleting all .msh files in your mod's directory, as these will be regenerated once the map is reloaded in the editor and might solve the issue | ||
| ==== Error loading file, resetting (Check log for details) ==== | ==== Error loading file, resetting (Check log for details) ==== | ||
| - | {{http://puu.sh/kEvzH/6f99e751a5.png}} | + | {{http://puu.sh/kEvzH/6f99e751a5.png?direct&}} |
| This is likely caused by a problem with one (or more) of your objects in the map having a quotation mark in one of the textboxes under the respective properties of the object. (For example, in entities > urban > special > 00_01_newspaper_article, which is a readable, in the readables text box, we may have a quotation mark in there. | This is likely caused by a problem with one (or more) of your objects in the map having a quotation mark in one of the textboxes under the respective properties of the object. (For example, in entities > urban > special > 00_01_newspaper_article, which is a readable, in the readables text box, we may have a quotation mark in there. | ||
| - | {{http://puu.sh/kEvXh/2e11a6e032.jpg}} | + | {{http://puu.sh/kEvXh/2e11a6e032.jpg?direct&}} |
| To fix this, try following the instructions at [[https://www.frictionalgames.com/forum/post-329413.html#pid329413|this forum post]]. Essentially, it teaches you how to use the logs of an error in the Level Editor to fix your issues by yourself! I have not yet found any other particular errors other than using quotation marks, but if they come up, I'll post them here. | To fix this, try following the instructions at [[https://www.frictionalgames.com/forum/post-329413.html#pid329413|this forum post]]. Essentially, it teaches you how to use the logs of an error in the Level Editor to fix your issues by yourself! I have not yet found any other particular errors other than using quotation marks, but if they come up, I'll post them here. | ||
| + | |||
| + | ==== My lights/shadows cut off linearly ==== | ||
| + | |||
| + | This is a problem with normal maps not being applied or incorrectly applied to the material of something which has been imported or added to SOMA. | ||
| + | |||
| + | {{https://pp.vk.me/c623831/v623831131/50578/U13MntxPSxg.jpg?direct&}} | ||
| + | |||
| + | It can be fixed by adjusting the method of saving your normal map when using Photoshop's nVidia .dds plugin. | ||
| + | |||
| + | **Aaron**: Make sure you apply a normal map to your material, I have provided a small blank normal map in textures>technical I believe called blank.nrm. This should fix the problem. […] Yeah make sure it is saved through 3dc, we use the nvidia dds plugin for Photoshop for this. It is a setting where you choose which compression you want to use. Right now your normal map is sRGB so it's not correct! | ||
| + | |||
| + | Aaron's quote about this solution can be found in [[https://www.frictionalgames.com/forum/thread-30803.html|this forum thread]]. | ||
| ===== Model Editor ===== | ===== Model Editor ===== | ||
| Line 70: | Line 82: | ||
| {{http://puu.sh/kDPhv/21fbd7c304.png?direct&}} | {{http://puu.sh/kDPhv/21fbd7c304.png?direct&}} | ||
| - | This error occurs because steam_appid.txt is not in SOMA's steam folder. To fix it, navigate to SOMA's Steam folder, which by default, is located here: //C:\Program Files (x86)\Steam\steamapps\common\SOMA// and simply create a text file with Notepad, named // steam_appid.txt. // Within this text file, simply write 282140 and save the text file. Therefore, you should have something like this: | + | This error occurs because steam_appid.txt is not in SOMA's steam folder. To fix it, navigate to SOMA's Steam folder, which by default, is located here: //C:\Program Files (x86)\Steam\steamapps\common\SOMA// and simply create a text file with Notepad, named // steam_appid.txt. // Within this text file, simply write 282140 and save the text file. Therefore, you should have something like this: |
| {{http://puu.sh/kDPus/e3ca78fbd2.png?direct&}} | {{http://puu.sh/kDPus/e3ca78fbd2.png?direct&}} | ||
| Line 80: | Line 92: | ||
| ==== I cannot assign a Mod Picture ==== | ==== I cannot assign a Mod Picture ==== | ||
| - | This feature is not quite available yet. This will be updated when it is possible. | + | There are two kinds of Mod Pictures - one which you can see when you are viewing your modification in the ModLauncher, and the other which you can see when you are asked to select one for Steam to use. Since the Steam image has appropriate validation checks, this will cover the Mod Picture in the ModLauncher. As such, your picture may look like either of these two examples. |
| + | |||
| + | {{http://puu.sh/kKOVB/1211a68ed4.png?direct&400}}{{http://puu.sh/kJIUA/0f4b1cc4ba.png?direct&400}} | ||
| + | |||
| + | To fix this, you need to specify a "LauncherPic" variable to your entry.hpc file. You can learn about this by visiting this [[:hpl3:tutorials:mod-creation:setting_up_a_mod_entry|wiki page]] and **viewing the Setting up a StandAlone entry**. Make sure that your image is also a .png file (.jpg files are **not supported**) and it is named correctly. If you need help assigning it, the previously linked wiki page has an example set up you can download. If all goes well, it should display an image you want. In my case, I was able to fix it: | ||
| + | |||
| + | {{http://puu.sh/kJJbw/a250ae0263.png?direct&400}} | ||
| ===== Particle Editor ===== | ===== Particle Editor ===== | ||
| Line 128: | Line 146: | ||
| If you have a bug about SOMA, in terms of modding or the core game, please post it in the [[https://www.frictionalgames.com/forum/forum-74.html|Technical Support subforum]] and: | If you have a bug about SOMA, in terms of modding or the core game, please post it in the [[https://www.frictionalgames.com/forum/forum-74.html|Technical Support subforum]] and: | ||
| - | * Describe the problem in detail. How can it be replicated? | + | * Describe the problem in detail. How can it be replicated? |
| - | * What Operating System are you running? | + | * What Operating System are you running? |
| - | * Attach your hpl.log file after the bug has occurred. You can find it by following Problem X of the Troubleshooting Guide, it is pinned to the top of the subforum. | + | * Attach your hpl.log file after the bug has occurred. You can find it by following Problem X of the Troubleshooting Guide, it is pinned to the top of the subforum. |
hpl3/community/editors/troubleshooting.1444430926.txt.gz · Last modified: 2015/10/09 22:48 by romulator
