Any updates on anti-aliasing work?

I wonder if it was one of the reasons the console port was canned, building a new aliasing system doesnt sound like small work and would require more grunt even after all their work on optimising.
 
Temporal AA may not be suitable for Elite as it may make a mess of orbit lines.

The orbit lines are already a mess, especially on AMD hardware.

There are other games that seem to handle thin lines along with fairly agressive TAA at least as well as Odyssey does without it. Still, moving the orbit lines to a after the TAA pass and using a good AA method just for lines should be doable.
 
nVidia just launched DLAA... at least this would be a potential solution if Frontier ever decide to implement it. Together with DLSS it might be a way out for this "(unspeakable word)"...
 
Only way to "fix it" for me is enabling DLDSR at 2.25x on Gforce CP...
This seemed like a suggestion to try out. I opened GeForce CP and selected the option to add programs-specific features. I added Elite Dangerous Executable from the programs list that came up & the GF CP promptly crashed. Now it crashes whenever I open it, meaning I cannot undo the addition of Elite that crashed it in the first place. Any suggestions?

EDIT: Turns out if I am really quick I can select another page before the app crashes. Relaunching the app opens on the newly selected page so no crash. Apparently adding EDO to the GF CPs "Manage 3D Settings" page is what causes the crash, but if selected the page does not stay open long enough to remove the offending entry in the programs list.
 
Last edited:
This seemed like a suggestion to try out. I opened GeForce CP and selected the option to add programs-specific features. I added Elite Dangerous Executable from the programs list that came up & the GF CP promptly crashed. Now it crashes whenever I open it, meaning I cannot undo the addition of Elite that crashed it in the first place. Any suggestions?

EDIT: Turns out if I am really quick I can select another page before the app crashes. Relaunching the app opens on the newly selected page so no crash. Apparently adding EDO to the GF CPs "Manage 3D Settings" page is what causes the crash, but if selected the page does not stay open long enough to remove the offending entry in the programs list.


NVIDIA Profile Inspector will let you adjust most settings the control panel can and quite a few the control panel cannot. You can browse to the Elite: Dangerous profile and reset it to see if that makes NVIDIA's control panel work again.

That said, this shouldn't happen at all, and I'd suggest making sure your VC++ runtimes are updated then repair/reinstall the NVIDIA control panel via the Windows Store (assuming you're using the DCH drivers which are currently the only supported ones for Win 10 and up).
 
@Morbad -- Thanks, resetting in nPI undid whatever the problem was. I will check the other things you mentioned but as I keep things updated whenever notified I would be surprised if that is the source of the problem.
 
Last edited:
Looking at AMDS forthcoming FSR version 2.0, i wonder if frontier will implement that into the game to upgrade from version 1.0. That may get rid of some of the issues with jaggies as its features some kind of temporal solution
 
iu
agreed, I always preferred Thunderbird
 
I presume it was forgotten... just like pinning engineers blueprints that was promised in U8 🤷‍♂️
But at least we have a fresh batch of bugs with each update.
 
This is the primary reason I stopped playing last year. I built a new PC with an RX 6900XT for ED, and I've enjoyed everything except ED on it. The broken orbit lines are too much for my mildly OCD brain to handle.
 
After playing Horizon's since the end of May last year, I finally bought and downloaded Odysee last night. After my morning work 1 hour play session completing the on foot tutorial mission and then looking around my home space station on foot, there was just one serious gripe I have about the game. This is in the context of a generally positive impression so far.
I did a search on the forum in relation to my issue, since there's no way no one else has not noticed this, and I landed here.

Aliasing​


This game can't draw anything that isn't a vertical or horizontal line properly. It's hugely distracting, especially when orbit lines are switch on on the HUD and you are supercruising around a system. The inside of the space station is a high quality textured mess due to the aliasing. This is at 1680 x 1050 resolution and high texture settings which is running fine on a modest 4GB VRAM graphics card. Not walked on any planets yet, so the jury is still out on the settings I will need to settle on for all play situations.
This needs fixing. I might need to consider playing in Horizons unless I want to do something on foot until this is addressed.
 
Nice fairy lights:
fRti0oz.jpg


A hot mess:
1rEY8Ve.jpg

Worse, the checkered effect light glow kind of dances around a twinkles as squares as the ship pitches and rolls in flight.
It's so distracting I'll have to remove the fairy lights (recent CG reward) when flying in Odysee.
 
Nice fairy lights:
fRti0oz.jpg


A hot mess:
1rEY8Ve.jpg

Worse, the checkered effect light glow kind of dances around a twinkles as squares as the ship pitches and rolls in flight.
It's so distracting I'll have to remove the fairy lights (recent CG reward) when flying in Odysee.
These seem to tint to red on the right hand side, too... Lighting effects / lens flares are very much messed up in Oddyssey right now. The pylons at the Guardian ruins for instance do not emit a pillar of light when activated, contrary to Horizons.

There's a similar issue to the cockpit cosmetics currently being discussed in the forum it seems - with plasma accelerators: https://forums.frontier.co.uk/threa...ted-in-odyssey-any-ideas.601202/#post-9785009
 
Worse, the checkered effect light glow kind of dances around a twinkles as squares as the ship pitches and rolls in flight.
It's so distracting I'll have to remove the fairy lights (recent CG reward) when flying in Odysee.
IIRC changing Bloom should fix that (try some of the other values). It also looks like you have FSR enabled (it is now enabled by default for every graphical preset since U11).
 
Back
Top Bottom