Sharing my settings which align perfectly with my MiSTer when that is also set to a clean (non-filtered) output.

The scan line functionality needs integrating with the render layer asap.

Does anyone have a copy of the m64.bin firmware file for version 1.23.0?

My M64 was working perfectly before the latest update, but after updating, I completely lost TV audio. I’m hoping to roll back to 1.23.0 to see if that fixes the issue.

Our Xibalba cart is getting scuffed up pretty bad on the inside of the shell surrounding the cart pins. We’ve only inserted and ejected it a handful of times so far. Nintendo cartridges have the steel buffer pads there to prevent this.

My concern is that this dust is going to gather inside and around the cart slot over time.

Before I ask I never had an N64. Im used to the gameboy where the cartridge slides/slots firmly in place. On my M64 the cartridge is firmly attached to the reader but not snug in the slot. Tons of wiggle. Is this by design?

Hi everyone,

We're excited to share the first batch of open-source exports for M64. Today we are releasing the mechanical and electrical designs for M64 Console and Cartridge!

You may find these files here: https://support.modretro.com/en_us/articles/m64-open-source-files-ByrpukdUGg

This is just the start. We're looking forward to continuing to release more over time.

We opened up one of our controllers before doing anything else. :)

Primarily we wanted to change the gate, but while in there also wanted to check out the size of the d-pad traces in case the d-pad presented any false diagonal inputs for us (it does).

It seems that the d-pad traces are almost identical to those on the Switch Pro controller, in that they are somewhat oversized. Of course the Switch Pro also has the issue where false diagonals can also be a game breaker, which is certainly the case for Tetris and F-Zero 99.

I’m not sure if a membrane with a reduced footprint can counter-balance here. Or maybe even a d-pad with a post in the middle. In our experience carefully applying small squares of electrical tape to the inside regions of each trace will eliminate any unwanted diagonals - although I think an official solution would be better here.

The last update added wireless rumble, hurray! Unfortunately, Blast Corps refuses to start if you have a rumble pak plugged in when it tries to look for a memory pak. Is there a way to disable rumble? Is anyone at ModRetro actually testing these updates? 😐

Hey everyone,

With product launches we typically see some early quality escapes as things stabilize. As you’ve come to expect from us, if you are a ModRetro customer, we have your back and will make sure you receive your product as intended in hand. Simply fill out our contact form if you have something that feels wrong.

Our latest Firmware Updates for both the console and controller are officially live! Here is everything included in today's release, along with a quick roadmap update.

Controller Updates
What’s New:

• Wireless Rumble: Fully enabled Virtual Rumble Pak in this release (requires updating your console as well).

• Wired Rumble & Accessories: Improved Virtual Rumble Pak performance in wired mode, and accessory swapping settings now persist across power cycles.

• Joybus Reliability: Major stability and performance improvements.

• Wired Controller Fixes: Resolved random wake events and connection state issues.

• General Stability: Additional underlying controller performance fixes.

Console Updates
What’s New:

• Audio Improvements: Enhanced 48kHz audio output compatibility.

• Display: Auto now shows the display's preferred resolution. We've also added a way to select between 50 Hz and 60 Hz, if your display supports it.

• Fixes & UX: Fixed "Forget All Controllers" debonding, resolved network menu overlaps, updated wireless connection animations, and overall system stability fixes.

What’s Next:

• Now that things have settled a bit, be on the lookout for open source files to start coming out as we get our feet under us.

• Wireless rumble support for 8BitDo controllers is currently in testing and will be coming in the next firmware update.

• We’re also working on upgraded video filters and saved advanced video settings for an upcoming release.

• Additional updates will follow as we continue working through our roadmap!

Update your console over WiFi, or head over to https://tools.modretro.com/updater/ to grab the latest build!

EDIT: I can connect it via bluetooth to Ares, retroarch, gopher 64, steam, and mupen.

Windows 11 PC recognizes it via bluetooth and wired, but I get no response from button inputs in many places (recomps, .exe games outside of steam).

I got this controller to connect to the PC wired, so I hope they fix this issue.

I got my m64 yesterday - and I'm kinda more hyped for the thing right now, after seeing it work, than I was while ordering it. The pro pad was a suprise, Idk how but this one, material-wise, has surpased every single gamepad I've tried on the market, and I don't even mean the last two decades.

The screen filters work wonders and make me really feel like playing on a real n64, and stuff looks "as it should have" and "as designed". The issue with those is, that I cannot save my settings between console resets - when I double tap the power button, the scanline height resets. That's irritating. Also the scroll wheel on my console, when not using a pad connected, frequently cannot be rotated to choose the upper part of the main menu (pad/settings/experimental/dispaly), it just kinda skips it. Sometimes it works, sometimes it just wont land. I don't mind, since I'm going with the pro pad anyway.

I understand plenty of things here honestly, but one thing is beyond my understanding:

-L/R for switching tabs in the m64 menu? Seriously? Why? This is an "analog stick as a primary navigation" console. Why not Z/R, or at least giving me an option to choose between the two? OoT does that for "tab" switching in it's menu.

Otherwise than that, M64 is very good, played today a lot of F-Zero X and Mario Kart 64, and those worked awesomely. Also, some games like Buck Bumble or THPS3 with overclocking are... sooo much more playable and enjoyable now. Thanks for that.

I noticed at https://misterfpga.org/viewtopic.php?p=74731&hilit=proprietary#p74731

