I had a lot of trouble searching for threads that had the answer to my problems in terms of bugs.:x To eliminate the need for time consuming searches, this thread will tell you of some of the common mistakes they aren't really mistakes and how you fix them. (feel free to add some you have found too!)
Make sure you have the latest version of BSf
Adding depth to modules/weapons
This will often result in an error. Whenever you add depth to weapons or modules (or modify depthed weapons or modules) always save and then open another ShipMaker and save the ship again.
Using TachyonNuke, Repeating Artillery, and some others
For some reason, some weapons don't have a preset bullet sprite so you will need to specify them in the weapons above. There are some other weapons also that don't have preset sprites.
Weapon with trigger-on and trigger-off from two different sources
As of 0.90d, you cannot properly save sb4 file of a ship when your ship have weapon(s) having its/their trigger-off and trigger-on coming from two different sources.
SHP file created will work without glitches, but SB4 file will have incorrect information. (the triggers will disappear or extra incorrect triggers will be put on when you re-load the ship in SM) So that when you reload the ship to the shipmaker, those connections need to be re-done.
The only temporary work around is to keep track of the specific lines of codes describing trigger links and make a note of them (through comparing shp and sb4 files using text editor, since SM can load the file properly with those lines of code, just cannot save them properly), or manually re-make trigger connections each time you update the ship and would like to export the new ship as SHP. You can also leave SM open and never close it once you make the connections.
Ship Deployer n
Common mistakes that lead to bugs
Moderators: th15, Moderators
Common mistakes that lead to bugs
Last edited by 25000st on Wed May 27, 2009 8:09 am, edited 3 times in total.
-
AnnihilatorX
- Commander
- Posts: 116
- Joined: Sat Mar 01, 2008 3:49 am
Weapon with trigger-on and trigger-off from two different sources
As of 0.90d, you cannot properly save sb4 file of a ship when your ship have weapon(s) having its/their trigger-off and trigger-on coming from two different sources.
SHP file created will work without glitches, but SB4 file will have incorrect information. (the triggers will disappear or extra incorrect triggers will be put on when you re-load the ship in SM) So that when you reload the ship to the shipmaker, those connections need to be re-done.
The only temporary work around is to keep track of the specific lines of codes describing trigger links and make a note of them (through comparing shp and sb4 files using text editor, since SM can load the file properly with those lines of code, just cannot save them properly), or manually re-make trigger connections each time you update the ship and would like to export the new ship as SHP. You can also leave SM open and never close it once you make the connections.
As of 0.90d, you cannot properly save sb4 file of a ship when your ship have weapon(s) having its/their trigger-off and trigger-on coming from two different sources.
SHP file created will work without glitches, but SB4 file will have incorrect information. (the triggers will disappear or extra incorrect triggers will be put on when you re-load the ship in SM) So that when you reload the ship to the shipmaker, those connections need to be re-done.
The only temporary work around is to keep track of the specific lines of codes describing trigger links and make a note of them (through comparing shp and sb4 files using text editor, since SM can load the file properly with those lines of code, just cannot save them properly), or manually re-make trigger connections each time you update the ship and would like to export the new ship as SHP. You can also leave SM open and never close it once you make the connections.
