Frictional Game Wiki

Link to this comparison view

--- hpl3:community:editors:troubleshooting [2015/10/09 10:38]
romulator created
+++ hpl3:community:editors:troubleshooting [2015/10/29 15:01]
romulator [My lights/shadows cut off linearly]
@@ Line 13: / Line 13: @@
 If your map is not loading, and you have since editted scripts for the mod, chances are that there is an error in your script. Most of the time, you will be prompted by a window with information about where the potential error is located in your script. It should look similar to this:
-{{http://puu.sh/kDNWk/0629817d2b.png}}
+{{http://puu.sh/kDNWk/0629817d2b.png?direct&}}
-Some of the errors which come up include:
+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-DO: A list of errors. Template: **errorType**Description. //How to fix// \\
-Example: **No matching signatures to <Function>(Syntax); ** An error usually meaning that the function syntax has been written incorrectly. //To fix, make sure that the data types (string, bool, int, float) are correctly written, there are enough commas (,) and there are not too many quotation marks "".>//
 === Invalid Filepointer Returned! ===
@@ Line 25: / Line 23: @@
 This error comes up when your modification cannot locate a particular map (or .hpm) file. This error will likely be caused when loading or changing map. In the case of:
-**Loading a map from Start:**There is likely a directory or naming error in your main_init.cfg. The lines you want to be looking for are within the StartMap group, specifically the //File// and //Folder// attributes. Check for any naming errors or directory problems. Personally, mine say: //File="base_map.hpm"//
+**Loading a map from Start: ** There is likely a directory or naming error in your main_init.cfg. The lines you want to be looking for are within the StartMap group, specifically the //File// and //Folder// attributes. Check for any naming errors or directory problems. Personally, mine say: //File="base_map.hpm"// //Folder="mods// /<//modfolder>/maps/".//
-//Folder="mods/<modfolder>/maps/".//
-**Changing from one map to next:**In your script, check your map transition script to make sure there are no errors in spelling. Be sure to check your modification's resources.cfg as well, you may not have declared your maps folder as a resource.
+**Changing from one map to next: ** In your script, check your map transition script to make sure there are no errors in spelling. Be sure to check your modification's resources.cfg as well, you may not have declared your maps folder as a resource.
-==== Some assets/models/entities/static objects/sounds/music are missing/do not play? ====
+==== Some assets are missing/do not play? ====
 Check your modification's resources.cfg file and add appropriate directories to your assets, sounds, music, etc. Furthermore, make sure any custom assets are included in your modification when you release it and test it.
@@ Line 48: / Line 45: @@
 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.
+==== Error loading file, resetting (Check log for details) ====
+{{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.
+{{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.
+==== 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 =====
@@ Line 57: / Line 76: @@
 ==== Steam API failed to initialize! ====
-{{
+{{http://puu.sh/kDPhv/21fbd7c304.png?direct&}}
-http://puu.sh/kDPhv/21fbd7c304.png}}
-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 //
+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:
-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}}
+{{http://puu.sh/kDPus/e3ca78fbd2.png?direct&}}
 This is not required if you are loading your modifications from the mods folder and are not using Steam to publish your work on the Steam Workshop.
@@ Line 72: / Line 88: @@
 ==== 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 =====
@@ Line 90: / Line 112: @@
 ==== Steam client must be running to be able to publish ====
-{{http://puu.sh/kDQXc/9bd641ec74.png}}
+{{http://puu.sh/kDQXc/9bd641ec74.png?direct&}}
-See Mod Launcher - Steam API failed to initialize! for information on how to fix.
+See //Mod Launcher - Steam API failed to initialize!//    above for information on how to fix.
 ===== 3rd Party Applications =====
@@ Line 106: / Line 128: @@
 === I cannot open any of my scripts? ===
-Make sure your installation of CodeLite is located on the same drive as what SOMA is.
+Make sure your installation of CodeLite is located on the same drive as what SOMA is. ( [[https://www.frictionalgames.com/forum/thread-30930.html|Forum Thread]] )
-(
-[[https://www.frictionalgames.com/forum/thread-30930.html|Forum Thread]]
-)
 ===== Got a bug to report? =====

Frictional Game Wiki

User Tools

Site Tools

Page Tools