[OLD] Old OXCE+ discussion thread

[Meridian]

No, but something similar.

If a retaliation mission would spawn in a region, which already has an active retaliation mission... the second one is not spawned.

[Eddie]

Hmmm... the region specific thing might not work as intended. The base with the retaliation mission was in china, the UFO I shot down was in north afrika. This was in Piratez mod. I loaded several times but shooting the UFO in north afrika would not trigger a retaliation. Save attached.

[Meridian]

Hmmm... the region specific thing might not work as intended. The base with the retaliation mission was in china, the UFO I shot down was in north afrika. This was in Piratez mod. I loaded several times but shooting the UFO in north afrika would not trigger a retaliation. Save attached.

The chance to spawn in your case is 24%... after about 7 attempts, it generated a retaliation mission for me in North America (=home region of Airspeeder-1).

[Eddie]

Thanks for clearing that up. So I just wasn't trying hard enough and had bad RNG.

I didn't look up the actual retaliation odds and thought they were higher. Sorry for wasting your time.

[robin]

Got back from a mission and the amount of items exceeded my store capacity, so the game asked me to sell some, opening the attached screen.
Problem is that it wants me to "Transfer" instead of selling, and since I only have 1 base I can't do it and I'm stuck at this screen.

Using OXCE+ 3.10a (v2018-05-19)

ooops I'm an idiot.

[BlackStaff]

Hello,
I hope I'm not in the wrong place to post this problem! 
Just a quick question!
You don't have to involve Delta Force!
In my OXCE+ (version 19/05) I have this crash!

[08-06-2018_17-35-43]   [FATAL]   A fatal error has occurred: vector::_M_range_check: __n (which is 7) >= this->size() (which is 7)
[08-06-2018_17-35-43]   [FATAL]   Unfortunately, no stack trace information is available
[08-06-2018_17-35-59]   [FATAL]   OpenXcom has crashed: vector::_M_range_check: __n (which is 7) >= this->size() (which is 7)
Extra information has been saved to openxcom.log.
If this error was unexpected, please report it to the developers.

Note: The save is old. In this game I'm almost at the end. I can do the Cydonia mission whenever I want! I use a lot of Mods.
Maybe all this explains it.
mods:
  - "xcom1 ver: 1.0"
  - "Aliens_Pick_Up_Weapons ver: 1.0"
  - "UFOextender_Psionic_Line_Of_Fire ver: 1.0"
  - "XcomUtil_Statstrings ver: 1.0"
  - "centre_entrainement_UFO ver: 1.0"
  - "Advanced_Medikit ver: 1.01m"
  - "Expanded_Ubase_Rework ver: 1.2 WIP"
  - "alien-armoury-expanded ver: 1.5b"
  - "alien-inventory ver: 2.0"
  - "aliens_lukes_extra_UFOs ver: 1.4"
  - "armored_vest ver: 1.32m"
  - "extra_pockets ver: 1.0"
  - "firestorm_aircraft ver: 1.0"
  - "lightning_aircraft ver: 1.0"
  - "muton_commander ver: 1.1m"
  - "new_flare_laser ver: 1.00"
  - "new_weapons_pack ver: 1.12m"
  - "personal_armor ver: 1.01m"
  - "raven_interceptor ver: 1.0"
  - "retaliator_interceptor ver: 0.9"
  - "scout-drone ver: 1.0"
  - "weapons_rebalanced ver: 1.31m"
  - "mass_weapons ver: 1.2m"

Thanks !

[Meridian]

Most likely an issue with one of the mods.

If you post a save just before the crash, I may be able to help; or at least explain what's wrong.

[BlackStaff]

Thank you! I'll try to make a backup just before the crash!

[Yataka Shimaoka]

Next android release when?

[BlackStaff]

Most likely an issue with one of the mods.
If you post a save just before the crash, I may be able to help; or at least explain what's wrong.

It seems the error came from UFO-415.
Sectoid terror ship - Central Asia.
When he tries to land between Ankara/Bagdad/Teheran!

Perhaps the following data:
  - race: STR_SECTOID
    nextUfoCounter: 0
    spawnCountdown: 180
    type: STR_ALIEN_TERROR
    nextWave: 3
    liveUfos: 0
    uniqueID: 122
    missionSiteZone: 7
    region: STR_CENTRAL_ASIA


Save in attachments !
Tks !

[Edit] I've disabled all Mods. But I have the same problem!

[Meridian]

[Edit] I've disabled all Mods. But I have the same problem!

Turning mods off doesn't heal the damage they may have already done (to your save)... like in this case.

Try searching for this in your save and replace "7" with something lower, e.g. 6.

Code: [Select]

  - race: STR_SECTOID
    nextUfoCounter: 0
    spawnCountdown: 180
    type: STR_ALIEN_TERROR
    nextWave: 3
    liveUfos: 0
    uniqueID: 122
    missionSiteZone: 7 #<----------------- replace 7 with 6 or lower
    region: STR_CENTRAL_ASIA


[BlackStaff]

Try searching for this in your save and replace "7" with something lower, e.g. 6.

With the value 6 everything seems to have returned correct!
Thank you very much !

[Nord]

Can i make a suggestion?
During dogfight. Maybe it will be correct to not count disabled weapon (red by mouseclick) when using cautious mode? Right now if i disable weapon with best range and chose cautious, ufo stops at this range and does nothing.
Sorry for bad spelling, a flu is guilty.

[davide]

Can i make a suggestion?
During dogfight. Maybe it will be correct to not count disabled weapon (red by mouseclick) when using cautious mode? Right now if i disable weapon with best range and chose cautious, ufo stops at this range and does nothing.

+1

To fix the issue we could add the check on array _weaponEnabled

Code: [Select]

void DogfightState::minimumDistance()
....
void DogfightState::maximumDistance()

if ((*i)->getRules()->getRange() < min && (*i)->getAmmo() > 0 && _weaponEnabled[idxWep])
{
min = (*i)->getRules()->getRange();
}



[robin]

is there an option to make the zombification happen only if unit is effectively damaged by the hit?