Everybody's Gone to the Rapture

Everybody's Gone to the Rapture

View Stats:
 This topic has been pinned, so it's probably important
Misterfooks 23 Jun, 2016 @ 7:31am
Everybody's Gone to the Rapture - Patch notes v. 1.01
Hi everyone,

As mentioned previously on the forums, these past few weeks have been spent working on a patch to address the concerns and issues the players had been discussing, and Patch 1.01 is now available - read on for the patch notes.

Please note translated versions of these patch notes will be available very soon.

Thanks again for your patience and your support.

General Performance
Graphics settings have been tweaked to improve performance. We have also fixed a bug that would change some settings upon loading after the initial run.

SLI performance
We have identified an issue with NVIDIA SLI setups related to cloth meshes in the game, which were causing GPU stalls during geometry updates. This is now fixed.

21:9 Ultra-wide resolutions
We have now added support for ultra-wide 21:9 monitors.

Field of view
We have added a command line variable which allows the default field of view to be changed. To do this, edit the following line in the 'system.cfg' file, located in the root of the install folder (by default: C:\Program Files (x86)\Steam\steamapps\common\Rapture\):

Cl_fov=X

(where ‘X' is a value between 25 and 80)

Please note that the game was designed with a default FOV of 52, and changing this setting may cause some minor clipping issues within the environment.

Main GPU vs. integrated GPU detection
Some users have reported an issue with the game defaulting to their integrated GPU, rather than their main (more powerful) GPU. We have added a command line variable which provides an alternate detection method, which may help these users. To enable it, please edit the following line in the 'system.cfg' file located in the root of the install folder:

r_overrideDXGIAdapter=X

(off by default = '-1'; try setting value to '0', '1' or '2' to cycle through available GPUs)


Crash on triggering scenes
A small number of players have reported Microsoft Visual C++ related crashes upon tuning some of the manually-activated scenes. We have been unable to reproduce this issue internally, but have implemented a tentative fix by including additional dll’s in the game install.

Windows System Timer
In rare instances, the game may run slower if the Windows System Timer defaults to low resolution. To force the game to enable a high-resolution timer (and potentially improve performance), please edit the following line in the 'system.cfg' file (located in the root of the install folder):

sys_highrestimer=1

Manual save points
Separate to this patch, we have also implemented a new "beta" feature that allows players to manually save at every framed map in the game world. Please note that this is a big change to the game, which wasn't designed with this feature in mind. Whilst we have tested it internally without any observed issues, your mileage may vary.

Since this is a "beta" feature, it is only available by opting in to the "beta" branch of the game on Steam. To access it:
  1. In your Steam Library, right-click on "Everybody's Gone to the Rapture"
  2. Select "Properties"
  3. In the Properties window, click on the "BETAS" tab
  4. Under "Select the beta you would like to opt into:", select "map_save"
  5. Click on the "CLOSE" button at the bottom of the window. Steam will then download an update for the game.

Please note that the manual save system will not be available:
  • while a scene is playing, or for up to 20 seconds after the end of a scene
  • if you are in the vicinity of a manually-activated scene (even if said scene isn't currently playing)
  • during time-of-day transitions between chapters

In case you encounter an issue with any of your save files, it's possible to revert to a previous save by doing the following:
  1. Navigate to your save folder: C:\Users\<USERNAME>\Saved Games\Rapture\SaveGames
  2. Delete the two most recent files in the folder (or move them to a different folder if you want to keep them): one has the *.csf extension, the other the *.meta extension.
  3. Start the game again and select "Continue" – the game should load in the penultimate save location.
Last edited by Misterfooks; 23 Jun, 2016 @ 7:45am
< >
Showing 1-15 of 64 comments
himmatsj 23 Jun, 2016 @ 8:11am 
Can you explain a bit how have the graphics options been "tweaked"?

For those who've tried the patch, is the improvement major or minor?
Misterfooks 23 Jun, 2016 @ 8:15am 
You shouldn't see much of a difference (if any at all) in the visuals but our internal tests show a consistent framerate improvement of between 5 & 15 FPS on "High" graphical setting.
Tried a few different settings, and did four runs from Tipworth station back to the Yaughton playground but it seems that for my system the performance staid exactly the same (FX6300/GTX750TI/16GB/1080p=+/-30fps, though the Appleton farm sees drops to 20fps).
Still seems Object Detail is the real killer, so at low it stays :D
Misterfooks 23 Jun, 2016 @ 9:14am 
That's really surprising; we have a roughly similar PC here (better CPU, worse GPU) on which we get a consistent 45+FPS on "High" - are you restarting the game after changing settings? Might be worth also checking the 'Windows System Timer' section above to see if that helps.
himmatsj 23 Jun, 2016 @ 10:35am 
Originally posted by Misterfooks:
That's really surprising; we have a roughly similar PC here (better CPU, worse GPU) on which we get a consistent 45+FPS on "High" - are you restarting the game after changing settings? Might be worth also checking the 'Windows System Timer' section above to see if that helps.

Eh, worse GPU than a GTX 750 Ti? Getting 45fps on HIGH??? Man, I don't even get 45fps on High on my GTX 960 (pre-update)!!!
Misterfooks 23 Jun, 2016 @ 10:39am 
Geforce GTX 670, don't have the exact CPU model at hand (Intel i7) - have you tried playing since we released the patch?
himmatsj 23 Jun, 2016 @ 10:42am 
Originally posted by Misterfooks:
Geforce GTX 670, don't have the exact CPU model at hand (Intel i7) - have you tried playing since we released the patch?

No, let me try now. At the starting area it should give me a good idea (finished the game). Looking at the village from the starting area at medium settings used to drop me to 40fps. I'll report back.
Misterfooks 23 Jun, 2016 @ 10:44am 
Originally posted by himmatsj:
No, let me try now. At the starting area it should give me a good idea (finished the game). Looking at the village from the starting area at medium settings used to drop me to 40fps. I'll report back.
Thank you!
himmatsj 23 Jun, 2016 @ 10:55am 
Originally posted by Misterfooks:
Originally posted by himmatsj:
No, let me try now. At the starting area it should give me a good idea (finished the game). Looking at the village from the starting area at medium settings used to drop me to 40fps. I'll report back.
Thank you!

DAMNNNNNN!!!! :steamsad:

Like I said, before at the starting area, overlooking the village, I would hit 40fps.

On the exact same settings as before, overlooking the starting village again, I moved around and the MINIMUM framerate I am now seeing is 50fps.

Guys, on the one hand I'm happy you guys have improved performance by ~25%. Great work. I'm happy that the people who play after this can expect a better and smoother performance.

But on the other hand, I am very disappointed cause it came after I completed the game.

With all due respect, it is precisely stuff like this that makes me not want to buy games at launch (be it AAA or indie). I mean, same thing happened with The Witness and SOMA...by the time the patches came about, I had completed the game. I truly want to support indies, but I think going forward any graphically intensive indie game will have to wait unless the optimization is stellar off the bat.

Game settings:

AA on
Motion Blur off
Textures very high
Shadows medium
Detail medium

System specs:

i5 3330
GTX 960 SC 4GB
8GB VRAM
Windows 10

Test Location: Starting area, overlooking the village

Before: Lowest framerate = 40fps

After: Lowest framerate = 50fps

Performance improvement: 25%
Last edited by himmatsj; 23 Jun, 2016 @ 11:36am
Misterfooks 23 Jun, 2016 @ 11:07am 
We understand how you feel, and we're very sorry about not spotting those issues before the game's initial release on PC. The changes we made were settings that hadn't really been changed from the PS4 version, as they weren't causing any noticeable issues on that platform. Unfortunately, for some reason, that wasn't the case on PC, as you and other players have reported. We can only extend our apologies to you and the fans who got the game early.
Aries the 1st(2die) 23 Jun, 2016 @ 11:35am 
Originally posted by Misterfooks:
That's really surprising; we have a roughly similar PC here (better CPU, worse GPU) on which we get a consistent 45+FPS on "High" - are you restarting the game after changing settings? Might be worth also checking the 'Windows System Timer' section above to see if that helps.
TBH I'm not complaining (as for me the FPS matters little vs the eye candy on offer, hehe), and yep I did full restarts (as I had an edited game.cfg as well as autoexec+system.cfg).

1st run was the settings as I had them (no AA/motion blur/textures@very high/shadows@very high/object detail@low) , 2nd was with base .cfg files, 3rd was on high, 4th was on low. Everytime GPU usage maxed out, but FPS staid roughly equal.

BTW the GTX 670 isn't a worse GPU, per se, it has approx double the floating point performance :D Only chimed in to show what users with the same CPU/GPU could expect
Misterfooks 23 Jun, 2016 @ 11:38am 
Originally posted by Aries McBeard:
BTW the GTX 670 isn't a worse GPU, per se, it has approx double the floating point performance :D Only chimed in to show what users with the same CPU/GPU could expect
Thanks for that - feedback is absolutely what we're looking for :)

Sorry to hear you're not seeing the improvements we were hoping you would, though...
himmatsj 23 Jun, 2016 @ 11:41am 
There is a bug mate. Motion Blur keeps turning back on by itself each time I relaunch the game. Might wanna check that out!
Misterfooks 23 Jun, 2016 @ 11:46am 
Originally posted by himmatsj:
There is a bug mate. Motion Blur keeps turning back on by itself each time I relaunch the game. Might wanna check that out!
I just checked and I'm seeing the same issue here - we'll look into it with our coder tomorrow. Thanks!
EDIT: same issue applies to the Anti-Aliasing setting. We're investigating.
Last edited by Misterfooks; 23 Jun, 2016 @ 12:29pm
Misterfooks 23 Jun, 2016 @ 11:52am 
Originally posted by cronopio:
Hi, I cannot launch the game now, each time i try steam client bootstrapper crashes. Trying from the executable doesn't seems to do anything.
Not sure why that would be happening - can you try restarting your PC to try and clear up any possible issue with Steam?
< >
Showing 1-15 of 64 comments
Per page: 1530 50