• Breaking News

    Saturday, June 26, 2021

    Hardware support: Thanks to Windows 11, Scalpers Buy Out Add-on TPM 2.0 Modules

    Hardware support: Thanks to Windows 11, Scalpers Buy Out Add-on TPM 2.0 Modules


    Thanks to Windows 11, Scalpers Buy Out Add-on TPM 2.0 Modules

    Posted: 25 Jun 2021 05:02 PM PDT

    Clampdown On Crypto Mining Cuts China's GPU Prices Nearly 45 Percent

    Posted: 25 Jun 2021 06:04 PM PDT

    Hyperscalers such as Amazon, Google, and Microsoft pay less than 1/3 MSRP for Server CPUs, 64C AMD Milan processors for $2,000

    Posted: 25 Jun 2021 09:36 AM PDT

    All of this is from Patrick at ServeTheHome

    Cloud providers are paying less than 1/3

    https://youtu.be/b2bEoW6FcBA?t=366

    64 core processors are selling for like $2000ish, maybe less

    https://youtu.be/e96mboM155g?t=1407

    submitted by /u/dylan522p
    [link] [comments]

    More FSR / TAAU / DOF Testing with KingsHunt - Detailed IQ Testing with all FSR / TAAU levels

    Posted: 25 Jun 2021 11:20 PM PDT

    Hello, I made this post 2 days ago showing how Digital Foundries testing of KingsHunt was invalid.

    Alex did reply, but sadly he didn't actually update the article images to include fixed ones with DOF properly disabled, since it is disabled on his TAAU screenshots which makes the game look much better as depth of field, even when disabled in options, blurs out the character, especially the lace dress.

    I did make a mistake in my original post with the wrong scaling command for TAAU, which did make my resized TAAU incorrect (it was actually native rendering size) but the major bug being TAAU disables DOF was also validated when someone linked me to the developer of it on unreal forums: https://forums.unrealengine.com/t/gen-5-temporal-anti-aliasing/152107/5

    So big thank you to /u/TechTuts and /u/KeinZantezuken for that (and many others for their overall kind comments).

    Out of curiosity, will the new TAA upscaling behave well with depth of field? Currently when you set r.TemporalAA.Upsampling=1 , most of the DOF just disappears.

    So when r.TemporalAA.Upsampling=1, it basically forces r.DOF.Recombine.Quality=0 that looses the slight DOF convolution, and that is due to DiaphragmDOF.cpp's bSupportsSlightOutOfFocus. There needs to have some changes in the handling of the slight out of convolution (about 5pixels and below) when doing temporal upsampling that I didn't have time to come down to. And we were only using temporal upsampling on current gen consoles. Wasn't a big deal back then because if your frame would need to be temporally upsampled, that probably meant you didn't have the performance to run DOF's slight out of focus… However we exactly ran into this issue for our Lumen in the Land of Nanite demo running on PS5, but it is still prototype and I'm not sure whether I'm gonna have this finished by 4.26's release. But yeah given how temporal upsampling is going to become important, it's definitely something to fix very high on the priority list.

    So basically its expected bug because if someone was using upscaling, they don't want a perf hit from DOF, at least when initially designed.

    Here are all of the images in one album: https://imgur.com/a/2tfolwa

    All screenshots are @ 3440x1440 with max settings except motion blur disabled and DOF disabled (though in game option doesn't actually disable it as you'll see).

    Commands used:

    r.TemporalAA.Upsampling 1 -- Enable TAAU - This disables FSR as well

    r.DepthOfFieldQuality 0 -- Disable Depth of Field

    r.ScreenPercentage ### -- Set screen percentage. The game uses 77% for Ultra Quality, 67% for Quality, 58% for Balanced and 50% for Performance FSR modes (slider updates when you select). I used the same 4 + 100% for TAAU tests.

    Setting DOF "Enabled" DOF Force Disabled
    Native https://i.imgur.com/ojRTbjp.jpg https://i.imgur.com/Khwm8gC.jpg
    Ultra Quality FSR https://i.imgur.com/ZmrnQ2W.jpg https://i.imgur.com/w7erTwj.jpg
    Quality FSR https://i.imgur.com/mUkZsal.jpg https://i.imgur.com/7flMoJR.jpg
    Balanced FSR https://i.imgur.com/a2Ez5ua.jpg https://i.imgur.com/ngGSmJa.jpg
    Performance FSR https://i.imgur.com/uOzHtUI.jpg https://i.imgur.com/t5kBOOI.jpg
    TAAU 100% https://i.imgur.com/u0jEOsv.jpg https://i.imgur.com/CRdVSkM.jpg
    TAAU 77% (Ultra Quality) --- https://i.imgur.com/Zzhq66a.jpg
    TAAU 67% (Quality) --- https://i.imgur.com/TQEqhiR.jpg
    TAAU 58% (Balanced) --- https://i.imgur.com/5fFmHZB.jpg
    TAAU 50% (Performance) --- https://i.imgur.com/fRRscfe.jpg

    I didn't do all the TAAU w/DOF setting enabled since it doesn't make a difference when comparing 100% on vs off and would have just taken more time. As you can see there is no performance difference when disabling it vs disabling it for all other tests. I'd also bumped the mouse and had to re-position it and its slightly off for the last few TAAU tests and the bonus tests.

    And for a bonus I did renderScale 120 for FSR UQ and Native, I don't think it actually scaled properly but it did do the sharpening pass for FSR

    120% FSR UQ: https://i.imgur.com/u6pC45n.jpg

    120% Native: https://i.imgur.com/AIe7TYC.jpg

    From the performance being basically equal (it fluctuates few fps) I don't think the "UQ" part of FSR was applied at all, which would have scaled it down to 92% or so, so would want to test that in the future with a 100% FSR vs 100% Native as well. I'm glad games like DOTA are allowing users to pick the exact scaling values, excited to see more games integrate that, and hopefully a sharpening slider as well.

    Anyway, I hope this helps to clear up any misunderstandings from my first post. I had thrown in FSR / TAAU comparisons quickly but was mostly trying to point out that DOF was broken when TAAU was enabled. Unfortunately Digital Foundries while acknowledging that their testing was flawed, did not correct it, and even originally posted Godfall photos that were also flawed before people called them out on it on twitter. I hope Alex or someone else from Digital Foundries fully corrects the article with updated KingsHunt images and uploads a new video correcting it as well, DOF makes a massive difference in image quality in this game (no clue why the devs have the main character out of focus, their lace texture is ruined and it costs performance!).

    Another note regarding performance, that would need to be tested for longer, as there is quite a swing in fps while just standing still, the fire/wall effect on the left side of the screen is likely the cause as it is what is changing the most. So while FPS is displayed, it would need to be captured for a while and averaged out to really compare performance between any of the modes as it did swing +- 5-10fps or so.

    submitted by /u/badcookies
    [link] [comments]

    NVIDIA to launch A100 PCIe accelerator with 80GB HBM2e memory

    Posted: 25 Jun 2021 02:18 PM PDT

    Will Microsoft Pluton (security chip equivalent) be integrated in AMD Ryzen 6000 and Intel 12 Gen

    Posted: 25 Jun 2021 11:39 PM PDT

    https://www.anandtech.com/show/16269/microsoft-pluton-hardware-security-coming-to-our-cpus-amd-intel-qualcomm

    With the announcement of Windows 11, Microsoft has announced their commitment of doubling down on security by design. So will they encourage the chip makers to include the pluton security?

    submitted by /u/rocket5421
    [link] [comments]

    I made charts showing how much efficiency AMD GPUs and Nvidia GPUs have gained in 10 years.

    Posted: 26 Jun 2021 02:22 AM PDT

    submitted by /u/Vito_ponfe_Andariel
    [link] [comments]

    AMD Radeon RX 6600XT and RX 6600 with Navi 23 GPU appear in the drivers

    Posted: 25 Jun 2021 05:07 PM PDT

    [AnandTech] AMD EPYC Milan Review Part 2: Testing 8 to 64 Cores in a Production Platform

    Posted: 25 Jun 2021 07:23 AM PDT

    Tenstorrent Wormhole Analysis - A Scale Out Architecture for Machine Learning That Could Put Nvidia On Their Back Foot

    Posted: 25 Jun 2021 10:33 AM PDT

    "Lexar Announces Development of SD Express Memory Cards"

    Posted: 25 Jun 2021 02:09 PM PDT

    Comparison of typical high-end Nvidia cards for the past 10 years

    Posted: 25 Jun 2021 02:27 PM PDT

    Inspired by the post made by u/Vito_ponfe_Andariel, I decided to make my own visualization using slightly different data, so I'm sharing it now. Here are the decisions I made for this:

    • I decided to look only at GPUs that were available on the $500 to $700 range, since cards like the 2080 Ti and 3080 Ti have an entirely different value proposition that doesn't compare too well to lower price brackets. Thus, this is a comparison of what you can get on the <$700 segment.

    • Prices were adjusted to inflation for 2021.

    • I took the best version of some chips that were sort of "rebranded" with minor improvements, namely the 580 over 480, and 2080 Super over 2080.

    • For the RTX 3000 series I chose the $600 3070 Ti, because the $700 3080 is a heavily cut-down version of a larger chip (GA102), while the 3070 Ti is a full GA104 chip. While the 3080 is certainly a better product, the massive transistor count of the GA102 (a large part of which is disabled on the 3080) would have thrown off the transistor cost comparison causing an unrealistic, misleading result.

    • Power consumption and relative performance data comes from techpowerup.com reviews.

    So, here are the graphs:

    Million transistors per dollar

    Performance per dollar

    Performance per watt

    Data table

    So in the $500~$700 range, Ampere has been a substantial increase in performance/$ and transistors/$, but improvements in performance/watt have stagnated compared to the massive jumps that Maxwell and Pascal brought.


    Edit: And just for the sake of curiosity, though I don't think this means much, here is a "relative performance per transistor" chart.

    submitted by /u/sociableewe
    [link] [comments]

    Semiconductor Engineering: "Rocky Road To Designing Chips In The Cloud"

    Posted: 25 Jun 2021 03:44 PM PDT

    Micro Center Slams AMD GPUs, CEO Issues Apology

    Posted: 26 Jun 2021 02:37 AM PDT

    The amount of hoops I had to jump through to be Windows 11 compatible on my 4 year old totally hardware compatible system is ridiculous, and something I can't imagine 95% of users will have the patients to do.

    Posted: 26 Jun 2021 02:38 AM PDT

    Maybe this will help some people out that also previously upgraded from Windows 7 to 10, and save them a few hours of research when trying to get Windows 11.

    You might have less trouble than I ran into if you have a clean Windows 10 install with UEFI set up properly in BIOS with Legacy boot disabled.

    My specs: 8600k with an Asrockz370m pro4 motherboard build in 2017.

    Main problem was that my original Windows 7 OS was installed using Legacy boot mode, and not UEFI.

    Tried following this guide from the AMD reddit regarding getting things compatible on the software/firmware side.

    Finding IPT to turn on wasn't too difficult, but knowing that I also had to set the default keys was something I didn't figure out until I did another 10-20 minutes of research and trouble shooting with half a dozen reboots. No idea what any of these settings did, so I was overly careful.

    Getting "Security Processor" to show up under Device Security wasn't too difficult, but that's where it gets fun.

    I couldn't find the setting to force UEFI in my BIOS at first, but later realized what I really needed to do was disable Compatibility Support Module (CSM), which I believe does the same thing. It's frustrating when all motherboard vendors use different names for the same settings. Disabling CSM just results in more problems, though. If your OS was installed using the MBR instead GPT of method you'll just end up in an endless boot loop. When I disabled CSM at first, my system would just bring me back to the BIOS on a restart instead of ever entering Windows. ...Enabled it again, and back to the google.

    Luckily it's possible to convert it using this method. One of my mistakes was likely trying to do it from within Windows 10 being fully loaded as (shown further down the page), instead of the recommended method of using the Recovery Environment (Windows RE) shown at first, although I'm not entirely sure that would have fixed my main issues.

    Trying to run "mbr2gpt /convert /allowFullOS" in the command prompt just resulted in "Error while creating the EFI system partition.". Thinking my 25gb of empty space out of the 240gb SSD total was not enough, I just started uninstalling, moving files, and using Disk Clean to free as much room as I could. After multiple restarts, it still gave me the same EFI error.

    The place it failed is in the attempt to shrink the OS partition. Here is that solution. Even using Windows Disk Management tool I was unable to shrink the volume of the drive while it was only half full now. It always said 0 MB available to shrink. I actually had to follow those 6 steps from the link above to get it to work in addition to defragmenting my SSD using Power Defragmenter because Windows 10 won't let you defragment an SSD. After that I ran the "mbr2gpt /convert /allowFullOS" command again.

    Had I followed the conversion method using Windows RE, I would have probably could have skipped a few steps, but I think defragmenting my SSD was probably still needed. To me what's strange is that I thought you are NEVER supposed to defrag an SSD because of the wear on it. Windows 11 ready now, though.

    ¯(ツ)

    EDIT: **patience not patients.

    submitted by /u/bubblesort33
    [link] [comments]

    Has AMD Killed Off Old GPU Drivers Too Soon? DLSS + FSR At Same Time? June Q&A [Part 2]

    Posted: 25 Jun 2021 04:19 AM PDT

    No comments:

    Post a Comment