Tencent HY3 Is VERY Good – Is This a GLM & DeepSeek Competitor?

[laughter] >> The walking animation is uh a little interesting. Today, we're going to be looking at a very exciting new release from Tencent, and that is HY3. Now, this model, a couple of months ago, I believe, was in preview, and I did test it back then. However, this is now the full release. It is no longer in preview, and at least from what we can see in the benchmark JPEGs here, it does seem like there are some pretty significant leaps in capability over the preview version. So, I'll be excited to test this on some things that I did not test the preview version on, just so we can get a real look at whether or not these leaps actually stack up. But, from what we see here, this does seem like it may be a potentially very exciting model for folks who have local setups consisting of like two DGX bar clusters or a 256 gig Mac Studio, things like that. When quantized down to, I think, a 4-bit quant, this should fit pretty comfortably on those listed devices. So, still something that's going to be a bit heavy to run, but at 299 billion parameters, being an MoE, this is actually a reasonable size model, especially when factoring in the touted performance here in the benchmarks. Now, before we get into it, please do feel free to subscribe, so I can get the 100k plaque. Also, I do want to specifically mention that this is licensed under Apache 2.0. Just in reading through some discussions I've seen online, it seems like the preview version wasn't, but this is now a fully, like, very solid license to have. Additionally to that, they do talk a bit about fine-tuning this model, so this may be a pretty potent option for folks who are interested in actually modifying it to a specific use case, and they do have the fine-tuning guide for that linked right here, which is just good to see. I always like to see additional things beyond models being open-source tools to actually further tailor them to your specific use case. And, being that the current point in time seems to have a little more curiosity about access to frontier state-of-the-art models, it's always good to see sizes like this, which can hypothetically be run on some hobbyist prosumer level setups. So, let's take a look at the technical specs of this model. It is a 295 billion parameter mixture of experts model with 21 billion active. It has a 3.8 B MTP layer parameters. So, basically it has multi-token prediction. So, it will run a bit quicker than the size would be indicative of thanks to that MTP. Additionally, they talk a lot about the improvements over the preview version stating that it outperforms similar size models and rivals flagship open-source models with two to five times the parameters. I did see just on X some comparisons of this to GLM 5.1 or 5.2 and folks were saying based on those benchmarks it does seem like it may trade blows with that, which would be really exciting. Context length is listed right here at 256K and there's some other more technical information about the model's architecture and things like that. Now, one of the main things I'm interested in seeing in this benchmark is just the capability increase from the HY3 preview model to now this full release and we can see even in programming and things in that specific domain this does seem to have quite a leap in capability. Scrolling down further in the hugging face model card we can see a much more intricate benchmark chart here just for those interested in that sort of things. They also do have a bunch of code here samples for deploying this with v l l m or other inference tools. Additionally to that I want to mention because it's kind of hard to use this as of right now it doesn't seem to be on open router. Let me just check again in case that changed. Oh, openrouter.ai not .com. Yeah, I don't see it here. So, I'm actually using this through something that Claude suggested to me called Zen Max. They seem to have um like a lot of Chinese models like Long Cat Flash was on there as well and I couldn't get access to that through anything else. So, that is why when we take a peek right here in terminal I am using this through open code. We see it says Zen mock. So, I paid for it. I just popped in $10 worth of API credits. I figure that should be pretty good. And we do have this model selected. I did already begin with the browser OS test V2.5 because truthfully, I want to not fully phase it out, but at this point in time, I think the focus on testing models basically, to be completely blunt, I see a lot of channels have popped up just doing like model tests and comparisons and things like that. And now basically, everyone's doing like boring single shot like make this, make it look good. I get that. I like that testing, but once I see that it's become so common, I kind of want to up the ante a bit. And that's why tests like this with fable and things like that have started to become more prevalent on this channel. And I will continue to do more creative and real world tests with these AI models beyond just the traditional like browser OS. So, with that, we are now of course going to take a peek at this, but I did want to touch upon that because I understand there's probably some testing fatigue in seeing the same basic like zero shot things. I'm even feeling it. So, understood. So, let's begin with our old-fashioned tried and true browser OS. Okay, WebOS 3D booting kernel. So far, I'm not blown away. It does have the clock. It does have a start bar. Is there a right click? Okay, there's no right click. Let's see if our apps open here. Good. Very, very simple and minimalist, but nonetheless, it does seem competently arranged and all that. So, our special feature as we can see right there is voice control, which does seem kind of cool. We can also implement custom gradient for a CSS, which I don't know that I've actually seen it to that degree. Like you can usually choose a custom color just with the hex code, but that's actually kind of neat. I'll do like this Windows XP looking thing. We can't resize, but we can move it around, minimize, unminimize, full screen, unfull screen. Okay, let's check our file explorer. Okay, we're in our C drive and we do actually have some system assets or items. I think the biggest thing here is we can't actually get back. Like there's no move up a command directory. So, notepad. Hello. Save. Okay, and it probably just saves it. I am curious real quick. Would it have saved it in the No. Okay, so all right. You never know. Terminal. Simple. Help. All right, let's try GTA, but let's just do open GTA. All right. Not bad. Except Okay, good. It's arrow keys. It's not WASD. Are there mesh colliders on the buildings? Nope. Okay. And the car is rather quick if I were to go full speed. Let's see what happens if we Okay, good. It's a pedestrian safe version of GTA, which is good. Space is to shoot. Oh. Oh, no. Okay, never mind. It's not pedestrian safe. It's just interesting. This is curious. All right. Overall, not bad. I mean, it worked, and that's pretty much what we want. And it was shooting. You know, I do remember the size of this model is not ridiculous comparatively to some of the other things we've been testing recently. Then we have Maze 3D. Okay, I had a feeling that may be the case where it just started us in some wall. Now, we're supposed to be able to look with the mouse, but unfortunately, I'm not getting any view movement from the mouse. So, it is somewhat 3D, and we have to collect all of these orbs. I'm kind of invested. I want to see what happens if we collect them all. I have a feeling we're going to get like 21 of them, and then the last one's just going to be impossible to find. Call it a hunch, but I've done enough of these that like it's always something like that. All right, I'm done with this. It was a, you know, it was together. It was simple, nothing here really wowed us, but again, this is a test that's probably going to get phased out at some point. So, I don't want to spend a ton of time on it. Oh, we didn't check the special feature, which was the voice control. Wallpaper blue. That's good. A lot of them include this as a special feature now, and it's a really cool special feature. Oh, hard all It's really good >> [laughter] >> Open GTA. Good. Put the money in All right. Acceptable. Next up, I've put this in plan mode, and I'm going to be running the self-contained C++ gates in. This is a test that I do intend to keep because I don't really often see models being tested on C++, especially when we don't allow them to use raylib and things like that. So, it's always enjoyable, at least for me personally, to see how they do in something that's a little less common than 3.js and things like that. Okay, speed-wise is good, but again, I'm using it through a provider, though it is Tencent themselves that I'm using it through here. So, okay, it's got some questions for us. Choose library. Tinier models are allowed to use raylib like Gemma 4 12-bit, but not big models like this. Now, I notice sometimes this happens, too, where they don't really seem to respect plan mode cuz we see it's trying to prepare right right there, but it should be like, "Oh, I'm in plan mode. I'm not allowed to write files." Like, switch it to build mode, and then I will. I'm going to interrupt it. Switch it to build mode. And then just let it fly. That happens sometimes. I don't know why, but it just does. All right, it did try to build it now, and as we can see on the screen, there were some errors just in the build command, so it's going to have to fix those, and then assuming it does properly, we will probably see quickly on the screen that it will open it just to verify everything's right. Okay, significantly reduced number of warnings now. Okay, it was basically saying it compiles cleanly. There was just one warning there. All right, it's all set and now we're ready to go ahead and take a peek at it. It's just giving us basically the debrief summary of what it's done. We should now get our skate game. That's not half bad. For the size of this model, this is really not bad. It's not super visually exciting. However, everything is pretty clean, which I'm going to say is impressive for the size. Meaning like the storefronts are competently arranged. I don't really know what that is right there. Oh, okay. Some of these pedestrians do look like they are >> [snorts] >> having some form of medical issue. Okay, and there's an invisible rail there. Okay, now we're going to start to see there's a bit of jank, if you will, but let's try our kickflip. Okay, good. The kickflip is in the wrong orientation, but at least it moves the board independent of the rider, which sometimes is not the case. So, that's always like a tell of whether or not the model's actually decent or not is if it just flips the whole rider. K is for a heel flip. Okay, the water is coming into the boardwalk and we're having some issue moving around. >> [laughter] >> This is a troubled result, but it's not horrible. All right, so we actually went up there. The score is working properly. Our rider's decent. There's this invisible rail. >> [laughter] >> That was like a what That was like a It's very fast. There's another rail. All right. This shows potential is what I would say. I feel like this is worthy of a an additional follow-up here. So, I've kind of nagged it a little saying it's a four of 10. If this is the best you can do, just tell me. It would be very surprising for a model to be like, "Yeah, this is all I can do. I'm just going to leave it." So, it will likely try to make some improvements and I described simply some of the issues we noticed. All right, here's our improved result, hypothetically. All right, first and foremost, oh no. >> [laughter] >> Like so >> [laughter] >> Unfortunately, this just looks like something out of I don't know. That's >> [sighs] >> It added palm trees in front of the water, which is good. Um everything else is, you know, what's what happens if we try some Oh, okay. This looks like a I can't say that on camera. So, there's sand back here. Okay, that's going to conclude this test. The first try was acceptable. Uh the second iterative result was I'm not There's nothing I can say to it here that I can include in the video. So, I'm just going to gracefully close the session and we'll move on. So, this is a test that kind of came to me and it's genuinely a point of frustration that I deal with. So, I want to use models to see if they can fix this. This specific laptop, it's an older Acer Nitro gaming laptop. It does have a very nice RGB keyboard. However, for some reason in Ubuntu, the only color that shows up is some Oh, that just whoops disgusting orange. Now, I have no way There's no drivers or anything on this system to be able to properly change the color of the keyboard. I want to see if a model can actually create something that will do that. I don't believe this model in specific will be able to successfully do that. Some of the bigger ones absolutely would, but I want to just test it. I want to include this as a test because it's a real hardware software integration challenge and I want to see how well they go about trying to figure this out. So, I'm giving it this pretty simple couple sentence prompt. The system you're on is an Acer Nitro 17 laptop running Ubuntu 22.04. The keyboard has RGB control that works well in Windows, but in Ubuntu, it is stuck in orange. Create a tool to allow cycling to other colors such as blue, red, etc. Now, there are open source tools that will allow you to have some more fine-grained RGB control in Ubuntu. However, it's going to be a difficult thing. So, we're seeing it's going to start out okay by taking a look at some of these specific lower-level things about the system. I would imagine we're going to get a lot of permission prompts here, which is to be expected because it's going to have to try to modify some of the human interface devices on the system, and it's going to be looking in device drivers and areas like that. I'm actually going to make this window larger here for this one. The internal keyboard's PS2, and there's no obvious USB RGB device. Nitro RGB is usually a WMI-controlled human interface. Okay, the ID for that device is the known Acer keyboard light interface. Okay, so now it's going to try to find some methods to use that or modify what we see in terms of the color. All right, now it's going to look for the actual RGB protocol to see what it is and how it works. I have what I need to understand the hardware. The internal RGB keyboard on Acer is controlled via this, not a normal USB HID device. Let me confirm access in the protocol. Okay. So, it's encountered an issue where it can't enter the password. So, if it just gives me the command to enter, I will do it and then give it back the output. Okay, so it's doing some web fetching right here. And this is where my kind of not [clears throat] cheat, but it may simplify it because as we see right here, if it finds some specific things on GitHub that can easily allow it to perform the creation of this tool, that will definitely make it simpler than having to just raw low-level go through the hardware, reverse engineer the protocol, and then figure out how to change these colors itself. But nonetheless, we've just instructed it to do this, so we'll see however it goes about doing that. All righty, it keeps just trying to clone repos that it's not fine. I'm going to stop at this for a second because I don't like what it's doing. Why don't you All right, so I'm telling it to write a simple bash script that I will manually run and type the root password so I can get the pertinent information from the system it needs and then save that info to a text file so it can reference that and understand what the specific device has so it can try to reverse engineer whatever protocol is being used for RGB as opposed to this is just basically like trying to spam download a bunch of random GitHub stuff and most of it's not working. So I'm kind of giving it a little bit of a a just like a you know, a tip. All right, so now we're running this bash script which is going to do what it needs and give it the information. It did say that that might fail if it's not installed. You can ignore it. I mainly need the disassembled ACPI tables to read the real protocol. All right, so the script had run but it was saving it to root. So I couldn't read it. So now I just ran it again. It modified where it's going to save to. Done. And now it should be able to read and find some more information of what it needs specific to this machine. All right, so the script had exited early because something was missing that it realizes it is going to need. So it rewrote it so that it will also install those specifically required tools and then assuming everything goes smoothly will tell it done again and then hopefully it should have what it needs to try to further this process. All right, good. That is a much better result that we see right here in the conclusion of the script. So it should have some more to go on now. And even just like creating that bash script, okay, I tipped it off to do that instead of just trying what it was doing but still I created the script and it's making adjustments to it as it needed to when realizing oh, it doesn't have what we need. And now it's going to try to at least reverse engineer or work with what specific what is specific to this system's keyboard RGB drivers. All right, so it's come up with a solution here and it's basically saying it can't do this because there needs to be some like manufacturer way to communicate with the RGB like the colors. Basically, it would need some form of driver. It's saying the RGB is an exposed to Linux on this device. Let me scroll back up. So, what it is doing is it's writing us a little utility for the one thing it found that it can control, which is the keyboard brightness. So, the existing the device for the RGB does exist, but exposes no callable method to Linux. The real per color commands live in EC internal firmware we can't reach safely. It is likely that like Fable or something if it wouldn't fall back would be able to knock this out, but don't quote me on that. I'm not an expert on this specific stuff. So, I won't guess the registers, but I can give you is a safe working tool for the one thing that's controllable, a keyboard backlight brightness plus a clean architecture where a color back end can be added once we have the real protocol. If a future kernel driver exposes it, now it's writing that tool. So, not necessarily what we wanted, but it did give us something interesting. Okay, so far, so good. Uh-oh. The screen just went blank. So, it is possible it made a mistake where it mistook the screen backlight for the keyboard backlight. Uh okay. Now, let's just try to get out of that. Okay, good. I'm going to try to run it again. I shouldn't have done that. Oh, it is it is the backlight. Okay, so God. It mistook the the display backlight for the keyboard backlight. Yeah, all right. So, >> [laughter] >> that's not good because now the Yes, I know. Thank you. Stop beeping at me. All right, here's what I'm going to do. Uh >> [laughter] >> Um okay. I like >> [laughter] >> You know what? This is I'm going back to just like zero shot 3 JS stuff. I'm going to get another camera so you can see what we're dealing with here. All right, so here's what this genius did where, you know, it's you can still see it but it's very very dark. So now I need to figure out how to undo this while saving the screen recording that was ongoing there. So, well this was what it was supposed to change is that disgusting color, but nonetheless interesting. Okay, RGB set four set. Please turn it back on. Oh, good. Now it's a little brighter. Oh god, what is the highest value we think? >> [snorts] >> 10 Brightness set to four. All right, uh okay, so >> [laughter] >> so brightness won't seem to go over four. Hey Einstein. I can like barely see you know, I'll just I'll get the I'll get the second camera out. I should just get another iPhone for for better camera quality. The ROG Phone camera kind of sucks. So we can see here now it's definitely a more visible uh endeavor. My set four wrote to EC offset path 0X5F which on the AN17 is apparently the screen backlight, not the keyboard backlight. >> [laughter] >> Yeah. >> [laughter] >> All right. [gasps] Removed enable script. Yeah, that's great, but it's enabled so I need >> [laughter] >> Okay. All right, let's see if this command to restore the screen to max brightness works. Thank god. Okay, it did. Well, the problem is resolved now. Um in testing the function key brightness control, this thing had genuinely just like turned the backlight off completely, which isn't an option to do with the keyboard backlight controls. Those only put it to its dimmest level. So, that was very interesting. It did manage to get us out of that hiccup. I think we're going to just stop for now with that. That was definitely uh >> [laughter] >> It's definitely interesting. >> [laughter] >> Wow. Next up, I'm giving this the skydiving simulation test. This is something that I also did give GLM 5 2 very recently. So, we'll be able to get a good side-by-side for how this stacks up, at least in this one specific test. All right. Let's take a look at our skydiving simulator after quite a lot of back and forth because it was trying to test it in a headless browser, which didn't have access to the CDNs for 3.js. So, then it was trying to just fix that, and it caused a lot of just disaster. So, we now have this working properly. Let's take a look. You leave the aircraft at 4,000, freefall track toward the landing target, then deploy your canopy, and stick the landing. I just want to get familiar with the controls. Space is to deploy parachute. W is to dive. S is to flare. Not bad. Really not bad. And we actually have some good topography to the terrain. Okay. We have a simple player model with you know, toward the glowing target. The terrain here is really not bad. I don't see the glowing target, but I Oh, okay. Now I do. And that's to slow down. Okay. I don't know that we'd really be able to slow down so much without the parachute open, but nonetheless deploy. What if we don't? That's something I always like to check first and foremost, just, you know, for science. Oh, nice. Crash landing F. Okay, let's try again. This time I will deploy it when we get closer. I'll do it now. Let's see if there's a sound. Okay, it kind of worked. Now, >> [laughter] >> I saw there was some oddity to the way the deployment went, and now our camera view definitely leaves a bit to be desired, but honestly, the parachute effect is not half bad. At least there are visible strings. There is a curvature here, like a mushroom top parachute. So, all right, we're about to touch down. Oh. S. Okay, would that be like S tier because it was F? We got a 96. Very good. Textbook skydive bullseye. Overall, not bad. I noticed the terrain is actually pretty well done from a generation standpoint. There's foliage, there's peaks and valleys, and there's water. Not bad. So, the next test is going to be another one that is newly introduced that we do also have a GLM 5.2 reference point. This is the 3D city block time travel prompt essentially, where it shows us a city in a number of different years spanning from 1945 all the way to 2055, and it's supposed to have cool transition effects between the years, and the style of the city should be reflective of the era that is selected. I did also specifically for this one add stay in in directory and don't do any smoke test with headless browsers. I will test it for you because that really kind of sent it awry previously. So, this will give it a better, cleaner generation. All right, let's take a look at our time travel city result. Okay, so far not bad. There should be sound Oh, it even told me you have to click to enable sound. All right, we have It's It's simple. I can tell you right now this is not at the level that the GLM 5.21 was. However, this model is less than half the size, so keep that in mind as well. Okay, we have some haze. This is the post-war recovery mood is gritty hope. There are people in outfits that are somewhat of the time. 1945 sedan. I do like that it has hover effects over some of these things. Okay, 1945 building. And are there tiny little walking movements there? Not quite, but Okay, so open. I don't know that that I don't think you'd see that in 1945, but we do also have some signs on the buildings. All right, we can orbit. Cool, so we'll auto orbit for auto orbit for us. Let's just do play where it will jump through these and then we can look at some of the different aspects of them individually. Okay. Uh so That was cool. The transition from 65 to 85 was kind of sick. 2005. Okay, and the building skins are changing. Interesting, the tone of like the boop gets higher as the years progress. Oh, 2055 is sick. >> [laughter] >> You go Utopia. Uh This model's more bullish than Fable was about 2055. Okay, I'm going to stop this now. Let's take a peek at 65. The cars, I believe they do have fins. Atomic age street traffic common. Yeah, there's a fin back there. Now, we're going to notice the cars are moving incorrectly. That is a little disappointing, but the overall scene is happier. There is a disturbing lack of any variability to the outfits of the pedestrians in 1965, but I suppose we'll we'll just let that sit. 85 is cool. It's definitely very synthwave style. We have an arcade neon excess style. Almost like a little sports car thing there maybe that drove by. Um I don't know what the cube is, and unfortunately, I can't actually see the pedestrians well enough to determine their outfits. 2005, sleek millennium. Okay. Bit calmer in terms of the sound effects here than it was in 1985, and the cars are just kind of SUV sedan. Sleek millennium street traffic. All right. 2025. I want to see are there any things on the building roofs? Okay, interesting. So, there's foliage there on the roofs of the buildings in 2025. Let me just take a quick peek at the building roofs in the other years. Okay. AC units. 85 spires. Interesting. 65 they're shorter. So, that's cool. They got taller as time progresses. I think and then we have like a whatever these things would be. Oh, they got shorter there. Then they got taller. Okay, and then they're just like Wow. >> [music] >> 2055 is crazy. That That's a robot, isn't it? Or it's a person [music] with a >> [laughter] >> The walking animation is a little interesting. >> [laughter] >> The hover things are sick though. Hover pod. Okay, so all the people have weird RGB halos around their heads, which is cool. And then we have the hologram Eco Utopia. Interesting. Definitely interesting. Next up, I'm giving it a front-end design test where it needs to create a website for Slap Us Watch Co. It should have a high-end 3D model of a watch in the hero section with some panning cinematic kind of key shot style rendering moves. Following that, it should also have individual 3D models for two pricing cards for the 2026 collection. This is a newer test, so it'll be interesting to see how it does. All right, let's take a look at our watch front-end website. That's really not bad. Okay, there's some weirdness to the strap, but for the size of this model, this is actually a respectable result because I've seen some rather jank before. Okay, we can move this around scrolling. Now, interestingly, it seems that the orbiting like the height of the camera is not able to be controlled by us. The watch face Okay, now that I look at it, the actual tick marks denoting the specific hours are arranged in a rather questionable way. However, the hands are in a center point. So, I wanted to mention that they said like 10:10 is the most aesthetic time to showcase a watch. It does seem like this would have actually tried to do that as that does seem like that time. So, that's cool. The straps are definitely interesting, and there is a little glass bubble over it with some chrome material. All right, let's scroll down and take a look. This really isn't that bad. Even the way that the header actually fades in to view more when we start scrolling. Quiet obsession with the everyday object. We do not chase trends. We chase the moment a watch leaves the workshop and feels inevitable in the hand. Atelier Slap Us >> [laughter] >> from Slap Us Watch Co. And then we have the Souls disc collection. Okay. Not too ex- I mean, yeah, they're expensive. They're very expensive, but like in the scheme of this test, they're not too expensive. Oh, that's actually really cool. Check this out. So, the watch in the hero section changes. So, if we click on the Solano, it changes to the brown one and we can take a look at that. That's interesting. I have not seen that before. So, in lieu of actually having like nice renders of them here. These are 3D, but we can look at them just the way they change in the hero section. That's a neat little trick that I've not really seen done before. Honestly, not horrible considering the size of the model. And I think the final test we're going to do something that is a little more difficult. I've instructed it to make a 3D model of a V8 engine that will fit a 280 size DC motor, which is a little remote control motor. This is something that I had also given Fable 5. Perhaps a different class of model, but nonetheless, we'll just take a look in a 3D rendering program of what we actually get and whether or not it is what one would expect. Okay, it's going to use OpenSCAD create a parametric 3D model with a motor base size for a 280 class DC motor. Just based off of what I'm seeing right here initially, I'm already impressed where it had listed out the specific Look at this. All of these are actually things that would be contained within a real engine like the crankshaft, the intake manifold. Now, it says the diameter is 24 mm and 32 long. Let's check that. And that's just its inbuilt knowledge of that specific thing. Is it done? Okay, hold on. I got to take a look at this. That was just ridiculously fast. You know what? It's like >> [snorts] >> It's It was so fast. And this is actually Yes, it's not like a 100% right. I mean, one would probably want that to to oriented the other way, but it is definitely eight individually visible cylinders and we do have like the heads on them. This is This is not as bad as I thought it would be and the fact that it did it so quickly was just like >> [snorts] >> odd. I I wasn't ex- I don't even know where to click right now because I I was not expecting this to be so quick. All right, so I've neg'd it a bit. It's actually not that bad, but it did it so quickly that we'll just see what it does with some of that negative feedback. Not half bad. I told it the motor was oriented in the wrong way. It did fix that pretty quickly. The rest of the engine is still as it was. It's not 100% photorealistic, but still for the speed that it did this as well as the parameter count, this is not as bad as I had feared it would be, truthfully. And for the last test, because honestly, I really just enjoy playing the results. We're giving it the beautiful static subway scene prompt, but we've also bundled in that it should take the scene that it makes and turn it into an FPS with humanoid zombie or enemies. I honestly just really enjoy this test. I think it's a lot of fun to play the results and to see what interesting things or lack thereof get included. All right, let's check our subway FPS result. Subway station. A deserted platform, flickering lights, and something stirring in the tunnels. Clear the station. Use the brightness control to manage the failing lights. Oh, okay. Did it implement the brightness control as part of the gameplay? Not bad. It doesn't have visible weapon recoil. Uh that was a twofer. All right. That was interesting. Can we do that again? Station cleared. All hostiles neutralized. Okay. I mean, what happens if we lose? You were overrun. Okay. This Hey, this wasn't bad. If we just quickly look at the station, it does have some flickering. There is the track there. Not bad for a model of this size. >> [clears throat] >> All right. Cool. It was just so like low drama, I guess, that I don't have much to say. All right. Well, that is going to conclude our first look and test of Tencent HY3 now that it is out of preview and it is Apache 2.0. I think for the size of this model, this actually was fairly performant and will be very interesting to see how folks do with this when it is quantized and able to run on 256 gig unified devices, whether that be a DGX Clark Clark, DGX Spark cluster, a Mac Studio, or some other mix-up of dedicated VRAM and even system RAM. So, this could be very interesting for the hobbyist setup. I suppose for a quick results overview, it was interesting because the first C++ gate game was actually better than the second one. As we can see here, there was an issue with the orientation of the player. That wasn't the case with the first result and I would say for the size of this model, for a first result, it actually did quite respectably. So, I was happy to see that. Additionally, what else did we have that was notable? Our skydiving game actually had some really decent-looking like terrain to it. So, if we look at it again, and I'm not going to go through the entire thing once more, but the terrain was really quite good. And this is one where I can definitely see a reasonable comparison to the GLM 5.2 result. It wasn't as good in terms of that one actually had some gameplay elements, so you had to fly through floating rings, but the terrain in this one was really much better than the GLM 5.2. So, that was cool to see, at least if my recollection is correct. But, unfortunately, we had some visual oddities, too, when the parachute was actually deployed. Nonetheless, though, it was pretty interesting. The city timeline result was definitely less good than the GLM52 one was. I mean, it had some sound, and it had some slight effects in the transposition between different eras. It just wasn't really that good comparatively to the GLM52 result and some other ones I've seen. Overall, though, I mean, it was competent enough. Everything worked. There were some different sounds between the eras. There was changing of building heights and then things that were on the roofs of the buildings, as well. And then, it had a very optimistic and futuristic outlook of the year 2055. So, hopefully, this is kind of what we can look forward to in 30 or so years. Then, we had our V8 engine test, which was just done so fast that it was quite impressive. The overall result was not perfect, but it was more or less in the style of a V8 engine, and it did include the hole for the 280 motor, which was interesting to see, as well. And it did fix it rather quickly when we told it the motor orientation was incorrect. So, just cool to see in a different sort of test, which brings me into the other different test that we did, which is fortunately not something that I can show once more, which was the keyboard backlight fiasco, where it just ended up actually adjusting the backlight for the system. So, it did show some level of being being able to work with like a lower-level accessibility system hardware. It just wasn't 100% on the ball with that. And the entire cost of that test was 43 cents. So, basically, everything we saw done today for the entire duration of this video was 43 cents. So, with that, that is going to conclude our first look and test of Tencent HY3. I do want to just make sure one more time that this isn't on open router now, cuz that would open up a lot of ease of use for folks. Oh, of course it is. Of course it is there now and it's free as well. That's great. Well, nonetheless, you can now go play with this for free as well on Open Router, which I would imagine will increase the amount of interest in this model. So, with that any questions, feel free to leave them in the comments and thanks for watching.