- Thread starter kristianity77
- Start date
- Views 130,517
- Replies 511
- Likes 1
What issues if you dont mind me asking? We have a bug report channel on jits that the port devs watch closely so i can report the issues there or you can report it directly.
Don't worry, the issues were reported already. But thanks for letting us know that's a possibility!
D
Deleted User
Guest
I'm having some trouble building the fgsfdsfgs build, I think the building instructions are outdated since I look at how to build the pc version and it's much simplier, even when I got everything installed, using source $DEVKITPRO/switchvars.sh gives me an error that it doesn't exist even though it does and I get an error whenever I tried to build.
Is this your video? How do you put 3DS games like Samus Returns on the switch? Or are those fake? Sorry if this is well known, I am a bit out of the loop I guess...
EDIT: Apparently this is just a shortcut for RetroArch to directly load the game. Nice.
Last edited by Patatas,
D
Deleted User
Guest
dude said or are those fake...rolls eyes to infinity and beyond....
New update about the Render96 HD Model Pack v1.3 (PC Port only)
The Switch fork of sm64ex is somewhat outdated, so the SGI pack won't work on it. I will sync it to upstream eventually.
Would love to see this on Xboxone, would have to be compiled into an appx tho...
I wonder if this could be built into a Retroarch Game core?
there is Doom/Quake etc.. but I think ninty would go nuclear if that happened lol
D
Deleted User
Guest
Thanks, looking forward to it, would this include the build instructions? Cause I've been having some issues with that.
I’ve just got myself a switch lite for handheld play and have installed v7 (same as I have installed on my normal switch)
where are the saves for v7 so I can transfer them over and carry on with my game?
where are the saves for v7 so I can transfer them over and carry on with my game?
I ended up using JKSV to export them from one switch and import on the other as they are no longer on the root of SD and are saved to the Emunand like other saves
HI fellow Tempers, a new version of this post for the latest repo is on the tutorials section
https://gbatemp.net/threads/building-sm64-for-nintendo-switch-from-sm64ex-alo-repository.652092/
Use the next steps for the old fgsfdsfgs repo, for the new one go to tutorial
Hi, I hope the next steps help to somebody, first forgive my bad English, is no my native language.
Switch Compilation Process
If you read the guide:
https://github.com/fgsfdsfgs/sm64pc/wiki/Compiling-for-Nintendo-Switch
The steps are loosely explained, but they don’t work well for me, so I decided read a lot of documentation and this thread completely.
When you want to compile by yourself the code for Nintendo Switch, you will need have a functional MSYS2 shell, for installing it you need:
Download the latest version from: https://github.com/msys2/msys2-installer/releases
Install the version corresponding to your Operating System (64 or 32 bits).
Accept the defaults in installation program of MSYS2 once you finish the installation you will have shortcuts for MSYS2, MinGW32 and MinGW64. MSYS2 is used to compiling POSIX binaries for Linux from Windows.
MinGW32 & MinGW64 compile Native Windows binaries using a linux toolchain (gcc, bash, etc.)
Launch MSYS2 shell and execute the command: pacman -Syuu several times until you get the message: "there is nothing to do".
In order to compile the Switch binary you must first confirm all works fine compiling a binary for Windows. So do the next steps:
Install prerequisites
In a MinGW64 shell (or MinGW32 if you have a Windows 32 bit edition, why?). Be sure the prompt shows MINGW64 or MINGW32 if not you started the wrong shell, close it and open the right one.
Please execute the next command, several times until you get the message "there is nothing to do", you can be asked to restarts the MINGW64 environment few times:
Then execute the next command:
Once the installation end, verify the MSYS2 database again:
Clone the repository, using the
The repository is cloned to a subfolder of the "Home" directory of MinGWXX Shell, on the prompt "~" means your home directory.
You need copy a legal copy of the original ROM in the cloned directory, it must be in "Big Endian" formatted and called:
copy the file to the path
If your ROM isn't on Big Endian format, use https://hack64.net/tools/swapper.php to convert it.
You should set the
And for Windows 32 bits use:
The repository needs you to compile the AudioFile library, so you need to run these commands:
Then you need to edit the
By:
Pay attention to the space before "
Last, you can compile the Widows executable using make and the build options you choose, by example:
If all go through you get an
Troubleshooting
After all works fine and a Windows binary is created, you can run extra steps for make a Switch
First you need to install DevKitPro.
You need to edit the
And add the next lines at end of it:
Import the cypher keys of DevKitPro
In my case the command fail because the server didn’t send the correct file:
So, I did save the next content on a file called pubring.gpg: ()
Then import it manually:
By example:
Next sign locally the key:
Then verify the key is working well:
You should get a response just like:
Install DevKitPro Keyring
Now verify MSYS2 database:
Install DevKitPro packages:
Set needed variables
By last run the next commands in order to make the NRO file, PLEASE DO NOT FORGET TO COPY THE EXE FILE GENERATED FOR WINDOWS TO OTHER PATH, it will be deleted on the next step.
(optional)
You can use any build options you want, one example:
BUILD OPTIONS
Optional Steps
If you want a Banner for the
By these:
After the NRO file is created, you can use SAK Switch Army Knife to make a NSP forwarder installable on the HOS.
-edited to update the new packages dependencies-
--edited to correct some typos and code errors--
https://gbatemp.net/threads/building-sm64-for-nintendo-switch-from-sm64ex-alo-repository.652092/
Use the next steps for the old fgsfdsfgs repo, for the new one go to tutorial
Hi, I hope the next steps help to somebody, first forgive my bad English, is no my native language.
Switch Compilation Process
If you read the guide:
https://github.com/fgsfdsfgs/sm64pc/wiki/Compiling-for-Nintendo-Switch
The steps are loosely explained, but they don’t work well for me, so I decided read a lot of documentation and this thread completely.
When you want to compile by yourself the code for Nintendo Switch, you will need have a functional MSYS2 shell, for installing it you need:
Download the latest version from: https://github.com/msys2/msys2-installer/releases
Install the version corresponding to your Operating System (64 or 32 bits).
Accept the defaults in installation program of MSYS2 once you finish the installation you will have shortcuts for MSYS2, MinGW32 and MinGW64. MSYS2 is used to compiling POSIX binaries for Linux from Windows.
MinGW32 & MinGW64 compile Native Windows binaries using a linux toolchain (gcc, bash, etc.)
Launch MSYS2 shell and execute the command: pacman -Syuu several times until you get the message: "there is nothing to do".
In order to compile the Switch binary you must first confirm all works fine compiling a binary for Windows. So do the next steps:
Install prerequisites
In a MinGW64 shell (or MinGW32 if you have a Windows 32 bit edition, why?). Be sure the prompt shows MINGW64 or MINGW32 if not you started the wrong shell, close it and open the right one.
Please execute the next command, several times until you get the message "there is nothing to do", you can be asked to restarts the MINGW64 environment few times:
pacman -SyuuThen execute the next command:
pacman -Sy --noconfirm base-devel git make mercurial python3 subversion unzip autoconf automake libtool pkg-config autoconf-wrapper mingw-w64-x86_64-cmake mingw-w64-x86_64-gcc mingw-w64-x86_64-glew mingw-w64-x86_64-SDL2 mingw-w64-x86_64-toolchain mingw-w64-x86_64-SDLOnce the installation end, verify the MSYS2 database again:
pacman -SyuuClone the repository, using the
--recursive option in order to clone all the trees.git clone --recursive https://github.com/fgsfdsfgs/sm64exThe repository is cloned to a subfolder of the "Home" directory of MinGWXX Shell, on the prompt "~" means your home directory.
You need copy a legal copy of the original ROM in the cloned directory, it must be in "Big Endian" formatted and called:
./baserom.us.z64copy the file to the path
c:\msys64\home\USERNAME\sm64exIf your ROM isn't on Big Endian format, use https://hack64.net/tools/swapper.php to convert it.
You should set the
$PATH variable. For Windows 64 bits use the command:export PATH=/mingw64/bin:/mingw32/bin:$PATHAnd for Windows 32 bits use:
export PATH=/mingw32/bin:/mingw64/bin:$PATHThe repository needs you to compile the AudioFile library, so you need to run these commands:
Code:
cd sm64ex/tools/audiofile-0.3.6/
autoreconf -i
LIBS=-lstdc++ ; ./configure --disable-docs
make
mkdir ../lib
cp libaudiofile/.libs/libaudiofile.a ../lib/
cp libaudiofile/.libs/libaudiofile.la ../lib/Then you need to edit the
sm64ex\tools\Makefile file using a decent Text Editor and change the line:tabledesign_CFLAGS := -Wno-uninitialized -laudiofileBy:
tabledesign_CFLAGS := -Wno-uninitialized -laudiofile -lstdc++Pay attention to the space before "
-lstdc++". then run the commands:
Code:
cd ..
makeLast, you can compile the Widows executable using make and the build options you choose, by example:
Code:
cd ..
make BETTERCAMERA=1 NODRAWINGDISTANCE=1 TEXTURE_FIX=1 EXT_OPTIONS_MENU=1 -j9If all go through you get an
.exe file on build subfolder of sm64ex.Troubleshooting
- If you get the error gcc: command not found or make: gcc: No such file or directory you do not install all needed packages or run the wrong Shell, be sure of running «MINGW32» or «MINGW64» and what that is pointed on the prompt in purple.
- If the ROM is missing or wrong format/version you get the error Failed to open baserom.us.z64! Verify the correct ROM at the c:\msys64\home\<username>\sm64ex.folder.
- If you get the error make: *** No targets specified and no makefile found. Stop. You are on the wrong folder the last make command should be run from c:\msys64\home\<username>\sm64ex folder.
- Be sure of get the responses Target: i686-w64-mingw32 or Target: x86_64-w64-mingw32 when you run the command gcc -v if else other is shown on screen you install the wrong gcc package or run MSYS shell, remember the process should be run on «MINGW32» or «MINGW64» shells.
After all works fine and a Windows binary is created, you can run extra steps for make a Switch
NRO fileFirst you need to install DevKitPro.
You need to edit the
pacman.conf on c:\msys64\etc\And add the next lines at end of it:
Code:
[dkp-libs]
Server = https://downloads.devkitpro.org/packages
[dkp-windows]
Server = https://pkg.devkitpro.org/packages/windows/$arch/Import the cypher keys of DevKitPro
Code:
pacman-key --recv BC26F752D25B92CE272E0F44F7FD5492264BB9D0 --keyserver keyserver.ubuntu.com
pacman-key --recv F7FD5492264BB9D0In my case the command fail because the server didn’t send the correct file:
Code:
gpg: keyserver receive failed: General error
==> ERROR: Remote key not fetched correctly from keyserver.So, I did save the next content on a file called pubring.gpg: ()
Then import it manually:
Code:
pacman-key --import "FULL_PATH_TO_FOLDER_CONTAINING_pubring_gpg"By example:
Code:
pacman-key --import "C:\downloads\DevKitPro"Next sign locally the key:
Code:
pacman-key --lsign BC26F752D25B92CE272E0F44F7FD5492264BB9D0
pacman-key --lsign F7FD5492264BB9D0Then verify the key is working well:
Code:
pacman-key -l BC26F752D25B92CE272E0F44F7FD5492264BB9D0
pacman-key -l F7FD5492264BB9D0You should get a response just like:
Code:
pub rsa4096 2018-02-28 [SC]
BC26F752D25B92CE272E0F44F7FD5492264BB9D0
uid [ full ] Dave Murphy (WinterMute) <[email protected]>
sub rsa4096 2018-02-28 [E]Install DevKitPro Keyring
Code:
pacman -U https://pkg.devkitpro.org/devkitpro-keyring.pkg.tar.xzNow verify MSYS2 database:
Code:
pacman -Sy
pacman -SyuInstall DevKitPro packages:
Code:
pacman -S --noconfirm switch-dev devkitA64 dkp-toolchain-vars libnx switch-tools switch-mesa switch-libdrm_nouveau switch-sdl2Set needed variables
Code:
export DEVKITPRO=/opt/devkitpro
export DEVKITARM=/opt/devkitpro/devkitARM
export DEVKITPPC=/opt/devkitpro/devkitPPCBy last run the next commands in order to make the NRO file, PLEASE DO NOT FORGET TO COPY THE EXE FILE GENERATED FOR WINDOWS TO OTHER PATH, it will be deleted on the next step.
Code:
git stash
git checkout master
git pull
git checkout -f switch
make clean
Code:
source $DEVKITPRO/switchvars.shYou can use any build options you want, one example:
Code:
make TARGET_SWITCH=1 BETTERCAMERA=1 NODRAWINGDISTANCE=1 TEXTURE_FIX=1 -j9BUILD OPTIONS
| Build option | Default | Possible values | Description |
| VERSION | us | us, eu, jp, sh | Which ROM to use. The selected ROM has to be in the repo folder with the name baserom.$VERSION.z64. sh is currently broken. |
| TARGET_BITS | 32, 64, | TARGET_BITS=n appends some compiler flags for an n-bit build. If the value is empty, the option does nothing, assuming your native toolchain will set everything up by itself. Use this only if you're having trouble otherwise. | |
| TARGET_RPI | 0 | 0, 1 | If 1, select optimal settings for Raspberry PI hardware. See the main article (https://github.com/sm64pc/sm64pc/wiki/Helper-compiling-script-for-Raspberry-Pi) on that. |
| TARGET_WEB | 0 | 0, 1 | If 1, build Emscripten version. See the main article (https://github.com/sm64pc/sm64pc/wiki/Compiling-for-the-web) on that. |
| WINDOWS_BUILD | 0, 1 | If 1, build for Windows. Usually set automatically if building on Windows. | |
| OSX_BUILD | 0 | 0, 1 | If 1, build for OSX. |
| WINDOWS_CONSOLE | 0 | 0, 1 | If 1, append -mconsole to Windows CFLAGS, making a console window appear while the game is running. Can be useful for debugging purposes. |
| DEBUG | 0 | 0, 1 | If 1, build with debug symbols and default optimization level. Otherwise build with -O2. |
| RENDER_API | GL | GL, GL_LEGACY, D3D11, D3D12 | Select rendering backend to use. GL corresponds to OpenGL 2.1 (gfx_opengl.c), GL_LEGACY corresponds to OpenGL 1.3 (gfx_opengl_legacy.c). Direct3D backends will also force WINDOW_API to DXGI. |
| WINDOW_API | SDL2 | SDL2, DXGI | Select windowing backend. GL renderers force SDL2 and D3D renderers force DXGI for now, so you don't need to specify this. |
| AUDIO_API | SDL2 | SDL2 | Select audio backend. There's only one right now. |
| CONTROLLER_API | SDL2 | SDL2 | Specify list of controller backends to use. There's only one right now. |
| BETTERCAMERA | 0 | 0, 1 | If 1, build with analog camera support (uses Puppycam). |
| NODRAWINGDISTANCE | 0 | 0, 1 | If 1, build with disabled draw distance (every object is active at all times). May affect gameplay. |
| TEXTURE_FIX | 0 | 0, 1 | If 1, enable various texture-related bugfixes (e.g. fixes the smoke texture). |
| EXT_OPTIONS_MENU | 1 | 0, 1 | If 1, enable Options menu. Accessed from the Pause menu by pressing R. |
| EXTERNAL_DATA | 0 | 0, 1 | If 1, load textures and soundbanks from external files. Allows you to use texture packs. The default data is copied to a res folder next to the produced executable. (En Switch va en la carpeta raíz), para PC no lo genera |
| DISCORDRPC | 0 | 0, 1 | If 1, enable Discord Rich Presence support. Only works on x86_64. |
| TEXTSAVES | 0 | 0, 1 | If 1, use INI-based save format instead of binary EEPROM dumps. Experimental. |
Optional Steps
If you want a Banner for the
NRO file, you need to put a file called nx_icon.jpg on the sm64ex folder and BEFORE run the last make command you edit the Makefile file and replace the next lines
Code:
# add `--icon=$(APP_ICON)` to this when we get a suitable icon
%.nro: %.stripped %.nacp
@elf2nro $< $@ --nacp=$*.nacp
@echo built ... $(notdir $@)By these:
Code:
# add `--icon=$(APP_ICON)` to this when we get a suitable icon
%.nro: %.stripped %.nacp
@elf2nro $< $@ --nacp=$*.nacp --icon=$(APP_ICON)
@echo built ... $(notdir $@)After the NRO file is created, you can use SAK Switch Army Knife to make a NSP forwarder installable on the HOS.
-edited to update the new packages dependencies-
--edited to correct some typos and code errors--
Last edited by impeeza,
Its complete but being optimized. I have it, its a finished product content wise and everything works but its very laggy at the moment. The dev team is working on optimizing some code and then it will be released. The reason for the long delay is a combination of this being a big update in terms of work put in and also waiting for some other connected projects to finish.
Similar threads
- Question
- No one is chatting at the moment.
-
-
-
-
-
@
CameronCataclysm:
Why no blog posts about Nitendont going after Garry's Mod repos that have been up for a decade or 2? -
-
-
@
Xdqwerty:
Is it safe to update a modded ps3?
Can I play online in pirated games? (with ps3hen either enabled or not) -
-
-
-
-
-
@
Xdqwerty:
@salazarcosplay, I used apollo save tool to activate my ps3 offline so i could play a game that wasnt working
-
S @ salazarcosplay:from what I understood. you load up the piratged game. you the clear the syscalls, then you play
-
-
-
-
-
-
-
-
-
-
