right. It didn't like it stayed like in the joking theme. All right. As one of the final things we're going to do, I'm giving this the Chrono City test where it shows the city over a number of different time periods and has to transition between them. However, I'm going to be telling it to do this using C++ and it can't use Rayb. I find it interesting to do this same test or some of the ones that we're used to seeing in 3JS, but instead making the models do them using C++. It makes it more difficult. But based off of the skate game that this made, this may put out like a really stellar result here. All right, our Krono City timeline and Okay, I think we can assess that something has gone quite wrong here. It took so long to do this test. And I also realized that I don't think my coding plan is getting used for this. I think I'm just paying for API. I'm mad about this one. Doesn't this like Yeah. Let's Okay, so here's a bunch of like screenshots that I took from this. Okay. Garbage. Uh 1985. Still garbage. Well, we can look at it this way. 2005. Something went quite quite quite wrong here. Okay. Are you all right? Well, I'm going to just call that one cuz this I've been filming this for like 5 hours. The final thing I had this do was make a proper 3JS mockup of this specific computer right here, an Acer Aspire Predator G7700. The reason these images are here is because I had 56 Soul and Fable 5 try to replicate this front end case so I could 3D print it. Uh, they both did horribly. So, let's just take a look at the You know what? That's actually kind of sick. This makes me so much less angry than I was a few seconds ago because of that city chrono timeline disaster. Yeah, it doesn't look like it. I mean, mainly I think the biggest thing that's frustrating me here is it's the wrong color. But if we just look at this as like a like a computer, it's kind of cool. And we can actually disable specific things of this reset view. Oh, okay. Fan spin LED glow and then auto orbit. All right. Again, not not at all. I I'm not even going to say not quite. I'm going to say not at all. But judged independently just as a computer, this actually kind of sick. This may have to be a test that I keep in in some form or another. And really that's going to bring me to the conclusing concluding thoughts of this very very very long test. I think overall the absolute winner here was this NYC skate game in C++. This didn't use Ray. I mean we got hit by a a taxi cab in this. That's just levels of immersion that I have not seen before. And this was really just like well thought out. When we got too close to the buildings the camera would actually raise up like that so we could still see the player. stuff like that was just truly like well done. And then again, we can like Oh, good. We missed it this time. But this was just so significantly better than I expected. And it was a different prompt. I've never run it with this specific map. So, really well done. Also, that wedding site, it was actually quite good. There was a lot on here and it also demonstrated some creative writing chops just because it had to make the entire origin story for this couple and everything like that. And it had some clever things in here just like the way he proposed which related back to the way they met. It was very clever and nicely done. I did like this. The browser OS again was acceptable. It was actually pretty cool. The GTA game was pretty bad just because the car was capped at like 40 km per hour which is just kind of just just not it. Um what else? I mean, overall, I guess really my takeaway here is the most impressive result by far was that New York City Skate Simulator in C++. The rest of the stuff, I don't know that anything really blew me away. It's competent. It's really good. It's going to be open weights, and that's awesome. But I almost feel like when you factor in the size of this model, I'm expecting to be more impressed when considering the size with the Quen 3.827B that's going to come out in X number of days. So overall, I saw some things here. I would have liked to have seen better results to be honest with you. Aside from that New York City skates sim that was absolutely stellar, but everything else just felt like good, but not great. And at 2.4 trillion parameters, I am kind of looking for great. So at the beginning of this video, I said we couldn't track cost individually because I just had that random plan right here for the coding plan. Yeah, that has its own specific API key. I didn't use that. I use the API key that's just linked to my account that gets charged. So that means we can actually now look at some of what this cost us which is you know things like this happen. I have to say this dashboard is just very very difficult to make sense of and use. It's very busy and very like pain. So the entirety of today's test cost basically why are you showing $32? But that's only show. So, the entirety of this test cost $32. Keep that in mind as well. Um, that's a bit annoying. It's $32. I didn't intend on spending to create this video, especially because my monthly subscription should have handled that. Nonetheless, it gives us a better judge of how much this model costs to use. So, everything we tested cost around $32. Keep in mind, if you do have one of these coding plans, you need to use the API key specific to it, or else you get charged as well. So, just a nice little surprise to top it all off with that. That's probably going to conclude our first look and test of the