• Nurse background (uiIndex=266) has ap_assault listed twice. Both values are the same (-5), so no real problem, but still, one should be removed.
  
• Sapper background (uiIndex=302) has:
  
  • ap_fortify listed twice. Values are different (-20 and 10) - should obviously be set to -20.
    
  • explosives listed twice. Values are different (5 and 8) - should probably be set to 5.
• Mental Patient and Wrestler backgrounds (uiIndex=307 and 308) have resistance_physical set to 20, but in-game hover tooltip shows the value is only 10, so it seems that the value is somehow limited by the game mechanics to be 10 at max. It seems that either the 10 hard-limit should be removed from game, or the values in these backgrounds lowered to 10 (and perhaps some other value could be raised instead).
  
• Tech Whiz background (uiIndex=296) should probably have hackerskill set, otherwise there is no way to have I.M.P.-created character capable of hacking. I think the value should be something around 80, as that's Speck's value and his background is Tech Whiz also.
  
• Graduate background (uiIndex=297) should probably have hackerskill set, too, as there is a similar background (Harvard graduate, uiIndex=45) for Gumpy NPC and he has this skill set to 60. However, I would set it lower (graduate != Harvard graduate, after all), let's say around 40. This would again widen the possibilities for player to have his I.M.P. character chance to do some hacking.
  

Hello,
I have a minor problem with my self compiled rev8928 on gamedir 2580.

Situation: Mine blows up after a merc tries to lay a mine or tries to disables a mine.
Anticipated behavior: Single explosion or follow up explosions if the merc has something explosive in inventory.
Observed behavior: Single explosion (OK), sometimes normal follow up explosions (OK), sometimes excessive amount of follow up explosions (>30, not OK) with damage values >500. Screenshot-> https://ibb.co/2dX6sfp

Additional information: I tested the same thing with a rev8922 exec from a polish form which didn't seem to have this problem.

Cowering animations are buggy in the game, for example, cowering merc cannot stand up but can go prone, and if ordered to move will just stand up with buggy animations.

sevenfm wrote on Tue, 09 February 2021 11:04

Cowering animations are buggy in the game, for example, cowering merc cannot stand up but can go prone, and if ordered to move will just stand up with buggy animations.

Iirc, in 8675 mercs stand up instead of cowering (fixed in 8684). Could this might be related?

1. Item duplication bug: Entire sector inventory sometimes keeps getting duplicated whenever I doubleclick on that sector to open its inventory. In other words, whenever I open the sector inventory, the game creates another copy of each item in that sector. Not sure why it happens but I've encountered this bug in three different playthroughs. Restarting the game seems to fix it.
   
   Update: Apparently some other people also reported this bug way back in 2017.
   
   thepit.ja-galaxy-forum.com/index.php?t=msg&goto=352104&&srch=duplication#msg_352104
   thepit.ja-galaxy-forum.com/index.php?t=msg&goto=350380&&srch=duplication#msg_350380
   
   
2. Enemy duplication bug: Recruiting enemy soldiers using the "turncloak" feature creates another copy of them on the same sector. Doesn't matter if you kill the rest or managed to convince all of them to join you as militia, the sector never gets cleaned since an identical number of enemies show up on the same sector. Let's say that there are 20 enemies in a sector. If you have successfully convinced all of them to join you, there are now 20 militia and 20 enemies in that sector. If you convince them partially, say 15 of them and start a battle with the rest and then you defeat them without any death, you now have 15 enemies as well as 15 militia. (Update: Just tried it with the build 8955/2584 and it also has the same problem which is easily reproducible. You don't see the enemy in the tactical screen though, they only appear in the strategic view).
   
   
3. Another major problem regarding the "turncloaks" feature is that if you "activate" the recruited enemy soldiers in real-time (i.e. without starting a turn) most of the time the game gets stuck either on the militia's turn or on the enemy turn, in other words their turn never ends. The only way to reliably avoid this issue is to first start your turn by pressing D end then activate them.
   
   
4. Getting hit by stray bullets from a battle taking place in a different sector: Not sure what triggers it but sometimes when you get into a fight in far away a sector, one of your mercs in a totally different sector, who's been repairing stuff or training, gets hit by stray bullets from a battle in a different sector which isn't even close. It's most likely the first merc you hired, in my case it was the IMP guy.
   
   
5. Sometimes when a merc notices a new enemy just before throwing a grenade, he doesn't actually throw it but the grenade still disappears from his hand and the action points required are still reduced.
   
   
6. I keep seeing a red shirt enemy in the top left part of every single sector, which looks like some kind of a graphical glitch cause he's not actually there.
   
   
7. Mercs disguised as enemy soldiers sometimes lose their enemy uniforms. In other words, even though you gave them both an army shirt and an army pants, when you take them off you only receive one of them and not both. The same thing happens when the enemy sees through their disguise as well (i.e. when their enemy uniforms are automatically removed).
   
8. Build 8918 & 8955:
   
   After taking care of the enemies in the first sector of Omerta, if you hire more mercs or IMPs without leaving the sector, neither the helicopter nor the mercenaries actually show up, even though the game adds them to squads and plays the landing dialogue. Not only that but the game keeps repeating their dialogues about the flight for the new mercs (IMPs) and doesn't play the dialogues for all the new mercs.
   
   

Line 153 in function NumHostilesInSector in file Queen Command.cpp

(sSectorX) > (MAXIMUM_VALID_X_COORDINATE) but should be less than or equal

im playing 1.13 wildfire with 8766.exe and WF 6.07 maps and a german language patch (german voices and some texts)

when i enter the drassen SAM d15 with my spy, give him the assignment to collect intel and fast forward time i get this error a few minutes before the hour is over


Quote:

Assertion Failure [Line 153 in fUnction NumHostilesInSector in file Queen Command.cpp].

(sSectorX) > (MAXIMUM_VALID_X_COORDINATE) but should be less than or equal

there are 12 enemies in the sector at this moment.
it works on other sectors but this particular one crashes the game.


i have not yet enough comments to attach links to my savefile but ill report back if something similar happens later on

Regarding the bug with meanwhile-scenes (at POW-camp (Joe punch) and Arrive-at-Meduna-Outskirts (Deidranna shooting Eliot), both resulting in endless clock), I could narrow it down a bit. It's still working with 8904/2573 , but 8908/2573 already has the bug (I have no copies of 8905-8907, couldn't test). Reading SVN-changelog, could it be happening in 8905? The part with "CancelAIAction: reset bNextAction and next action data" and "clear next action data before making decisions" ?

[Dynamic Opinion Settings]

;*********************************************************************************************************************** *******
; In this section you can specify whether mercs form dynamic opinions on each other
;*********************************************************************************************************************** *******

; mercs can form dynamic opinions of each other, this in turn will affect their morale
; for more info on what can affect opinions, see Dynamic Opinion Modifiers Settings in Morale_Settings.ini
DYNAMIC_OPINIONS = FALSE

; notify the player of opinion changes in the message log
DYNAMIC_OPINIONS_SHOWCHANGE = TRUE

Build 8955: Attached a detonator into the first slot on the second row on a TNT (by manually placing the detonator on that slot) and the detonator simply vanished into thin air despite producing a "successful attachment" sound. WTF?