Zoom Crash Starts at Chapter 3

[Gniarf]

I don't have time to think about the issue right now, I'll make another post later today.

Originally Posted by Chancellor23

I agree. This problem makes no sense to me. Why does it affect only one specific function of one specific weapon beginning with one specific chapter? It’s like this weapon has data that is stored outside of its definition file.

I keep thinking buffer overflow; and keep hoping it is not. (hence the sentence in my previous post)

Originally Posted by Chancellor23

I don’t know the programming language(s);

Lua

Originally Posted by Chancellor23

Just guessing, but it looks like a lot of variable assignments (“set”) or counters (“tick”). Except for the “[C]…” line, which looks like a looping statement (“foreachi”).

Set is use to set the x,y,z components of a vector.
Tick is called at periodic short intervals to simulate continuous behavior of all things (weapons, ennemies, bullets, effects...) in the game.
foreachi = for each i (I guess i is for item in a array or integer representing a identifier of a instance of a class (a bit like a pointer)).

Originally Posted by Chancellor23

I assume that the code is executed sequentially.

Correct

Originally Posted by Chancellor23

So, why are there seven lines in the error message?

It's the call stack, deepest on the first line. The problem is that this call stack dump is INCOMPLETE !! I mean, the game says:
./Data/LScripts/Classes/Types/Vector.lua:53:Set
./Data/LScripts/Classes/CPlayer.lua:1880:Tick
but at CPlayer:1880 there is a call to Current Weapon's Tick function. And ofc Tick happens to be the n°1 longest and most subfunction calling function. Yippee!

Originally Posted by Chancellor23

Boy, this game sure looks scruffy with these video settings.

Boy, I do love my 1024.
Boy, the devs used 1024.
Boy, don't say "scruffy" until you have tried putting Cfg.GraphicsQuality=0 in config.ini. xD

Originally Posted by Chancellor23

Same size as yours: 7,646,505 bytes (7,647,232 bytes on disk).

So I'll assume we have the same

Originally Posted by Chancellor23

The only good thing I can say about this bug is that it’s consistent: GEW98 with Bayonet, Mouse2, beginning with Chapter 3.

Quite unorthodox for a buffer overflow...

Originally Posted by Chancellor23

I suppose I could use the “nvnweapons” cheat code for Chapter 3 and pray that the bug goes away in Chapter 4. But I’m not a Cheat Coder. I wouldn’t experience the game “the way it’s meant to be played.” With or without NVIDIA.

1-haha lol
2-Or you could simply avoid the gew98 and find&use the other rifle (smle). But that would be admitting defeat.

Apparently you seem to have some coding experience, so you can try downloading a tool named "Painfull" by xentax to extract the .pak files. Extract lscripts.pak in data\lscripts and you can strat editting the code with notepad. No need to compile or repack the data. (ie: you can delete lscript.pak once its content is extracted, the game directly reads the extracted content)

[Gniarf]

Put the following CWeapon.lua in NecroVisioN\Data\lscripts\Classes. It will not solve your problem, but it'll log all calls from a CWeapon to CVector:Set into a GniarfLog.txt, which should be in the same directory than script_error.log.

Report the latest (bottom) number.