I'd say it's worth a try if you own it anyway. It has its moments. Maybe if you go in with the expectation that everything you see and do is largely textural, impressions of or responses to the setting rather than there being an explicit narrative core to it, it could help. To me anyway, it's kind of like if a TV show was mostly made up of filler episodes; a lot of color and feeling, not much directionality. By the end of the second or third act you'd have a pretty good idea of whether or not it's your kind of thing.beep boop I bought into the hype somewhere around Episode 4's release, sure it would be all out soon after, and was excited when the fifth episode came out. And then I heard people gushing about why it was so good and I realized I likely would absolutely hate it. I've yet to try it but congratulations for making your way through it.
Thanks again! Sounds like something I might enjoy, since I already turn off music in big budget racers.Copying my Steam comments to Kurt Russell since I guess it's a description.
Need For Speed: Payback - It was... OK. The map design was nice, but I didn't enjoy Drift, Drag and Dirt as much as normal racing or police escapes. Dirt picked up in the second league, because the tracks had more verticality but fell of a bit in the third one (which was still better than the first one).
The two biggest problems were the music (the OST wasn't that great overall and some tracks are relegated to cars of different classes, which makes it more repeatable than it would be normally) and upgrade system, which is based on RNG stat cards. So you need to either grind races in hope of getting something good, hope something good appears in the upgrade shop (which refreshes stock every 10 minutes) or hope you get something good from a literal slot machine that you pay with a currency you sell old cards for or get from lootboxes because of course. I saw people complaining about the cars having separate classes which you can't switch and have to buy the car again, and I guess it's valid, but I kinda just stuck to the starting cars anyway.
On the other hand, I enjoyed the scripted story missions way more than I expected. I cringed hard when I first saw them at E3 and while the first isn't that great, the rest was pretty damn fun. Not because the scenes themselves were interesting, but they switch between characters and by that, different playstyles on the fly - so they don't get boring and stand out from the standard races.
tl;dr - I haven't played a car racer in ages and I had a bit of fun. More experienced in the genre and especially fans of the series might disagree due to other games doing stuff better.
So I lied I spent 3-4 more hours trying to fix it and found a solutionWell Alan wake is complete shit
I installed it 3 times (After having it installed ready to play already)
It played fine at first then I adjusted settings, reststarted the game and it bluescreened my computer. Followed up by it uninstalled itself. So I reinstalled it/downloaded it again and put it on my SSD instead of my HD drive to see if it that was the problem? Then looked around on the internet and pc gaming wiki or whatever saw it might have to do something with Vsync and I had turned on Free sync because of my monitor so I basically turned everything off and tried again turning it on again for Wake.
Yeah it did it again another 3 times for blue screening/uninstalling its self.
I'm going to find another game to play that was dumb.
I just finished Alan Wake (not part of blitz) and I think I was lucky not to have much issues. Only needed to use -noblur to get rid of the awful blur, was making me nauseous just turning the camera.So I lied I spent 3-4 more hours trying to fix it and found a solution
Alright, so I was able to find a work around for it crashing my entire computer by looking up "crash problem solutions" the devs suggested in 2012 with the stating Alan Wake on its on will never cause a computer to blue screen on its on so its clearly the fault of a GPU or a failing power supply.
Well the solution to get it to work is setting steam start up commands forcing the game to start in Windowed mode, no vsync, no blur, (I also used the start up command to force it to delete my cloud save), along with forced resolution of 1920x1080
Surprise surprise it doesn't crash my computer anymore. It just crashes the fucking game whenever I quit the game and creates a crash file that they ask me to PLEASE SUBMIT CRASH LOG FOR THE QUALITY OF THE GAME
95% of the time Stuff on PC is super simple but there's always that 5% that is just annoying as shit
So far my takeaway of playing chapter 1 is I have no fucking idea what's going on besides that dude fucking loves flashlights and he would of murdered everyone in a scooby doo episode
Fake edit:
I forgot that I might as well list my launch options for Alan Wake:
-window -novsync -noblur -w1920 -h1080
Additional commands you can put into the launch options for steam ( I used the cleancloud setting once to delete my cloud save since that stores game settings for you):
-w: Screen width, e.g. -w1280
-h: Screen height, e.g. -h720
-window: Force windowed
-novsync: Disables v-sync
-showfps: Shows a frame rate counter on screen
-forcesurround: Forces 5.1 speaker mode
-forcestereo: Forces stereo 2 channel speaker mode
-nosound: Disables sound
-cleancloud: Deletes your save games and settings for Alan Wake from Steam Cloud
-noblur: Disables the in-game vector blur
-locale=xx: Forces a selected locale, e. g. -locale=en for English
-developermenu: Adds new menu [Developer Menu] to start screen to get guns, flashlight and more