steam-2216770.zip
Here is the proton log, I guess drop didn't work.
Hello @mark9539, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/7539#issuecomment-2558549592.
Compatibility Report
System Information
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
(Proton log added as a zip file)Symptoms
In some levels there is an extra challenge to complete the objective using a limited number of commands - when running this game from my linux partition then each of the commands appears to be double counted (making it hard to complete!).
If the same python script is run (on the same pc) under Windows then the commands count for 1 each as expected.
On Linux it does count as a single operation if using the single step over under "Debug" - it is the "Run" mode which shows the problem.
I have checked the main branch as well as pre-release. Using DirectX 12 and directx 11 launch options.
Reproduction
<I've broken down the minimal steps without having to understand or solve the problem on the level, or import an example script>
0) Click "Play Game" on the computer to get into the game proper.
AirliftCrane.first().pickup()
It goes before the while loop so it only executes once. This should count as a single command for the challenge.
To reproduce the error:
4) a) Press the reset sim environment button - lower right side - ( the counter will not reset between tests otherwise)
b) Under the map briefing text on the right side of the screen there will be a counter in yellow or green text (Note: the extra challenge text and counter appear only after starting the 1st run - not on load)
b) Press Run at the top of the code window, the count of operations updates to 2 (bug) - this does not happen under windows - it will count 1 operation as expected
Alternatively: (demonstrates counter is working in debug mode)
5) a) Click reset again to clear current state / operations counter to 0.
b) Click beside line number 11 to set a breakpoint
c) Press the Debug icon at the top of the screen
d) Press "Over" (F10) to single step past the "pickup()" operation.
Then single step again or run (F5) to ensure it is in the while loop - the count will remain at 1 (correct)
e) It is the single step that is key, choosing either Continue (Free run to next breakpoint) or Into (Step into) will
produce the error.