aliens

Author Topic: Bugs, crashes, typos & bad taste  (Read 1071967 times)

Offline shaigan

  • Squaddie
  • *
  • Posts: 2
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1710 on: March 28, 2019, 06:47:55 pm »
I got an after-battlescape crash very often

Code: [Select]
[14-12-2018_10-41-01] [FATAL] A fatal error has occurred: Segmentation fault. This usually indicates something missing in a mod.
[14-12-2018_10-41-01] [FATAL] 0x8861e0 OpenXcom::CrossPlatform::stackTrace(void*)
[14-12-2018_10-41-01] [FATAL] 0x889870 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[14-12-2018_10-41-01] [FATAL] 0x401750 signalLogger(int)
[14-12-2018_10-41-01] [FATAL] 0x77035020 RtlKnownExceptionFilter
[14-12-2018_10-41-01] [FATAL] 0x76ff97cf RtlInitializeExceptionChain

Offline Meridian

  • Global Moderator
  • Commander
  • *****
  • Posts: 8597
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1711 on: March 28, 2019, 07:50:44 pm »
I got an after-battlescape crash very often

Code: [Select]
[14-12-2018_10-41-01] [FATAL] A fatal error has occurred: Segmentation fault. This usually indicates something missing in a mod.
[14-12-2018_10-41-01] [FATAL] 0x8861e0 OpenXcom::CrossPlatform::stackTrace(void*)
[14-12-2018_10-41-01] [FATAL] 0x889870 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[14-12-2018_10-41-01] [FATAL] 0x401750 signalLogger(int)
[14-12-2018_10-41-01] [FATAL] 0x77035020 RtlKnownExceptionFilter
[14-12-2018_10-41-01] [FATAL] 0x76ff97cf RtlInitializeExceptionChain

Attach at least the whole log please.

And a save, if possible.
« Last Edit: March 28, 2019, 07:52:33 pm by Meridian »

Offline krautbernd

  • Commander
  • *****
  • Posts: 1116
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1712 on: April 05, 2019, 08:10:29 pm »
Code: [Select]
  STR_GIANT_SPIDER_GREEN_ARMOR: "Armored Spider Combat Analysis"
  STR_GIANT_SPIDER_PURPLE_ARMOR: "Death Spider Combat Analysis"
  STR_GIANT_SPIDER_ALLOY_ARMOR: "Stealth Spider Combat Analysis"

Is this intended? I was quite fond of how the colors kind of intuitively matched the spiders. Especially with the armored spider using the alloy spider sprite.
Nevermind, i must have misremembered this. Somehow i associated green=death, purple=stealth and alloy=armored. Still weird that the armored spider doesn't use the alloy sprite though :P
« Last Edit: April 05, 2019, 08:18:22 pm by krautbernd »

Offline Alex_D

  • Colonel
  • ****
  • Posts: 482
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1713 on: April 06, 2019, 08:48:04 am »
Would it be better if the BOps Smart Pistol list order was 20330, so it fits better in the purchase screen ?

Code: [Select]
  - type: STR_BLACKOPS_SMARTPISTOL
    #listOrder: 20360
    listOrder: 20330

Offline Solarius Scorch

  • Global Moderator
  • Commander
  • ***
  • Posts: 11408
  • WE MUST DISSENT
    • View Profile
    • Nocturmal Productions modding studio website
Re: Bugs, crashes, typos & bad taste
« Reply #1714 on: April 06, 2019, 04:23:59 pm »
Code: [Select]
  STR_GIANT_SPIDER_GREEN_ARMOR: "Armored Spider Combat Analysis"
  STR_GIANT_SPIDER_PURPLE_ARMOR: "Death Spider Combat Analysis"
  STR_GIANT_SPIDER_ALLOY_ARMOR: "Stealth Spider Combat Analysis"

Is this intended? I was quite fond of how the colors kind of intuitively matched the spiders. Especially with the armored spider using the alloy spider sprite.
Nevermind, i must have misremembered this. Somehow i associated green=death, purple=stealth and alloy=armored. Still weird that the armored spider doesn't use the alloy sprite though :P

They were always named like that. Internal strings are different for my own sanity. ;)

Would it be better if the BOps Smart Pistol list order was 20330, so it fits better in the purchase screen ?

Code: [Select]
  - type: STR_BLACKOPS_SMARTPISTOL
    #listOrder: 20360
    listOrder: 20330

You're right, it's misplaced, but why 20330? It's already take by the standard pistol. I'll give it 20335.

Offline Alex_D

  • Colonel
  • ****
  • Posts: 482
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1715 on: April 07, 2019, 02:46:15 am »
You're right, it's misplaced, but why 20330? It's already take by the standard pistol. I'll give it 20335.

The 20330 number was chosen just to see if it gets on the same spot as the Standard BO Pistol. I assumed that the game will sort two items with the same list order by the order they appear on the .rul file. But, thanks, whatever works to placate my OCD  :)
On the same note, I bring to your attention:
Code: [Select]
ufopaedia:
  - id: STR_CAWS_CONT
    #listOrder: 22654
    listOrder: 22655
items:
  - type: STR_CAWS_CONT
    #listOrder: 22654
    listOrder: 22655
