Bugs, crashes, typos & bad taste

[Alex_D]

The filter is odd, but it may to do with the handob of what the exalt guy is carrying.

[Kozinsky]

Some strange graphics...

I'm having the same problems. I'm pretty sure it's a bug in the Arsenal Addition submod.
However, I keep forgetting to check this error after disabling this submod and all submods that depend on it

[AndyFox]

With mods disabled, it does not allow you to complete the mission when you have cyber disks under your control (there were 2 units). Mission to destroy the enemy base.

[Solarius Scorch]

With mods disabled, it does not allow you to complete the mission when you have cyber disks under your control (there were 2 units). Mission to destroy the enemy base.

Um... What do you mean "does not allow you to complete the mission"? How am I supposed to debug something like that?

Do you have a save? And can you please state what to check?

[Kozinsky]

Aliens are trying to abduct Natasha Morozova!

[psavola]

Very strange. I understand very little of this, but I suppose the MOROZOVA region should not be used to spawn random abduction missions, because its regionWeight is undefined in regions_XCOMFILES.rul which should default to 0. Maybe OXCE is bugged somehow, you have a corrupt mod copy or some other mods are messing up by introducing non-zero regionWeight. Or I'm missing something, which is also entirely possible.

[Jimboman]

Aliens are trying to abduct Natasha Morozova!

I had a crash with that as well with the 3.4 version from github and openexe 7.11, no mods.

I went into my savegame and deleted all references to 'Natasha' missions and that sorted it.  It hasn't returned in three or four game months since then.

Maybe a holdover from something being changed?

[CrazedHarpooner]

Very strange. I understand very little of this, but I suppose the MOROZOVA region should not be used to spawn random abduction missions, because its regionWeight is undefined in regions_XCOMFILES.rul which should default to 0. Maybe OXCE is bugged somehow, you have a corrupt mod copy or some other mods are messing up by introducing non-zero regionWeight. Or I'm missing something, which is also entirely possible.

This is true, but the alien abduction missions in XCF have been redifined to have objective: 3 which makes it a site spawning mission and those follow their own rules by what I've understood, rendering the regionWeight irrelevant for this particular mission. I believe the issue lies in that REGION_NATASHA_MOROZOVA_HIDEOUT defines 2 missionZones for reasons unknown to me, perhaps WIP or from an old idea that got discarded, but as far as I could see, the 2nd zone (missionZone 1) is not actively used anywhere, yet for abduction site spawning purposes it's considered valid, at least until it has to spawn the UFOs and then it encounters the issue of no zone 5 (typical UFO entry/exit zones) defined for that region.

The fix in this case should be simple enough if nothing truly requires that missionZone 1, deleting the dash for said zone and allow for its missionAreas to be consolidated into missionZone 0 and thus, the region will no longer be a valid target for abductions.

Currently defined region

Spoiler:

Code: [Select]

- type: REGION_NATASHA_MOROZOVA_HIDEOUT
    missionZones: # European and American mountains, and Ural
      -
        - [142, 142, -73.5, -73.5, -317]
        - [93, 93, -84.5, -84.5, -317]
        - [213, 213, -80, -80, -317]
        - [118, 118, -72, -72, -317]
        - [44, 44, -68, -68, -317]
        - [163, 163, -66, -66, -317]
        - [82, 82, -63, -63, -317]
        - [61, 61, -67, -67, -317]
        - [129, 129, -67, -67, -317]
        - [160, 160, -63, -63, -317]
        - [36.34, 36.34, -68.47, -68.47, -317]
        - [44.81, 44.81, -67.02, -67.02, -317]
      -
        - [158, 158, -55, -55, -316]
        - [105.7, 105.7, -53.87, -53.87, -316]
        - [89, 89, -58, -58, -316]
        - [57, 57, -62, -62, -316]
        - [51, 51, -64, -64, -316]
        - [35, 35, -62, -62, -316]
        - [46.91, 46.91, -60.85, -60.85, -316]
        - [137.64, 137.64, -51.39, -51.39, -316]


Consolidated into single zone

Spoiler:

Code: [Select]

