- Joined
- Nov 11, 2016
- Messages
- 3,072 (1.13/day)
System Name | The de-ploughminator Mk-II |
---|---|
Processor | i7 13700KF |
Motherboard | MSI Z790 Carbon |
Cooling | ID-Cooling SE-226-XT + Phanteks T30 |
Memory | 2x16GB G.Skill DDR5 7200Cas34 |
Video Card(s) | Asus RTX4090 TUF |
Storage | Kingston KC3000 2TB NVME |
Display(s) | LG OLED CX48" |
Case | Corsair 5000D Air |
Power Supply | Corsair HX850 |
Mouse | Razor Viper Ultimate |
Keyboard | Corsair K75 |
Software | win11 |
DLSS has access to the raw imagery earlier than FSR, so it can 'reconstruct' data that would have been thrown out by the time FSR sees it
Like uhhh.... seeing the data for a fence *before* a motion blur effect is added, instead of after: more to work with, so a slightly better image
Actually DLSS uses something called camera jitter, which Intel copied with their XeSS, to reconstruct pixel-wide objects that even 4K Native resolution would flicker
Here is an example in CP2077