Super Mario 64 PC Port

>I implemented a 3-point texture filter that's more accurate to the N64 than the emulator is
The N64 looked like shit big surprise. Doesn't mean PJ64 + Angrylion are less accurate.

Custom maps when?

>implying vaseline64 ever looked good

>Needing plugins to have accurate emulation
Pathetic.

Besides, who would want to play in 240p without a CRT and a clean signal.

Join the discord if you want to see modding progress and share builds

discord.gg/uBRYZJU

>no comparison
ahh yes great job user

You're missing the point, fucking retard. The end goal of emulation is to preserve the output that the real hardware would spit out. It doesn't matter what display you send it off to, all that matters is the completed frame rendered by the emulator looks exactly like it did on the console. You want to put that on a CRT? Go for it. Has fuck all to do with the emulator. You want to slap a CRT shader over that output and view it on a 4k OLED? That's up to you.

>Pathetic
Imagine giving a fuck about how an emulator accomplishes its goals.

>You're missing the point
If I wanted a framebuffer accurate experience, I wouldn't have blown up the resolution to begin with. You're missing the real point, which is to convert the exact look of SM64 to a HD PC experience.
>Imagine giving a fuck about how an emulator accomplishes its goals.
The fact that the emulator has broken rendering out of the box is quite embarrassing. Plugins are supposed expand possibilities, not patch what ought to already be there.
Imagine if PS1 games all had texture filtering and you needed a plugin to get the intended look? That would be scorned.

Wow that was fucking hard. I captured the screenshot in a 640x480 NTSC window, instead of exclusive fullscreen with integer scaling to get a higher resolution image which would be easier to compare to the original post one. Whoop dee fucking do. And if I wanted an "HD" PC experience of Super Mario 64, why would I ever waste my time using a shittily implemented 3 point filter which fails to even function properly? (note the blurring from forced bilinear filtering in your pc vs the hard square pixels from my original pic)

>The fact that the emulator has broken rendering out of the box is quite embarrassing.
There is nothing broken about the EMULATOR, the only thing broken is using HLE renderers that have lower compatibility than a LLE CPU based software renderer. What a fucking surprise. The emulator itself is still sending the same commands to the plugin and getting pixel accurate output.

Attached: SUPER MARIO 64_0001.png (640x480, 406.43K)

>Also, mobile port when
Can't you just play the WASM version on your phone?

nah the browser version loads but the controls dont work right

>note the blurring from forced bilinear filtering in your pc vs the hard square pixels from my original pic

It's not like Project64 doesn't suffer from the same problem when the resolutions get blown up.
Besides, it's an easy toggle I didn't enable. The port already scales 2D elements properly.
For the record, in case you misunderstood me, I wasn't referring to your picture when I talked about blowing up.

>There is nothing broken about the EMULATOR, the only thing broken is using HLE renderers that have lower compatibility than a LLE CPU based software renderer

I fucking hate reductionists.
Rendering is a huge fucking chunk of emulation. If you're just running logic without getting any visual feedback, you aren't really emulating it properly, are you?

This is what it looks like fresh out of the public PC port. It's technically an upgrade, but it's an inaccuracy.

Attached: default.jpg (1920x1080, 315.77K)

i was normally playing the analog camera version when the game crashed as soon as i entered hazy maze cave, did that happen to anyone else?

Attached: 1561858172435.png (500x375, 95.08K)

yeah its because for some reason if its compiled on windows it crashes when trying to boot from save. I've been looking for another version but cant find one.

You simply don't understand how Nintendo 64 emulation works. The emulator is essentially passing GPU commands to the plugin. It's not just "running logic" like you put it. It's processing all the vertices and drawcalls and passing it to the plugin which then handles compiling it all and filling in the colors for the pixels. The emulator is responsible for setting up the frame, the plugin is responsible for shading it.

And no, Project64 does NOT suffer from forced bilinear filtering when you use Angrylion. It is actually using a CPU based texture filter that doesn't result in the smooth and blurry mess we see in things like GlideN64 and the native PC port.

Just tested it and it worked perfectly fine for me. Does it crash consistently when you enter?
That's only true for 64-bit analogue camera builds I believe.

>Passnig GPU commands
>Commands
So yeah, running logic with a null hardware replacement.
>Project64 does NOT suffer from forced bilinear filtering when you use Angrylion
That's good and all, but that just brings me back to my point; relying on plugins to achieve accuracy is quite underwhelming, and this wouldn't be acceptable on a PS1 emulator.

what's the best version to play on Windows 10? OpenGL or DX12? How do I know which version I have?

Is there a way to boot straight to fullscreen?

honestly got spooked and immediately quit. just tried again and it didn't crash this time ? don't really understand why it seems to work half the time. same goes for launching the game- sometimes it'll crash as soon as it opens for a few times and then it'll actually boot up normally with my saves still intact. weird shit man

i saw someone post some autohotkey script to make this boot to fullscreen - how do I get that to work? What filename? How do I get Steam to use it?

Has anyone completely removed the filters? I am curious to see the pixelated game.

Attached: nearest.png (583x465, 188.52K)

Does anyone know if there's a way to save the game? Everytime I re open it, I lose my progress.