🚀 go-pugleaf

On Sun, 15 Nov 2015 13:39:10 -0500, Rin Stowleigh
<rstow...@nevrhadgmail.com> wrote:

>
>This is quite possibly one of the most idiotic things to happen in PC
>gaming in a couple of decades.
>
>http://www.technobuffalo.com/2015/11/10/fallout-4-framerate-capped-and-tied-to-game-speed/
>
>Once upon a time, the timing of games and the frame rate were tied to
>the actual speed of the CPU.  Like, approximately 35 years ago when
>the developer of a game for a given computer only needed to test their
>game on a computer for which there was only one CPU available for.
>
>So, for example an early PC I owned had a chip that was twice the
>clock speed of the original IBM PC.  Running games written for the IBM
>PC ran rediculously fast (which was good for something like a turn
>based game which was not timing sensitive, but was a problem for an
>action game which would in essence become twice as difficult by
>playing on the faster chip).  So, a lot of times I used a utility that
>would in essence force the game to run at the proper speed (or at
>least close enough to it).
>
>However, Bethesda seems to have been practicing at one point for a
>real nuclear war, because they seem to have shoved their heads so far
>up their own asses that they have become oblivious to the advancements
>of chip technology since the early 80s.  
>
>You might be wondering how I came across this.  Well long story short
>there is a nasty bug that exists when hacking/using terminals at
>higher framerates.  More times than not, the player just becomes stuck
>when they exit the terminal hacking mode; stuck as in cannot move,
>must reload a quicksave.  Not a problem if you don't really need the
>terminal access to advance, but there are some places where it is
>required to complete a quest milestone.  So, I was looking around at
>options and fixes.  Apparently this is some sort of built-in bug that
>Bethesda added to penalize folks with real computers for having decent
>hardware -- I guess they would prefer we just said fuck it and bought
>the console version instead?
>
>If you want to read about possible fixes for the stuck at terminal
>bug, just google "fallout 4 terminal hacking bug".
>
>Bethesda's apparent solution to GSYNC monitors is to have a locked
>72hz vsync'ed mode!  And, if you're used to real gaming, playing at
>that feels like youre playing with your optical mouse sitting in a
>bowl of peanut butter.
>
>GSYNC is one of those technologies that in itself is pretty much
>flawless.  You don't have to do much and it just works.  In fact, you
>have to work pretty hard to fuck it up.  Bethesda apparently put in
>the man hours to do just that, because they fucked it up royally in
>this game.  Nice job, morons.

Rin,

Thanks so much for the warning !!

A console port hacked for the PC. Thanks for lowering your standards
BethSoft... NOT !!

Anyway, I am so glad that I did not purchase Fallout 4. Maybe by the
the time the PC version of the GOTY comes out (at a reasonable sale
price, of course), then BethSoft might have removed their heads from
their collective a**es.... 

Yes, I also have GSync and it had better work properly with GSync,
maxing out with Vsync off at my chosen default frame-rate... otherwise
I will very happy to give it as miss.

John Lewis