SOMA
Jeba 2015년 9월 22일 오전 2시 22분
[spoiler?]stuck in comm center
None of the 8 codes to establish a connection with a site on the big computer work. there are no additional codes hidden in papers or audio logs. Cant open the hatch I came from to backtrack. Any tips appreciated
< >
8개 댓글 중 1-8개 표시
Gnoffah! 2015년 9월 22일 오전 2시 28분 
After typing in a a code for the station you are to call, do you not get a screen where you move a cross to tune in on the signal?
Jeba 2015년 9월 22일 오전 2시 30분 
Ah I see. that was quite stupid of me to not realize it. thanks
Sytch 2015년 9월 23일 오후 1시 47분 
Uhm, I've managed to connect two sites but now the "Back" button became disabled for some reason and I can't get to the main screen where you enter codes. Is it a bug? Also screenshots are completely black.

I'm on Debian Stretch amd64.
Resmi 2015년 9월 23일 오후 2시 04분 
Fwiw, I have the same glitch as RKFG and I'm afraid I'll have to restart. It really killed the mood. :(

Edit: I should say that I own the PS4 version.
Resmi 님이 마지막으로 수정; 2015년 9월 23일 오후 2시 05분
Sytch 2015년 9월 23일 오후 2시 10분 
Rez, I've started to connect from the last to the first and this time it worked. However, if I start to connect them in the usual order, top to bottom, on Lambda it doesn't start the script. Very unfortunate bug.

For the devs: Here is my save[rkfg.me], just before the comm center computer. Start connecting the stations (2201, 2202 etc.) and you'll trigger the bug.
Sytch 2015년 9월 23일 오후 2시 20분 
Ah, got it. So the problem was that I haven't even noticed that something happens on the big screen after entering the code and started to enter the next one. Simon should raise his head so it's visible. While it tries to establish connection, enter the next code quickly. Voila, it breaks. The terminal should be locked until the "connection" script finishes I suppose.

Also, after that exiting to the main menu seems to be crashing the game. I have this in dmesg:

[20663.433894] Soma.bin.x86_64[28677]: segfault at 98 ip 0000000000e30fcb sp 00007fffc194e050 error 4 in Soma.bin.x86_64[400000+1904000] [21059.487149] Soma.bin.x86_64[28861]: segfault at 8 ip 00007fe7e3cd2fde sp 00007ffdb54779a0 error 4 in libnvidia-glcore.so.355.11[7fe7e2dba000+126f000] [21948.563802] traps: Soma.bin.x86_64[30539] general protection ip:e1532f sp:7ffe4241f880 error:0 in Soma.bin.x86_64[400000+1904000]

Log isn't very useful probably but anyway: http://pastebin.com/r3mpbe5N
Sytch 님이 마지막으로 수정; 2015년 9월 23일 오후 2시 22분
Marisa the Magician 2015년 10월 3일 오후 1시 09분 
I have to butt in here to say that I'm getting A LOT of those segfaults in libnvidia-glcore too (and at the same offset of +126f000, too). They can happen completely at random, but always when either exiting to the main menu, alt-tabbing or interacting with screens.

This has been going on since the very beginning of the game, and I've only managed to go further into the game thanks to all the new beta updates that have been coming out. As of now, I last left off on the zeppelin to Theta, I had the bad luck of accidentally pressing escape in the middle of the whole thing.

Same drivers, but I'm on a 560Ti. Here's my log, which I don't think is helpful either: http://ix.io/laq

This could probably deserve its own separate topic, I guess.
Sytch 2015년 10월 3일 오후 1시 31분 
Marisa님이 먼저 게시:
exiting to the main menu
not check
Marisa님이 먼저 게시:
alt-tabbing
check
Marisa님이 먼저 게시:
or interacting with screens.
not check again. My experience with the latest build was satisfactory though Alt+Tab crash is annoying of course. I'm not actually Alt+Tabbing as I'm using Awesome WM, I'm pressing Alt+1..9 but effectively it's the same. I had crashes on exiting to the main menu before but not after the latest patch. Maybe you run out of GPU memory? Too bad HPL3 doesn't log the traceback on segfault like UE4 does. They could have used google breakpad to save minidumps for instance.
< >
8개 댓글 중 1-8개 표시
페이지당 표시 개수: 1530 50

게시된 날짜: 2015년 9월 22일 오전 2시 22분
게시글: 8