- type: REGION_NATASHA_MOROZOVA_HIDEOUT
    missionZones: # European and American mountains, and Ural
      -
        - [142, 142, -73.5, -73.5, -317]
        - [93, 93, -84.5, -84.5, -317]
        - [213, 213, -80, -80, -317]
        - [118, 118, -72, -72, -317]
        - [44, 44, -68, -68, -317]
        - [163, 163, -66, -66, -317]
        - [82, 82, -63, -63, -317]
        - [61, 61, -67, -67, -317]
        - [129, 129, -67, -67, -317]
        - [160, 160, -63, -63, -317]
        - [36.34, 36.34, -68.47, -68.47, -317]
        - [44.81, 44.81, -67.02, -67.02, -317]
        - [158, 158, -55, -55, -316]
        - [105.7, 105.7, -53.87, -53.87, -316]
        - [89, 89, -58, -58, -316]
        - [57, 57, -62, -62, -316]
        - [51, 51, -64, -64, -316]
        - [35, 35, -62, -62, -316]
        - [46.91, 46.91, -60.85, -60.85, -316]
        - [137.64, 137.64, -51.39, -51.39, -316]


[Jimboman]

I had a crash with that as well with the 3.4 version from github and openexe 7.11, no mods.

I went into my savegame and deleted all references to 'Natasha' missions and that sorted it.  It hasn't returned in three or four game months since then.

Maybe a holdover from something being changed?

You won;t believe this, but literally an hour or so after I posted that I had the same crash and 'repaired' it in the same way.  It's not game-breaking as I delete the missions from the save, it's just a little annoying.

[Jimboman]

This is true, but the alien abduction missions in XCF have been redifined to have objective: 3 which makes it a site spawning mission and those follow their own rules by what I've understood, rendering the regionWeight irrelevant for this particular mission. I believe the issue lies in that REGION_NATASHA_MOROZOVA_HIDEOUT defines 2 missionZones for reasons unknown to me, perhaps WIP or from an old idea that got discarded, but as far as I could see, the 2nd zone (missionZone 1) is not actively used anywhere, yet for abduction site spawning purposes it's considered valid, at least until it has to spawn the UFOs and then it encounters the issue of no zone 5 (typical UFO entry/exit zones) defined for that region.

The fix in this case should be simple enough if nothing truly requires that missionZone 1, deleting the dash for said zone and allow for its missionAreas to be consolidated into missionZone 0 and thus, the region will no longer be a valid target for abductions.

Currently defined region

Spoiler:

Code: [Select]

- type: REGION_NATASHA_MOROZOVA_HIDEOUT
    missionZones: # European and American mountains, and Ural
      -
        - [142, 142, -73.5, -73.5, -317]
        - [93, 93, -84.5, -84.5, -317]
        - [213, 213, -80, -80, -317]
        - [118, 118, -72, -72, -317]
        - [44, 44, -68, -68, -317]
        - [163, 163, -66, -66, -317]
        - [82, 82, -63, -63, -317]
        - [61, 61, -67, -67, -317]
        - [129, 129, -67, -67, -317]
        - [160, 160, -63, -63, -317]
        - [36.34, 36.34, -68.47, -68.47, -317]
        - [44.81, 44.81, -67.02, -67.02, -317]
      -
        - [158, 158, -55, -55, -316]
        - [105.7, 105.7, -53.87, -53.87, -316]
        - [89, 89, -58, -58, -316]
        - [57, 57, -62, -62, -316]
        - [51, 51, -64, -64, -316]
        - [35, 35, -62, -62, -316]
        - [46.91, 46.91, -60.85, -60.85, -316]
        - [137.64, 137.64, -51.39, -51.39, -316]


Consolidated into single zone

Spoiler:

Code: [Select]

- type: REGION_NATASHA_MOROZOVA_HIDEOUT
    missionZones: # European and American mountains, and Ural
      -
        - [142, 142, -73.5, -73.5, -317]
        - [93, 93, -84.5, -84.5, -317]
        - [213, 213, -80, -80, -317]
        - [118, 118, -72, -72, -317]
        - [44, 44, -68, -68, -317]
        - [163, 163, -66, -66, -317]
        - [82, 82, -63, -63, -317]
        - [61, 61, -67, -67, -317]
        - [129, 129, -67, -67, -317]
        - [160, 160, -63, -63, -317]
        - [36.34, 36.34, -68.47, -68.47, -317]
        - [44.81, 44.81, -67.02, -67.02, -317]
        - [158, 158, -55, -55, -316]
        - [105.7, 105.7, -53.87, -53.87, -316]
        - [89, 89, -58, -58, -316]
        - [57, 57, -62, -62, -316]
        - [51, 51, -64, -64, -316]
        - [35, 35, -62, -62, -316]
        - [46.91, 46.91, -60.85, -60.85, -316]
        - [137.64, 137.64, -51.39, -51.39, -316]


