Perturabo wrote:The game won't accept custom sprites that are .PNG instead of .png. It doesn't like capitals, apparently.
Hey, Perturabo, i have a novel idea. I might seem to be out of my mind to you, but it would still be a great honor if you spared a minute of your precious time to consider it. If you're not too busy, of course - i realize im asking a lot here.
Could you, perchance, in your infinite kindness, read the documentation before posting things mentioned there as a bugs?
___________________________________________
ERROR in
action number 1
of Destroy Event
for object ShipSection:
In script tr_destroyClear:
Error in code at line 11:
tr_offpar2.tr_onch[ tr_ppdim1[4], tr_ppdim2[4] ] = -4
at position 24: Unknown variable tr_ppdim1 or array index out of bounds
Upon the destruction of my latest ship, which uses triggers and links and drivers. Repeats once, then plays on. No real idea what's causing it. PM for the sb4 if needed.
I've noticed a second bug with my afore mentioned ship. It has a pair of extendible engine pods, but when the rear of the ship is destroyed (taking the pods with it) sometimes in the ship schematic on the right the pod is still visible, without any connection to the ship itself - the connecting components are destroyed but it appears that somewhere in the game it's got confused.
The problem with this is that it causes a series of continuous errors that appear to be related to components that could be the ones on the pod.
_________________________
Ok, so after typing that I though I might as well investigate. I can confirm that destroying the mobile section supporting the external pods (mounting only 4 ex thrusters) results in a set of terminal errors in the flavour of:
___________________________________________
ERROR in
action number 1
of Step Event
for object ThrusterEx:
Error in code at line 1:
image_angle = rs_owner.image_angle-rs_owner.l_angle + l_special6
at position 24: Unknown variable image_angle
Aederrex wrote:
WARNING: Opening this in shipmaker will screw up all the triggers, in particular, it changes all the trigger 2 off conditions to match trigger 1 off. If anyone REALLY needs to know how I did this I'll make up a file with the triggered sections marked and post some instructions.
I checked and it didn't look like he also posted that bug here. I checked it out real quick on some ships I've been working on, and the triggers are, in a phrase, totally fucked. I hardly ever build a whole ship in one sitting. this one is a nasty one.
I just got finished putting the hull plating on my ship and started putting on some armor, now it won't load up in the sandbox or encounter maker. The last version without all the hull plating on it will still load up but the one with all the hull plating won't, the ship is under 600 sections so i know its not too big, i had a ship well over 1000 sections before open up fine in the last version of the game but not the v90a one
Sometimes the distortion effect from the destruction of a ship fails to disappear. The unusual thing is that the distortion only affects movement/ targeting lines. After another ship is destroyed, the effect goes away.
___________________________________________
ERROR in
action number 1
of Destroy Event
for object ctr_Turrets:
Error in code at line 40:
image_angle = rs_owner.image_angle-rs_owner.l_angle + l_arcoffset
at position 33: Unknown variable image_angle
EDIT:
Same error is obtained if the core is directly destroyed using destroy mode. There is no error if the ship is destroyed section by section.