Update 14.02

[CMDR The Riz]

It's ofcourse the end of the world that a game goes down for a few hours when delivering an update.

This forum keeps amusing me no end, or should that be bemusing me..

If everyone thinks this was bad, y'all should have seen what happened to Destiny 2 last week...

 

[[VR] Mad Mike]

I didn't have long but was dissapointed that the instance i dropped into was stalled.

 

[CMDR Karrde Sun]

At this point it's hard not to conclude that the current batch of devs have no historical understanding of code written before they were put on ED and have no interest in correcting someone else's mistake. They likely don't know where the errors occurred and haven't got a clue on where to look.

The botched thrusters are a prime example.

I'll happily "mea culpa" when/if I'm provem wrong...

Fixes making into the patch notes and not into the build is a curious one. Would it be that hard to update to the release build and check the changes from your ticket are still committed? Hmmm maybe whoever checks in last is the winner. See the point is from working at startups to multinational fortune 500's... walking up to someones desk to double check still works. Maybe they aren't allowed to do that either?

Doesn't matter how experienced you are at coding or your codebase if you care, or are allowed to care. Just saying.

 

[Markov Chaney]

I apologise for posting something actually positive about this release, but... is it me or have frame rates picked up quite a bit even in Horizons? Landing seems like a much less laggy experience now...

 

[Rat Catcher]

and no update on the AMD planetary rendering issue

True, it is absolutely DISGUSTING!!!
I'd have thought that AMD would have sorted their drivers by now...

ETA: But, if you have a 6000 series AMD card, you can still use 22.5.1 which was the last version before AMD broke the drivers...
Or, like me, have a 7900 XTX, have EDO working in pancake, but issues in VR.

 

[[VR] Mad Mike]

True, it is absolutely DISGUSTING!!!
I'd have thought that AMD would have sorted their drivers by now...

ETA: But, if you have a 6000 series AMD card, you can still use 22.5.1 which was the last version before AMD broke the drivers...
Or, like me, have a 7900 XTX, have EDO working in pancake, but issues in VR.

I have no idea who is at fault there.... and my gut feeling is probably AMD too.... but it may not be.

hypothetically if drivers 22.5.1 and older actually implemented a feature in a way which was not within spec of the DX / Vulcan or what ever (DX11 in this case) standards but FD based a feature in their software which made use of the poorly implemented AMD kludge..... then I can see an awkward scenario where AMD making their drivers work properly could cause issues.

I am not completely talking out of my exhaust here either as something similar did actually happen with nvidia and an emulator i use.............. nvidia actually fixed their driver to act correctly, which proceeded to break the emulator for a number of releases................... ultimately the emulator did have to update.

 

[Rat Catcher]

I have no idea who is at fault there.... and my gut feeling is probably AMD too.... but it may not be.

As the issue only appears to affect AMD cards of a single generation (6000 series) and appeared following a DX11 makeover from AMD (with gains in both DX11 & OpenGL performance) and previous generations showing no issue (and newest only in VR) it does suggest very strongly that AMD have changed something that was fine in previous driver releases.

But, I know nothing, of course, and just concluded that when an issue is quite so selective on what it affects, that Frontier may not be responsible.

 

[ferus]

True, it is absolutely DISGUSTING!!!
I'd have thought that AMD would have sorted their drivers by now...

ETA: But, if you have a 6000 series AMD card, you can still use 22.5.1 which was the last version before AMD broke the drivers...
Or, like me, have a 7900 XTX, have EDO working in pancake, but issues in VR.

Is this the same issue morbad has a thread on?
I thought this was already fixed by AMD. I am currently running on 22.11.2 and have no problems in Ody.

 

[CMDR Karrde Sun]

Is that gamma setting new?

THANKS!!!!

I'll take it. Half a really important item off the list. Now if only they could rewrite the oddyssey renderer to not bake planets into the skybox.

Also.. they said something about some armstrong moment at some point. I can't believe they left that as star trek teleporting.. yet UPGRADED the srv armstrong experience.. it is far more detailed than in horizons. Wow.

Yeah im happy atm (i dont even care that interiors are super bright now, my space is back enough).

 

[Rat Catcher]

Is this the same issue morbad has a thread on?
I thought this was already fixed by AMD. I am currently running on 22.11.2 and have no problems in Ody.

I assume so. (and @Morbad fixed it for my 6900 XT too!)

The fix doesn't work for VR - but then, the latest (23.1.2) on the 7000 series still has the issue in VR for me, but not in pancake.
Post 22.5.1 drivers also had issues in a few other games - so it wasn't as if EDO was exclusively affected.

 

[Flimley]

I'm not interested in "the war" one single bit. Frontier seems to have found something that sticks and are going with it full potato.
I feel as though this game is moving away from my interest these days.
I don't hold very much hope for any other part of the game anymore.

Flimley