@hahatmo>"Also did you ever work in IT? Some fixes need time. Especially when it's a bug causing undesired behavior and not just a balance change."
I work in IT and thankful that EA didn't deploy anything on/before the weekend. The devs likely knew about the issue on Thursday, the smart ones asked themselves "We can either deploy a patch Friday, risk breaking Apex for everyone and end up working the whole weekend or do you want to wait until next week?"
The most likely timeframe would look like: Monday find/fix the issue, Tuesday for regression testing, Wednesday to prep all the deployment pipelines, Thursday to "Release the hounds!"
@ToastyCeral Exactly. Never deploy on Friday. Especially when there is another huge update already sheduled for Tuesday next week. Makes just no sense. I just hate to see the sentiment towards the devs in some comments. Also people don't even get that it's not EA working on Apex. People are so out of touch sometimes. I am glad I am not working directly in that field. GabeN put it well on a HL3 release. You can suck the consumers pipi and they still will bit** about stuff.
Somewhat more transparency would be nice tho, Maybe a trelllo board bug tracker which is linked to some (probably Jira?) tickets.
@hahatmoI'll test with Fortnite on win7 unpatched to see if the EAC also throws anything without the last windows 7 patch.
may take a while 23 gb to go. anyone got an updated fortnite on win7 they can test with?
@omegaamoeba btw i figured out a fix today for my issues. If anyone has random crashes midgame without an error. Try to disable XMP. It didnt work the first time i tried it but today I was able to play 3 hours without a crash. Its definitely not a longterm solution but it works so far.
nice work
well at least the error in apex is more forthcoming in it's information this is the error in fortnite for EAC
