Bugs & Crash Reports

[Cristao]

I suspect something with the enemy deployment, or engine explosion, but I've never seen this error before. Anyone knows what it means?

EDIT: it's not deployment, I ran it like dozen of times in QB mode. Invalid terrain seems unlikely as well, it happens too often and the terrains are well-tested...

It happened once to me in Battlescape when I was fighting the Doom enemies. A bomb/grenade went off and I got the error.

[Dioxine]

Good to know. So all the evidence seems to be pointing at engine explosion... any code experts? Maybe it has something to do with explosion chaining in OXCE? Too bad we can't test damaged UFOs in QB...

[Meridian]

Good to know. So all the evidence seems to be pointing at engine explosion... any code experts? Maybe it has something to do with explosion chaining in OXCE? Too bad we can't test damaged UFOs in QB...

I will have a look in the evening.
Should I have save scumming on or off? I.e. does the error come always or only sometimes?

[Dioxine]

Only sometimes, 50% of cases I think. And thank you very much.

[Quanti]

There seems to be a problem with the new healer armour, whenever I hit the button to manufacture it the game crashes. Using the old exe (OpenXcomEx.exe) lets me start manufacturing but as soon as one is completed the game crashes. Doesn't show up on the list of options in new battle on the main menu either.

[Dioxine]

Somehow a portion of the code got lost between battle tests and release. WTF. Anyway, to fix this, add this to Piratez.rul, under 'items:' section

Code: [Select]

  - type: STR_NURSE_OUTFIT_ADV
    size: 0.3
    costSell: 80000
    listOrder: 1684

[Meridian]

Only sometimes, 50% of cases I think. And thank you very much.

So far:
 - I can confirm it happens because of engine explosion
 - I am still trying to find a more specific place... but it happens "randomly", so I am now removing randomness, because once it crashes, I need to start debugging again and just starting PirateZ takes about 20 minutes (yes minutes, not seconds) on my computer... so I can do 3 attempts per hour
 - I now made engine always explode and always explode with maximum damage (250)... btw. with minimum damage (180), it doesn't crash!!

[Dioxine]

- I now made engine always explode and always explode with maximum damage (250)... btw. with minimum damage (180), it doesn't crash!!

And that was the last missing piece of chaos Turned out a few tiles pointed to non-existing tiles on being destroyed. You might try it, just to be sure, but several tests ended in no crashes (files go into /TERRAIN). Thanks a lot! I'd probably never figured it out by myself, or at least, not that quickly...

[Meridian]

You might try it, just to be sure, but several tests ended in no crashes (files go into /TERRAIN).

Doesn't crash anymore.

[Galwail]

Wow, thanks for the quick fix 

[Zharkov]

Not a bug, more like a minor inconvenience: Guardian/Heavy Carapace Armor and Harbinger/Advanced Power Armor have different designations in the Bootypedia/Manufacture Interface.

[Foxhound634]

I have observed some strange pathfinding in this patch. Sometimes when ordering a gal to go somewhere, rather than making the closest thing to a bee line, they deliberately avoid taking a direct path, even though it is on flat terrain and there are no obstacles. According to the estimates of remaining TUs, the AI is just choosing the shortest path, but the calculations doesn't make sense. Again, this does not always happen, but it occurs frequently

EDIT: see attached

[Dioxine]

There are obstacles, just hidden - the grass is blocking movement for some reason. I could repair that but I don't want to change Hobbes' terrains too much.

[Cristao]

@Foxhound. I noticed the same and I think Meridian did as well in his video #33. It is not a game stopper/changer for me.

[Dioxine]

The difference is, Meridian landed on Savanna and the high grass there is supposed to be slowing you down. This terrain (Taiga) is *not* supposed to act like this.