Thanks, I'll try this fix and see if it works.

[Kozinsky]

You won;t believe this, but literally an hour or so after I posted that I had the same crash and 'repaired' it in the same way.  It's not game-breaking as I delete the missions from the save, it's just a little annoying.

The fast fix is just replace "REGION_NATASHA_MOROZOVA_HIDEOUT" with "STR_EUROPE" in yor save-file.

[theboyinblue101]

I recently installed this mod and it keeps giving me the error:

Spoiler:

ERROR: failed to load 'X-Com Files' ; mod disabled
Weapon STR_HUMAN_SONIC_SHOTGUN has clip size 0 and no ammo defined.
Please use 'clipSize: -1' for unlimited ammo, or allocate a compatibleAmmo item.

I checked the items_XCOMFILES.rul and decided to give it a clip size of 3. Now it's saying there's a problem with the heavy cannon. I think there may be an issue with how the mod codes the ammo types for these two weapons.

Spoiler:

ammo:
0:
compatibleAmmo: [STR_HUMAN_SONIC_SHOTGUN_PELLET_CLIP]
tuLoad: 12
tuUnload: 6
1:
compatibleAmmo: [STR_HUMAN_SONIC_SHOTGUN_FOCUSED_CLIP]
tuLoad: 28
tuUnload: 8

ammo:
0:
compatibleAmmo: [STR_HUMAN_SONIC_HEAVY_CANNON_CLIP]
tuLoad: 25
tuUnload: 9
1:
compatibleAmmo: [STR_HUMAN_SONIC_HEAVY_CANNON_FOCUSED_CLIP]
tuLoad: 28
tuUnload: 10

Every other weapon in the game from what I can tell uses code like:

Spoiler:

compatibleAmmo:
- STR_CHEMTHROWER_GAS_CLIP
- STR_CHEMTHROWER_CHRYSSALID_GAS_CLIP

I think the difference in how these two examples are coded is the cause of my issue, but I don't know how to fix it. I hope my detailed explanation helps to improve things and leads to a solution.

I managed to fix the issue by adding the second example on top of the previous ones with the respective ammo types.

Unfortunately I now get another error whenever I dare to open my inventory.

Spoiler:

[22-05-2024_11-27-29]   [FATAL]   A fatal error has occurred: Segmentation fault. This usually indicates something missing in a mod.
[22-05-2024_11-27-29]   [FATAL]   0x54f2d0 OpenXcom::CrossPlatform::stackTrace(void*)
[22-05-2024_11-27-29]   [FATAL]   0x552ba0 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[22-05-2024_11-27-29]   [FATAL]   0x40dca0 signalLogger(int)
[22-05-2024_11-27-29]   [FATAL]   0x87fe90 xbrz::nearestNeighborScale(unsigned int const*, int, int, int, unsigned int*, int, int, int, xbrz::SliceType, int, int)
[22-05-2024_11-27-29]   [FATAL]   0x770933c0 UnhandledExceptionFilter
[22-05-2024_11-27-29]   [FATAL]   0x7727bdd0 RtlInitializeExceptionChain
[22-05-2024_11-27-29]   [FATAL]   0x7727bd00 RtlClearBits
[22-05-2024_11-27-36]   [FATAL]   OpenXcom has crashed: Segmentation fault. This usually indicates something missing in a mod.

Unfortunately I have no idea how to fix this one since I don't know where I need to look. If anyone here can help me, I'd appreciate it.

[Meridian]

You need OpenXcom Extended to run XcomFiles.

OpenXcom will not work.

[Solarius Scorch]

I don't know exactly what happened with REGION_NATASHA_MOROZOVA_HIDEOUT, but I see that it had two mission zones instead of just one, so I merged them. Hopefully this will be enough to prevent any further accidents.

I have updated GitHub. To those players who use it instead of waiting for an official release: please test it. (Note that changes will only apply starting next month.)
If this doesn't work, I'll do more extensive fixing.

[Jimboman]

I don't know exactly what happened with REGION_NATASHA_MOROZOVA_HIDEOUT, but I see that it had two mission zones instead of just one, so I merged them. Hopefully this will be enough to prevent any further accidents.

I have updated GitHub. To those players who use it instead of waiting for an official release: please test it. (Note that changes will only apply starting next month.)
If this doesn't work, I'll do more extensive fixing.

That seems to have sorted the problem as I had an abduction mission with no problems.  Thank you.