Fallout 2: Dogmeat issue

[psemiletov]

When I found Dogmeat at Cafe, I can't interact with the dog (wearing just a Vault suit). Is that releated to Fallout 2 CE or usual Fallout 2 bug?

[JanSimek]

It would be helpful if you attached your savegame

[JanSimek]

There are other issues with the dogmeat script but even when I played with the Restoration Patch it did not work. It turns out ECDogMet.int script uses tile_num_in_direction with the origin argument as pointer instead of tile number:

tile_num_in_direction(self_tile, Random(0, 5), 1); // tile integer
tile_num_in_direction(dude_obj, Random(0, 5), Random(5, 10)); // pointer

I couldn't find any modification of this function in the Sfall code, so I assume that's how it works in the original engine as well although the MMapper guide only mentions tile number.

[JanSimek]

Turns out this was a vanilla bug that will be fixed in the next RPU release: BGforgeNet/Fallout2_Unofficial_Patch@55a08f4

Here's an explanation from NovaRain:

in the original engine the function would return an "impossible to reach" tile number based on the value of object pointer (e.g. I got 181576192 from calling tile_num_in_direction(dude_obj, random(0, 5), random(5, 10));
a more detailed example:

val1 := random(0, 5);
val2 := random(5, 10);
display_msg("Dude obj ptr: " + dude_obj + ", rnd dir: " + val1 + ", rnd dist: " + val2);
tmp := tile_num_in_direction(dude_obj, val1, val2);
display_msg("tile_num_in_direction: " + tmp);

Result:

Dude obj ptr: 181642728, rnd dir: 4, rnd dist: 7
tile_num_in_direction: 181642135

[phobos2077]

Since this is a script error and has nothing to do with the engine, I suggest closing.

[psemiletov]

But Dogmeat works as intended at Fallout 2 for Windows, as a companion.