I've run it twice and run into (maybe) separate problems both times. The first produced an Error 5, UseFuel message that could be clicked past for several turns before becoming incessant. The second attempt from a (far too old) save resulted in a freeze in which the game never moved to the next time increment after the new wreck was created.

The problem ship is a prize captured by boarding. In both cases the boarders had previously (many turns before the freeze/error message loop) been returned to dropships and all fuel had previously been transferred to other ships. The only other detail I think might be relevant is that commander auto-assignment had given the ship a CO in both cases, but he showed up in the lifepods after the Abandon Ship order was issued from the Damage Control tab on the ship screen. In the second instance all TG orders had been canceled for the captured ship, but that might also have been the case in the first instance in an attempt to minimize the notices that an unfueled ship couldn't complete its orders.

I welcome advice on getting past the hang up; I'd really like to abandon the ship and salvage it because it's in no shape to make it to my shipyards ... I did shoot it up before boarding.

I am getting a strange bombardment issue. I had a colony that was terraformed to cost zero and had a population of around 90m, invaders turned up and sent missiles to the colony. This resulted in a total loss of all population, and installations along with an amount of radiation and dust. Once the overall battle in the system had been won and I have scouted out the rest of the system out to a distance of 1.5bkm in all directions I presumed things would be ok to resettle the world. However every few hours or so I seem to get damage messages, these seem to set at random times and I have checked to ensure there are no other enemy ships around. If they are in the system then they have missiles or beams with a range beyond 2bkm which I find highly improbable.

Things have gotten that bad that I am loosing populations numbers I do not even have as the population is zero, along with dust and radiation levels constantly rising too. Here is a copy of the last few messages from the event log. The last on after I did some SM to the colony to remove all dust and radiation simply to see what would happen.

Just to add to this issue, I went ahead and abandoned the colony and then set up a new colony on the same body. Now it seems the civilian colony ships are setting up new colonies on the same planet every time they arrive and not just adding to the existing colony. Worse still even if I leave the planet totally abandonded then civilian ships go ahead and set up new colonies all by themselves even when I check the ban body button

Towing was the first thing I tried. No bugs with that, just too many fuel warnings to be bothered with---I'd shot up the fuel tanks and the game wouldn't just let the tug tow it in peace. That's when I decided to scuttle it. Restarting a couple of times after the freeze ultimately got me past whatever the problem was.

If all else fails, store your save file sideways and SM the ship out of existence.

Gotta clue me in on what saving the file sideways means, if it's something other than simply making a copy of the stevefire.db. I restarted after a couple of freezes and that seemed to get me past whatever the problem was. Captain and crew of the abandoned prize made it home just fine.

"Error 11, division by zero" notice that seems to be related to damage control for fighters recovered by a carrier, possibly in relation to queued damage control components.

It might be related to a damaged crew quarters on one of those fighters. I get notifications of "complete life support failure" on a fighter that has no crew and the damage control has not fixed that component while (many) others have been repaired on other fighters.

**** I really think it's related to this. I've just switched to fixing a different damaged component and I get no error messages as time rolls; the crew quarters is even in the queue, so the error might be specifically related to crew quarters selected in "Current damage Control Assignment". Error messages resume when crew quarters finally make its way up the queue and repairs on that component are never carried out. ****

Plenty of maintenance supplies on carrier, damaged fighters have been docked.

EDIT: the error message is specifically related to 0 crew after life support gives out. I don't know if the inability to repair crew quarters in hangar is related to what underlies the error message or if it's just coincidental.

This design is classed as a Commercial Vessel for maintenance purposeswhile

It seems to me which one gets shown depends on the order you put them in: the first one added is shown. This affects both brief and full summary areas, both component areas show properly both/all types of jump engines included.

Alternatively only one type of jump engine (or even only one piece of that type) may be allowed.

Error in UpdateGameLogError 3163 was generated by DAO.FieldThe field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data.An instance of the Error 94 then occurred with each of the components I scrapped from those ships, but later resumed at the end of each time increment (set for 1 day, but possibly interrupted by task completions, etc.) during/at the end of a turn in which ground HQ unit suffered a loss of readiness and the commander received a GCB.

I find this odd, considering the Error 94 messages immediately popped up in response to component scrapping and ceased when I did. The regular resumption of the error messages began 7 time increments later with situation I described, the only other new events being the launch (not the scrapping) of several new civilian ships. Since that turn, the last event update in each time increment is the Error 94 message.

EDIT: The error has ceased repeating after exiting and resuming play, but I don't believe the conditions changed.

Error 3022 was generated by DAO. RecordsetThe changes you requested to the table were not successful because they wouldcreate duplicate values in the index, primary key, or relationship. Change the datain the field or fields that contain duplicate data, remove the index, or redefine theindex to permit duplicate entries and try again.