Death end re;Quest 2

Death end re;Quest 2

View Stats:
Syous Aug 18, 2020 @ 8:03am
Performance?
Last game's performance wasn't that good on PC. How is it on this second iteration? Any info about that?
< >
Showing 1-15 of 23 comments
My1 Aug 18, 2020 @ 10:25am 
well how? the game hasnt released so nobody really can play
Syous Aug 18, 2020 @ 10:42am 
Beta testers, maybe?
Last edited by Syous; Aug 18, 2020 @ 10:43am
My1 Aug 18, 2020 @ 10:45am 
are you aware that IFI generally has betatesters agree to an NDA (a contract stating you may not say anything about the beta) when signing up for a beta test?
AI Sin || SinNoAria Aug 18, 2020 @ 10:45am 
Reviewers/Beta testers breaking NDA aside, what are the chances of them answering your question at this point? That said, game releases soon so people will probably be able to answer the question a bit after that.
Syous Aug 18, 2020 @ 11:08am 
I see, that's unfortunate. Fortunately the game is out now, hopefully someone could give us some info about that!
Link Aug 18, 2020 @ 11:11am 
The game's out - so my NDA is expired by now. The game's performance didn't seem too different from Der;Q 1 to me. So, if your PC ran Der;Q 1 fine - you shouldn't have issues.
patyos Aug 18, 2020 @ 11:43am 
Should run fine constantly at 60fps+ like DERQ1

Unless you have a low tier PC

If you meet the Recomended specs listed on store page you should be fine.
Last edited by patyos; Aug 18, 2020 @ 11:47am
KingKrouch Aug 18, 2020 @ 12:39pm 
From what I've seen, it's in line with how the forest area where you find Lucil performs in the first game.

Getting around 45-50FPS on an RX 5700 and Ryzen 7 2700X.

Also, I just released a patch to uncap the framerate:

https://steamcommunity.com/app/1266220/discussions/0/4907188445924781130/
Gregory Aug 18, 2020 @ 1:27pm 
Originally posted by patyos:
Should run fine constantly at 60fps+ like DERQ1

Unless you have a low tier PC

If you meet the Recomended specs listed on store page you should be fine.


I'm blowing the recommended specs for fun here with a 2060, and DERQ1 at just 1080p60 drove that GPU to 40% constant usage, for these graphics.A 1060 then should be near 80% usage at 1080p60 for this joke.Pathetic optimization and why i refunded.
Last edited by Gregory; Aug 18, 2020 @ 3:01pm
Kvik Aug 18, 2020 @ 2:55pm 
Does anyone have any impressions of resolution support? The last entry has the internal resolution locked to 1080p
KingKrouch Aug 18, 2020 @ 3:08pm 
Originally posted by Kvik:
Does anyone have any impressions of resolution support? The last entry has the internal resolution locked to 1080p


Every option aside from the 4K native option is still upscaled from 1080p. Performance is the same between 4K Native and 1080p from my testing.

The game has some optimization issues, but I'm at least glad that they added better keyboard binding support.
Zankro Aug 18, 2020 @ 3:11pm 
So, i´m the only one who has heavy FPS Drops in the City ?
Like from 60 to 35 ish ?

Ryzen 2600 with a 1070

Playing on Native 4K, can´t reduce the Resolution on Fullscreen
Othoric Aug 18, 2020 @ 4:34pm 
Does anyone know how to enable 4K native WITHOUT having to set DSR in Nvidia Control Panel and then changing the OS resolution to 4K?
I'm running fine at 1600x900. No significant issues yet even while streaming.
KingKrouch Aug 18, 2020 @ 5:02pm 
Originally posted by Othoric:
Does anyone know how to enable 4K native WITHOUT having to set DSR in Nvidia Control Panel and then changing the OS resolution to 4K?

Sadly not.

Honestly, the whole 4K Native option should be replaced with every resolution running at the resolution that they are advertising, alongside a resolution percentage that goes from 25-200% that upscales/downscales from that. That, and those presets should be replaced with an array of every fullscreen resolution supported by the GPU/display anyways.

Attempting to run in fullscreen mode on 5120x2160 or 3440x1440 causes the image to be stretched.

It's especially interesting as a majority of post-processing effects only run at a quarter of 1080p (from my time analyzing shaders and render targets inside of Special K), so it results in a really muddy looking image.
< >
Showing 1-15 of 23 comments
Per page: 1530 50