Can you still access your energy saving settings and services for example?7950 downsampled to 2560x1440 @ W8 with no problem at all here, though I had to disable UAC
Can you still access your energy saving settings and services for example?7950 downsampled to 2560x1440 @ W8 with no problem at all here, though I had to disable UAC
so i can do it on my 1080p monitor? Doesn't have to be 1440p?The downsampling happens because your monitor can't display that resolution, so it scales it to 1920x1080, theoretically reducing the size of any artifacts.
This is less "expensive" because it's your monitor that does the scaling in this case, not any of the hardware.How is this different from the Supersampling AA option? That also renders at a higher res and scales down.
It's as hardware intensive as conventional SSAA. The game is rendered at the higher resolution and downsampled by the monitor (essentially a form of ordered grid super sampling). It's just compatible with more games (in theory).This is less "expensive" because it's your monitor that does the scaling in this case, not any of the hardware.
Moot point anyways, the original tool doesn't work with the latest drivers, workaround or not.
Really? I've always had much better performance with downsampling than super-sampling at the equivalent rate. Sure there's no difference? (Disclaimer: I have absolutely no idea what the technicalities are behind it, just going from first-hand experience)It's as hardware intensive as conventional SSAA. The game is rendered at the higher resolution and downsampled by the monitor (essentially a form of ordered grid super sampling). It's just compatible with more games (in theory).
There are some optimizations with modern implementations of SSAA (and even more with SGSSAA), but 2xSSAA is roughly equivalent to twice the horizontal and vertical resolution. That's similar to the jump from 1080p to a 4k resolution. The main difference is that the monitor is doing the pixel blending with downsampling.Really? I've always had much better performance with downsampling than super-sampling at the equivalent rate. Sure there's no difference? (Disclaimer: I have absolutely no idea what the technicalities are behind it, just going from first-hand experience)
so i can do it on my 1080p monitor? Doesn't have to be 1440p?
Full Scene Anti Aliasing was a marketing term that 3dfx used for their version of SSAA. (which was accumulation buffer based SSAA.)Is there a difference between FSAA and SSAA? Or is it two different names for the same thing?
Fixed it for you..There are some optimizations with modern implementations of SSAA (and even more with SGSSAA), but 4xSSAA is roughly equivalent to twice the horizontal and vertical resolution. That's similar to the jump from 1080p to a 4k resolution. The main difference is that the monitor is doing the pixel blending with downsampling.
SSAA does not work with every game. This did... Yah did..... :'(How is this different from the Supersampling AA option? That also renders at a higher res and scales down.
Ahhh.... that explains why I've always had better performance with downsampling over SSAA. I was effectively running at 1.333 SSAA as I was downsampling from 1440p to 1080p.Fixed it for you..
2xSSAA would be equivalent to 1.5x horizontal and vertical or 2x in one direction.
Calulate using total amount of pixels as the NxSSAA is about samples per pixel.Ahhh.... that explains why I've always had better performance with downsampling over SSAA. I was effectively running at 1.333 SSAA as I was downsampling from 1440p to 1080p.
Yes, it's valid value.Is that a valid value for SSAA or is it only positive integers?
I made a video of some pretty bad display corruption I get when using AMD Downsampling on my TV. Could someone in the know explain why I'm seeing this? Basically there's tiny black dots flashing everywhere.
http://youtu.be/p9hLQ5gd9hU
The hex editing is too complicated. I have numerous reg entries and none of them are specificed by the listed categories in question
In the Registry Editor window -> Edit -> Find 'ModeTimingOverrides'
Right click 'ModeTimingOverrides<stuff>' -> Modify
In here look for your native resolution @ what you're going up to
Then go down the list in order, the first is for example
'Width
80 07 to 00 0A'
So find the first instance of 80 (should be on the first line), double click it, and type 00. Then double click 07 and type 0a. Etc
Are those numbers for 1440p?
Hmmmm doesn't work for me. I get an error that says Windoes could not change your display to this resolution. Try a different resolution.
So roughly translating the forum, the guy said for windows 8 I need a modified monitor driver? He said something about running it with the disabled driver signature.
I now have a 2560x1440 monitor, let's see how much I can squeeze out of this.
That error is because you need to uncheck the box under Monitor Settings to "Hide modes that this monitor cannot display".
Otherwise you'll get this error
You can check the OP for a more complete explanation.
Can you post your settings when you're done please?
AMD DOWNSAMPLING LIVES
AdapterIndex 0
DisplayIndex 10
TimingStandard 1
PossibleStandard 14
RefreshRate 120
Width 1920
Height 1081
TimingFlags 0
HTotal 0
HDisplay 0
HSyncStart 0
HSyncWidth 0
VTotal 0
VDisplay 0
VSyncStart 0
VSyncWidth 0
PixelClock 0
HOverscanRight 0
HOverscanLeft 0
VOverscanBottom 0
VOverscanTop 0
When I try to run the Create_Custom_Resolution.bat file after modifying the CustomResolution.txt file, I get:
ERROR: ADL_Display_ModeTimingOverride_Set() failed!
Am I doing something wrong?
Here is what I have in my CustomResolution.txt
When I try to run the Create_Custom_Resolution.bat file after modifying the CustomResolution.txt file, I get:
ERROR: ADL_Display_ModeTimingOverride_Set() failed!
Am I doing something wrong?
Here is what I have in my CustomResolution.txt
AMD DOWNSAMPLING LIVES
(testing on 13.11 beta1)
Ok, so it looks like it had something to do with me setting the refresh rate to 120 instead of 60 (I have a 120hz monitor). So while I was able to set a custom 1440p resolution, it is only at 60hz. Haven't been able to figure out how to get it to 120hz.