sorry, i won't read the rules my fault...Yes, but sharing and asking for it here is against the rules.
sorry, i won't read the rules my fault...Yes, but sharing and asking for it here is against the rules.
I got all that working. Almost everything went smoothly, but:On Ubuntu, open Settings, go to Keyboard Shortcuts and assign anything to Toggle fullscreen mode (e.g. Super+F), then press it in the game.
You can use:Code:make TARGET_N64=0 -j$(nproc)
/usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libGL.so when searching for -lGL
/usr/bin/ld: cannot find -lGL
/usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libSDL2.so when searching for -lSDL2
/usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libSDL2.a when searching for -lSDL2
/usr/bin/ld: cannot find -lSDL2
collect2: error: ld returned 1 exit status
Makefile:702: recipe for target 'build/us_pc/sm64.us.f3dex2e' failed
make: *** [build/us_pc/sm64.us.f3dex2e] Error 1
rm build/us_pc/bin/bidw_skybox.c build/us_pc/bin/bbh_skybox.c build/us_pc/bin/ccm_skybox.c build/us_pc/bin/clouds_skybox.c build/us_pc/bin/wdw_skybox.c build/us_pc/bin/water_skybox.c build/us_pc/bin/bits_skybox.c build/us_pc/bin/bitfs_skybox.c build/us_pc/bin/ssl_skybox.c build/us_pc/sound/sequences/00_sound_player.o build/us_pc/bin/cloud_floor_skybox.c
It definitely requires 64-bit libraries. Perhaps your distribution's packages are too old? I'm using Ubuntu 20.04, by the way.I got all that working. Almost everything went smoothly, but:
Code:/usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libGL.so when searching for -lGL /usr/bin/ld: cannot find -lGL /usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libSDL2.so when searching for -lSDL2 /usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libSDL2.a when searching for -lSDL2 /usr/bin/ld: cannot find -lSDL2 collect2: error: ld returned 1 exit status Makefile:702: recipe for target 'build/us_pc/sm64.us.f3dex2e' failed make: *** [build/us_pc/sm64.us.f3dex2e] Error 1 rm build/us_pc/bin/bidw_skybox.c build/us_pc/bin/bbh_skybox.c build/us_pc/bin/ccm_skybox.c build/us_pc/bin/clouds_skybox.c build/us_pc/bin/wdw_skybox.c build/us_pc/bin/water_skybox.c build/us_pc/bin/bits_skybox.c build/us_pc/bin/bitfs_skybox.c build/us_pc/bin/ssl_skybox.c build/us_pc/sound/sequences/00_sound_player.o build/us_pc/bin/cloud_floor_skybox.c
Do some of my libraries need to be 32-bit versions, or is there still a way I can use 64-bit libraries?
The MakeFile is actually forcing to compile the port as 32-bit:It definitely requires 64-bit libraries. Perhaps your distribution's packages are too old? I'm using Ubuntu 20.04, by the way.
ifeq ($(WINDOWS_BUILD),1)
LDFLAGS := -m32 -march=i686 -Llib -lpthread -lglew32 `sdl2-config --static-libs` -lm -lglu32 -lsetupapi -ldinput8 -luser32 -lgdi32 -limm32 -lole32 -loleaut32 -lshell32 -lwinmm -lversion -luuid -lopengl32 -no-pie -static
else
LDFLAGS := -m32 -march=i686 -lm -lGL `sdl2-config --libs` -no-pie -lpthread `pkg-config --libs libusb-1.0 glfw3` -lasound -lX11 -lXrandr -lpulse
Yea I've just seen vids of people starting the .exe with it starting up immediately and I'm scratching my head about what to do...@Bagel1900 same (also first post on GBATemp)
I guess we don't have the same source code, then.The MakeFile is actually forcing to compile the port as 32-bit:
Code:ifeq ($(WINDOWS_BUILD),1) LDFLAGS := -m32 -march=i686 -Llib -lpthread -lglew32 `sdl2-config --static-libs` -lm -lglu32 -lsetupapi -ldinput8 -luser32 -lgdi32 -limm32 -lole32 -loleaut32 -lshell32 -lwinmm -lversion -luuid -lopengl32 -no-pie -static else LDFLAGS := -m32 -march=i686 -lm -lGL `sdl2-config --libs` -no-pie -lpthread `pkg-config --libs libusb-1.0 glfw3` -lasound -lX11 -lXrandr -lpulse
Update: Removing or commenting out all usages of '-m32' in the Makefile will make the compilation finish successfully. Now it's time to see whether the executable 'sm64.us.f3dex2e' will actually work...
I guess we don't have the same source code, then.
Just how many versions have been leaked?
fullscreen false
key_a 38
key_b 51
key_start 57
key_r 54
key_z 37
key_cup 328
key_cdown 336
key_cleft 331
key_cright 333
key_stickup 17
key_stickdown 31
key_stickleft 30
key_stickright 32
The MakeFile is actually forcing to compile the port as 32-bit:
Code:ifeq ($(WINDOWS_BUILD),1) LDFLAGS := -m32 -march=i686 -Llib -lpthread -lglew32 `sdl2-config --static-libs` -lm -lglu32 -lsetupapi -ldinput8 -luser32 -lgdi32 -limm32 -lole32 -loleaut32 -lshell32 -lwinmm -lversion -luuid -lopengl32 -no-pie -static else LDFLAGS := -m32 -march=i686 -lm -lGL `sdl2-config --libs` -no-pie -lpthread `pkg-config --libs libusb-1.0 glfw3` -lasound -lX11 -lXrandr -lpulse
Update: Removing or commenting out all usages of '-m32' in the Makefile will make the compilation finish successfully. Now it's time to see whether the executable 'sm64.us.f3dex2e' will actually work...
patch -p1 -i/path/to/sm64pc.diff
Key Code ¦ Key Code ¦ Key Code
¦ ¦
Esc 1 ¦ A 30 ¦ Caps Lock 58
! or 1 2 ¦ S 31 ¦ F1 59
@ or 2 3 ¦ D 32 ¦ F2 60
# or 3 4 ¦ F 33 ¦ F3 61
$ or 4 5 ¦ G 34 ¦ F4 62
% or 5 6 ¦ H 35 ¦ F5 63
^ or 6 7 ¦ J 36 ¦ F6 64
& or 7 8 ¦ K 37 ¦ F7 65
* or 8 9 ¦ L 38 ¦ F8 66
( or 9 10 ¦ : or ; 39 ¦ F9 67
) or 0 11 ¦ " or ' 40 ¦ F10 68
_ or - 12 ¦ ~ or ` 41 ¦ F11 133
+ or = 13 ¦ Left Shift 42 ¦ F12 134
Bksp 14 ¦ | or \ 43 ¦ NumLock 69
Tab 15 ¦ Z 44 ¦ Scroll Lock 70
Q 16 ¦ X 45 ¦ Home or 7 71
W 17 ¦ C 46 ¦ Up or 8 72
E 18 ¦ V 47 ¦ PgUp or 9 73
R 19 ¦ B 48 ¦ Gray - 74
T 20 ¦ N 49 ¦ Left or 4 75
Y 21 ¦ M 50 ¦ Center or 5 76
U 22 ¦ < or , 51 ¦ Right or 6 77
I 23 ¦ > or . 52 ¦ Gray + 78
O 24 ¦ ? or / 53 ¦ End or 1 79
P 25 ¦ Right Shift 54 ¦ Down or 2 80
{ or [ 26 ¦ Prt Sc or * 55 ¦ PgDn or 3 81
} or ] 27 ¦ Alt 56 ¦ Ins or 0 82
Enter 28 ¦ Spacebar 57 ¦ Del or . 83
Ctrl 29 ¦ ¦
Given most PC ports games also on the N64 (or vice versa) were often radically different what are we going to do here?A pc port that's era approprite that runs on windows 95 and uses glide would be so cool
Yeah coincidence. The original decompilation leaks and proper release were months back ( https://github.com/n64decomp/sm64 ) and made by decompilation (a technique that has been increasing in viability for a few years now). Removing all the stuff to interface with the N64 and instead making it work on the PC is then the next logical step really, though I am still somewhat impressed at the timelines. The recent leaks were leaks in the classical sense of someone wanders into somewhere they are not supposed to be and grabs the interesting stuff, finds an old drive not properly disposed of, or breaks trust with files they have access to and shares with others.Since I've seen this news, I've thought of some questions:
Are the Nintendo leaks and SM64 Port leak at the release happening around the same time purely coincidental? Who is the actual creator behind this .exe file? (I'm sure you're wondering about this one) Is it safe to run the Port program when it is being shared by many sources, passed down from many different people, from links that originated from some Discord server (that won't be named, I'm sure, for good reasons), and 4Chan?
Correct me if I'm wrong about any of this, I definitely could of missed something important.