1 00:00:00,000 --> 00:00:06,720 I would love nothing more than to sit here and tell you guys the AMD Radeon 2 00:00:04,319 --> 00:00:12,059 challenge has been sunshine so that we could all kick Team Green to 3 00:00:08,639 --> 00:00:14,700 the curb once and for all unfortunately 4 00:00:12,059 --> 00:00:19,920 that's just not how it went luckily none of it was see Sonic's fault 5 00:00:17,100 --> 00:00:26,939 who sponsored this video but from hard crashes to FPS drops to graphical bugs 6 00:00:23,100 --> 00:00:30,779 Luke Jake and I have each run into our 7 00:00:26,939 --> 00:00:33,660 share of issues but in spite of that I 8 00:00:30,779 --> 00:00:39,180 am not going back to Team Green at least not yet and neither is Jake 9 00:00:36,480 --> 00:00:44,879 Luke on the other hand yeah I I went back right after the initial 30 days it 10 00:00:41,700 --> 00:00:47,100 was a huge problem for me but I will say 11 00:00:44,879 --> 00:00:51,539 I retested it fairly recently and things did improve quite a bit I mean In 12 00:00:49,559 --> 00:00:56,760 fairness to AMD maybe if you'd had a second see Sonic power supply in your 13 00:00:53,879 --> 00:01:00,600 janky setup instead of that crusty antec thing you wouldn't have had a problem I 14 00:00:59,100 --> 00:01:04,799 don't think that that was it yeah neither do I but I needed an excuse to 15 00:01:02,940 --> 00:01:10,200 shout out see Sonic's quality products and outstanding warranty terms before we 16 00:01:07,080 --> 00:01:13,200 jump right into my experience 17 00:01:10,200 --> 00:01:15,180 unlike Luke my Radeon issues could 18 00:01:13,200 --> 00:01:21,060 either be explained Away by bugs in other software or they were just minor 19 00:01:18,240 --> 00:01:24,600 overall like my in-game steam overlay being transparent here for some reason 20 00:01:22,619 --> 00:01:29,040 or the graphical bugs that I encountered playing tears of the Kingdom via Vulcan 21 00:01:26,520 --> 00:01:34,080 in the Yuzu switch em relax guys I know you can just switch to opengl and relax 22 00:01:30,720 --> 00:01:37,200 Nintendo I did buy a copy however these 23 00:01:34,080 --> 00:01:39,659 kinds of small issues are subjective and 24 00:01:37,200 --> 00:01:43,680 an inconvenience for me could be a game breaker for you for instance back in 25 00:01:41,939 --> 00:01:48,860 April I was working on a review of the Rog Ally at home where I happened to 26 00:01:46,020 --> 00:01:54,360 have a 100 AMD ecosystem at the time threadripper and the 7900 XTX in my 27 00:01:51,420 --> 00:01:58,619 desktop and the AMD Z1 extreme Apu in my handheld and while my overall experience 28 00:01:56,280 --> 00:02:03,659 with the Ally was great I gave it a very positive review one of the coolest use 29 00:02:01,200 --> 00:02:09,119 cases that I could imagine for its 120 hertz display was using the power of my 30 00:02:06,540 --> 00:02:14,099 desktop to stream to it overcoming the limitations of its mobile hardware and 31 00:02:11,760 --> 00:02:18,660 as an extra bonus it dramatically reduces the latency that normally makes 32 00:02:16,140 --> 00:02:22,140 streaming feel less responsive it's something that NVIDIA has put a lot of 33 00:02:20,700 --> 00:02:27,420 development into over the years with their encoder and generally with my 34 00:02:24,300 --> 00:02:29,700 NVIDIA setup using Steam remote play it 35 00:02:27,420 --> 00:02:34,020 worked really seamlessly but then on my all AMD setup all I could see in do 36 00:02:31,800 --> 00:02:39,300 maternal was the loading screens at a glorious 120 frames per second 37 00:02:37,020 --> 00:02:43,379 now that particular game is working now and it really is as awesome as it sounds 38 00:02:41,340 --> 00:02:46,620 because it significantly boosts both game performance and battery life 39 00:02:45,180 --> 00:02:51,780 compared to what a mobile device can do on its own but these issues still crop 40 00:02:49,620 --> 00:02:55,860 up from time to time a month ago I was having issues where Halo infinite would 41 00:02:53,580 --> 00:03:00,120 crash almost every time I launched it but before it would crash I was seeing 42 00:02:58,500 --> 00:03:04,200 that same problem where it would stream a black screen instead of 43 00:03:01,980 --> 00:03:08,340 you know the game and it gets even better or worse 44 00:03:06,360 --> 00:03:12,720 depending on who you're cheering for or if you're able to detect sarcasm I don't 45 00:03:10,800 --> 00:03:16,800 remember the last time that I saw a driver timeout while taking a screenshot 46 00:03:14,459 --> 00:03:20,760 and this blue screen of death do you guys see this that I got while I was 47 00:03:18,659 --> 00:03:25,560 video chatting with my sister-in-law is possibly the wildest one that I have 48 00:03:22,560 --> 00:03:28,319 ever seen in all my years of doing this 49 00:03:25,560 --> 00:03:32,940 once again this could have just been Windows or Whatsapp being poo poo but on 50 00:03:31,680 --> 00:03:38,040 the other hand these are simple day-to-day tasks that should just work 51 00:03:35,760 --> 00:03:42,900 on basically any remotely modern PC Hardware configuration 52 00:03:39,840 --> 00:03:45,180 did before I switched up my GPU 53 00:03:42,900 --> 00:03:48,959 also you guys saw at the end of the last video that I'm one of the few remaining 54 00:03:46,620 --> 00:03:53,340 Halo infinite players and the good news is that it ran great for the most part 55 00:03:51,000 --> 00:03:57,840 including over the optical cables to my home theater that gave me trouble during 56 00:03:54,720 --> 00:04:00,900 the Intel Arc challenge but then this is 57 00:03:57,840 --> 00:04:02,459 kind of rough timing just a month ago it 58 00:04:00,900 --> 00:04:06,720 started giving me random game crashes actually I shouldn't say random they're 59 00:04:04,500 --> 00:04:12,959 pretty predictable if I launch the game it crashes uh it's probably the big 60 00:04:10,319 --> 00:04:15,720 update that Microsoft pushed out but at the end of the day the average gamer 61 00:04:14,220 --> 00:04:20,160 doesn't care who's causing the issue they just don't want to see it 62 00:04:18,120 --> 00:04:24,060 another super cool feature that NVIDIA figured out a while back is allowing you 63 00:04:21,900 --> 00:04:29,220 to seamlessly update your GPU drivers without restarting your system they do 64 00:04:26,400 --> 00:04:32,520 recommend that you do it anyway but I never bother and I haven't had an issue 65 00:04:30,900 --> 00:04:37,139 with it in years with AMD on the other hand I mean this 66 00:04:34,500 --> 00:04:40,560 is a sample size of like three updates that I installed throughout the 67 00:04:38,100 --> 00:04:44,280 challenge but that one failure was a doozy 68 00:04:41,580 --> 00:04:48,540 considering who I am though A Serial tinkerer and the fact that my experience 69 00:04:46,259 --> 00:04:52,740 with NVIDIA isn't perfect either I don't think I'm gonna be going back 70 00:04:49,919 --> 00:04:57,060 not because AMD is better but because it's fine and I could probably solve at 71 00:04:55,560 --> 00:05:00,900 least a handful of my problems with a fresh Windows installed also changing 72 00:04:58,919 --> 00:05:04,560 out a GP with Hardline tubing is a royal pain in the butt even if somebody else 73 00:05:02,580 --> 00:05:09,540 does it for you speaking of pain in the butt like Linus I also had some driver 74 00:05:06,840 --> 00:05:14,540 timeouts and crashes but unlike Linus mine were constant and I was also having 75 00:05:11,880 --> 00:05:19,680 full system shutdown without notice so I suspected that it 76 00:05:17,460 --> 00:05:23,639 might be power supply related since I am running my GPU outside of my case 77 00:05:21,479 --> 00:05:28,800 anyways I hooked up a secondary power supply for the Radeon card this did 78 00:05:26,220 --> 00:05:34,440 improve things it was still crashing but a little bit less so that's a win I get 79 00:05:31,320 --> 00:05:36,960 yeah however my card's temps were always 80 00:05:34,440 --> 00:05:41,160 reasonable so it felt like super weird Behavior at the time after I added an 81 00:05:39,360 --> 00:05:44,880 additional power supply for just the GPU itself and a driver update the crashes 82 00:05:43,380 --> 00:05:49,440 went down from every two to three hours to about once a day which honestly felt 83 00:05:47,460 --> 00:05:53,820 downright functional compared to what I was originally dealing with In fairness 84 00:05:51,479 --> 00:05:58,620 to AMD though you're running on a riser who does that yeah that's fair there's 85 00:05:56,160 --> 00:06:01,620 even some issues with like pci4 cards on risers and stuff but I tried two 86 00:06:00,180 --> 00:06:05,759 different risers it was fine on the Titan RTX and I would like to be able to 87 00:06:03,720 --> 00:06:10,860 run the card on a riser when I wasn't crashing though I was still running into 88 00:06:07,800 --> 00:06:13,380 various hurdles frames in tarkov would 89 00:06:10,860 --> 00:06:18,539 sometimes go from like 80 FPS to 20 rapidly making it an unplayable puke 90 00:06:16,139 --> 00:06:23,100 Fest YouTube videos would randomly just stop on a particular frame while the 91 00:06:21,000 --> 00:06:26,639 audio kept going a refresh would fix this every time but then it would just 92 00:06:24,600 --> 00:06:30,960 happen again like 20 seconds later and even just screen sharing and like teams 93 00:06:29,100 --> 00:06:35,580 for work would cause the system to become completely unresponsive or like a 94 00:06:33,539 --> 00:06:39,900 five FPS slideshow making everything super laggy and hard to interact with as 95 00:06:37,919 --> 00:06:43,020 soon as I stopped screen sharing boom it was back to normal I'd like to think 96 00:06:41,340 --> 00:06:49,319 that that's just teams being a piece of garbage or AMD's less mature encoder but 97 00:06:46,199 --> 00:06:51,060 it's still it still happens right so I 98 00:06:49,319 --> 00:06:54,720 don't know I even ran into issues where it would sometimes just feel like my 99 00:06:52,620 --> 00:07:00,120 entire computer was just halting every two to three seconds restart would fix 100 00:06:56,699 --> 00:07:02,759 that too even just typing with Blues td6 101 00:07:00,120 --> 00:07:07,139 open was a challenge and that's not a demanding game speaking of halting I 102 00:07:04,800 --> 00:07:11,400 also had some sleep issues well I always have those but I mean my computer had 103 00:07:09,060 --> 00:07:15,780 some sleep issues there seemed to be a random chance after waking up where it 104 00:07:13,680 --> 00:07:20,220 acted like my monitor was set to like five Hertz or something super weird I've 105 00:07:18,780 --> 00:07:25,979 never experienced anything like that before and a restart would always fix it 106 00:07:23,160 --> 00:07:29,940 but shouldn't your PC just not just do that like ah struggling through frames 107 00:07:28,080 --> 00:07:34,340 just to save something or if I just really needed to use the computer really 108 00:07:31,620 --> 00:07:40,080 quickly became hyper annoying chores awesome real cool launch experience I I 109 00:07:38,160 --> 00:07:44,880 work from home a lot and needed to actually use my computer during this 110 00:07:42,180 --> 00:07:49,199 challenge so I went back to the Titan RTX 111 00:07:45,900 --> 00:07:50,940 however after a few months once LTX was 112 00:07:49,199 --> 00:07:54,780 over and we were finally getting around to shooting this video I Decided it 113 00:07:53,340 --> 00:08:00,780 probably made sense to give it another shot and I have to say while it's still not 114 00:07:58,319 --> 00:08:04,919 perfect I'm at the point now where honestly I think it's here to stay I 115 00:08:03,000 --> 00:08:10,199 think I'm Gonna Keep the card it's actually that much better I I've had one 116 00:08:08,220 --> 00:08:15,300 totally random crash when I was playing uh wow classic hardcore with my brother 117 00:08:12,300 --> 00:08:16,639 that was weird it's kind of felt on its 118 00:08:15,300 --> 00:08:20,400 own and then two in Starfield technically three but one of them is 119 00:08:18,900 --> 00:08:24,300 entirely my fault I didn't install the launch day driver oh so that that one's 120 00:08:22,680 --> 00:08:29,220 on me I don't count that one this is a good thing but it's also a bad thing because if you're on the same card you 121 00:08:27,360 --> 00:08:34,200 were using before it means it wasn't just defective yeah yeah yeah and like 122 00:08:32,399 --> 00:08:37,860 now I've had it in my system for a month and there's like two legitimate crashes 123 00:08:36,419 --> 00:08:43,560 and they both happen to be in the same game starfield's been great for me yeah like 124 00:08:41,339 --> 00:08:47,339 I'm not really sure how to justify my thoughts on this just yet but most of my 125 00:08:45,540 --> 00:08:52,620 recent crashes don't feel like they're entirely the GPU's fault like they did 126 00:08:50,279 --> 00:08:56,880 before like I've played actually a lot more Baldur's Gate 3 and battle bit on 127 00:08:55,019 --> 00:09:00,899 it since the reinstall than Starfield and it's never crashed in those games 128 00:08:58,740 --> 00:09:06,060 and oddly enough every time a crash happens Discord closes and it takes the 129 00:09:03,779 --> 00:09:11,399 longest to recover out of everything so I'm just not sure I'm not saying that 130 00:09:08,580 --> 00:09:15,240 the card is innocent here but it feels more complicated than that this time I 131 00:09:13,200 --> 00:09:19,100 will mention you do have that super sketchy CPU 132 00:09:17,040 --> 00:09:23,820 yeah did you forget about that no no it's 133 00:09:21,720 --> 00:09:28,140 stable with the Titan RTX okay stable through everything else and when the 134 00:09:25,440 --> 00:09:32,459 drivers crashes it's it's specifically a GPU driver crash every single time okay 135 00:09:30,540 --> 00:09:37,260 PCIe signaling last of all I've got a even weirder 136 00:09:35,519 --> 00:09:42,120 sleep issue where my computer is just restarting itself sometimes when it goes 137 00:09:39,300 --> 00:09:45,660 to bed all of my apps have some kind of Auto saving feature so it's honestly not 138 00:09:44,040 --> 00:09:51,480 the worst thing for me ever but if you're the kind of person who leaves a bunch of unsaved notepads all over your 139 00:09:48,540 --> 00:09:57,180 desktop then your mileage may vary so it was a really Rocky start and if 140 00:09:55,140 --> 00:10:01,800 I'd purchased this card myself honestly I probably would have returned it but I 141 00:09:59,640 --> 00:10:05,880 didn't and now it's mostly stable and it pumps some serious performance so I'm 142 00:10:03,839 --> 00:10:09,839 keeping it however you said this yourself if you had purchased the card 143 00:10:07,800 --> 00:10:14,640 you would have returned it and while Jake's experience was relatively 144 00:10:12,420 --> 00:10:21,060 positive okay we'll get to you in a second Jake I promise we can't excuse 145 00:10:17,459 --> 00:10:25,260 these terrible launches right we just 146 00:10:21,060 --> 00:10:27,180 reviewed the new 7800 XT and while the 147 00:10:25,260 --> 00:10:31,860 card seems like a decent Buy in terms of price to Performance the lab also had 148 00:10:30,240 --> 00:10:37,740 issues during testing with the Press driver most notably f123 kept crashing 149 00:10:35,459 --> 00:10:42,600 and cyberpunk had some really bad Shadows popping in and out 150 00:10:39,660 --> 00:10:46,260 so maybe AMD just needs to leave these cards in the oven for another month or 151 00:10:44,220 --> 00:10:50,880 two because the software side of things coming out Half Baked and this is based 152 00:10:48,660 --> 00:10:54,839 on your own experience and our testing is going to leave a sour taste in a lot 153 00:10:53,339 --> 00:10:59,700 of people's mouths okay Jake your turn you're done yes to counter that point I 154 00:10:57,959 --> 00:11:05,880 love having competition against NVIDIA so ah it's so hard to be anti-AMD but 155 00:11:02,820 --> 00:11:07,800 he's right aside from having to employ a 156 00:11:05,880 --> 00:11:11,640 drill to even get the card into my computer thanks Linus this went 157 00:11:09,839 --> 00:11:15,420 relatively smoothly for me all of the modern games I play like Modern Warfare 158 00:11:13,320 --> 00:11:19,740 2 Star field and OverWatch are a joy when running AMD but going back in time 159 00:11:17,579 --> 00:11:23,579 to the original Borderlands it was a bit of a mess wait I saw that on my 160 00:11:21,839 --> 00:11:28,320 steampunk there was a thought it's like he's playing Borderlands what 161 00:11:25,019 --> 00:11:31,260 Borderlands one yes Diablo yeah yeah 162 00:11:28,320 --> 00:11:35,399 why Nostalgia I guess I didn't quite remember that there's basically no story 163 00:11:32,880 --> 00:11:39,240 in that one to AMD's credit the enhanced Game of the Year version is not really 164 00:11:37,380 --> 00:11:43,860 known for stability so I really can't blame team rev directly but while I was 165 00:11:42,360 --> 00:11:48,060 crashing my friends on Team Green weren't and I wasn't able to reproduce 166 00:11:45,720 --> 00:11:51,660 the issue on my 3080. the other major issue I ran into during this challenge 167 00:11:49,560 --> 00:11:56,339 actually had to do with freesync now I didn't go out of my way to use freesync 168 00:11:53,940 --> 00:12:02,700 it's on by default which I guess makes sense a good thing yeah yeah but it was 169 00:11:58,980 --> 00:12:04,440 my second monitor oh so turning it off 170 00:12:02,700 --> 00:12:09,600 did seemingly fix the random blue screens I was getting but ah it's just 171 00:12:07,620 --> 00:12:12,540 it hurts my brain and you shouldn't have to do that kind of troubleshooting just 172 00:12:10,980 --> 00:12:16,320 to play video games exactly people shouldn't have to find random Guru 3D 173 00:12:14,579 --> 00:12:19,200 and Reddit posts just to figure issues like this out I don't know if it's been 174 00:12:17,760 --> 00:12:24,959 fixed in the newer drivers but I'm not exactly hurting for a tear-free experience in Discord so it's just gonna 175 00:12:22,560 --> 00:12:29,579 stay to say another issue I'm not really able to fix but able to tolerate is just 176 00:12:27,360 --> 00:12:35,640 how mediocre AMD's Hardware accelerated encoder is nvank on team green rocks 177 00:12:32,820 --> 00:12:39,480 amds so I've gone back to my CPU for all the 178 00:12:37,680 --> 00:12:43,320 media encoding I do which is annoying because while the quality is there I'm 179 00:12:41,519 --> 00:12:49,700 sure as Floatplane knows it takes forever at the point where sorry that 180 00:12:46,139 --> 00:12:51,600 was kind of a NVIDIA rocks AMD walks 181 00:12:49,700 --> 00:12:54,180 I mean it's true though it does take forever that's fine I'm at the point 182 00:12:52,980 --> 00:12:58,560 where I'm trying to figure out how to use the 1660 TI that I have in my Nas to 183 00:12:56,760 --> 00:13:03,959 this work instead but if you're a streamer this could be a real issue av1 184 00:13:01,620 --> 00:13:07,800 should help level this playing field but nobody really supports it yet YouTube 185 00:13:05,339 --> 00:13:12,420 exactly nobody and until then I guess NVIDIA has the leg up here one thing I 186 00:13:10,200 --> 00:13:17,880 can't fix though is the high idle power draw I was personally seeing a hundred 187 00:13:14,700 --> 00:13:19,860 plus even 150 watts while idling which 188 00:13:17,880 --> 00:13:23,100 is a lot especially as someone who likes to leave their PC running luckily we 189 00:13:21,600 --> 00:13:26,220 don't pay much for electricity in Vancouver it's all hydroelectric but if 190 00:13:25,019 --> 00:13:31,620 you lived in Europe and you're paying like 50 cents a kilowatt that's 400 to 191 00:13:28,860 --> 00:13:35,339 700 per year in idle power draw alone not even gaming that's a lot of money 192 00:13:34,019 --> 00:13:40,740 you could use instead to buy merch from LTE store.com Stubby's screwdriver yeah finally in 193 00:13:39,060 --> 00:13:43,800 stock yeah there have been some recent updates that apparently have fixed that 194 00:13:42,180 --> 00:13:48,540 issue for other people but I'm still affected I just checked yesterday 91 195 00:13:45,899 --> 00:13:52,079 Watts at idle so sick buyer beware while my experience was overall far from 196 00:13:50,639 --> 00:13:55,620 perfect I just want to clarify that overall I'm pretty satisfied I wouldn't 197 00:13:53,639 --> 00:13:59,579 have been returning mine being able to use the same 8-pin power cables was 198 00:13:57,420 --> 00:14:04,380 great and even though the 16 pin issues are mostly isolated incidents I had zero 199 00:14:02,399 --> 00:14:08,579 fear of my cable melting and burning my computer to the ground AMD Radeon 200 00:14:06,480 --> 00:14:12,180 software has also been nice to use it's a bit cluttered but still easy to 201 00:14:10,380 --> 00:14:16,740 navigate and I love that I don't have to register for and then sign into a 202 00:14:14,579 --> 00:14:20,639 discrete account just to get easy driver updates I also love that it doesn't look 203 00:14:18,360 --> 00:14:26,760 like it's from 2005. it feels moderate just like just like shout out the video 204 00:14:23,519 --> 00:14:28,440 driver panel like not GF even GFE looks 205 00:14:26,760 --> 00:14:33,240 old it does shame you for how much you play video games right on the home screen yeah as someone who actually buys 206 00:14:31,620 --> 00:14:37,380 their graphics card I'm going to continue with AMD this generation I just 207 00:14:35,100 --> 00:14:40,139 can't justify spending like 2 thousand twenty five hundred dollars Canadian to 208 00:14:38,820 --> 00:14:43,860 get an upgrade with Team Green this generation especially when these AMD 209 00:14:42,000 --> 00:14:48,000 cards exist but I can understand if you chose the opposite so I think it's fair 210 00:14:46,019 --> 00:14:55,860 to describe the challenge this time around as a mixed bag Jake's experience 211 00:14:51,540 --> 00:14:59,100 was quirky but fine Luke's was terrible 212 00:14:55,860 --> 00:15:00,839 until he did some tweaks and then got a 213 00:14:59,100 --> 00:15:06,120 driver update that pretty much made it also fine and then mine was 214 00:15:03,600 --> 00:15:10,320 also fine okay it's a less mixed bag than we thought and In fairness to AMD 215 00:15:08,519 --> 00:15:14,880 some of us are running pretty odd configurations and we should have all 216 00:15:12,720 --> 00:15:20,519 done fresh installs yeah but who does that well that's a good question not 217 00:15:18,480 --> 00:15:24,720 everybody who buys a new GPU does that and they don't want to I mean running 218 00:15:22,079 --> 00:15:28,139 ddu which we all did and then installing new drivers should be enough to get you 219 00:15:26,880 --> 00:15:31,139 up and running without random driver crashes and timeouts although maybe 220 00:15:29,940 --> 00:15:37,620 that's something that could be improved by making sure you have a proper power supply yeah Luke I have a seasonic power 221 00:15:35,339 --> 00:15:42,779 supply in the system and I'm running an external power supply and I've swapped 222 00:15:40,260 --> 00:15:46,620 that out even for like unrelated issues but that never actually changed anything 223 00:15:45,120 --> 00:15:51,660 okay fine so maybe the power supply wasn't the problem the point is that see 224 00:15:49,139 --> 00:15:56,279 Sonic needs some love again so hey see Sonic and it's true having a good 225 00:15:53,760 --> 00:16:00,139 quality power supply really does make a huge difference to system stability if 226 00:15:58,500 --> 00:16:06,060 you're having an issue that otherwise cannot be explained through mortal means 227 00:16:03,180 --> 00:16:09,839 it's either RAM or it's your power supply and see Sonic has a wide range of 228 00:16:08,279 --> 00:16:13,860 products to help get your system performing its best I'm personally 229 00:16:11,940 --> 00:16:17,880 running a prime titanium thousand watt these days and it is dead quiet and 230 00:16:15,660 --> 00:16:22,199 super efficient coming around then to the performance side of the AMD 231 00:16:19,680 --> 00:16:26,880 challenge I was more than happy with the 7900 XTX I don't really care that much 232 00:16:24,600 --> 00:16:32,279 about Ray tracing nothing that I play uses it in fact I play either online 233 00:16:29,579 --> 00:16:37,680 Shooters mostly Halo infinite or like casual pixel art games absolutely 234 00:16:34,680 --> 00:16:39,360 nothing in between and right now not 235 00:16:37,680 --> 00:16:43,740 only is the high end really performant but AMD's mid-range is a specially 236 00:16:41,880 --> 00:16:48,600 competitive compared to Team Green if you're anything like me especially their 237 00:16:45,899 --> 00:16:52,860 last gen 6000 series wow so if you want to give it a shot I'm 238 00:16:50,399 --> 00:16:57,480 willing to say come on give them a chance there's jelly beans yeah it might 239 00:16:55,440 --> 00:17:00,360 be some minor issues but there's a lot of benefits look if you're buying AMD 240 00:16:59,040 --> 00:17:05,760 just buy it like two months after it comes out and you'll probably be fine that's good advice we'll have a variety 241 00:17:03,480 --> 00:17:09,540 of well-priced Radeon gpus links down below and also some power supplies that 242 00:17:07,620 --> 00:17:13,140 we consider to be excellent matches for them from our sponsor seasonic if you 243 00:17:11,819 --> 00:17:19,319 guys enjoyed this video thank you for watching and make sure to check out the Intel Arc challenge for 244 00:17:16,919 --> 00:17:23,939 even more hilarious Shenanigans another thing that's improved over time I think 245 00:17:20,939 --> 00:17:25,319 you need to do a follow-up on Arc yeah I 246 00:17:23,939 --> 00:17:30,000 don't want to Hardline your break again I'm not going to go Hardline anymore oh 247 00:17:27,600 --> 00:17:33,559 great tubing melted yeah yeah yeah his computer is dead again by the way yeah 248 00:17:31,440 --> 00:17:33,559 yeah