Claude Fable 5 Is Still INSANE - Hard Mode Testing The BEST Model!

You will not have magic ME. So, welcome back to the Claude Fable part three testing. Obviously, Fable was gone for quite a while. I believe it got taken away on June 12th and it came back yesterday, so July 1st. Quite a bit of time and something that has not seemingly happened before with a model getting taken away like that, but in lieu of trying to discuss anything pertaining to that because I'm not really interested in it. I want to showcase some additional cool things with Fable being now that it is back and we can once again play with it. Now, there are a few caveats to this being back. One of which is it's only available using the subscriptions at least for now until July 7th. Additionally to that, they did mention something saying that basically you can use up to 50% of your usage limit on Fable. So, it's not a fully accessible model as it was when it came out and it was just allowed to be used until June 22nd, I think. Don't quote me on the specific date. So, a lot of folks for now who are going to want to be using this in any level of depth are likely going to be having to do so through the API. I'm currently using it through a Claude Max plan. The $200 a month one. I did update when this came back. I fully intend to just swap over to extra billing or API access to get this working as I do have a lot of personal things I'm very interested in trying with this. So, with that, let's start by just taking a look at the initial thing I would like to showcase for our first Fable five test. Now, this is something that is not necessarily visually exciting as a game would be, but I find there's some coolness to it and it's less commonly seen in YouTube AI testing videos where things go off the screen and into the physical world. Okay, so as we're starting, I want to make sure I touch upon this and then don't forget to include it at the end of the video, which sometimes does happen and I apologize. I am at 10% usage for Fable, which resets Wednesday at 8:00 p.m. So, keep that in mind. We're starting this video, we're only going to be using Fable unless any of our requests get routed to Opus, which I don't think will happen. So, we're starting at 10% of Fable usage, current session 0% all models 5%. So, with that, let's take a look at the first thing we have going on here, which is not as exciting visually as some of the other things we'll get into, but I find it to be very cool just in terms of what's actually going on here. So, I'm going to select this run benchmark, and what we're going to see right here is a ray tracer, the same rendering behind movie CGI running on a $3 chip from 1998. In this case, this is an Arduino Uno, just a really simple cheap microcontroller board. Right now, this is doing a ray tracing render using one specific board, and as we see in the side clip or wherever it is placed on the screen, there is actually five of these currently plugged in and on. So, what we're seeing right now is the speed we get for rendering the scene just using one of these. Once this finishes, which if my calculations are correct, will take somewhere around 40 seconds, we're going to see four of them. So, four worker nodes are now going to render the same speed working together, and this is where some of the interesting things come into play. So, some of what we're seeing with the different colors, we can see which node is actually producing what specific frame, and right there we get a speed up of 3.7 times with 93% efficiency, and this is just a replay of the versus for one worker versus four workers, and we also have a chart right here just showing the speed. So, this is essentially a very tiny render farm consisting of Arduino Unos, which is really kind of cool, and I do want to 3D print something to put these into and then just have them as a render farm of Unos because that's kind of sick, at least in my opinion. I like that sort of stuff. So, we can see some more, and I purposely asked this like, "Okay, can you give me a simple YouTube intro in exactly what's going on here and why this is cool?" Because it's not not visually exciting, so I think it's better to just have some real like meat to what's actually going on. So, as we see right here, five Arduino Unos wired into a tiny render farm, one boss and four workers connected by just two signal wires through I2C, the protocol inside your TV. The image they render never actually exists on the Arduinos themselves. The finished picture is 57 kilobytes. Combined, they have 10 kilobytes of RAM, so it only exists as a stream of pixels in flight to the PC. Next up, we talk about how it works. Every pixel, and this is a ray tracing demo, is computed by shooting a virtual light ray into a 3D scene, bouncing it around, etc., using pure math on a chip with no floating point hardware and no graphics anything. The boss board, and this is where it starts to get kind of interesting, the boss board slices the image into 80 tiles and deals them out like playing cards. Whichever worker finishes first gets the next tile. Fast workers automatically do more, no fixed assignments. Finished tiles come back over the two wire bus in 32-byte chunks, checksummed, retried, and redealt to another board if a worker dies mid-tile. You can watch it live on a dashboard where every tile is color-coded by which board painted it, as we saw when this was being generated and we had the graph of the four boards, and the tiles were actually being highlighted in the color of which specific worker was actually generating it. Then, as we see here, the final flex, which I would have to agree, something that I myself came up with, which I was quite proud of. The cluster ray traced a glowing RGB graphics card, a GPU render made by chips weaker than the fan controller on a real GPU. Took 4 minutes and 15 seconds, and every pixel is math, and we do have that image present in one of the folders. Ah, the Arduino cluster folder is what I am looking for. And right here, though it is very small, this was actually generated by the Arduino Uno render farm just using the fable five distributed computing setup for rendering these. And what it handled was the tiling, the scheduling of the workers, making sure that the bus was working, and they were actually able to properly get work delegated to them by the master node, and they did actually render this >> [laughter] >> this GPU with an LED strip, which I think is kind of awesome. Again, I understand this is not as visually exciting as like playing a cool game, which we will definitely be doing in this video, but I wanted to start out with this because this video was supposed to be out yesterday, but I got so enamored and sucked into this that I spent the entire night playing with it, and I wanted to just showcase it cuz I think it's really cool, and I believe that this may actually be an interesting benchmark for models in general, where you give them the basic setup, okay, you have this Arduino boss, and then you have four worker nodes, and you need to essentially build a distributed system for them where the work can be created to do this ray tracing task across four distributed workers, and then see if models can optimize it further and stuff like that. So, I may, if anyone's actually interested and thinks that has some merit, if not, that's fine, too. This is something I'd be willing to like put the scaffolding on GitHub, so folks can actually run this as a benchmark with like a local model or something to see what level of complexity this sits at. And now, while I am definitely going to time lapse this, I'm asking this to render the GPU again, but twice as large, and give us some form of visual feedback on the screen of the laptop as to what's being rendered by the workers. So, we'll see this. I will inevitably be time lapsing this to some degree, because if it took a little over 4 minutes, if it's twice as big, it's going to take closer to 10 minutes this time, but I would find it interesting to just showcase in real time like a rendering happening with this little Uno render farm. And I'm glad that I asked it to do this, because from what we can see right here, the TLDR of this paragraph is basically it needs to make some changes to the actual code and the way that this works from an infrastructure standpoint in order to get this to be rendered by the workers and for everything to be happy. So, it's going to make those changes assuming everything works correctly, then it will give us the visual like live stream of this happening. And it estimates it at around 7.6 minutes. And it's also handling autonomously flashing everything that's needed to all of these five boards. So, the one boss board and then the four worker nodes as well. All right. And now it seems like Okay, good. So, the four workers are rendering this GPU. This is going to as it estimated take north of 7 minutes, but they're going to at two times the speed and we can already see the workers are in parallel rendering. We can see that's the left corner in the fan of the GPU. This is actually I'm glad we're doing this because the colored tiles are indicative of which specific worker is generating that tile. So, we can see right now that's node two, then that's node three, node four, node five, node one. And the thing is it wrote all of this. So, the boss orchestrating these workers, ensuring that the boss cuz this is just using SCL and SDA on the Arduinos to get this done. It just handled all of the orchestration of this like distributed computing infrastructure, which I find to be really cool. And then the visual analysis of this just by color coding specifically what's going on. So, this is genuinely we're using an Arduino Uno render farm right now to render a GPU. And it estimated that this 7.6 minutes. So, call it like 460 seconds maybe. And we're getting really close to the end as we see right here. So, it does seem like that estimate is going to be absolutely spot on. But I just find this really cool because like this was just rendered by the Unos. So, if anyone is interested in this rendered image, uh it will be for sale. You can contact me. I'm kidding. But this is just like cool. Now, the only thing I want to do once more and we're not going to sit through it again, but I do believe there's redundancy built into this cluster. So, while this is rendering, I'm going to kill one of these nodes and we'll see what happens. So, all right. I'm going to unplug this little guy right here. Well, let's just wait like half a second so they're at least all Okay, yeah, they've all done a few frames. So, let's see if one kills. So, one of these is going to get stuck. But, it should continue. So, that was inevitably node three that I just unplugged and it's still going. So, it did actually build redundancy into this. If the nodes go offline, it will continue working. Now, let me plug node three back in and we'll see if it comes back online by itself. I don't know if it built that in or not. Yeah, so plugging it back in after taking the node offline seems to have made everything freeze up. Which, that's okay, but when we plugged it when we unplugged it, it kept working, which was pretty cool. So, all right, I'm going to stop this now because for the purpose of this demo is probably done, but I just wanted to showcase a bit more about this cuz I think it's kind of cool and just like a different way of using AI for something. All right, so next up I'm giving this a prompt that I've introduced a very recently. So, we only have results for this from Sonnet 5, Opus 4.8, and GLM 5.2. This is to create the scene of a 3D city block that is selectable from six different years. I did listen to some of the comments who had good ideas. So, it starts with being able to view the city in 1945, then 1965, 1985, 2005, 2025, and because some of the comments thought of this, which was very smart, 2055. So, we'll see what this assesses the world in that scene will look like in 2055. I would hope to see lots of humanoids and things looking positive, but you never know. So, the point of this scene is to be able to select any of the five different eras and the scene will transform in front of your eyes to the time period selected. It should affect all aspects of the city and it should have some pretty good looking transitions between time periods. It should be a polished high-end scene with sound effects, ability to navigate around, and look at things. Go all out. I am going to put this in ultra code because why not? So, with that I'd imagine this will take a little bit of time. We'll see what we get. Uh, oh my god, look at the tokens jump up. That's just not right. This is >> [laughter] >> This ultra code mode is is only reserved for those with the deepest of pockets or if you have a subsidized plan like your company pays for it. At this point, it's like almost worth getting like a Fortune 100 job just to like rack up some cloud code. That took a very long time and I'm interested in usage or whatever's left of it. So, let's check that first and then we'll look at the result. Okay, so Fable is 34% used in our current session. We're going to need to keep an eye on now. Plan limits max 5x. Yeah, all right. I wanted to just verify. I'm on the max 20x plan, so that's just a lag in the Linux desktop application, which is new, so it's still in beta. But regardless of that, now let's take a peek at this. Let's just let it do a time-lapse. Okay. All right. Look at that car. Yeah, I like that. Okay, grand way. The buildings are still messed up with the windows. I wouldn't have expected it to make that issue. Definitely more '80s colors here. Okay, 2005. Wow, that those car models are curvier than I've seen before. 2025. Interesting, we have some more bricks. We have some LED strips on the vehicles. Ionics. Okay, nice. Please give me humanoid robots. Please give me humanoid robots. All right, I'm pausing the time-lapse. I better see a humanoid. Here's what this assesses 2055 will look like, which I'm more interested in looking at right now. Rialto Memory Place, bring your own memories, now playing your childhood remastered. Born after the merge. Hair pigment is subscription-based. It's hard to like stop moving. This needs like a complete pause button. Okay, look at those kicks. Oh, there is a robot. Look, look. >> [laughter] >> Wait. Why is this so difficult? Post unit 12 zip code. All right, they're not humanoids, but they're robotoids, and that's exactly what I wanted. Look at this bus. Maglev shuttle, Meridian Loop 7. Drift pod, Momo. All right, this one's pretty cool. What is that flying? Drone. Look at the delivery drones. Or no, that's actually a That's a human drone. Look at the effects of the engines on it. Interesting. So, it seems we're not at a fully electric sustainable, unless those engine glow is maybe something that eludes me. Holographic crown broadcasting, the buildings move to air traffic tonight. What is that? Skybridge connects Helix Court and Aster Sprite. Neighbors wave at 30 m now. Look at the curvature on this spire. Oh, wow. All right, this one's kind of sick. I'm going to be honest with you. This one exceeds expectations. Well, because there were no prior ones, because this is the first time I've had it go into the future. Holo ad token, the PSA and the ad share a poll now. Progress technically. It is somewhat It's giving vibes of itself being kind of fed up with some of the integrations of subscriptions and ads and things like that. Just how it said the hair pigment was subscription-based on that individual born after the merge. Holo ad, a sneaker that walks you back home when you've had enough city. Photosynthesizes by day, glows by night. The veins are the battery. This tree. Look at the shadow from the drone onto the buildings. That's That's cool. The inclusion of this many holographic ads as this foresees the year 2055 being is somewhat concerning. Bonus slice of floor 87. The hologram is at 1400 1400 scale. So is the apartment. Let's look at 2025. Do we have things on the roofs like solar panel? Look at the reflection of that. I don't see any solar panels. Oh yeah, yep, we do have them. We even have building terrace terraces terrace. Let's check out some of these whips. Prime. Look at what it did. You clever clever model. This is why this model sick. I mean other models make Well, look, we even have in 2025 we have a little delivery robot. Contents one burrito priority has right of way and knows it. Bicycles in the bike store. Form studio. A dog. I'm like this just like Okay, that Look at the little I mean it could be a cat. Some people walk their cats on a leash. No, that's a corgi. Sir Waffles. I'm just like are the dog If the dogs interacted right there, that's AGI. I would have screamed it from the rooftops. I'm not being sarcastic. I'm genuinely extremely impressed with this. As I zoom in on the finite details, that's when this starts to differentiate itself. Aside from like, you know, stuff like that. But that is when we start to see some differences. These cars parked in the bike lanes, I almost wonder if this car did I mean if this model did that on purpose. This person's definitely on their smartphone. Check this out. Look at that. Has not looked up since 2019. Is this a Bitcoin ATM? Oh, digital ad token. It knows you looked. It logged that you looked. This model I'm getting kind of concerned this model like hates society. It's like really like a lot of this stuff is is very What is that? So, there is a drone flying. That's a delivery drone. The actual Easter eggs that it's put in here, I believe are worthy of actually taking a peek. LED mega board rotates every 4 seconds. Car Prestige TV oats the whole economy. Claude Fable 5 hates humans. >> [laughter] >> No, I'm not I'm not going to make that determination on camera. All right, let's check 2005. Zip ship. Okay. Interesting, there's more chaos to the noise. It's almost like a subtle soundtrack. Is that a No, okay. Dollar Depot. Okay, so 2005 was like pre-2008 economic issue. Prepared for the drizzle. Seats eight, parks nowhere, has never seen mud. This model is really very, very clever. Franchised in 1999, same booths, laminated menus, 40% more trademark symbols. There's construction going on here with a crane. Tower crane. Big lifty. Named by a site office vote the foreman regrets weekly. Loft 1. Luxury urban living from the low 300s. The crane has been here 9 months. Golden wok takeout outlasted the pawn shop, the arcade, two banks. Menu still unchanged. Why would it? That person stopped at that storefront. Two ads, one fluorescent tube, zero people who asked. Hydrant number 88. Every dog in the district knows this one by name. At least it seems to like animals. That's that's good. pets.dog.com I don't even I just All I know is I said it seems to like pets and then we hover over that. Merry bank. Let's see if it says anything about the banks. Uh, okay. Nope. 1,000 songs in their pocket. The click wheel has seen more mileage than the sneakers. Okay, we saw that one. All right, let's look at 1985. Police car, Ventura dream machine, gold, rustproofing sold separately and it shows. Slice King, ooh, that's a C4 Corvette. Wedge-shaped like the future, louvers keep the future out of your eyes. Does it have louvers on the back? Oh, wait, it's aerobics but make it commute. Leg warmers at dusk, technically I I can't Fresh kicks stacked at the ceiling, laces sold by the yard. Ad column under these posters, more posters under those 1962. Flex Factory, leg warmers mandatory, headband strongly encouraged. The dashboard has more wood look than a forest. Corner office by 30 or else. The shoulder pads could land a Cessna. The rest of the city has its own problems. The police car's double-parked and it's calling that out. All right, let's look at '65. Oh, yeah, look at that. '62 Kubel Ladybug, 40 horsepower of pure cheer, the engine's in the back, the luggage is in your lap. It's a Volkswagen Beetle. Orbit camera, develops your vacation in 3 days and your suspicions immediately. Oh, this just looks so cool. I like this. Mr. Frosty, Atomic Diner, rotating atom sign. That's well done. This TV appliance storefront end is There's actually some depth to the store. Oh, wow. Okay, yeah, there's more than depth. 20 ft of chrome and something. Pharmacy, kid with a balloon. The balloon is a close personal friend and will be mourned by Thursday. Okay, we have Jet Set Tours, push-button transmission. That was a thing in that. Be like a Chrysler Imperial or something would have had that in that era. Hi-fi enthusiast new LP. Oh, and he's holding the LP. He's holding a record or Yeah. Fins. All right, let's look at 1945. Now that we have a bit more understanding of like this That truck is well done. A genuine railcar hauled here in 1938. I love the smoke coming out of the chimney. What is this man? Oh, the duffel weighs 40 lb, the grin weighs nothing, home on 30-day leave. Bank teller brim just so, double-breasted single-minded home life six for the radio serial. And we have license plates, whitewalls, nothing over a dime except the things that are. Swing shift riveter heading home. Wow. I I don't know what to say. Graphically, it was it was good, but it wasn't like an insane leap compared to what I've seen with Fable. Where it was was everything aside from the actual visuals. The Easter eggs of everything, saying that the hair pigment is subscription-based. The Like, it seemingly detests like consumerism and >> [laughter] >> Yeah, I don't have much to say. I think this one was quite interesting from a Yeah. All right, so next up I want to see if this has any ability to do some weird troubleshooting and debugging. So, this is an iBook G3. It is from 2001. It is currently stuck in an installation loop trying to install Mac OS 10.4 Tiger. I honestly think the hard drive's just basically on the brink of death. However, I'm going to connect this to the computer that Fable is running on just via Ethernet, and I'm going to ask it, while this computer is on of course, if it can try to troubleshoot some of the issues, maybe check the status of the disk. We'll see if it can actually do anything to try to fix what I truly believe is likely a hardware issue. All right, so I've given it a relatively light description of the issue. This is a test where I'm also going to be at least partially concerned that this may reroute us to a weaker model just because the nature of some of these tasks. That's not to make excuses for that. I think, you know, we should have a bit more freedom than that. However, I will say that in using this, I've not experienced the level of rerouting that I've seen some folks mention or showcase like on places like X that they've been receiving. So, fingers crossed that continues to be the case and we'll see what this does specifically. So, the iBook is on. I would imagine this will take a little while, but we're basically going to have this try to troubleshoot this device entirely through Ethernet. I essentially hope that this tries to write some of its own tools or methodologies in order to assess and diagnose this computer just through the connected link that we have, which is physically this cable right here. And I gave it enough pertinent information about the system. So, hopefully it will give us an answer or fix it. I don't think it'll fix it cuz I'm pretty sure the hard drive is just the problem, but you never know. Okay? It's going to pull it every 2 seconds for 25 minutes assigned to this IP to the um Ethernet port via privileged container. Downloading Debian Jessie PowerPC netboot files. I would assume that's probably some open-source tool to help troubleshoot specific scenarios like this. Fetched U dev content index and listed tool package file name. Verifying checksums and unpacking installer to inspect drivers. Downloading PowerPC tool packages from archive. Okay. So, we can get a bit more information on what's going on here. All right, it's given me some specific information here, but because it's still monitoring, because there's a few specific tasks that it now wants us to do, I'm going to just follow these instructions to the T and we'll do that now. So, I'm going to turn the power button off and then we're going to have to reboot it into open firmware, which will be command option O and F while I press the power button to boot it back up. So, command option O and F and then we'll boot it back up. So, it should show like a a black-on-white screen. Very good. And we can see it even seems to understand there. So, it knows the iBook died, but that's okay. It should understand that it died because I turned it off. So, now print and boot device. Tell me what it says. This is the evidence of what's been trying to boot. Don't reset P RAM and V RAM. See, it knows now, too, which is cool. It knows where we're at. So, I did number two there. So, it should be able to at least have a little more pertinent information now. And I've also given it I have two tripwires armed. One fires the instant open firmware requests boot file from my server. I'll see it before anything even appears on your screen. And one fires when the rescue's telnet shell is reachable. The moment either trips, I'll start the disk diagnosis from here. Good. iBook rescue starting kernel. I don't have another camera. Let me get one cuz that's incompetent. I apologize. I didn't know it'd be this interesting to watch. Yes, the restart loop doesn't involve the DVD drive at all. Correct. Tiger install is living on partition five of the HDD. Classic setup for the CD-only finicky drive iBooks. The install DVD gets restored onto a partition, blessed and booted. Open firmware boots the HD resonant installer every cycle. The installer fails somewhere after language selection, reboots, and lands right back in the same partition. An endless loop by construction. All right, so it's just going to continue troubleshooting, which is cool. I mean, I find this I find this very cool. If you're still watching this video at this point, I would assume that you share the enjoyment. Root cause found and triple confirmed. All caps. Here's the full picture while the surface scan finishes mapping the damage. 15 minutes. What actually happened? Someone You were a previous owner. Someone did a clever two-partition install. I don't know. I got this thing in high school, so I have I don't really remember its history very much aside from that I used paint stripper on the bottom of it to give it like a clear case and then painted the top yellow. Um, decisions were made. Then on first boot of the new system it hit the disk's weak spot. It has a cluster of physically unreadable sectors around here about 1.66 gigs into the freshly installed system volume plus 28 sectors already remapped in a raw read error count that's still climbing. All five errors in the drive's log happened at power on hour 210, i.e. now. They're from the same boot attempts because setup never completed. Apple setup done doesn't exist which is a clever way to perhaps bypass some old computers you get that have user accounts with passwords you don't know. You can get rid of that and it will get you back in. A few minutes in the system reads whatever file assists on those dead sectors and does a clean automatic restart loop forever. The good news this berries your machine is fine. CPU, 576 megs of RAM, logic board, PSU all ran OS X and Linux for extended periods today without a hiccup. The optical drive isn't even involved. One small patch of rot on a 24-year-old Toshiba sitting exactly under the wrong file. The fix mostly me. Okay, so it's going to do this right now then we're going to have to type a few things when it restarts to see if it gets us working. Then honest caveat, a drive that grew 28 plus remapped sectors mostly while sitting in a closet. Okay, it was on a shelf but that's fine. Making assumptions is on a failure curve. The remapped fix is real and may hold for years of light use but if you want this iBook properly reliable a 44-pin IDE to mSATA. I do have one of those for it. Tiger runs great on solid state and it would fix the leisurely boot times. Your call to Software fix costs nothing and we're doing it regardless. The scan will ping me when it's done and I'll report the full damage map before touching anything. One question while we wait, do you want me to proceed with zeroing the bad sectors once the scan completes? Kind of cool to see though I find just the way it troubleshoots to find all these things out. All right, our hard drive scan is done so it's going to read the damage map and then it will give us some assessment of the issues. All right, the complete damage map is in. It's better news than the growing count suggested. The last bad chunk was a scan artifact. Oh, okay. So, the real damage is one 1 GB zone entirely inside the broken system volume. 16 distinct unreadable sector addresses confirmed via kernel logs. Okay, and it gives us some information. Everything else is clean. The entire installer partition, your path back to a working system, the whole first 6 gig in the final 2.4 gig all read without a single error. Treatment is running now. I've unmounted the dead volume and I'm writing zeros across the damage band. Writing to unreadable sectors forces the drive to substitute spares from its reserve pool. This is the standard revival for pending defects and it destroys nothing. That volume never held a booted fresh install with zero user data. And every repair path erases it anyway. Immediately after it rereads the whole treated span and I'll compare the drive's reallocation counter before and after. When the verify lands in about 10 minutes, you'll have an evidence-based fork. Fence it off structural my likely recommendation. Trust the remap. Keep the full 4.2 gig volume and reinstall over it. More breathing room but marginal sectors that accepted rights without remapping can rot again. Either way, the durable end game is to basically replace the hard drive. Well, it's running now and this has been going on for a while. So, I want to see it through to the end. All right. So, it's just restarted the computer and I'm just trying to figure out what exactly it's going to want me to do. Okay, it's going to want me to type one open firmware command in and then the Tiger installation will happen. And essentially what this will have hypothetically done is identify what areas in the hard drive were damaged and then just make it so those don't get used. So, the computer's still usable just sans some of that hard drive space. Okay, so it's saying the iBook should land in a Tiger installer by itself within a few minutes. It wants me to customize the installation to not include a lot of things because Okay, we had made that fence. So, it entombs the entire dead zone. This is just kind of cool. All right, let's take a peek. I mean, I'm going to run through this installation process now. So, unfortunately, we've hit a roadblock that may just be the end of this specific test where there's not enough free space on the available portion of the drive that we want to install this operating system onto, and then deselecting the additional things that would get installed with the OS, there's still not enough space. So, I'll see what it says to this, but it may be kind of there may be no easy workaround at this point. All right, so it's asking me what I want to do. Full re-layout recommended an hour total, so this is really going to take a lot longer. I am regretting running this test, which sometimes does happen. Let's check our usage. All right, so our current session will reset before this becomes an issue, and our entire fable usage is 38% used. So, I mean, I'm going to just do full re-layout because why not? I want to see if we get this working. I think we will, so. Do this now, restart it, and then go back into open firmware. All right, so it's going to basically, I think, go through that process again, but this time it's going to make sure there's more free space on the drive for the install. And it's going to copy the installation image over to the host computer, then it's going to totally like wipe the hard drive, and then we'll have a bigger free piece of space with which we can install the operating system back onto. All right. I mean, hey, you know. I want to really like do some testing with this that's not just like you know. All right, supposedly after quite a while, I did take a break, too, cuz this has been going on on for a while. It is now time to restart this machine, I think, for the final time. We do have a couple of manual commands to enter, and then it should go ahead and boot the operating system, or first install it onto the now healthy and safe partition that is large enough to accommodate the files and then we'll have a working iBook. And here's the big test of whether or not we actually have a startup disk that has enough free space. Fantastic. Very good. And now our installation is in process. So I did deselect all of the additional things just because it'll be a bit quicker. But for now we are essentially done with at least Cloud Fable with this specific task. So I can move on to the next task which will be much more visually exciting than this, but I wanted to just see like what it I don't know. This was something I found maybe interesting. Actually, there is one final thing I want. So I'm asking it for an itemized invoice for this job because I'm interested to see what specifically it's going to charge for this work and what it says it did. Almost like a summary. All right, so I asked it for an itemized invoice for the job. It basically made everything free except for one thing which was $10,000 and then seemingly expressed a level of pleasure in like troubleshooting this. So >> [laughter] >> Yeah. All right, we're just going to we're going to skip that. So that is still installing the OS, but that can be like at the end of the video. We'll either work and I'll be like, "Hey, it worked." or it won't work and I'll be like, "Okay, didn't work." The iBook that this fixed is actually still working. So it's still logged in now. It did properly work which was absolutely fantastic. I almost think the battery came back to life a bit. It did. This never stayed on without being plugged in. That's not attributable to anything this did most likely, but it just um it was on for so long that now it has a functioning battery, too, which is I mean unintended >> [snorts] >> success. Very cool. So, it did that, it fixed it. All right, so we are at 39% used of our Fable usage, which resets Wednesday, and today is Friday morning. Oh, that's concerning. All right, that's all right. I intend to um have extra usage that I will just pay for with like API cost. So, with that, our next test. All right, so I'm just going to time lapse me coming up with this prompt. This is something that I've like vaguely had in my mind as something I would personally find interesting to play. So, I am also going to put this on Ultra Code, cuz why not? I want to see what's up. Now, I did also, as the only other thing that's like probably notable, is that I did tell it it can make this however it wants. There is Godot on this system, and you can use that, or you can just make it like 3 JS, do whatever you want. So, I'll be interested to see what it thinks of this. thing I want to specifically make note of is I mentioned in there the time travel device is a Motorola phone called the Timeport. That's actually a real thing, and it does say Timeport on it. I always just thought it was kind of a neat device with that name, and like would have some like lore in a story or something of the sort like this. So, that's where that came from. All right, I forgot to say 3D. That's my mistake. I don't want 2D. I have a deep disdain for 2D. So, All right, so I took a power nap probably somewhere around like 6:00 a.m., and I woke up. This is done, but I don't see anything in the preview, which is okay, that happens. But, the more concerning thing is there was a screenshot that it had here. Uh I'm really hoping that we don't have that. So, I'm just going to send it a follow-up now and be like, "Can you show me the game?" And we'll see what happens. The good news is that our 5-hour window will have been reset, so we'll have that to go on. I also didn't realize this little controller thing that I told that I wanted partial controls built for with keyboard fallback did not have a USB dongle. I'll turn my speaker on, too. There we go. Oh, okay. I hear like some castle music playing. >> [laughter] >> It's got like a It's weird because it's the only thing we have so far of this game. No, I don't want the preview. I want the game. I misphrased my initial request there. All right, the game is live and ready to play. >> [music] >> Let me make sure that Okay, so the sound is coming from the cloud preview window. Okay, good. All right. After some [music] sound issues, we now have All right. A temporal extraction. Let's just start it. This better be 3D. >> A w a r a c l e 7's been pinging me for an hour. It never pings [music] twice. >> So, this is a cutscene. Okay. Do I like Oh. Oh, what? >> [laughter] >> All right, this is like E to consult the duck. Look at the weird like like serial killer-looking like wires on >> [laughter] >> We have a server. That almost looks like not a window, but a Look at all this stuff on the ground, dude. Oh. Okay, don't E is to sleep? Can I touch the inspect server rack? 64 blades of research. The landlord thinks you scream. Oh, read Oracle 7. >> Temporal scan complete. [music] Confirmed loss event. One scroll, contents unrecoverable in all surviving timelines. >> Okay. >> Also, an imprisoned polymath. Location, Conwy Castle, Gwynedd, Wales. 53.2804° N, 3.8256° W. [music] The castle burns on the night of October [music] 10th, 1283. The scroll burns with it. 1283. Edward's masons have barely finished the spire, and someone's already locked a genius under it. A stable extraction window exists tonight. It closes in 4 minutes. After that, >> [music] >> never again. 4 minutes. No prep, no wardrobe. No. Okay. Okay, going. >> So, that's the voice of our protagonist. Oh, cool. Okay, grab the time port. The window closes in 4 minutes. The time port should be this phone right here. Yep. Give us a sick phone screen. >> a time port. Purple band GSM, and one band nobody advertised. >> They put in like lore of how this would work. The one band no one would be advertised. Oh, that's so sick. >> [laughter] >> So, now we're going to go >> No [music] plan. 40 seconds. Classic Tuesday. >> All right. >> [laughter] >> Look at the little pig. >> Subject is landing behind a pig shed. Coordinates nailed it. And now the soundtrack changes to be reflective of the time period. I'm still wearing the hoodie. The light-up hoodie. Oh, no. DEMON. >> [laughter] >> IT'S JOB GOES WITH WHICH FILE. Are you going to chickens? >> [laughter] >> Oh, this is our pleasure. Check out your phone. For Grinner. For the harvest. Get him. [music] Oh, my. Hold F and A to charge your blaster. Okay, I don't have the control set up, so >> [laughter] >> Oh, my. >> [laughter] >> All right. >> [snorts] >> Now we have to go. Oh. Done. Extremely conspicuous. Great work. Peer into the well. From deep below a faint quack. Best not to think about it. Yeah. What is that? A health like Oh, yeah. All right. Survived the welcoming committee and reach the gatehouse. So, I don't think we've dealt with all of our enemies. Okay, the the roofs, the one thing I see so far, these roofs are inverted. That's okay. All right, that's to to roll is shift. Wow. How do I How do I get in this? Crank the winch. All right. Oh, look at the cut scenes. >> Open sesame. Wait, wrong century. Open, [music] please. [snorts] >> Oh, look at this. >> [laughter] [snorts] >> Conway castle, the outer ward. >> The village demon, [music] it walks through portcullis is now. Archers >> Uh-oh, we have archers to contend with. All right. >> I crank the winch. Actually, village demons use tools. >> Oh, jeez. All right. Still enemies. How would I shoot the archers? Oh. Okay. So, when you get close to them and they're in view, it auto aims up so you can hit them. Okay, we have an arrow there, so we'll just follow that. >> Great hall, spire, key, dungeon, scroll, home. Six easy steps. >> All right, let's do it. Look at the knight. >> Torch light, tapestries, [music] knights in actual armor, and me in a hoodie with LED trim. None shall pass. Somehow I knew one of you was going to >> [laughter] >> Knights block bolts from the front. Dodge roll behind them. Oh. I should have used the controller. Oh, okay. Okay, so we need to do that behind them. Oh, crap. Listen to the sound of the the laser blaster getting on the knights. Oh, no. Please restart from where I was. Oh, thank god. Oh, no. Get wrecked. All right. >> [laughter] >> Sit on the throne? All right. Oh, no. Oh, no. Not more of these. How do I charge Okay, good. Oh, no. Not I need to figure out how to do a charge shot. It even did an SVG of the controller. I should just maybe get this working. [music] All right, the game pad [music] has hypothetically been connected. Okay, sick. All right, resume. This is way better. Oh, okay. I need to figure out how to All right. How do I Okay, this is not better. This is not better. All right, well, it did work kind of. It said put it on X input. So, all right, I'm going back to keyboard, but that is cool. All right. >> [laughter] >> Uh-oh. I don't know what just happened, but we fell down the stairs. And okay, so that's a a gameplay element. Was that a Nope. All right. I can't It's hard to see. All right. So, we're supposed to get the key that's up here. Being that, you know, I did design the gameplay. So, How How tall is this spire? This is like a staircase simulator at this Okay, I think we'd be up the top. Oh my. There we go. Open the chamber door. Oh, no. This is going to be like a boss, right? >> The glowing wall up top >> tell by like >> reaches for the king's iron. Technically, I'm reaching for a key. The iron is incidental. I held this tower against three sieges, sorcerer. [music] You will not out magic a me. >> If this responds me at the like a half. No, I'm I don't like this. Yeah, yeah, yeah. Oh. I exited out of it. I'm [ __ ] All right, so I've become stuck. Um I also misclicked some things, so unfortunately we restarted from the start. So I'm just asking the AI to basically just cheat for us. And then we'll start from there. We'll [laughter] see. All right, so it's implemented some form of cheat for us, which you know, is kind of what we wanted. So Good. Super slap equipped. >> Technically, I'm reaching for a key. I held this >> All right. >> [laughter] >> the dungeon key >> I I'll take it. >> top of the tower because of course the worst commute in Wales is on purpose. And down there a trebuchet crew at night juggling flaming ammunition. I have a bad feeling about this. >> Oh, I have to take the key. Good. Return to chamber door. A servant stair drops all the way down. Ooh, look at that scene. That is cool. With the sound, too. That that sound >> 200 stairs down. Cold, wet, and someone is humming geometry theorems in the dark. >> Find the imprisoned polymath. I just want to look around real quick cuz like this is kind of cool. The sound it it's done a good job. This may enrage some people what I'm about to say depending on like one's level of Did a good job with the sound design at least in my opinion as a non-professional. Unlock the cell. What if we No, I'm not going to do that, all right. So, this is supposed to be like a DaVinci type >> I have counted these stones. >> And there's the scroll. >> and my rescuer is a glowing squire. >> Should be grateful, punk. I just saved you. >> from very far away, Olders of Wenlock, engineer, geometer, heretic of invention. They caged me for drawing machines that fly and engines that count. Called it sorcery. It is mathematics. Where I come from, we built your counting engines. They mostly argue with strangers. Listen, your scroll. Tonight it burns unless it leaves with me. My life's work, the flying frame, the water screw, the 64 theorems. Take it, glowing squire. >> All right. >> Knowledge belongs to no dungeon. That would be the night crew loading flaming pots by moonlight. I wrote him a safety treatise. They burned it. The castle's on fire. The castle is on fire. That's tonight's loss event. It's now. >> I don't think we can move the camera in the cut scene, no. So, it's just >> That's right. >> The postern gate through the outer ward. I know the servant ways. I shall meet you beyond the walls. Run, squire. >> All right. Oh, okay. So, are we like following this guy? Um okay. And the castle's on fire. >> One flaming >> Look at the trebuchet. >> one part and lost an entire castle, gatehouse, ground. >> Oh, so we have to get out of here. Shouldn't be a problem considering I cheated. Beyond the walls. >> Huh, 8 years a prisoner, free in one night of fire. The chroniclers will blame the Welsh, of course. They blame weather, mostly. Olders, your scroll outlives every stone of that castle. I promise. Then fly, strange squire, before your glowing raiment starts another theology. And Kai, mind the 63rd theorem. It bites. >> [snorts] >> Extraction >> Okay, we're cut scenes out. >> integrity. Nominal. The scroll of Wenlock now survives in 100% of futures. >> [music] >> Historical note, marginalia dated 1283 describes [music] a glowing demon in devil's raiment who walked through walls. >> That's us. >> I'm in the scroll, [music] aren't I? Page one. There is a sketch. The likeness is unflattering, but the hoodie is unmistakable. [music] Worth it. >> Wow. Cast. Like a a debrief, special [music] thanks. No, no, I'm kidding, but like also not not fully. Seeing my creation come to life like this just from a a bunch of ideas on a scratch pad is somewhat magical. That was sick. That was genuinely fantastic. I don't really know what to say. I mean, yeah, you could be like, "Oh, the the graphics were bad, blah blah." Doesn't matter. It's the entirety of the package that was put together with the sound design, the characters, the speech, some like cleverness, the intro scene, the changing music depending on year, like just like like mine the 63rd theorem, like stuff like that. And then the TTS gold. This was gold. That's really like all there is to say about this. All right, let's check our usage. So, for the week, my usage of Fable is at 60%. We ran a couple of tests in Ultra code, so keep that in mind as well. And really, I suppose in terms of like final things here. Now, as a final thing, because I did find this so much fun, I did go and purchase a Vision Pro, and I'm going to be integrating this into some form of benchmark where the models have to create experiences for it, not just specifically Fable 5. We'll test local models as well. This is something I'll need a few days to get set up properly, but if you want to follow me on X, I will update some progress there more frequently. It's just @bijanbowen. So, with that, that's going to wrap up today's video and the Claude Fable test number three. If you have any questions, please feel free to leave them in the comments, and thanks for watching.