David Board  [developer] Jul 2 @ 12:45am
CAMERA/CHECKPOINT BUG IN CHASM LEVEL -- FOUND IT!
(Note: a bit of background here, but if you just want the workaround, skip down to the end.)

As some of you know... there has been a bug that has vexed me since early access, one that several times I've thought we'd fixed. The issue is that when you die in the chasm level (for some users), the camera gets stuck looking at the place where you die. And then when you restart and choose "Resume Game" you are placed back at the prior level (Research).

Well... I'm happy to report I found the problem! I have been digging into this issue again the last few days, determined to find a solution. The trouble was, I had NEVER experienced it myself, nor had any of my "internal" testers. I tried again last night--everything I could think of to duplicate it, including deleting spawnpoint objects in the editor as the game was playing, etc. in attempts at breaking the game so I could experience the problem and then go about fixing the code that caused it. Nothing worked. For me, the game continued to reset perfectly after player death no matter what I did.

And then tonight... I recalled some advice from a programmer I hired a few weeks ago (to implement the Xbox One port). He said the issue was likely due to a physics/collision issue. These usually crop up when frame rates are too low. In the 1.2 build we implemented some code to help address this, but recent posts made me realize it was still happening. Well, it occurred to me that I could force lower frame-rates on my pc by running burn-in software in the background as I played the game. So I ran Prime 95 which sent all cpu threads to 100% usage... and then I ran the game. Frame rates when down to single digits, and sure enough, the camera bug appeared--every time!

Can't tell you how happy I was to finally see this for myself, after hundreds and hundreds of hours playing the game and never seeing it, but hearing about it every few days or so from a gamer. And since I was able to repeat it, I was also able to see the error logs, pointing me right to the issue. Essentially, when you ride the platform in Research, the player object is parented to the platform. But because of the low frame-rates, leaving the platform isn't always triggered. Then later when you die, the camera looks for the player object... and doesn't find it as he's still a child object of the platform. This is a pretty easy fix, but we'll do some testing and tweaking of the related systems to make sure it's really solved. I have no doubt whatsoever that this is the issue.... FINALLY!


SHORT-TERM FIX:
If you run into this bug, you can fix it by quitting the game, restarting and then choosing New Game -> Chasm. You will not have to repeat the Research level, nor will you experience a stuck camera and total progress reset when you die.

LONG-TERM FIX:
We'll be uploading a new build as soon as we can to permanently address the issue... details to come.

Thanks for your patience and understanding, everybody. We'll finally have this fixed for good very soon!

Thanks again,
Dave
Showing 1-5 of 5 comments
< >
Гончаров Олег Jul 2 @ 1:11am 
Жаль на русском нет у вас разраба, что патчноты описывал. А то гугол плохо переводит.(((
Last edited by Гончаров Олег; Jul 2 @ 1:12am
Гончаров Олег Jul 2 @ 1:18am 
Лучше сделайте лог ошибок или дамп ошибок - в случае ошибки лог отправлялся вам на мейл.
Better make the "error log" or "dump error" - in case of an error log is sent to your email. srry bad english.
Last edited by Гончаров Олег; Jul 2 @ 1:19am
David Board  [developer] Jul 2 @ 1:21am 
The problem was until my stress test tonight the error logs were always totally clean-- there were no error log messages... Obviously, I should've tried the stress test sooner, but I didn't think low frame-rates could cause this kind of error. Lessons learned... so many lessons!
Гончаров Олег Jul 2 @ 1:28am 
Originally posted by David Board:
The problem was until my stress test tonight the error logs were always totally clean-- there were no error log messages... Obviously, I should've tried the stress test sooner, but I didn't think low frame-rates could cause this kind of error. Lessons learned... so many lessons!
ok.ok.srry. my fault.
"Мы никуда не спешим - мы ждём от вас релиза"
"We are not in a hurry - we hearing from you release the game"
Although game currently "just":
"COOL"
^_^
Last edited by Гончаров Олег; Jul 2 @ 1:34am
PepperKilo Jul 13 @ 6:16am 
Dude, I've never seen a dev go so in-depth with the bug fixing before. This dev is legit, this guy makes it known that he f#$%ing loves his work enough to fix such pressing issues. respect.
Showing 1-5 of 5 comments
< >
Per page: 15 30 50