[Outdated][Bug 1.04] Game Crash Under Particular Circumstance

Production Line Bug Reports
1

Boy do I have a hell of a bug report for you today, Cliff.
Now, i discovered this when I was using Cheat Engine to cheat in game, because I wanted to rush end game.
However I noticed that if I was in game, and then proceeded to search for Cheat Engine (6.6) in Cortana then the game crashed. After a little more experiementation I discovered that the bug lay within Windows UAC.

Firstly, I am running an i7 3770K, not overclocked. An RX 480, Windows 10 with the latest updates. All graphics drivers etc are fully updated.

To replicate this bug:

Open Production Line, either into an actual game or onto the menu.

Open either Cortana, or the Windows Start Meny.

Proceed to search for and launch any application that requires Windows UAC permissions to run. (Cheat Engine, Intel Extreme Tuning etc)

Once the UAC dialog comes up and you accept it, Production Line has crashed.

SIDE NOTES:

This bug only happens if the application requires UAC, other applications do not cause PL to crash.

You do not have to launch the program though Cortana/Windows - If you have a UAC required program on the start menu, Production Line will still crash.

That covers that: Cheers!

2

Can confirm that there’s something weird going on. But for me Production Line goes into the Black Screen error state.

Btw Cliff, the *.log files in My Documents… have timestamps in GMT, which is super confusing when that’s not the computer’s timezone :wink:

3

Why do you need cheat engine for this game ?
The save-files are simple xml-files that can be edited with most text editors (Numpad++ for example)

If you need more money, the value is written as a simple numeric value near the end.

4

hi, if you set the game to run in a window (if you had an early build, you might need to nuke prefs.ini) but still the same screen size, so it looks fullscreen, does this still happen? It sounds like a relation to the original alt-tab bug, now fixed because the game runs in borderless windowed mode by default.

5

Hey Cliff, sorry about the late reply.
I only run my game in Windowed Mode.

I also recently updated to 1.03 and the issue persists in Windowed Mode and “Fullscreen” mode. I also confirmed something I expected, in that it only freezes the actual graphics of the game. The game continues to run in the background.
This means that you can “click” on elements and hear them register on the main menu, but the GUI never appears and the game is frozen.