Difference between revisions of "FAQ: My Script Doesn't Work!"

imported>Jimhsu
imported>Jimhsu
Line 63: Line 63:
That sounds like a packaging problem. Consider the following:
That sounds like a packaging problem. Consider the following:
*'''Did you accidentally leave out any meshes or textures?''' Textures might not cause an outright crash, but will definitely make things look weird (i.e. purple). Missing meshes may lead to graphical anomalities or outright crashes. Check also that the paths in your meshes are relative, not absolute (If you see "program files" or something in your textures, then something is wrong).
*'''Did you accidentally leave out any meshes or textures?''' Textures might not cause an outright crash, but will definitely make things look weird (i.e. purple). Missing meshes may lead to graphical anomalities or outright crashes. Check also that the paths in your meshes are relative, not absolute (If you see "program files" or something in your textures, then something is wrong).
*'''Are you using a custom script that extends another custom script?''' There is a [http://forums.bethsoft.com/topic/1347451-serious-flaw-with-the-packaging-algorithm-for-bsa-creation/|bug] in the .bsa packager where if the parent custom script is not actually present in a base form in the game, then it will not be listed in the file selector for the packager. The solution is to create a dummy mesh that has the parent script attached, or manually include it in the .bsa on build.
*'''Are you using a custom script that extends another custom script?''' There is a bug[http://forums.bethsoft.com/topic/1347451-serious-flaw-with-the-packaging-algorithm-for-bsa-creation/] in the .bsa packager where if the parent custom script is not actually present in a base form in the game, then it will not be listed in the file selector for the packager. The solution is to create a dummy mesh that has the parent script attached, or manually include it in the .bsa on build.


==Object Creation==
==Object Creation==
Anonymous user