Watching the video you long for the days when getting each star required a significant challenge to be completed even if several are located in the same area....oh Odyssey what have you done!
-
Ever wanted an RSS feed of all your favorite gaming news sites? Go check out our new Gaming Headlines feed! Read more about it here.
-
We have made minor adjustments to how the search bar works on ResetEra. You can read about the changes here.
A PC port of Mario 64 has appeared out of nowhere
- Thread starter RoboitoAM
- Start date
Oh I followed that pastebin from A to Z. Didn't work. Encountered the issues I've mentioned above :(
Were you getting warnings? I'm helping someone else who was anyway I'm running through the build right now.
Indeed...with each tied to an actual challenge not " can you ground pound or climb a tree?"
To the people having trouble building the game, try the steps here instead:
Before Building
how to build the super mario 64 pc port binary will be in build/sm64.us.f3dex2e get the sm64 US rom in z64 format, rename to baserom.us.z64 and put it in the sm64pc root folder you can also use the japanese rom (except rename to .jp instead of .us) and when you run make you would pass VER...
rentry.co
I dunno, Odyssey would have been a giant pain in the ass if you were sent to your ship every single time you got a moon.
I was thinking of keeping it in Odyssey's spirit; 100 easy braindead, 100 medium somewhat a challenge, and 100 hard actually a challenge moons.
I know your banned but in case you were seriously asking or in case other people are wondering about how to legally create their own ROMs, all you need is a retrode and the N64 add-on. After that it's a really simple process of plugging it into your PC and letting it do the work. Being able to create your own Room library has become a lot easier because of retrode.
The Ripping Thread - How to build your own legit retro ROM library.
Hey all, First things first, I don’t want this thread to be about piracy-talk. At the contrary, I’d like this thread to be a tool for anyone who’d like to tackle emulation with their own games. In many, if not all emulation threads there is the infamous piracy talks/accusations that fly off...
www.retrogameboards.com
Very likely tbh. I feel like it's going to be the new Doom that people port for fun
Isn't that basically the pastebin but in a web format? How different is the OpenGL / DirectX downloads versus the master branch on Github?To the people having trouble building the game, try the steps here instead:
Before Building
how to build the super mario 64 pc port binary will be in build/sm64.us.f3dex2e get the sm64 US rom in z64 format, rename to baserom.us.z64 and put it in the sm64pc root folder you can also use the japanese rom (except rename to .jp instead of .us) and when you run make you would pass VER...rentry.co
The github decomp is the source code for building an N64 ROM. The PC source code leaked from the same people who did the N64 one, both in a DX12 version and a OpenGL version. Remember that it's a leak with no official instructions, that's why building it's such a mess right now. I had a super hard time with it as well.
Yep...kids can do the first 100, regular players the first 200 and experts the final 100. .
Ah, so the Github repo builds a ROM (which...I guess you could run on a physical N64 or N64 emulator), but the leak is modified to produce an executable?
Yeah cuts away most of the bloat while keeping a good amount of content in today's environment.
So then...why wasn't this a pull request lol? Somebody was working on it then it got swiped off their PC and was posted? The repo is a really cool idea, but it looks like nothing's happening to it. I assume it's being talked about on the discord they have linked, but that makes their future intentions a little opaque.
Got it working.
Any ideas what I could put into the config file? Besides controls and fullscreen?
Any ideas what I could put into the config file? Besides controls and fullscreen?
Now can someone please make this for Perfect Dark? I have my cartridge ready!
It took me a while, but I think I finally nailed the times. I honestly didn't know the input lag on the N64 was a thing, and how it actually helped lol
It took me a while, but I think I finally nailed the times. I honestly didn't know the input lag on the N64 was a thing, and how it actually helped lol
To the people having trouble building the game, try the steps here instead:
Before Building
how to build the super mario 64 pc port binary will be in build/sm64.us.f3dex2e get the sm64 US rom in z64 format, rename to baserom.us.z64 and put it in the sm64pc root folder you can also use the japanese rom (except rename to .jp instead of .us) and when you run make you would pass VER...rentry.co
This changes the issue that Buff DrinkLots was seeing, so that it installs the correct component.
That being said I still run into issues following that method:
Code:
$ CC=x86_64-pc-msys-gcc CXX=x86_64-pc-msys-g++ ./autogen.sh --prefix=/usr/
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
configure.ac:16: installing './compile'
configure.ac:19: installing './config.guess'
configure.ac:19: installing './config.sub'
configure.ac:12: installing './install-sh'
configure.ac:12: installing './missing'
Makefile.am:16: error: 'pkgconfig_DATA' is used but 'pkgconfigdir' is undefined
docs/Makefile.am:60: warning: '%'-style pattern rules are a GNU make extension
docs/Makefile.am:63: warning: '%'-style pattern rules are a GNU make extension
docs/Makefile.am:66: warning: '%'-style pattern rules are a GNU make extension
examples/Makefile.am: installing './depcomp'
libaudiofile/Makefile.am:113: warning: source file 'modules/UT_RebufferModule.cpp' is in a subdirectory,
libaudiofile/Makefile.am:113: but option 'subdir-objects' is disabled
automake-1.16: warning: possible forward-incompatibility.
automake-1.16: At least a source file is in a subdirectory, but the 'subdir-objects'
automake-1.16: automake option hasn't been enabled. For now, the corresponding output
automake-1.16: object file(s) will be placed in the top-level directory. However,
automake-1.16: this behaviour will change in future Automake versions: they will
automake-1.16: unconditionally cause object files to be placed in the same subdirectory
automake-1.16: of the corresponding sources.
automake-1.16: You are advised to start using 'subdir-objects' option throughout your
automake-1.16: project, to avoid future incompatibilities.
parallel-tests: installing './test-driver'
autoreconf: automake failed with exit status: 1and then once I change directory into libaudiofile and run make -j5:
Code:
$ make -j5
make: *** No targets specified and no makefile found. Stop.So yeah, not sure what I'm missing, but those instructions don't do it for me either :/
The PC port had been done for a while, but it was/is only in their private repo.
The team had been debating for months on how to release this because they wisely wanted to avoid Nintendo's attention.
But then someone leaked the exe and then one of the devs just shrugged his/her shoulders and released the code on an external site.
I think they're trying to separate the disassembly/educational aspect of the project and the inevitable "piracy"/porting aspect as much as possible.
Oh God that sounds amazing.
I wasn't quite ready to try this just yet, but this detail has piqued my curiosity.
Iirc, the team mentioned that the n64 game is triple buffered which explains the lag.
Someone else showed me the first issue, make sure you file paths are correct. Sys2 -> sm64pc, sys2 files -> sm64-master, libaudio, baserom.us.z64. As for the next thing it some stupid Windows with Makefile's shit, first rename the make file to have no extension.
I FINALLY managed to build it on Windows, apparently. Previously I only managed to do it on a Linux VM, and it was a pain in the ass to do so.
I followed this tutorial, step by step:
The only problem I had is that the first time I did pacman -Syu it told me to close the window and run the command again. That didn't appear in the guide, but I did it. Everything else went according to the guide.
EDIT: It did in fact build!
I'm gonna poke at the source code now to see if I can make some dumb changes. I have very limited progamming knowledge but maybe I can make Mario jump higher or something lol
I followed this tutorial, step by step:
Before Building
how to build the super mario 64 pc port binary will be in build/sm64.us.f3dex2e get the sm64 US rom in z64 format, rename to baserom.us.z64 and put it in the sm64pc root folder you can also use the japanese rom (except rename to .jp instead of .us) and when you run make you would pass VER...
rentry.co
The only problem I had is that the first time I did pacman -Syu it told me to close the window and run the command again. That didn't appear in the guide, but I did it. Everything else went according to the guide.
EDIT: It did in fact build!
I'm gonna poke at the source code now to see if I can make some dumb changes. I have very limited progamming knowledge but maybe I can make Mario jump higher or something lol
It was made by the same people who made the decomp. They meant to have a proper full release when the port was 100% finished, but it leaked early.
That's smart, but also if Nintendo does come after them because Nintendo thinks they crossed the line somewhere are they even going to have the funds to defend themselves?
I'm not trying to be a negative Nancy. I think this project is awesome. I just think they were in a tough position even before this port was leaked. I hope to have it running on my machine someday (when I can get a legal ROM).
Nope because this was legally dumped. They figured out that you could actually decompile the game by doing some trickery and it would literally give the entire source code because nintendo forgot to optimize the code so it was all basically there for them to see.
Did you make it work?
I tried to do the smoke fix edit but it wouldn't compile.
I get that they think they're legally in the clear. I'm just saying if Nintendo decided to go to court anyways (say, because they have their own version coming out soon) who would have the cash to defend their argument in court? Mario's a pretty big deal and "bankrupt the other party to settle for our way" is a somewhat viable strategy for bigger companies.
I mean they can just say we're looking at a copy of a game we all own on a version we own, and we're modifying our own copies or something stupid. But yeah ninty will just shovel millions to drown them out.
This is the kind of narrative that sport lawyers get excited about. Little person vs. Megacorp on a clear cut case of tech rights? Pro bono for days with potential for a huge payout.
Can't wait until someone figures out how to do this for Luigi's mansion 3's low health noise in 2042
Doesn't it depend on their country as well. I think things get sticky when they're in other countries especially countries that don't give a shit about piracy like say Russia.
I hope there is somebody out there willing to do that. I'd be incredibly bummed if this got shut down. At the very least, this would be a good resource to show how much of a technical jump it is to go from a solid 16-bit 2D game to a "primitive" 3D game.
Yes, it did work! I just commented these lines. No more annoying underwater low health sound
Holy cow just realized at least what i was missing for these steps. Classic dumb mistake, when I was typing "msys2" in the windows start menu, it auto fills to "MSYS2 MSYS", and NOT "MSYS MinGW 64-bit"
after starting a new terminal using MiniGW the commands appear to be working now *eyeroll*
I'm not a crazy SM64 aficionado that knows all the ins and outs of the game but, I am so amazed by the accuracy of this port. Everything I've seen seems to be fully replicated exactly like the original.
I don't know jack about programming, coding and all that but, it blows my mind that the code is technically not the original but a fan made solution yet it essentially equals to the same experience.
I don't know jack about programming, coding and all that but, it blows my mind that the code is technically not the original but a fan made solution yet it essentially equals to the same experience.
