GLideN64 is making some dramatic leaps. Copying auxiliary framebuffers to RDRAM helps fix everything from Pokemon Snap detection to Top Gear Hyper Bike's terrain. Even Vigilante 8's menus are working better now, though they're far from perfect. The horizontal wipes in Mario Tennis have never worked in any plugin besides Angrylion's until now.
>Pokemon Snap works?
It detects Pokemon thanks to new auxiliary buffer emulation. The part where the pictures are evaluated doesn't work currently on GLideN64 due to broken depth buffer, but it ironically does work on Glide64 and Jabo and so on.
I will point out, however, that it's not all peaches and sunshine. Copying auxiliary buffers to RDRAM is a somewhat significant performance overhead.
>Isn't GLide an Android Emulator?
>...So in other words, it's fucking pointless?
Whatever gave you that idea? GLideN64 is a plugin for N64 emulators such as mupen64plus and PJ64 and 1964. It also has a mobile version that runs on OpenGL ES.
im confused, what kind of television in the 90s was soo big...
Anyone got any tips for running N64 games on a potato computer? With Glide64 Final (textures settings set to best perfomance mode) in 1964 I can get OoT working at almost full speed (stutters a bit here and there), but Smash Bros has a fuck ton of slow down.
depends on the game. for zelda and super Mario it works. it's everything but terrible, that's an overstatement. besides this is not about what is better. everyone knows glide64/gliden64 is the superior. but for cheapskate hardware like his, jabo is more than fine! he probably configured it wrong or it's a game that emulates bad generally.
>depends on the game. for zelda and super Mario it works.
It doesn't do noise effects and it doesn't do mipmapping. The Zelda games are riddled with problems in Jabo's plugins. Jabo's list of shortcomings is mindboggling.
Something unpleasant. This must be about 180°. I don't know what happens if I gow further, I will try soon...
I keep having studders when i emulate Banjo kazooie on project64 is this a known issue ?
How the fuck do i fix this ?
>probably configured it wrong
There's really not much to configuring Jabo, so I don't know how I could have done it wrong. I genuinely think my computer is just too shitty to run SSB. As recommended here, http://emulation-general.wikia.com/wiki/Recommended_N64_Plugins I've been using Glide with best performance setting at 720x480. SSB is still pretty laggy, though OoT is definitely playable with small stutters here in there (usually when I start the game up). If you have any recommendations for me, I'd be glad to hear them (maybe there's a different core I should use? 1964 0.99 seems to work the best at the moment).
I played through the whole OoT and am currently at MM with Jabo on PJ64 1.6. I have Glide available but switched back to Jabo because no difference at less workload. No problem whatsoever. The only thing is that is noticable is that walls are less solid, like you can see through a wall if standing directly in front and using C up, but i actually like that.
Waht big problems are you talking about, cause I don't see any.
>The only thing is that is noticable is that walls are less solid, like you can see through a wall if standing directly in front and using C up, but i actually like that.
That is actually a really serious problem with Jabo's culling due to it using ancient versions of DirectX.
It's probably things like missing effects, nothing that would make it unplayable, just not visually faithful.
Kinda like the Vanish Cap effect or the Peach portrait fading into the Bowser portrait in Mario 64. Some plugins get those things wrong, meaning they're genuine problems, but a player who is none the wiser (or who just doesn't care enough) would never stop and think "oh, this shit's broken," compared to something like Vigilante 8 or Gauntlet Legends, which are utterly broken.