I’m frustrated. Exceedingly so.<\/p>\n\n\n\n
You see, I had a busy day today. Had a major go-live today that soaked up most of my waking hours from 6 AM to 4 PM.<\/p>\n\n\n\n
I was looking forward to playing Assassin’s Creed: Mirage. I even made sure to download it early this morning so it’d be ready when I was off work and relaxed.<\/p>\n\n\n\n
First sign of trouble: The download had apparently stalled at around 75% percent.<\/p>\n\n\n\n
Ok, well, whatever. I’ll kill it and restart it, after trying with great futility to get it to resume.<\/p>\n\n\n\n
That ended up launching into incorrect error diagnostics with Ubisoft, reinstalling Ubisoft connect, rebooting multiple times, restarting my router, and then FINALLY I managed to get it downloaded and installed.<\/p>\n\n\n\n
I load into the game, adjust a few display settings, and deal with the forced restart to apply the new settings.<\/p>\n\n\n\n
You know, I absolutely adore all the disclaimers, intros, branding videos and more that I just can’t skip. I really do.<\/p>\n\n\n\n
I then get back in, and hit benchmark; I get that classic interactive loading screen where you can run around, so I do. It’s smooth, and looks decent enough. I don’t expect a big engine improvement over Valhalla; I figure that part has gone pretty much untouched.<\/p>\n\n\n\n
Anyway, after a few seconds of running, the loading screen fades. It’s time to see what FPS I get..<\/p>\n\n\n\n
..And straight to the desktop it goes!<\/p>\n\n\n\n
I figure.. Ok, must be a fluke. I try again: No luck. Same CTD, same place.<\/p>\n\n\n\n
I update GPU drivers. Reboot. Try again.<\/p>\n\n\n\n
CTD.<\/p>\n\n\n\n
Verify game files. Try again.<\/p>\n\n\n\n
CTD.<\/p>\n\n\n\n
I am almost – ALMOST – to the point of requesting a refund and saying “fuck it”.<\/p>\n\n\n\n
I understand the difficulty in QA; I’ve worked in code for more than half of my life now, doing web, app, game, and software dev at various points in my life.<\/p>\n\n\n\n