hpl3:community:editors:troubleshooting
| Both sides previous revision Previous revision | |||
|
hpl3:community:editors:troubleshooting [2015/10/29 15:01] romulator [My lights/shadows cut off linearly] |
hpl3:community:editors:troubleshooting [2018/01/04 04:27] (current) cadely Added solution to Level Editor hanging on load |
||
|---|---|---|---|
| Line 40: | 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) ==== | ||
| Line 78: | 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 114: | Line 118: | ||
| {{http://puu.sh/kDQXc/9bd641ec74.png?direct&}} | {{http://puu.sh/kDQXc/9bd641ec74.png?direct&}} | ||
| - | See //Mod Launcher - Steam API failed to initialize!// above for information on how to fix. | + | See //Mod Launcher - Steam API failed to initialize!// above for information on how to fix. |
| ===== 3rd Party Applications ===== | ===== 3rd Party Applications ===== | ||
| Line 142: | 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.txt · Last modified: 2018/01/04 04:27 by cadely