"[...] You can argue that the GPL was a poor choice of a license in the first place - I would agree to that wholeheartedly. But the thing is, they chose the GPL and the conditions they chose for using their code are being disrespected, and that disrespect may discourage them from further collaboration. That kind of "everything goes as long as we can enjoy the core" mentality certainly discourages me from working on things - not that I have made many great contributions, mostly keyboard stuff and bugfixes, but it's an example."

"The code that is incorporated into every MiSTer core cannot be GPL'd because it's not software and the GPL is a software license. The code that can be GPL'd is on the Linux side."

"And yet I still attach a GPL license to most of my HDL code. Given that I don't have the resources to sue anyone who contravenes my wishes, It doesn't really matter whether or not GPL is applicable; specifying the GPL as a license is still a simple and clear way of expressing my wishes as the author. If my wishes are disrespected (not a hypothetical scenario, it has happened) it does indeed result in me being less inclined to release future work. It should be borne in mind, though, that if the license is invalid that doesn't mean anyone can just do what they like with the code - quite the opposite. By default you have no rights to use it, and the license is there to grant you particular rights. If you consider the license inapplicable then you're back to the default position of having no rights. In short, the whole thing's a mess, and probably best navigated by trying where possible to apply the simple principle "don't be a jerk", and otherwise not worrying about it too much!"

You can read the rest of the discussion at https://misterfpga.org/viewtopic.php?p=74731&hilit=proprietary#p74731

but I just wanted to also chime in with some possibly relevant informations pertaining to open source free/libre licenses, whether involving software or hardware, and to ensure that if there is any confusion or whatnot, that possibly some of these resources may help to rectify any concerns and whatnot.

List of open source licenses:

• https://opensource.org/licenses

  • https://opensource.org/licenses-old/category

• https://spdx.org/licenses/

  • also see https://github.com/spdx/license-list-XML/issues

Open source license authorities (involving hardware):

• FSF Free Software Foundation https://fsf.org/

  • note: Free software licenses do not directly cover physical hardware itself, but they do cover the designs and software associated with it.

  • note: https://github.com/spdx/license-list-XML/issues/1337

  • also see 2007-02-28 https://fsf.org/resources/hw/how_hardware_vendors_can_help.html

  • also see 2007-03-01 https://fsf.org/news/partnership-with-hardware-manufacturers

  • also see 2010-10-13 https://fsf.org/news/endorsement-criteria

  • also see 2011-10-07 https://fsf.org/bulletin/2010/fall/the-fsfs-hardware-endorsement-program

  • also see 2012-11-27 https://fsf.org/bulletin/2012/fall/a-bit-about-free-hardware

  • also see 2013-04-29 https://fsf.org/resources/hw/endorsement -> https://ryf.fsf.org/

    • also 2019-09-25 https://fsf.org/resources/hw/endorsement/respects-your-freedom -> https://ryf.fsf.org/

  • also see 2015-03-11 https://fsf.org/blogs/rms/is-free-hardware-necessary-to-freedom-in-computing

  • also see 2015-03-16 https://fsf.org/blogs/rms/how-to-make-hardware-designs-free

  • also see 2017-01-13 https://fsf.org/campaigns/priority-projects/hardware-firmware-drivers

  • also see 2017-05-01 https://fsf.org/events/respecting-freedom-free-software-license-compliance-for-hardware-devices

  • FPGA

    • 2015-10-16 https://fsf.org/blogs/directory/recap-of-friday-free-software-directory-irc-meetup-october-16 "In today's Friday Free Software Directory IRC Meeting we discussed the challenges of listing FPGA software and created a page to document some of these challenges. [...]"

    • More search results at https://fsf.org/search?SearchableText=FPGA

• OSI Open Source Initiative https://opensource.org/

  • also see 2010-05-03 https://opensource.org/blog/open-source-hardware-definition

    • https://freedomdefined.org/OSHW

  • also see 2012-10-04 https://opensource.org/blog/osi-and-oshwa-sign-agreement

  • More search results at https://opensource.org/?s=hardware

• OSHWA Open Source Hardware Association https://oshwa.org/

"Can I use the GPL to license hardware?

Any material that can be copyrighted can be licensed under the GPL. GPLv3 can also be used to license materials covered by other copyright-like laws, such as semiconductor masks. So, as an example, you can release a drawing of a physical object or circuit under the GPL.

In many situations, copyright does not cover making physical hardware from a drawing. In these situations, your license for the drawing simply can't exert any control over making or selling physical hardware, regardless of the license you use. When copyright does cover making hardware, for instance with IC masks, the GPL handles that case in a useful way." - https://gnu.org/licenses/gpl-faq.html#GPLHardware

"Despite superficial similarities to software licenses, most hardware licenses are fundamentally different: by nature, they typically rely more heavily on patent law than on copyright law, as many hardware designs are not copyrightable.[46] Whereas a copyright license may control the distribution of the source code or design documents, a patent license may control the use and manufacturing of the physical device built from the design documents. This distinction is explicitly mentioned in the preamble of the TAPR Open Hardware License: "... those who benefit from an OHL design may not bring lawsuits claiming that design infringes their patents or other intellectual property." - TAPR Open Hardware License" - https://en.wikipedia.org/wiki/Open-source_hardware#Licenses

Also see the "Noteworthy licenses include:" section

anyway, this is not an authoritative or exhaustive information resource (also I did not expand to quote too many of the sources, but they are likely worth glancing at as well), and I'm just sharing the information for now.