I'm not sure of which one is the correct one (I suspect the first one), but the CAWS second page entry shows before the main page.

Offline Solarius Scorch

  • Global Moderator
  • Commander
  • ***
  • Posts: 11408
  • WE MUST DISSENT
    • View Profile
    • Nocturmal Productions modding studio website
Re: Bugs, crashes, typos & bad taste
« Reply #1716 on: April 07, 2019, 07:26:51 pm »
On the same note, I bring to your attention:
Code: [Select]
ufopaedia:
  - id: STR_CAWS_CONT
    #listOrder: 22654
    listOrder: 22655
items:
  - type: STR_CAWS_CONT
    #listOrder: 22654
    listOrder: 22655
I'm not sure of which one is the correct one (I suspect the first one), but the CAWS second page entry shows before the main page.

Yeah, it's bit wonky. But now we have an option to make multi-pages, so it's probably no longer relevant. I just ned to learn how to do this.
EDIT: No, we can't. I'll just fix the numbers then.
« Last Edit: April 07, 2019, 07:31:42 pm by Solarius Scorch »

Offline Alex_D

  • Colonel
  • ****
  • Posts: 482
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1717 on: April 09, 2019, 07:39:24 am »
Do you have a save? I honestly can't say much from the minimap.

I got the same error (last enemy unit in the corner). See the save.

EDIT: A better save.
« Last Edit: April 09, 2019, 08:10:34 am by Alex_D »

Offline Solarius Scorch

  • Global Moderator
  • Commander
  • ***
  • Posts: 11408
  • WE MUST DISSENT
    • View Profile
    • Nocturmal Productions modding studio website
Re: Bugs, crashes, typos & bad taste
« Reply #1718 on: April 10, 2019, 09:11:59 pm »
Hmm, very interesting. There are no spawns there, and considering it's the {0, 0, 0} tile, it looks like a lost unit which failed to spawn somewhere and was reset to basic coordinates. I have never seen anything like this before and I have no idea how to approach this...

Offline justaround

  • Captain
  • ***
  • Posts: 93
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1719 on: April 11, 2019, 08:56:48 am »
I have never seen anything like this before and I have no idea how to approach this...
Adding a few more spawn points in case it's the game trying to spawn unit with all places being occupied/obstrcuted? A check that retries to spawn the unit next turn? Certainly some debug message for this would be useful, but I guess it's in general more of a base project issue than the mod one. Maybe the save should be forwarded to one of the guys managing that?

Offline krautbernd

  • Commander
  • *****
  • Posts: 1116
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1720 on: April 11, 2019, 09:38:55 pm »
Cybermite mines and caves in general have areas that can be blocked by enemies with your agents unable to see or attack them (mostly 1x1 spaces/alcoves, but also narrow tunnels). Is this intended?

Offline Solarius Scorch

  • Global Moderator
  • Commander
  • ***
  • Posts: 11408
  • WE MUST DISSENT
    • View Profile
    • Nocturmal Productions modding studio website
Re: Bugs, crashes, typos & bad taste
« Reply #1721 on: April 11, 2019, 09:53:08 pm »
Adding a few more spawn points in case it's the game trying to spawn unit with all places being occupied/obstrcuted? A check that retries to spawn the unit next turn? Certainly some debug message for this would be useful, but I guess it's in general more of a base project issue than the mod one. Maybe the save should be forwarded to one of the guys managing that?

The game wouldn't do that, if it runs out of spawn points, it spawns next to previous spawns.
But of course, any help is welcome.

Cybermite mines and caves in general have areas that can be blocked by enemies with your agents unable to see or attack them (mostly 1x1 spaces/alcoves, but also narrow tunnels). Is this intended?

Well... initially yes, but I don't really like it much after all and gradually remove such passages.
Dioxine loves them though, and puts it on all maps he makes. :P

Offline krautbernd

  • Commander
  • *****
  • Posts: 1116
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1722 on: April 11, 2019, 11:00:16 pm »
Dioxine loves them though, and puts it on all maps he makes. :P

:P

Also, might i request adding back the Hilariously Explosive™ rocket stacks to the Syndicate and Black Lotus base assaults? They always bring a smile to my face when i encounter them on outposts.
« Last Edit: April 11, 2019, 11:02:36 pm by krautbernd »

Offline Solarius Scorch

  • Global Moderator
  • Commander
  • ***
  • Posts: 11408
  • WE MUST DISSENT
    • View Profile
    • Nocturmal Productions modding studio website
Re: Bugs, crashes, typos & bad taste
« Reply #1723 on: April 11, 2019, 11:05:01 pm »

:P

Also, might i request adding back the Hilariously Explosive™ rocket stacks to the Syndicate and Black Lotus base assaults? They always bring a smile to my face when i encounter them on outposts.

I can't remember removing anything... But I'll have a look. :)

Offline krautbernd

  • Commander
  • *****
  • Posts: 1116
    • View Profile
Re: Bugs, crashes, typos & bad taste
« Reply #1724 on: April 11, 2019, 11:10:38 pm »
Might be one of those cases of selective false memory on my side, but i could have sworn shooting the rocket stacks on base assaults used to totally wreck the room and anyone in it. Now they just go 'poof', which resulted in my agents getting poofed by the surviving rocket launcher wielding supersoldier.