Vigilantes > Resolved Bugs

[Resolved]Graveyard escort mission failed to initialize

<< < (2/3) > >>

ushas:
One more hint, in case you haven't found the culprit already:
I can consistently get this issue when triggering the mission with 4 party members. With 3 it starts flawlessly. Maybe it has problem to position either one of the allies or one of the additional enemies who is added due to higher number of allies (by the in-log sequence it may be one of the MafiaAssociateM)? This time saved also the autosave too (v16, linux, HB, 23 July). If you need it, let me know.

Hm... I was letting Emilia wait for me ~18 days before coming for her.
I wonder if it was too early to declare other problematic missions working well...    Will recheck with 4.

ushas:
Yeah, of course...

Practically most of the missions on danger 3 (or high wealth) will now fail to initialize when using 4 party members.
(v16, linux, HB, 23 July)

So it's easier to list maps/missions (danger 3 / high wealth) that initialize well:
    Survivalists:   9 barbarians, 11 DirtyApartment, 13 DowntownConstruction1, 26 DowntownMed4, 27 DowntownMed5
    Mafia:   8 Meltdown, 9 barbarians, 11 DirtyApartment, 18 Blackmaii, 20 Bootleggers, 23 The Hit,  27 DowntownMed5
    Church:   9 barbarians, 11 DirtyApartment, 14 Grave diggers

Meaning all the others maps fail to initialize and (probably) there will be the same out of range exception as reported before. Danger 1 & 2 lvl tiles seem ok, but haven't tested all. Except, according to the surveillance info, I somehow managed to lower danger level from 3->1 after a mission on one tile. And then the map initialization will still not finish properly on this tile for those problematic maps. So perhaps it's more related to high wealth (difficulty)? Well, the issue somehow directly or indirectly relates to number of enemies...

Daithi:
Good information here. Didn't realise there was such a problem with Danger Level 3 + full party. Have made changes to restrict number of enemies spawned - so this might be already fixed, but will do some testing.

ushas:
July 27: Dear diary, guess what happened today?... Started Wolves of the Night on high wealth & danger 3 tile having all allies and no problem what so ever... Whole party thinks me crazy. Aside time I'm not sure what's different.

Also thought that perhaps it's somehow connected to the spawning issue you already resolved. So will let it be for now?
(will hide somewhere in the meantime ashamed of inconsistent reporting)

Also I'm not sure whether it's danger 3 or wealth 3, as both were aspects of those tiles. Is it possible the game starts with danger 3 tied to high wealth? For some reason I was thinking previously danger and wealth separately.

ushas:
An echo from the hideout: The map from July 27 started by launching the mission blindly from the cityscape, whereas most of the maps tested were called using the console. Now when I start it naturally more missions are suddenly working. Those usually report as Map# conf:1 (or conf:2). Called from console the ones freezing are reporting as Map# conf:0 (or conf:2) when used 'm'. 

Haven't you said that conf:1 is connected no larger number of enemies? So perhaps it's nothing new and already resolved indeed...

However, there is also this inconsistency with the console. When launching naturally I'm getting map initialization not working with 4 party members on high danger/wealth too (eg. Escort mission), but it's not the amount of maps as reported above any more. So perhaps there are more issues at play?

In case not so easy to reproduce/fix, I can simply try revisit in v17 and report any changes, now knowing more what to look after.

Navigation

[0] Message Index

[#] Next page

[*] Previous page