Need help with a bug.

[cw58]

Hello all. I need some help with a bug. Here's a screenshot:

bug.jpg (801.37 KiB) Viewed 1461 times

Has anyone seen or experienced this type of bug before? I've modified my game significantly (equip, efx, move files, etc.) and I'm fairly certain the bug is caused by my changes. I'm just not sure which changes. The bug has shown up in the Grand Campaign and also in other mods. It always happens several turns into the mod, at the beginning of the player's turn and seems to be whenever the scenario objectives change. Does anyone have any ideas what could be causing it? Thanks for any ideas or insight you might have.

[Loamshire]

Is it caused perhaps by some code interference caused by a single script. Perhaps a big script or maybe not, but a script that would be better off being split up in some way?

[cw58]

Thank you for your response. I agree with you that it's probably caused by a script, more specifically, a script that causes the mission objectives to change. That seems to be the common factor whenever the bug shows up.

The strange thing is that script commands are one of the few things that I don't modify. And I'm quite certain that it's my modifications that are interacting with the script in such a way to cause the malfunction. But I will take your suggestion and look closer at the script commands; maybe that will give me a clue as to what is wrong with my mod. Thank you

[terminator]

Maybe it has something to do with the Zones ? Have you made any changes with the Zones ?

[cw58]

Hi Terminator.

No, I have not modified the zones in any way. After Loamshire's comment and remembering past occurrences, I'm almost convinced it is caused by some interaction between a script that changes objectives and something in my personal mod.

As I was playing thru the Grand Campaign (with modified files), I had multiple scenarios where this bug popped up and, if I remember correctly, it was immediately after objective changes. It doesn't crash the game or cause it to lock up but slows the computer down so much that the only way to complete the scenario is to use the "endscn" cheat code. The next scenario begins normally, with no problems.

I was hoping that someone might have come across this before and knew a solution or at least the cause of the bug. I will try to find time today to look thru the scripts and at least find the triggering command; maybe that will give me a clue. But thank you for taking the time to respond. It's one of the things I like about this community; so many people are willing to help

[cw58]

Problem solved.

After removing my mod and re-installing the game, the problem still persisted. I finally located the source of the issue in the 1.32 exe file; it had evidently become corrupt somehow and was wreaking havoc with several scripts. With a new 1.32 exe file in place, everything is working as it should. Thanks to those who contributed ideas. And now to conquer Europe!

[terminator]

Problem solved.

After removing my mod and re-installing the game, the problem still persisted. I finally located the source of the issue in the 1.32 exe file; it had evidently become corrupt somehow and was wreaking havoc with several scripts. With a new 1.32 exe file in place, everything is working as it should. Thanks to those who contributed ideas. And now to conquer Europe!

How did you corrupt an exe file

[cw58]

Problem solved.

After removing my mod and re-installing the game, the problem still persisted. I finally located the source of the issue in the 1.32 exe file; it had evidently become corrupt somehow and was wreaking havoc with several scripts. With a new 1.32 exe file in place, everything is working as it should. Thanks to those who contributed ideas. And now to conquer Europe!

How did you corrupt an exe file

I have no idea. All I can say is that after reinstalling the game to 1.30 and applying the 1.32 exe, the bug was still there. Replacing the 1.32 exe with the 1.30 exe, the bug was gone. So I replaced the 1.30 exe with a new 1.32 exe and the bug was still gone. So I'm assuming there was something wrong with the first 1.32 exe.