Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

The hotel LodgeNet N64 controller now working unmodified on real Nintendo 64 ‘home game system’ with joypadOS. Fully open source, runs on pi pico, inexpensive parts, hot-swappable between SNES, N64 and GameCube LodgeNet controller variants. Convert to USB or native N64/GC console output. Were there millions of these in... show more

Robert Dale Smith

13,511 subscribers

10,249 views • 4 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

LodgeNet N64 and GameCube controllers working on real Super Nintendo!! Straight wire! 🤯 Ends up that the recently dumped, mysterious SNES dev cart rom with a GameCube controller displayed on screen, is indeed a controller tester rom used to test LodgeNet controllers. I decompiled the rom and discovered that it was bit banging a custom controller protocol over the normal controller’s data and latch pins.

LodgeNet N64 and GameCube controllers working on real Super Nintendo!! Straight wire! 🤯 Ends up that the recently dumped, mysterious SNES dev cart rom with a GameCube controller displayed on screen, is indeed a controller tester rom used to test LodgeNet controllers. I decompiled the rom and discovered that it was bit banging a custom controller protocol over the normal controller’s data and latch pins.

Robert Dale Smith

19,447 views • 4 months ago

Ocarina of Time, running natively on iOS and iPadOS for the first time. Not an emulator. Ship of Harkinian has run on Windows, Linux, macOS, Switch, Wii U, and Android. Never iOS. Now it runs on iPad, with iPhone in the build too. The game was decompiled to C and rebuilt as a native ARM64 app rendering through Metal. No N64 hardware being simulated, no ROM interpreted at runtime, no streaming from a Mac. It isn't stuck at the N64's 240p and 20fps. Widescreen, full resolution, 60fps. This game deserves a controller, so controller support is native. Pair a Bluetooth controller and play the whole thing. Touch, keyboard, and mouse work too. I used Codex 5.6 Sol to build the iOS layer. Open sourcing it all below.

Ocarina of Time, running natively on iOS and iPadOS for the first time. Not an emulator. Ship of Harkinian has run on Windows, Linux, macOS, Switch, Wii U, and Android. Never iOS. Now it runs on iPad, with iPhone in the build too. The game was decompiled to C and rebuilt as a native ARM64 app rendering through Metal. No N64 hardware being simulated, no ROM interpreted at runtime, no streaming from a Mac. It isn't stuck at the N64's 240p and 20fps. Widescreen, full resolution, 60fps. This game deserves a controller, so controller support is native. Pair a Bluetooth controller and play the whole thing. Touch, keyboard, and mouse work too. I used Codex 5.6 Sol to build the iOS layer. Open sourcing it all below.

Kahris

1,165,516 views • 14 days ago

"The Nintendo 64 has bad controls!" ... Does it actually? One of the most repeated "facts" about the N64 is how bad its games control, how weird the controller is, and how shooters must rely on auto-aim to even be playable. I think we can see here that's not really the case.

"The Nintendo 64 has bad controls!" ... Does it actually? One of the most repeated "facts" about the N64 is how bad its games control, how weird the controller is, and how shooters must rely on auto-aim to even be playable. I think we can see here that's not really the case.

Graslu00

60,813 views • 1 year ago

The Legend of Zelda: Majora’s Mask, running natively on iOS and iPadOS. After Ocarina, everyone asked me to bring Majora’s Mask over next. So here it is. Not an emulator. MaskPad is built on Harbour Masters’ 2 Ship 2 Harkinian, itself built from the community Majora’s Mask decompilation. My work was adapting that existing source port into a native ARM64 iOS/iPadOS app rendering through Metal. No N64 hardware being simulated, no ROM interpreted at runtime, no streaming from a Mac. 2S2H isn’t stuck at the N64’s 240p and 20fps. Widescreen, full resolution, 60fps rendering. This game deserves a controller, so native game-controller support is built in. Touch, keyboard, and mouse work too. I used Codex 5.6 Sol to build MaskPad’s iOS layer. Source and guide below.

The Legend of Zelda: Majora’s Mask, running natively on iOS and iPadOS. After Ocarina, everyone asked me to bring Majora’s Mask over next. So here it is. Not an emulator. MaskPad is built on Harbour Masters’ 2 Ship 2 Harkinian, itself built from the community Majora’s Mask decompilation. My work was adapting that existing source port into a native ARM64 iOS/iPadOS app rendering through Metal. No N64 hardware being simulated, no ROM interpreted at runtime, no streaming from a Mac. 2S2H isn’t stuck at the N64’s 240p and 20fps. Widescreen, full resolution, 60fps rendering. This game deserves a controller, so native game-controller support is built in. Touch, keyboard, and mouse work too. I used Codex 5.6 Sol to build MaskPad’s iOS layer. Source and guide below.

Kahris

229,149 views • 7 days ago

The next Nintendo 64 classic has just hit the Sega Dreamcast, thanks, once again, to the efforts of jnmartin! Here's over a minute of Super Mario 64 gameplay, captured directly from my DC! As is usual with jnmartin's work, the port plays like a AAA native release, with everything SH4ZAMed up, running fullspeed, and looking as crisp and vibrant as ever with the Dreamcast's sharp 480p video output! To convert your N64 ROM into a bootable Dreamcast image, follow the link to the automated builder on the GitHub repository: Let us know what you think and remember to keep Dreaming!

The next Nintendo 64 classic has just hit the Sega Dreamcast, thanks, once again, to the efforts of jnmartin! Here's over a minute of Super Mario 64 gameplay, captured directly from my DC! As is usual with jnmartin's work, the port plays like a AAA native release, with everything SH4ZAMed up, running fullspeed, and looking as crisp and vibrant as ever with the Dreamcast's sharp 480p video output! To convert your N64 ROM into a bootable Dreamcast image, follow the link to the automated builder on the GitHub repository: Let us know what you think and remember to keep Dreaming!

Falco Girgis

120,194 views • 7 months ago

Mario Kart 64, running natively on iOS and iPad, with touch controls designed for racing. The Mario Kart 64 decompilation community spent years reconstructing the original game code in C. Harbour Masters turned that into SpaghettiKart, the source port. I built the iOS layer on top. Not an emulator. The game code is compiled for ARM64 and renders through Metal. Your ROM is only used to generate the asset archive, on device. No N64 hardware being simulated, no streaming from a Mac. It isn't limited to the N64's original output resolution, and MK64 Reloaded's HD pack replaces the original artwork on top of that. That's the pack running in the video. Steering is genuinely analog, not left and right taps. Separate layouts for iPad and iPhone, and optional tilt steering. Pair a Bluetooth controller and it takes over. Four-player selection works and two-player split screen runs. Two other public SpaghettiKart iOS builds exist, Sunset-Dawn's and rebelancap's. Both install on an iPad. Neither was built around one. SpaghettiPad is. I built the iOS integration with Codex 5.6 Sol. Repo, guide, and IPA below.

Mario Kart 64, running natively on iOS and iPad, with touch controls designed for racing. The Mario Kart 64 decompilation community spent years reconstructing the original game code in C. Harbour Masters turned that into SpaghettiKart, the source port. I built the iOS layer on top. Not an emulator. The game code is compiled for ARM64 and renders through Metal. Your ROM is only used to generate the asset archive, on device. No N64 hardware being simulated, no streaming from a Mac. It isn't limited to the N64's original output resolution, and MK64 Reloaded's HD pack replaces the original artwork on top of that. That's the pack running in the video. Steering is genuinely analog, not left and right taps. Separate layouts for iPad and iPhone, and optional tilt steering. Pair a Bluetooth controller and it takes over. Four-player selection works and two-player split screen runs. Two other public SpaghettiKart iOS builds exist, Sunset-Dawn's and rebelancap's. Both install on an iPad. Neither was built around one. SpaghettiPad is. I built the iOS integration with Codex 5.6 Sol. Repo, guide, and IPA below.

Kahris

52,839 views • 12 days ago

UN-FREAKING-BELIEVABLE!!!! While I've been working on fixing the last couple of bugs in the Mario Kart 64 DC port, getting us ready for the alpha release, jnmartin has gotten STAR FOX 64 up and running on the Sega Dreamcast in just two freaking days!?!? Sure, there are plenty of graphical glitches, and there's no audio yet... but W T F, it even runs well already!?! Freaking INSANE!! Anyway, surprise! The next N64-to-DC port has been chosen! Practice your barrel rolling, Dreamcast fans!

UN-FREAKING-BELIEVABLE!!!! While I've been working on fixing the last couple of bugs in the Mario Kart 64 DC port, getting us ready for the alpha release, jnmartin has gotten STAR FOX 64 up and running on the Sega Dreamcast in just two freaking days!?!? Sure, there are plenty of graphical glitches, and there's no audio yet... but W T F, it even runs well already!?! Freaking INSANE!! Anyway, surprise! The next N64-to-DC port has been chosen! Practice your barrel rolling, Dreamcast fans!

Falco Girgis

44,070 views • 1 year ago

NOW ACCEPTING PRE-ORDERS FOR SNES GCC!! (Link in replies!) I'LL ALSO BE GIVING A SNES GCC AWAY! Giveaway ends 11:59pm EDT July 31st, 2023. HOW TO ENTER: - Like this post - Retweet this post - Follow me! I am very pleased to be able to announce the launch of SNES GCC! As mentioned in a previous post, SNES GCC is an upcycling project that takes broken or scrap GameCube Controller boards and puts their hearts and souls inside of a SNES Controller form factor! SNES GCC isn't just any ordinary Digital GCC Gamepad either, the D-Pad's inputs are treated as left analog stick inputs giving greater GameCube game compatibility! It also keeps rumble intact as well as allows the user to remap the Y and Z buttons via DIP Switches on the SNES GCC motherboard. Each SNES GCC will be hand-crafted, utilizing original GCC hardware, fully refurbished 2nd hand original SNES/SFC Controller shells, buttons, and button pads, and a black paracorded OEM GCC cable with a grey plug! All for only $65! Consider putting a pre-order in today! :) And good luck to all of you who enter the giveaway! Cheers!

NOW ACCEPTING PRE-ORDERS FOR SNES GCC!! (Link in replies!) I'LL ALSO BE GIVING A SNES GCC AWAY! Giveaway ends 11:59pm EDT July 31st, 2023. HOW TO ENTER: - Like this post - Retweet this post - Follow me! I am very pleased to be able to announce the launch of SNES GCC! As mentioned in a previous post, SNES GCC is an upcycling project that takes broken or scrap GameCube Controller boards and puts their hearts and souls inside of a SNES Controller form factor! SNES GCC isn't just any ordinary Digital GCC Gamepad either, the D-Pad's inputs are treated as left analog stick inputs giving greater GameCube game compatibility! It also keeps rumble intact as well as allows the user to remap the Y and Z buttons via DIP Switches on the SNES GCC motherboard. Each SNES GCC will be hand-crafted, utilizing original GCC hardware, fully refurbished 2nd hand original SNES/SFC Controller shells, buttons, and button pads, and a black paracorded OEM GCC cable with a grey plug! All for only $65! Consider putting a pre-order in today! :) And good luck to all of you who enter the giveaway! Cheers!

Cardosi Customs LLC | 🚗🔜 Afterburner, Genesis X3

15,492 views • 3 years ago

I think it's time we all get a reality check on Diddy Kong Racing 64 for the Sega Dreamcast, including myself... So here it is: original DKR for N64 vs our ported DKR for DC, direct comparison with FPS counters enabled. The truth is that I've been staring at the FPS meter all weekend, obsessing over every little dip, vectorizing, loop unrolling, and optimizing every little expensive-looking loop I can see in the codebase to win back 0.1FPS at a time... totally losing sight of what the basis for comparison even was from the original... So how long has it been since you've played the original on N64? I'm not talking about via emulation with higher FPS and fancy upscaling. I'm talking about directly, on an actual, physical Nintendo 64. Full disclosure... prolly been half a decade now, for me! Anyway, the devs behind the decomp were kind enough to share with me some of their performance and timing analysis captures... so I figured we'd take a step back and have a little fun! I had no idea it was running at only 20FPS tops, capped at 15FPS for the WizPig races!? I just remember pissing myself at having never seen a game look that good or realistic in my entire life back in 1997 when DKR came out for the N64... All I know is I want to do this game justice... but the truth is that even though we're still cooking, already the Dreamcast runs consistently at 10FPS higher and runs at 4x the screen resolution with progressive scan output... What do you guys think? How's our port comparing?🤔

I think it's time we all get a reality check on Diddy Kong Racing 64 for the Sega Dreamcast, including myself... So here it is: original DKR for N64 vs our ported DKR for DC, direct comparison with FPS counters enabled. The truth is that I've been staring at the FPS meter all weekend, obsessing over every little dip, vectorizing, loop unrolling, and optimizing every little expensive-looking loop I can see in the codebase to win back 0.1FPS at a time... totally losing sight of what the basis for comparison even was from the original... So how long has it been since you've played the original on N64? I'm not talking about via emulation with higher FPS and fancy upscaling. I'm talking about directly, on an actual, physical Nintendo 64. Full disclosure... prolly been half a decade now, for me! Anyway, the devs behind the decomp were kind enough to share with me some of their performance and timing analysis captures... so I figured we'd take a step back and have a little fun! I had no idea it was running at only 20FPS tops, capped at 15FPS for the WizPig races!? I just remember pissing myself at having never seen a game look that good or realistic in my entire life back in 1997 when DKR came out for the N64... All I know is I want to do this game justice... but the truth is that even though we're still cooking, already the Dreamcast runs consistently at 10FPS higher and runs at 4x the screen resolution with progressive scan output... What do you guys think? How's our port comparing?🤔

Falco Girgis

53,720 views • 15 days ago

Jesus Christ, jnmartin has officially implemented his first big improvement over the N64 original for the Sega Dreamcast port of Mario Kart 64! Now the jumpotron monitor screens in Wario Stadium and and Luigi Raceway are updating at a full 30FPS, or 6x the framerate of the N64! ...and he's doing this entirely in software with the DC's SH4 CPU performing slow, direct VRAM reads from the framebuffer into a temporary buffer in system RAM which is later passed to OpenGL which transfers it back into VRAM to update the jumpotron texture with... and the freaking Dreamcast doesn't drop a frame doing all this shit! Might want to keep that in mind, as a community... That accessing texture memory or the framebuffer directly from the SH4 via the "uint16_t vram_s[]" symbol that the video API within KallistiOS exposes, while comparatively slow, is not actually so slow as to be unrealistic for a well-optimized game to do anything useful with... very interesting!

Jesus Christ, jnmartin has officially implemented his first big improvement over the N64 original for the Sega Dreamcast port of Mario Kart 64! Now the jumpotron monitor screens in Wario Stadium and and Luigi Raceway are updating at a full 30FPS, or 6x the framerate of the N64! ...and he's doing this entirely in software with the DC's SH4 CPU performing slow, direct VRAM reads from the framebuffer into a temporary buffer in system RAM which is later passed to OpenGL which transfers it back into VRAM to update the jumpotron texture with... and the freaking Dreamcast doesn't drop a frame doing all this shit! Might want to keep that in mind, as a community... That accessing texture memory or the framebuffer directly from the SH4 via the "uint16_t vram_s[]" symbol that the video API within KallistiOS exposes, while comparatively slow, is not actually so slow as to be unrealistic for a well-optimized game to do anything useful with... very interesting!

Falco Girgis

24,032 views • 1 year ago

I wanted to show you guys how hard we've been working to get the Diddy Kong Racing decompilation to run this well on the Sega Dreamcast... So I took the liberty of splicing together some high-action moneyshots directly captured from the console for a look at how the game currently performs. Just a few days ago, it was dipping to below 20FPS with audio cutting in and out as the main thread couldn't keep up with the audio decoding while simultaneously handling rendering and game logic. I know, I know, how could a Dreamcast struggle with an N64 game? It's because these decompilations are written to essentially emulate the N64's unique hardware as accurately as possible. In this case, that means the Dreamcast's main SH4 CPU is emulating all audio decoding, mixing, and synthesis in software, including DSP effects. This was originally handled separately by the RSP coprocessor in the N64... Not wanting to have to rewrite the entire audio back-end to use the DC's AICA sound processor, I've vectorized the absolute living HELL out of the ADPCM decoder with my SH4ZAM library... Which gave us enough performance out of the SH4 to continue emulating all of the sound processing in software. You will notice in the footage that the only time the FPS isn't at solid 30 is when there is a lot of overlapping SFX from nearby racers chattering or items getting used. That's the SH4 having to work even harder to mix multiple audio channels together and possibly even apply DSP effects to them as well!

I wanted to show you guys how hard we've been working to get the Diddy Kong Racing decompilation to run this well on the Sega Dreamcast... So I took the liberty of splicing together some high-action moneyshots directly captured from the console for a look at how the game currently performs. Just a few days ago, it was dipping to below 20FPS with audio cutting in and out as the main thread couldn't keep up with the audio decoding while simultaneously handling rendering and game logic. I know, I know, how could a Dreamcast struggle with an N64 game? It's because these decompilations are written to essentially emulate the N64's unique hardware as accurately as possible. In this case, that means the Dreamcast's main SH4 CPU is emulating all audio decoding, mixing, and synthesis in software, including DSP effects. This was originally handled separately by the RSP coprocessor in the N64... Not wanting to have to rewrite the entire audio back-end to use the DC's AICA sound processor, I've vectorized the absolute living HELL out of the ADPCM decoder with my SH4ZAM library... Which gave us enough performance out of the SH4 to continue emulating all of the sound processing in software. You will notice in the footage that the only time the FPS isn't at solid 30 is when there is a lot of overlapping SFX from nearby racers chattering or items getting used. That's the SH4 having to work even harder to mix multiple audio channels together and possibly even apply DSP effects to them as well!

Falco Girgis

17,091 views • 20 days ago

Goldeneye is a great “better to ask for forgiveness than get permission” story. Released in August 1997, the game made $250m on a $2m budget. A major reason was its insanely fun multiplayer mode…which Nintendo didn’t ask for and developers snuck into the game at the last second. Many years later, Steve Ellis — a game developer for Rare — explained what went down: ➡️ “One of the things that always strikes me as crazy in retrospect is that until something like March or April of 1997, there wasn't a multiplayer mode at all. It hadn't even been started. It really was put in at the last minute – something you wouldn't dream of doing these days – and it was done without the knowledge or permission of the management at Rare and Nintendo. The first they knew about it was when we showed it to them working. However – since the game was already late by that time, if we hadn't done it that way, it probably never would have happened.” ⬅️ Rare had a team of only 10 core developers and it took 2.75 years to make the game, which actually came out 18 months after “Goldeneye” the film. Nintendo briefly cancelled the game but then pushed to release it (and expectations were low). Goldeneye was an instant hit with innovative stealth play, remote-control bombs and sniper rifles. Gaming mags (IGN, GamePro) have called it N64’s best multiplayer game, which is wild when you consider the platform also had Mario Kart and Super Smash Bros. Goldeneye became N64’s 3rd best-selling title ever (also impressive because 7 of the top 9 are all original Nintendo IP). 1. Super Mario 64 (12m units) 2. Mario Kart 64 (10m) 🚨3. Goldeneye (9m) 4. Legend of Zelda: Ocarina of Time (8m) 5. Super Smash Bros (6m) 6. Pokémon Stadium (5m) 7. Donkey Kong 64 (5m) 8. Diddy Kong Racing (5m) 9. Starfox 64 (4m) Most importantly: without the unapproved last-second addition of multi-player, I couldn’t have spent 100s of hours being OddJob and smoking my unsuspecting friends with proximity mines.

Goldeneye is a great “better to ask for forgiveness than get permission” story. Released in August 1997, the game made $250m on a $2m budget. A major reason was its insanely fun multiplayer mode…which Nintendo didn’t ask for and developers snuck into the game at the last second. Many years later, Steve Ellis — a game developer for Rare — explained what went down: ➡️ “One of the things that always strikes me as crazy in retrospect is that until something like March or April of 1997, there wasn't a multiplayer mode at all. It hadn't even been started. It really was put in at the last minute – something you wouldn't dream of doing these days – and it was done without the knowledge or permission of the management at Rare and Nintendo. The first they knew about it was when we showed it to them working. However – since the game was already late by that time, if we hadn't done it that way, it probably never would have happened.” ⬅️ Rare had a team of only 10 core developers and it took 2.75 years to make the game, which actually came out 18 months after “Goldeneye” the film. Nintendo briefly cancelled the game but then pushed to release it (and expectations were low). Goldeneye was an instant hit with innovative stealth play, remote-control bombs and sniper rifles. Gaming mags (IGN, GamePro) have called it N64’s best multiplayer game, which is wild when you consider the platform also had Mario Kart and Super Smash Bros. Goldeneye became N64’s 3rd best-selling title ever (also impressive because 7 of the top 9 are all original Nintendo IP). 1. Super Mario 64 (12m units) 2. Mario Kart 64 (10m) 🚨3. Goldeneye (9m) 4. Legend of Zelda: Ocarina of Time (8m) 5. Super Smash Bros (6m) 6. Pokémon Stadium (5m) 7. Donkey Kong 64 (5m) 8. Diddy Kong Racing (5m) 9. Starfox 64 (4m) Most importantly: without the unapproved last-second addition of multi-player, I couldn’t have spent 100s of hours being OddJob and smoking my unsuspecting friends with proximity mines.

Trung Phan

9,238,832 views • 2 years ago

FINALLY time for the big announcement everyone has been begging and waiting for... Here's a VERY EARLY direct hardware capture of Mario Kart 64... RUNNING ON THE SEGA DREAMCAST, of course! This game was literally just BARELY decompiled the other day, with a codebase that is still quite married to the Nintendo 64 platform... but this didn't stop jnmartin: the dark coding wizard who brought us a dynamically lit and bump mapped Doom 64 and Wipeout running at >100FPS on the DC! What you're seeing is the insane progress made by one man in just 3 weeks. As is to be expected, there are all kinds of visual glitches and rendering artifacts, the framerate is all over the place, and there's no audio yet... which is totally typical of any ambitious DC port in the early stages. The DC build wouldn't even get past the menu screen without crashing or running out of RAM until just a few DAYS ago, yet here it is, every level playable WITH multiplayer support already on the DC! Even in this early stage, you can already see the game benefiting from the PVR's crisp 480p output... Each players' little viewport window in 4 player mode is the same resolution as the entire screen was on the N64! Stay tuned for future updates as jnmartin continues his work to bring this classic to our little white box of Dreams!

FINALLY time for the big announcement everyone has been begging and waiting for... Here's a VERY EARLY direct hardware capture of Mario Kart 64... RUNNING ON THE SEGA DREAMCAST, of course! This game was literally just BARELY decompiled the other day, with a codebase that is still quite married to the Nintendo 64 platform... but this didn't stop jnmartin: the dark coding wizard who brought us a dynamically lit and bump mapped Doom 64 and Wipeout running at >100FPS on the DC! What you're seeing is the insane progress made by one man in just 3 weeks. As is to be expected, there are all kinds of visual glitches and rendering artifacts, the framerate is all over the place, and there's no audio yet... which is totally typical of any ambitious DC port in the early stages. The DC build wouldn't even get past the menu screen without crashing or running out of RAM until just a few DAYS ago, yet here it is, every level playable WITH multiplayer support already on the DC! Even in this early stage, you can already see the game benefiting from the PVR's crisp 480p output... Each players' little viewport window in 4 player mode is the same resolution as the entire screen was on the N64! Stay tuned for future updates as jnmartin continues his work to bring this classic to our little white box of Dreams!

Falco Girgis

55,593 views • 1 year ago

JNMARTIN HAS BROUGHT US CHRISTMAS EARLY THIS YEAR!!! His port of Star Fox 64 to the Sega Dreamcast is officially complete and was just released! Here's 9+ minutes of spliced direct hardware captures, featuring footage from every mission running on an actual physical DC at 480p! I have to say, the game feels incredibly smooth and responsive on the DC and controls extremely well. Also... as you can see, at twice the resolution with progressive scan, she looks gorgeous even with my cheap-ass HDMI cables and USB capture card. While jnmartin had the game up and running on DC within (literally) 2 days, there was an enormous amount of time and energy invested into faithfully recreating the experience graphically, implementing various bugfixes, and hunting for performance gainz... the man has never been satisfied with anything short of amazing with his ports, and it really shows. Like his Mario Kart 64 port, Star Fox 64 is also using my SH4ZAM library to hardware accelerate the math and linear algebra routines for DC; however, unlike last time, he's gotten so good at performance gainz that I barely did anything at all on that side, other than writing a few little inline SH4 ASM routines to cover some operations that I didn't already accelerate within the API... Suffice to say, though, that everything from the vertex TnL pipeline, to audio decoding, to gameplay-related trigonometry routines has been optimized for the SH4's FPU... jnmartin even got to bust out the SH4's MMU to accelerate the translation of of the segmented address scheme used by the game on N64 (which was apparently some suggested memory management model in the N64 docs) into the DC's virtual address space--which previously had to be done in software... So even more gainz! Sorry, though... but pretty sure this is why the game won't work in the Flycast emulator currently... whoops! 🤣 Shout-out to darcagent for contributing DREAMCAST RUMBLE PACK SUPPORT (among other things) to the release. Rumble support has historically been a pain-point within our KallistiOS homebrew DC SDK, as many 3rd party rumble packs are non-compliant and either do what they want with certain rumble commands or screw up the entire maple bus when they receive something they have decided not to fully implement... Great job getting that shit sorted out and tested with so many packs. All of my exotic (and cheapo) 3rd party rumble devices that I was able to test with seemed to work great! Finally, lets give SonicDcer a round of applause for being the lead dude behind the original N64 decompilation--as it was his original work that allowed for any of this to even be possible. He also continued to offer support and advice throughout the entire porting process, like a total chad. Here's the link to the official GitHub repo with instructions for building a Dreamcast image from a StarFox N64 ROM:

JNMARTIN HAS BROUGHT US CHRISTMAS EARLY THIS YEAR!!! His port of Star Fox 64 to the Sega Dreamcast is officially complete and was just released! Here's 9+ minutes of spliced direct hardware captures, featuring footage from every mission running on an actual physical DC at 480p! I have to say, the game feels incredibly smooth and responsive on the DC and controls extremely well. Also... as you can see, at twice the resolution with progressive scan, she looks gorgeous even with my cheap-ass HDMI cables and USB capture card. While jnmartin had the game up and running on DC within (literally) 2 days, there was an enormous amount of time and energy invested into faithfully recreating the experience graphically, implementing various bugfixes, and hunting for performance gainz... the man has never been satisfied with anything short of amazing with his ports, and it really shows. Like his Mario Kart 64 port, Star Fox 64 is also using my SH4ZAM library to hardware accelerate the math and linear algebra routines for DC; however, unlike last time, he's gotten so good at performance gainz that I barely did anything at all on that side, other than writing a few little inline SH4 ASM routines to cover some operations that I didn't already accelerate within the API... Suffice to say, though, that everything from the vertex TnL pipeline, to audio decoding, to gameplay-related trigonometry routines has been optimized for the SH4's FPU... jnmartin even got to bust out the SH4's MMU to accelerate the translation of of the segmented address scheme used by the game on N64 (which was apparently some suggested memory management model in the N64 docs) into the DC's virtual address space--which previously had to be done in software... So even more gainz! Sorry, though... but pretty sure this is why the game won't work in the Flycast emulator currently... whoops! 🤣 Shout-out to darcagent for contributing DREAMCAST RUMBLE PACK SUPPORT (among other things) to the release. Rumble support has historically been a pain-point within our KallistiOS homebrew DC SDK, as many 3rd party rumble packs are non-compliant and either do what they want with certain rumble commands or screw up the entire maple bus when they receive something they have decided not to fully implement... Great job getting that shit sorted out and tested with so many packs. All of my exotic (and cheapo) 3rd party rumble devices that I was able to test with seemed to work great! Finally, lets give SonicDcer a round of applause for being the lead dude behind the original N64 decompilation--as it was his original work that allowed for any of this to even be possible. He also continued to offer support and advice throughout the entire porting process, like a total chad. Here's the link to the official GitHub repo with instructions for building a Dreamcast image from a StarFox N64 ROM:

Falco Girgis

30,965 views • 8 months ago

Tens of millions of Americans "Doom Spending" their way to oblivion -- one in four. Especially the young, who are apparently giving up on buying a house or starting a family and taking cruises instead. The gutting of the Middle Class has been going on for 25 years now -- ever since the Fed replaced the real economy with money printers. It's now accelerating.

Tens of millions of Americans "Doom Spending" their way to oblivion -- one in four. Especially the young, who are apparently giving up on buying a house or starting a family and taking cruises instead. The gutting of the Middle Class has been going on for 25 years now -- ever since the Fed replaced the real economy with money printers. It's now accelerating.

Peter St Onge, Ph.D.

670,274 views • 2 years ago

IT'S FINALLY HERE! #Doom64 has officially landed on the Sega #Dreamcast with this flawless, AAA-quality port by jnmartin. I've been following his work the entire time, beta testing (and making sure we didn't break anything in KOS), and it has been an absolute pleasure to see how much care and attention to detail has been put into bringing this #N64 classic to the DC! He has released all of the source code and tools required to build and play the game on his GitHub... but there are still a few small additions I would love to see the community pitch in to help with. It already has some bitchin' VMU icons, but we should definitely add support for: Mouse + Keyboard, Dual-analog sticks, and Rumble packs, to ensure that the DC port is the definitive version! #gamedev #retrogaming #doom

IT'S FINALLY HERE! #Doom64 has officially landed on the Sega #Dreamcast with this flawless, AAA-quality port by jnmartin. I've been following his work the entire time, beta testing (and making sure we didn't break anything in KOS), and it has been an absolute pleasure to see how much care and attention to detail has been put into bringing this #N64 classic to the DC! He has released all of the source code and tools required to build and play the game on his GitHub... but there are still a few small additions I would love to see the community pitch in to help with. It already has some bitchin' VMU icons, but we should definitely add support for: Mouse + Keyboard, Dual-analog sticks, and Rumble packs, to ensure that the DC port is the definitive version! #gamedev #retrogaming #doom

Falco Girgis

48,189 views • 2 years ago

The time has finally come! Here's an actual hardware capture of me cruising through Corneria in jnmartin's port of Star Fox 64 running on the Sega Dreamcast! As you can see, the port has been progressing PHENOMENALLY over the last couple months. Everything plays super smoothly and is as responsive as lightning! The visuals also look clean and crisp rendered at 480p with the DC's PowerVR GPU. We're estimating that the port is about 95% completed, with the majority of the last few weeks being spent implementing the lighting and other special effects for certain areas (which you will soon be seeing as well). Finally, he's been working daily on JIT compiling the N64 display list code into SH4 assembly in real-time in addition to using my SH4ZAM library for what he hopes will be a final round of additional performance gainz! TL;DR: We have another AAA-quality Nintendo 64-to-Sega Dreamcast jnmartin port on our hands here! Stay tuned for the upcoming release!

The time has finally come! Here's an actual hardware capture of me cruising through Corneria in jnmartin's port of Star Fox 64 running on the Sega Dreamcast! As you can see, the port has been progressing PHENOMENALLY over the last couple months. Everything plays super smoothly and is as responsive as lightning! The visuals also look clean and crisp rendered at 480p with the DC's PowerVR GPU. We're estimating that the port is about 95% completed, with the majority of the last few weeks being spent implementing the lighting and other special effects for certain areas (which you will soon be seeing as well). Finally, he's been working daily on JIT compiling the N64 display list code into SH4 assembly in real-time in addition to using my SH4ZAM library for what he hopes will be a final round of additional performance gainz! TL;DR: We have another AAA-quality Nintendo 64-to-Sega Dreamcast jnmartin port on our hands here! Stay tuned for the upcoming release!

Falco Girgis

35,283 views • 9 months ago

THIS GUY BUILT A REAL JARVIS THAT TURNS HIS IDEAS INTO FINISHED PROJECTS ON ITS OWN, AND HE JUST SHOWED HOW THE WHOLE THING WORKS The whole system runs on one clean split he calls a blood-brain barrier. The second brain, his Obsidian vault, is only for things that aren't real yet. Ideas. Each one sits in a project-shaped folder, waiting to be processed and turned into something real. Nothing executes there. The vault is the place where ideas get shaped, not built. Once an idea is signed off, it crosses over to the execution pipeline. That lives on his actual machine, or an always-on box, or a Raspberry Pi, depending on what the project needs. Inside that machine is a fully Claude-native file system. The key piece is one CLAUDE.md file sitting in the root of his documents folder, acting as the map to everything in there. So he just opens Claude and says "go to my projects folder," and it already knows the whole structure, because that root file explains it. Two zones, one rule: the brain holds what isn't real, the machine runs what is. That separation is what keeps the ideas from tangling with the work. Bookmark this

THIS GUY BUILT A REAL JARVIS THAT TURNS HIS IDEAS INTO FINISHED PROJECTS ON ITS OWN, AND HE JUST SHOWED HOW THE WHOLE THING WORKS The whole system runs on one clean split he calls a blood-brain barrier. The second brain, his Obsidian vault, is only for things that aren't real yet. Ideas. Each one sits in a project-shaped folder, waiting to be processed and turned into something real. Nothing executes there. The vault is the place where ideas get shaped, not built. Once an idea is signed off, it crosses over to the execution pipeline. That lives on his actual machine, or an always-on box, or a Raspberry Pi, depending on what the project needs. Inside that machine is a fully Claude-native file system. The key piece is one CLAUDE.md file sitting in the root of his documents folder, acting as the map to everything in there. So he just opens Claude and says "go to my projects folder," and it already knows the whole structure, because that root file explains it. Two zones, one rule: the brain holds what isn't real, the machine runs what is. That separation is what keeps the ideas from tangling with the work. Bookmark this

Yarchi

87,650 views • 1 month ago

[New Xbox Controller Review] #ad Special thanks to Qrdgame_offcial for supplying me with a review unit of their Ferrox M5 Xbox & PC Controller QRD Ferrox M5 The QRD Ferrox M5 is a Wireless Xbox One–style gamepad with a transparent design. Since it targets Xbox One natively, it works automatically on PC and Xbox Series S/X. The included 2.4Ghz USB Dongle also supports Switch and Android with the right adapter (USB C), but I was not able to test those in time for this review. A Wireless Xbox Controller The QRD FERROX M5 comes in a familiar Xbox layout with Hall Effect joysticks, RGB rings around the sticks, and a magnetic & detachable clear shell that shows the internals. The controller feels very similar to a standard Xbox pad in terms of shape and size, but it’s slightly lighter at compared to the usual Xbox controller weight. The lighter weight makes it easier to hold for longer sessions without hand fatigue. The D-Pad is surprisingly good at dialing special moves feels as solid and responsive as the official Xbox controller, and that’s impressive at a lower price point. I spent a few days trying out the Mortal Kombat Legacy Kollection exclusively using this controller and I did not notice any difference at all. Capabilities From what I’ve tested, the controller performs extremely well for action games, fighting games, and shooters. The Hall Effect joysticks offer smooth movement and precise control with no drift issues. The D-Pad uses micro switches, so every input is tactile and accurate. The back triggers support an adaptive “trigger stop” mode, which shortens the travel distance for faster reaction time in FPS games or quicker blocks in Fighting Games. You also get 4 back macro buttons, turbo mode, and adjustable joystick sensitivity with deadzone options. Vibration strength and RGB lighting modes are also customizable. What can it do The FERROX M5 includes an 800mAh battery that lasts around 8 hours of gameplay. It only uses the 2.4Ghz wireless connection, not Bluetooth, so it always requires the included USB Dongle. The good thing is once you sync it with your Xbox or PC, you don’t need to sync it again—it carries over between both devices automatically. The 2.4G connection is stable and low latency, and the controller has a 3.5mm headphone jack for audio and mic support. It also features a quick calibration system to keep sticks and triggers accurate over time. The overall grip and shape feel close to the official Xbox controller, comfortable for long gaming sessions, and the transparent shell gives it a distinct look. Areas of improvement I initially had trouble charging the controller while playing because connecting it to the Xbox via USB would disable all inputs, making it unusable in wired mode. But luckily QRD Support helped and provided me with an updat - I had to connect it to a PC, download the firmware tool from QRD’s website, and update the controller manually. After installing the new firmware, the controller can now charge while being used normally on Xbox, so the issue is fully resolved. The Xbox button also behaves differently on Xbox, where the single press acts like hold and the hold acts like single press; this issue doesn’t appear on PC. Syncing with the dongle took a few attempts on both Xbox and PC, but once paired, it never needed syncing again. The wireless mode is strictly 2.4G with no Bluetooth support, so it cannot connect without the dongle, though the benefit is that one pairing works across both Xbox and PC. Final Summary ✅ Hall Effect Joystick ✅ Lights in the dark ✅ Good D-Pad for input dialing ✅ Light Controller ❌ First sync can be annoying on PC ❌ No bluetooth for phone usage - Dongle is necessary ❌ Needs an update for the Xbox Wired issues which require a PC The Controller is available on Amazon for $59.99, and will be part of the Black Friday Deals on their official website for even more discount! Amazon Link Website Link

[New Xbox Controller Review] #ad Special thanks to Qrdgame_offcial for supplying me with a review unit of their Ferrox M5 Xbox & PC Controller QRD Ferrox M5 The QRD Ferrox M5 is a Wireless Xbox One–style gamepad with a transparent design. Since it targets Xbox One natively, it works automatically on PC and Xbox Series S/X. The included 2.4Ghz USB Dongle also supports Switch and Android with the right adapter (USB C), but I was not able to test those in time for this review. A Wireless Xbox Controller The QRD FERROX M5 comes in a familiar Xbox layout with Hall Effect joysticks, RGB rings around the sticks, and a magnetic & detachable clear shell that shows the internals. The controller feels very similar to a standard Xbox pad in terms of shape and size, but it’s slightly lighter at compared to the usual Xbox controller weight. The lighter weight makes it easier to hold for longer sessions without hand fatigue. The D-Pad is surprisingly good at dialing special moves feels as solid and responsive as the official Xbox controller, and that’s impressive at a lower price point. I spent a few days trying out the Mortal Kombat Legacy Kollection exclusively using this controller and I did not notice any difference at all. Capabilities From what I’ve tested, the controller performs extremely well for action games, fighting games, and shooters. The Hall Effect joysticks offer smooth movement and precise control with no drift issues. The D-Pad uses micro switches, so every input is tactile and accurate. The back triggers support an adaptive “trigger stop” mode, which shortens the travel distance for faster reaction time in FPS games or quicker blocks in Fighting Games. You also get 4 back macro buttons, turbo mode, and adjustable joystick sensitivity with deadzone options. Vibration strength and RGB lighting modes are also customizable. What can it do The FERROX M5 includes an 800mAh battery that lasts around 8 hours of gameplay. It only uses the 2.4Ghz wireless connection, not Bluetooth, so it always requires the included USB Dongle. The good thing is once you sync it with your Xbox or PC, you don’t need to sync it again—it carries over between both devices automatically. The 2.4G connection is stable and low latency, and the controller has a 3.5mm headphone jack for audio and mic support. It also features a quick calibration system to keep sticks and triggers accurate over time. The overall grip and shape feel close to the official Xbox controller, comfortable for long gaming sessions, and the transparent shell gives it a distinct look. Areas of improvement I initially had trouble charging the controller while playing because connecting it to the Xbox via USB would disable all inputs, making it unusable in wired mode. But luckily QRD Support helped and provided me with an updat - I had to connect it to a PC, download the firmware tool from QRD’s website, and update the controller manually. After installing the new firmware, the controller can now charge while being used normally on Xbox, so the issue is fully resolved. The Xbox button also behaves differently on Xbox, where the single press acts like hold and the hold acts like single press; this issue doesn’t appear on PC. Syncing with the dongle took a few attempts on both Xbox and PC, but once paired, it never needed syncing again. The wireless mode is strictly 2.4G with no Bluetooth support, so it cannot connect without the dongle, though the benefit is that one pairing works across both Xbox and PC. Final Summary ✅ Hall Effect Joystick ✅ Lights in the dark ✅ Good D-Pad for input dialing ✅ Light Controller ❌ First sync can be annoying on PC ❌ No bluetooth for phone usage - Dongle is necessary ❌ Needs an update for the Xbox Wired issues which require a PC The Controller is available on Amazon for $59.99, and will be part of the Black Friday Deals on their official website for even more discount! Amazon Link Website Link

thethiny 🐰🍉

16,864 views • 8 months ago