Maybe if we post in Michael Brooke's pet thread?
Michael Brooks has a pet thread? What kind of pet?
Maybe if we post in Michael Brooke's pet thread?
I love and play this game like no other, over 18 weeks played according to the in game stats. Yesterday I looked at the PC and just couldn't bring myself to turn it on.
When I saw that the patch notes started with "- Fix for crash when dropping from orbit at Eafots LZ-H b10-0 D 1" I raced back out there only to find that the mising assets are still not in game. Was I jumping the gun, should I have waited for a patch note of "- Formidine Rift assets now in game"? I thought I was already being very patient waiting for an extra PVP centric beta to conclude before the fix went in.
The things I've been contimplating doing are staying parked on the planet waiting for the fix to be fixed, driving the SRV around the planet while using the bugged scanner, flying back to the bubble and taking part in the Ancient Ruin mission that sound like it's bugged, or spending even more hours jumping around the Maia area hoping to get 'hyperdicted' by aliens. None of these things interest me enough to start the game.
Come on FD, you can do better than this!
Michael Brooks has a pet thread? What kind of pet?
Maybe if we post in Michael Brooke's pet thread?
I used to have lots of patience and slack for them but they're taking the now.
I've been playing Witcher 3
I assume you mean the Canonn thread? Done.
sometimes i wonder ... why this thread is not sticky like the important ones ?
Yeah, I agree. I've worked in IT for a long time and am inclined to cut FDev a lot of slack, but the key to damage control in situations like this is frequent communication. Even Drew can't get answers out of them on something that is a major piece of content.
When Drew posted yesterday it just reinforced the horrible feeling that the whole thing was completely overlooked during beta.
Yeah, that's my fear....probably not a quick and easy fix. My complaint, though, is that FD should just say that and we can then make an informed decision as to whether to stay or go do something else.
The problem is, that it certainly seemed easy to fix. There was a typo in the code of a game asset that was being referenced, which was in the logfile of several cmdrs who encountered the CTD initially in December. This was documented in the bug report thread for the issue.
I am at this point without any reason whatsoever to believe that the Rift mystery has probably been bugged since launch and undiscoverable.
the usual 'facepalm meme' should be added here.
but i am too much tired and bored to do it.
My original CTD was near -8/-139.