EDO needs new graphic engine, the old one got pimped to the max already.
Any more "boost" will only explode the "engine block" and these FSR tricks are kind of nitrous injection - it works, but only as temporary solution.
State of the Game
- Thread starter Fuglydog53
- Start date
Any more "boost" will only explode the "engine block" and these FSR tricks are kind of nitrous injection - it works, but only as temporary solution.
I did wonder at some point (if FD ever did a XBSX port) I'd ditch the PC, buy an XBSX and 'hire' a PC via the Edge browser.
But that level of crazy takes me back to when I had a PS3 which I had Linux on running Windows 95 under emulation on. Because.
But that level of crazy takes me back to when I had a PS3 which I had Linux on running Windows 95 under emulation on. Because.
Now, I just read an article about FSR what makes me an expert.
And I know now, why ED won't ever have image quality that FSR is theoretically able to achieve.
The answer is in the first block.
AA is broken in ED, and visual artifacts become inherited to every step of "magic" that is made afterwards.
www.tomshardware.com
And I know now, why ED won't ever have image quality that FSR is theoretically able to achieve.
The answer is in the first block.
AA is broken in ED, and visual artifacts become inherited to every step of "magic" that is made afterwards.
What Is AMD FSR? FidelityFX Super Resolution Explained
A basic definition of AMD FSR
well, hopefully your optimism in fdev's 180 on prioritizing development going for quality work and not cheapest work proves true.
i'm still 50/50 on fdev deciding to sunset the game without ever releasing on consoles and just wiping their hands of it all and moving on with jwe2 and warhammer and other titles that are more lucrative, less involving and have a far less critical playerbase with 7 years of baggage from undelivered promises.
i'm still 50/50 on fdev deciding to sunset the game without ever releasing on consoles and just wiping their hands of it all and moving on with jwe2 and warhammer and other titles that are more lucrative, less involving and have a far less critical playerbase with 7 years of baggage from undelivered promises.
Have you played where's Jaques yet?
State of the Game
Don't forget the Jester's revolution of 1929. It is commonly thought to be a major trigger for economic uncertainty around the time. Smithers, why didn't you tell me about this market crash?!
forums.frontier.co.uk
** looks to rest of thread **
That should keep him busy for a bit
When people ask where update 7 is...
I salted my favourite enemy's porridge. They said it was nice. Dammit.It's the salting your favorite enemy's soup that makes it fun. Like,....
....Alright, time to put on the reggae again
Oh, and I have noticed something odd.
Those are allegedly default "scaling factors" of FSR.
AFAIR factors in config file that are set when you choose quality in menu are nothing like they should be according to this values.
For Ultra Quality should be 0.769 (1/1.3) in EDO it's 0.71
For Quality should be 0.666 (1/1.5) in EDO it'S 0.6x
There was 0.51 for some setting too.
I don't remember exactly, I am only sure that I had to enter them manually when I wanted to test 1.33 / 1.5 rates, because values in config were totally bizarre.
Now, I suspect FSR will work with any scaling factor, but the best results we can get by are "adding" +20%, +25%, +33%, +50% +100% to picture dimensions - what fits pre set Nvidia DSR hardware supersampled resolutions that follow this exact logic.
Scaling factors in EDO config look like someone just entered some values randomly with some "improvised" stepping, they make no sense.
What inevitably triggers more scaling artifacts, because rounding etc.
Those are allegedly default "scaling factors" of FSR.
AFAIR factors in config file that are set when you choose quality in menu are nothing like they should be according to this values.
For Ultra Quality should be 0.769 (1/1.3) in EDO it's 0.71
For Quality should be 0.666 (1/1.5) in EDO it'S 0.6x
There was 0.51 for some setting too.
I don't remember exactly, I am only sure that I had to enter them manually when I wanted to test 1.33 / 1.5 rates, because values in config were totally bizarre.
Now, I suspect FSR will work with any scaling factor, but the best results we can get by are "adding" +20%, +25%, +33%, +50% +100% to picture dimensions - what fits pre set Nvidia DSR hardware supersampled resolutions that follow this exact logic.
Scaling factors in EDO config look like someone just entered some values randomly with some "improvised" stepping, they make no sense.
What inevitably triggers more scaling artifacts, because rounding etc.
Last edited:
Which is why I don't do BGS. At all.
![[Diplomacy] Carnegie](https://forums-cdn.zaonce.net/data/avatars/m/123/123809.jpg?1553527149){kind=avatar}
This is where it all gets silly.
I just wanna be able to load a game on my mid-range system (2080GTX), select 'High' preset and have it run at 60 FPS. All this faffing around with a zillion options trying to squeeze extra performance out of it drives me nuts. I did all that malarkey with MS FS2004 and I'm completely over it now.
Call me when EDO doesn't require a PhD to set up.
Needs more salt, then.
So tell me: How many holes DOES it take to fill it? I've been wondering about that for decades!
Indeed. I'd clearly forgotton the Tao of Blam!Needs more salt, then.
I did ask, and was told it would blow my mind (out in a car).
Not too worried about that as far as my mind's concerned. They'd have to locate the vestigial remains of it first.
hrm.. in regards to 6.01.. i'm very surprised they didn't make "hold e to loot" not an option. but instead just reverted it.
They thought enough people wanted it to implement it in the first place. I dont get that kind of development process... was the request for it not real?
They thought enough people wanted it to implement it in the first place. I dont get that kind of development process... was the request for it not real?
I read the news today, oh boy. 4,000 holes. Assuming they are rather small and from Blackburn, Lancashire.
Last edited: