Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on User talk:Garrett

Downsampling and downscaling.

11
RaTcHeT302 (talkcontribs)

Do you know whenever they are the same thing? Also could this stuff be incorporated somewhere such as the Borderless thingy? http://pcgamingwiki.com/wiki/Downsampling

I wanted to use GeDoSaTo but I didn't understand why it wasn't working for me, so I made a simple guide instead.

Garrett (talkcontribs)

I don't think this counts as a distinct feature. The Nvidia/AMD Super Resolution feature works the same as a real display with that resolution. GeDoSaTo is useful for more advanced features or bypassing resolution limits.

I have previously covered this on the forums: Dynamic Super Resolution / Downsampling.

RaTcHeT302 (talkcontribs)

I don't really understand what you are referring to in that post, so that's not of much use to me. I know you can create custom resolutions on Nvidia cards, but I don't have access to this whole DSR thing, I think I'll just document the custom resolution method instead as that's the only thing I can test myself.

RaTcHeT302 (talkcontribs)

Nevermind I do have DSR, I was looking at the wrong menu.

Anonymous (talkcontribs)

When it comes to downscaling, NVIDIA/AMD's solution works similarly to GeDoSaTo, except NVIDIA/AMD are able to do it on the driver level as opposed to a purely software level. To quote the author of GeDoSaTo:

However, the largest advantages of a driver-based method are the following:
  • Compatibility - since you can act after the 3D API, and not on its level, you get compatibility with any API, including all versions of DirectX and OpenGL.
  • Input Independence – a lot of the hard parts both in writing GeDoSaTo and in configuring it come with making mouse input work, since the OS knows it’s actually running at resolution X while the game thinks it’s running at Y. When operating on the driver level, OS and applications will be on the same page again, removing a major source of issues and need for implementation work.
These are things which are far harder to achieve in GeDoSaTo, and will likely never be possible on the same level.

While I don't believe a guide is really needed, I do believe a glossary entry would be useful.

RaTcHeT302 (talkcontribs)

I really do not honestly care about all these things right now as I would've asked otherwise, I just wanted to know the main differences between the two terms, so that I could redirect the Downscaling to the Downsampling page. I didn't create the Downsampling page with the Glossary attachment as I also didn't know if the Glossary pages work any differently compared to the usual wiki articles, or if someone else has to specifically make such pages.

I've made a small guide for GeDoSaTo seeing as I've had issues setting it up, but I quickly figured out what I was doing wrong, which to some might not be so obvious. I usually create such sub guides when less than obvious steps have to be taken in order to ensure that everything works.

Anonymous (talkcontribs)

I was attempting to respond to Garrett's assertion; apologies for the confusion. :(

To actually answer your question, RaTcHeT302, downsampling is taking an image at a given resolution and, using some kind of image filter, converting it to a lower resolution. Downscaling is intentionally rendering a 3D scene at a higher resolution than the current monitor resolution, downsampling the generated frames to the current resolution, then displaying them. Put another way, downscaling is the reverse of upscaling. The difference is that downsampling can be done on more than 3D scenes (downslampling is what's typically used whenever a game renders textures at half-resolution, quarter-resolution, etc.), while downscaling specifically deals with how a 3D scene is rendered by the graphics card. Thus downsampling and downscaling are actually different, despite the latter using the former during its normal operation.

Also, I don't know if glossary pages are functionally different from wiki articles, so you'd have to ask someone like soeb or Garrett for that.

RaTcHeT302 (talkcontribs)

I got confused because of the lines next to the boxes so it's okay, I thought that answer was for me at first. I wish there was a better system for this stuff as things get a bit confusing. I'm also going to blame my lack of sleep too so it's my fault.

Garrett (talkcontribs)

I see I somehow lost the mention of terminology while rewriting before I posted. Expack3's response covers some of the technical specifics, but you'll often see sites use the two terms interchangeably to refer to the same method. Both Nvidia and AMD seem to only use "downsampling" to describe Super Resolution.

The Glossary: namespace has no special behaviour. The main purpose of the additional namespaces was to move non-game pages out of the main namespace.

RaTcHeT302 (talkcontribs)

I moved it to the namespace if that's fine, thanks.

Mirh (talkcontribs)

Referring back to my previous explanation of the difference between supersampling and downsampling here...
...and after reading some wikipedia stuff

I believe the only difference between the two terms is that sampling can be referred to both the whole image and individual pixels (preferably), whilst scaling is just linked to the former.

And please, take note that if downsampling is more or less equal to downscaling, so is upsampling with upscaling.
Which is not the same thing of supersampling/oversampling then