RUN Time Error please Help

[Ron WEEDseed]

i have updated my pc frpm ultimate to professional windows7 i installed steam and the game i stardet it with window and full screen

[Xaphir]

i have the same problem...

[dukope]

Try again and let me know if it magically works now.

[Jason]

I got this game last night (version 1.0.33). I was able to play for hours using the normal "Play Papers, Please" option in Steam. An update downloaded this morning (1.0.36a - don't know if this is related to anything). When I started to play today, I got runtime errors on the "Play Papers, Please" option, but was able to get the game to launch using Windowed Mode. I played for several hours in Windowed Mode. I exited the program (because the screen suddenly dropped to a tiny resolution when windowed), and when I tried to relaunch, now Windowed Mode gives a runtime error, too, in addition to normal "Play Papers, Please."

So the game doesn't run at all now in Steam.

[Alverada]

hi, I have the same problem: "runtime error" when launching the game. mayday.

[Alverada]

when launching exe from directory, the game run but i have the message "steam client failed". Help.

[dukope]

Can some super helpful person try re-installing Steam and let me know if that makes a difference?

[Dawnseeker]

Had the same problem today. Starting the game in windowed mode seems to have fixed it for me. I switched back to fullscreen after I got to the main menu.

[Aspic]

For what its worth - same problem here. Crashes on startup. Tried Dawnseekers advice above and tried to start in Windowed Mode but same problem. I've changed nothing on my system at all. This is on Windows 8 64bit.

[Jason]

I uninstalled and reinstalled Steam, lost all installed games, and reinstalled Papers, Please. Same issues. Will not load in windowed or fullscreen modes. Tried running in Explorer, and it loaded one time, gave Steam connection error, then closed. Relaunched in Explorer, and got paperplease.exe error again.

[Rocketman Dan]

I can launch from directory but i cant play the game because there's no connection to steam but the runtime error crashes the game on startup in windowed or non-windowed mode if launched from steam. It was working fine earlier today but I came back to it and it just won't work.

[dukope]

Originally posted by JC:

I uninstalled and reinstalled Steam, lost all installed games, and reinstalled Papers, Please. Same issues. Will not load in windowed or fullscreen modes. Tried running in Explorer, and it loaded one time, gave Steam connection error, then closed. Relaunched in Explorer, and got paperplease.exe error again.

Thanks for trying so much. Can you file a support request at http://papersplea.se/support and just say it's you somehow? You don't need to fill in any details. I want to try some stuff with you through email.

[black.stormy]

Full screen I get the "steam conneciton failed" error.
The debugger said for fullscreen:

First-chance exception at 0x76A8C41F in PapersPlease.exe: Microsoft C++ exception: Dynamic at memory location 0x0018F98C.

For win:
First-chance exception at 0x72627042 (nme.ndll) in PapersPlease.exe: 0xC0000005: Access violation reading location 0x00000004.
First-chance exception at 0x76A8C41F in PapersPlease.exe: Microsoft C++ exception: std::__non_rtti_object at memory location 0x0018FA30.
First-chance exception at 0x76A8C41F in PapersPlease.exe: Microsoft C++ exception: std::__non_rtti_object at memory location 0x0018FA30.
Unhandled exception at at 0x76A8C41F in PapersPlease.exe: Microsoft C++ exception: std::__non_rtti_object at memory location 0x0018FA30.

Let me know if I can help more...

[dukope]

Can some brave soul try deleting local game content and re-installing this buggy game? I just pushed an update (1.0.37) that should hopefully fix this runtime error startup crash.

[faelnor]

I still got the crash. "Version" in the assets folder contains 1.0.37.
If I start the exe manually, the game comes up but can't find Steam.

EDIT: Okay it works now. Weird...

[AcidTongue]

My game works now, yay. I didn't have to re-install, 1.0.37-S fixed it. Thanks for working so hard to figure it out, I doubt these types of things are easy to pinpoint.