- Joined
- Jun 27, 2013
- Messages
- 873
My save files are small, so I guess that's why I never noticed this issue. I never tried server with mupen64++, only p2p.If you've played with mupen64k/++ before you'd know about the ridiculous load times for larger save files. Mainly ones that were made using cheats from PJ64. You just have to rename the file and the save will work fine, but the load time will take several seconds.
Even if you do P2P the load time will still be there, It's not multi-threaded I guess. It's not a networking or cpu issue as much as it's a programming issue, and I was referring to really old computer builds from the 2000s, any modern piece of hardware won't have any problems with N64 emulation.
What do you mean they ruined the audio? I'm pretty sure you could change the audio but I don't remember. The only issue with Mupen is the fact saves have to be the same, but that goes for AQZ which is the best possible n64 netplay atm. Apparently isai always complained about delays playing smash with it (plugins problem), but I've never been able to confirm that. With that being said, Mupen64++ is the best optimal emulator for Smash Bros and Kaillera.
They ruined audio, as in it has more crackling, compared to offline gameplay. If only it was open source.. I like 1964 the most, for kailera. Although it also has that audio issue.
Tbh I've had more crashes with PJ64 1.4k than Mupen64++.The 58fps is caused by an option called "sync audio", disabling the option should fix that problem.Mupen64++ appears to be less stable for most compared to PJ64k
The PJ64 2.2 with kaillera locks at 58fps, which is unplayable
It seems that unless Kaillera is an option, it's going to be hard to convince people to move on. I'm certain people would move on to PJ64 2.3 if someone implemented kaillera in it, lower/eliminate the chance of ds, sync via cheats only, and allowed full screen. Seems nobody knows how to or cares to do it though.
2.2k already has lower chance of ds, can sync gameshark cheats (iirc), and full screen has also been fixed (iirc).
Well, PJ64's progress is going at a slower rate than anticipated. Rather than waiting, you're better off making those 2 minor changes and use 2.2k as the standard, until 2.3 is in better shape.I was referring to this post, unless this has been done?