3/24/2023 0 Comments Winebottler steam crashes instant![]() But then also I had to attach to the outer process after zink was loaded, so it was a real struggle. So in the end, I had to attach using the proton script, then while it was paused, attach to the outer process for driver debugging. Gdb -pid=$(pidof WolfNewOrder_圆4.exe) ended up what I needed, but this was complicated by the fact that I had to attach before the game crashed and without triggering the steam error reporter. ![]() What I actually wanted was to attach to the wine process itself so I could see what was going on in the driver. The problem now is that I’d attached a debugger to the in-wine process, which is just a sandbox for the Windows API. This solved the problem of getting a debugger in before the almost-immediate crash, but it didn’t get me closer to a resolution. PROTON_DUMP_DEBUG_COMMANDS enables dumping scripts for debugging from steam, including one which attaches a debugger to the game. Suddenly, I was back in 2004 trying to figure out how to debug wine apps. It turns out that having the GL compatibility context restricted to 3.0 is bad for getting AAA games running, so zink-wip now enables 4.6 compat contexts.īut then I was still getting a crash without any clear error message. To that end, as I hinted at yesterday, I began with Wolfenstein: The New Order, as chosen by Daniel Schuermann, the lucky winner of the What Steam Game Should Zink Use As Its Primary Test Case And Benchmark contest that was recently held.Įarly tests of this game were unimpressive. ![]() I’m not going to answer these questions, but I am going to be looking into getting them working on zink. ![]() …or in the very near future, the ol’ bumperino will have landed, putting zink at GL 4.5.īut that’s boring, so let’s check out something very slightly more interesting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |