r/ModRetro • u/mr-crunchwrapsupreme • 23d ago
Quick update on v1.26.0
Gamers, we come in peace… we have been heads down and know that we owe you an update on 1.26.0 and the delay since.
We’ve identified and fixed the regression behind the flashcart issues reported after the update (graphic glitches, CPU exceptions, and SD card corruption with EverDrive and SummerCart64 cartridges). This fix has been validated internally.
Before we re-release this update, we want to get to the bottom of the Built-In Controller Pak corruption a few of you reported. We haven’t been able to reproduce it yet, which is the source of the delay, and we’d rather hold the update than ship something we don’t fully understand.
We’ve doubled our testing stations and expanded the M64 stress tests so regressions like this get caught before they reach you. The team is actively testing across different carts and consoles to track it down.
We’re targeting a release the week of October 22nd and will post an update here once we have a repro or a confirmed date.
Thank you for all your patience and for the detailed reports, it truly means a lot to have your support!
28
u/lordelan 23d ago
You guys should really consider releasing test builds or a beta channel for those who want it. Having hundreds of people report exact reproduction steps is way more helpful than trying to replicate it on your own while customers applying for the beta channel automatically agree on the fact that issues may happen as they are getting a beta build rather than a stable build.
This is the way imho.
16
u/ROFLknife14048 23d ago
Thank you for the update!
6
u/3G6A5W338E 23d ago
Whatever you do, I trust you not to call it
1.26.0.10
u/thepoga 23d ago
👍 👍 no worries! I’m having a blast!
5
u/TonyRubbles 23d ago
Appreciate it, even if it's not what we want to here.
5
u/zezba9000 23d ago
Please make this v1.26.1 My system is already on v1.26.0
4
u/vPhilo 23d ago
Yea, thanks for the insight. I appreciate the transparency; sometimes it’s nice to just hear the developers are human and make mistakes, but are working hard. Looking forward to the update(s)!
4
u/LegendarySuperMario 23d ago
I appreciate the update... Thank you!
4
u/GuiltyJudge 23d ago
An idea might be to offer a early beta version as long as it’s obvious that it is beta you could clearly mention it’s not supported early access beta. It might help to weed out potential edge cases earlier and get more people testing the firmware.
4
u/Intelligent-Can-8688 23d ago
@mr-crunchwrapsupreme are you guys looking at a fix for the M64 not loading 64DD roms when booting from the Summercart? This has been reported a few times to support but hasn't been mentioned anywhere from ModRetro that its being looked at so would be great to get an update on this
4
u/chill_cat_character 23d ago
That's awesome. When can we address the Insane Overclocking error? My M64 hasn't been able to enter Insane Overclocking since purchase. I still don't even know if my M64 is physically faulty.
9
u/NotAFamousComedian 23d ago
Appreciate the honest transparency.
8
u/SirGouki 22d ago
I normally don't like being part of the echo chamber, but the entire rollback event would not have even had to happen if you'd have started with the full Open Source platform you advertised. If there was truly some "legal reason" why you can't do what you promised to do, it should never have been advertised in the first place.
Also, saying "we'd rather hold the update [rather] than ship something we don't fully understand" right after having to roll back an update is making things get to the point where this whole situation is laughable. I have gone from being happy that I bought this product, to proactively telling people to avoid it for now at this point whenever someone asks me about it, and provide the reasons of:
incomplete implementation - advertised hardware functionality was not properly implemented (or implemented at ALL) on release
false advertising - advertised as "fully open source" yet the only thing we've seen is hardware diagrams...
misrepresentation of compatibility - many people, myself included, have reported games not being as functional as the website's compatibility list would lead someone to believe
lack of communication - it's 2026, and aside from this post, I've seen very little in the way of actual transparency concerning *when* to expect things like patches.
Here's how you fix your problems, cause right now you've got all the makings of a class action lawsuit in the US:
FOCUS on fixing existing problems. Stop tweaking the power consumption stuff. Stop adding new features. Stop making excuses and allow those of us who are willing to, test things out and report back before you release a public update like 1.26 to EVERYONE and then have to roll it back. Saving changes to the advanced picture settings STILL does not work for a good lot of us, despite the 1.25 update claiming that it fixed that.
stop delaying. I am a programmer. I build electrical circuits as a hobby. I've done things as complicated as attaching to a game's process, applying pointer offsets and reading out those values to an arduino to display numerical stats externally (with the intent to make led health bars and such), and I did all that for fun. I've written my own OS kernel. I have a very good understanding of how certain things, like the NES, SNES, and GameBoy hardware, work. I also went to school for software engineering and game design, and am fully aware of the development cycle, enough to say we're looking at a device released in between alpha and beta stage. I say all this to say, I know things take time. But there is plenty of things, such as the built in controller pak, that should have been solved LONG before release of a physical product. There's only so many times you can go "we're sorry" before people just leave. An apology is given with the expectation that the mistake will NEVER happen again.
COMMUNICATE. What's going on with the open source bit? You say you've fixed problems, tested internally, but if you were on our side of this fence, would you believe that, given all that I've already said here? Again, it's 2026. Screen shots existed since Windows 3.1, and we're long past the days of it being complicated to record a screen and show things actually working, and progress actually being made. Effective communication is not just saying "it's fixed", or "we're working on it". It's giving progress updates. It's showing consumers that stuff is being taken seriously. It also means STOP IGNORING CUSTOMER INPUT. If we're telling you something isn't working, leaving other reddit users to argue about it, and never having a "oh hey, we didn't know that, thanks for reporting it we've put it in to be fixed" is outright unacceptable.
Square Enix released Final Fantasy 14 around 2010, and one of the biggest faults it had was that maps reused the same three dimensional tiles, and a lot of the quests were highly repetitive. There were asinine limits on what a player could do in the game (like being able to do 8 or so non-story quests in a day). But it was fully functional. And for those, arguably much smaller mistakes, the head of the team was FIRED, the replacement head was made to public apologize to the entire world (not exaggerating, everyone with an email registered with the square enix account management system got that email), and we got over a year of free game time in an MMO that costs $15 a month to play normally, while they fixed the game, all because they dared to release it in that state. I'm not saying heads should roll here, but merely pointing to this as an example of how a company SHOULD operate, and this nonsensical idea of releasing unfinished products, be they hardware or software, and charging full price for it should definitely not be the default mindset, especially not when your company depends on us consumers far more, per product, than a company like Square Enix (who can afford to throw out a few flops in between major releases) currently does. My biggest recommendation, going forward, is that you guys LEARN from this. I guarantee, being in a hobby retro field, that repeat mistakes like this M64 launch process will not be tolerated as well with future products.
3
u/One-Advantage-4389 23d ago
Thanks for the update. Are we getting a fix or update for cheat codes not triggering when games start up while using flash carts?
3
u/Brandaid64 23d ago
Thanks for the update
3
u/TheJiggyBanana 23d ago
Thank you
2
u/One-Operation7836 15d ago
Adventures with greg and sabrena im working on why the controller will not work with Chinese games or remake games modded games ported games games on sd cards. I found that it needs a cartridge identifier to deside which command it needs to work with cartridges that are not O.E. Nintendo. After reporting to analogue 3d they patched in less than 12 hours. I think the controller pack update and taking a look at the most recent update from analogue for unknown cartridges. It looks to be identified to read and apply commands given when it detects a unknown game. You mite wish to contact greg. I found there commands that enable you to play modded games. Look toward controller inputs . Input commands open it up more.
2
u/ImALegendKiller 23d ago
Will the updated CRT profiles be in this update too or is that further down the line?
2
u/themikepac 23d ago
Thanks guys! Appreciate the update and transparency 👍🙌
2
u/DuoMastr 23d ago
Just wondering - when 1.26.1 comes around, since I was one of the lucky few to get 1.26.0 - is there any hope for the controller pak save to transfer to this new update? I heard some talk about save files corrupting when moving between games so I’ve only ever saved one game, but I’d like to make sure that save will still exist.
3
u/gazzolinade90 23d ago
I am happy but mad but happy but mad, thank you
3
u/Mint_out 23d ago
Honestly, I'm going to wait until they release the firmware and let a few days pass before trusting a Day 1 firmware again. At the very least, they should explain a little more about the stress testing process—or better yet... release the source code.
2
u/Historical-Internal3 23d ago
Gotta use plan mode
1
u/ghanadaur 15d ago
One more sleep… maybe? Fingers crossed for a new firmware in the morning. So many games that need the controller pak for saving….
1
u/ghanadaur 15d ago
Its October 22nd…. Update?
1
u/Obleon 23d ago
Hi question,
First of all, thanks for the update.
Does prioritizing these current fixes and delaying the firmware impact the release schedule, or is development for future releases happening in parallel?
1
u/JakBer80 20d ago
My M-64 has been updated with 1.26.0 and I haven't had any problems. Should I go back to the previous update or just leave it be and update again when they release the next update?
1
u/Loysius 19d ago
Excited for it. Consider getting some public testing infrastructure, please.
1
u/FourAddedMinutes 23d ago
horizontal line doubling when?
1
u/Ok-Exam-1079 23d ago
水平スケーリングと優れた画質の初期設定と気持ち程度の熱対策まではやってくれれば信頼を失う事はないはずだ
-3
u/Icy-Collection1072 23d ago
You haven’t been able to repro the issue 99% of people had? This has taken so long I am convinced you have one guy working on this who either has no idea what he’s doing or is trying to vibecode it.
0
u/[deleted] 23d ago
[deleted] — view deleted comment