LuigiBlood
Mage Robot
Today in bad N64 emulation news
Today in bad N64 emulation news
It's not necessarily just framerate but it's also like, timing overall where it's just completely off and faster (that's what makes the framerate faster)Is this due to the A.I being tied to the framerate or something? What in the hell is this?
At this point that's not true anymore, and Nintendo has all the documentations they need.NSO's N64 emulator really sucks.
Is the N64 a more difficult console to emulate than the Saturn?
I saw gameplay footage of the game running on Mupen64 from 2019 and it's fine. The difficult console to emulate excuse does not work.NSO's N64 emulator really sucks.
Is the N64 a more difficult console to emulate than the Saturn?
That's unknown, but I'd still believe it's the case.Are IQue still the ones solely responsible for these releases?
NSO's N64 emulator really sucks.
Is the N64 a more difficult console to emulate than the Saturn?
I don't think they willingly improved games to run better, the emulator is just so terrible that sometimes they even had to inject lag in certain parts of some of the games to account for problems. I refuse to think they made the N64 emulator with improvements in mind.I don't think that's true. Nintendo's improved a lot of the games significantly. Some games like Pilotwings even run up to 60fps. It's not perfect of course - F-Zero X is a disappointment, and this needs fixing - but I've enjoyed the majority of the N64 offerings on nso.
I don't think they willingly improved games to run better, the emulator is just so terrible that sometimes they even had to inject lag in certain parts of some of the games to account for problems. I refuse to think they made the N64 emulator with improvements in mind.
They can't even implement automatic pak switching in games despite the fact that they emulate both the Controller Pak (unused) and Rumble Pak, and has the features that could allow this the entire time.
By all means, if you're enjoying your time with N64 NSO, I don't want to ruin that. I also enjoyed playing it too.You're right of course. I shouldn't talk on subjects like this as I know nothing tech related. Otherwise I'll just make a fool of myself.
Disagree. Disabling framerate limit can't be an automatic process, not to mention higher resolution rendering.I don't think they willingly improved games to run better
Just to answer the last part:Disagree. Disabling framerate limit can't be an automatic process, not to mention higher resolution rendering.
I know, you wont stop complaining yadda yadda, but try to be a bit objective for once. There have been improvements made, improvements that not even in the oldest, shittiest hobbyist emulator are made by mistake.
And sure, you're right overall, and you know about the subject waaay more than the average member of this forum, but you're entering literal hating territory here.
Also, i'd like to add that, shitty as the emulator is, some of your comments are a literal disrespect to the devs, i'm starting to see lazy devs rethoric here and mate, this isn't Twitter.
It's a mix of framerate and game design. Most N64 games feel heavy and sluggish because the console's average framerate is pretty low and the games are, probably, designed for higher framerates. Kinda like it happens with the graphics profiles of current gen games (or even some Switch games, like Grid Autosport)Why do soooo many N64 games feel so sluggish?
I replayed mario 64 last year. 2/3 of the 64 library feels more sluggish. Or is the emulation part of the problem?
N64 controller definitely doesn't map to well onto joy cons.
Tried 1080 and jfg, and since I don't have nostalgia it's hard to get into those games... they don't FEEL great to play.
Fzero (never played this one) and mario kart still feel fine.
I don't remember banjo and kazooe feeling this slow and weightless.
If anything, i wanted to thank your for your reply, as i said before - and i wasn't being sarcastic - you're obviously more knowledgeable than the average Fami and it shows. Your explanation fits perfectly with the final result, so i stand corrected on that one, the framerate stuff in particular feels like a eeeeh, it's good enough case, wich given the fact that they apply patches in other cases feels pretty whack.tl;dr edit:
I spent too much time explaining details when I can sum up this to this basic idea of what happens when you run PC games on a low end system and when you run them on a higher end PC. The game runs at a higher framerate automatically. You're giving free performance. That's exactly what happened to the N64 games, and then add the idea that the games MAY not have been planned for this higher framerate in mind even if it was not capped, and you can get a bad recipe for disaster.
edit 2:
Okay so I noticed too late that I appeared rather opinionated in my posts to the point I made people feel somewhat attacked.
Not in my intention to make you guys feel that way and I'm sorry about that, but I still stand by my posts, I tried to be informative, including on the idea that yes, making N64 games run faster is genuinely automatic. If that feels like a disrespect to the devs behind the emulator, sorry, but it isn't, that's how the emulator works, and now that I detailed this in the aspect that I feel very informative, I hope you guys get it that I'm not trying to disrespect anyone here.
Mind you, I defend the results of Pilotwings 64. I loved playing the game at 50 FPS (I played the PAL version, I just like playing in my native language).If anything, i wanted to thank your for your reply, as i said before - and i wasn't being sarcastic - you're obviously more knowledgeable than the average Fami and it shows. Your explanation fits perfectly with the final result, so i stand corrected on that one, the framerate stuff in particular feels like a eeeeh, it's good enough case, wich given the fact that they apply patches in other cases feels pretty whack.
I still think there are some merits to the, admittedly, accidental results, wich overall improves games that would be considered unplayable today (see Goldeneye for example)
I really want to point out that N64 NSO is still playable, it's still fine for most games. I still played some of the games on it, because I didn't necessarily take the time to play those games in the past either. And that's one reason why I think of retro NSO as a very important thing to me. Part of the fun of retro gaming nowadays, it's not just enjoying games, I want to share the joy, sometimes I discover games that I end up really loving, and sometimes I like seeing other people like me enjoying them.Believe it or not, despite being so adamant about this emulator being fine, i'm still hoping for a better N64 emulator on the Succ, it really stands out like a sore thumb compared to all the other NSO emus.
For the record, my biggest complaint with the N64 emulator is the lack of native rendering+scanline mode, it's such a glaring omission and it would help the visuals inmensely.
I really thought I was being somewhat calm when I made my posts, and couldn't tell I was coming off in this way on the moment, it didn't register. As much as I can get definitely heated about certain things, I usually never try to annoy people even in this way, and I'm sorry about this.EDIT: Also, thank you for your final introspection. I didn't want to tell you directly, but you were being pretty abrasive. Personally i wasn't feeling attacked, but it didn't feel right.
I have another theory that may sound kind of crazy, but it's also the same theory i have with the joycons' sticks:I don't think the issue is lazy devs so much as its a problem of Nintendo simply have not hired enough people to work on these emulators. Wouldn't be surprised if the number of people they have working on N64 NSO stuff was in the low single digits. Nintendo needs to hire more people to optimize NSO emulation and in general they need to stop being so stingy about NSO, especially when it comes to the NSO+EP stuff. The bad N64 emulation is made worse by how rarely they have bothered adding more games to NSO overall lately. GBA hasn't gotten an update since September. Genesis hasn't gotten an update since JUNE.
I don't like saying lazy devs, but I did say at times that, maybe, iQue is not fit for this.I don't think the issue is lazy devs so much as its a problem of Nintendo simply have not hired enough people to work on these emulators. Wouldn't be surprised if the number of people they have working on N64 NSO stuff was in the low single digits. Nintendo needs to hire more people to optimize NSO emulation and in general they need to stop being so stingy about NSO, especially when it comes to the NSO+EP stuff. The bad N64 emulation is made worse by how rarely they have bothered adding more games to NSO overall lately. GBA hasn't gotten an update since September. Genesis hasn't gotten an update since JUNE.
iQue had an history where they made the NES and GBC (and canned GBA) emulators for 3DS Virtual Console, which were okay, in fact N64 runs on the same emulator framework as those two, but honestly iQue Studio did not really do a lot of technical work on N64, the major part of that work was by BroadOn who handled the technical side behind chinese localizations of N64 games, as well as hardware, software and infrastructure of the iQue Player.I have another theory that may sound kind of crazy, but it's also the same theory i have with the joycons' sticks:
I think they signed a contract with iQue to port and mantain the emulator for x amount of years or just for the whole extent of the Switch's commercial life, either because of their history with N64 or because they already had an emulator running on ARM, wich would make it cheap and fast to release it for the NSO Expansion Pack.
Whatever the case, just like with the joycons' sticks, we're stuck with it at least until the Succ releases.
is jet force gemini good by the way?
Today in bad N64 emulation news
Does anyone know the song that plays at the end of the trailer when they all say available now? I figure it’s maybe stock music so no one will know. It’s catchy haha
I mean, NERD and iQue are both Nintendo subsidiaries. You don't generally have a bidding war between studios you own.I wonder why Nintendo hired IQue when they could have just hired NERD again seeing as they've been responsible for all the other emulators thus far, and have done pretty well with them. Keeps things consistent as well. Was there a bidding war or something?
I managed to finish JFG on Rare Replay and I'm at Mizar's Palace with Juno on the NSO.Fun fact; the sped up flying drones were a thing in the Rare Replay version of the game as well.
This was always one of those games that was fickle as a motherfucker to emulate, I always had to change settings within and outside the emulator to avoid crashes and to display vital visual info reliant on the framebuffer. After upgrading my hardware recently I still have arbitrary lag problems with the game that I'm too lazy to troubleshoot.
Given the past issues with the N64 emulator I'm actually pleasantly surprised that NSO got almost all of the common problem spots right for a smooth start to finish playthrough.
It's not really a bidding war thing but I'm genuinely uncertain of how good management was and currently is on this stuff because in the meantime, Nintendo has access to literally 3 different NES emulators:I mean, NERD and iQue are both Nintendo subsidiaries. You don't generally have a bidding war between studios you own.
I think it's as simple as "NERD doesn't have a monopoly on emulation at Nintendo". Like LuigiBlood said, iQue also had prior experience making Nintendo emulators, being responsible for the 3DS's NES and GBC emulators. We can argue it may not have been the right move, but I don't think it's that big a surprise that Nintendo would want to distribute the work for NSO emulation among the two of them rather than have one studio shoulder the whole workload