New LLE RSP Plugin (accurate, fast but untested?)

[theboy181]

Originally Posted by HatCat

No, the June 2014 edit to my post was just to move the plugin download from filesend.net to dropbox.com.

I have some archival of the release history:

2013.12.12:  public release 6
2013.12.04:  public release 5
2013.06.09:  public release 4
2013.05.15:  public release 3
2013.05.13:  public release 2
2013.04.14:  public release 1

Hm...although looking at it now, I had no idea my release history was this consolidated. I'm surprised everything is from 2013. I know development-wise I had testers helping me find oddities in games back in 2011, but I didn't see a reason to release for 2 years.



I never did a public release, ever, without thinking each version could be the last.

I only did a public release once I felt I'd hit final perfection (usually in terms of performance, since accuracy was not a big issue thanks to zilmar's and MAME RSPs to study), and that anything else left to do in the plugin was just a matter of needing feedback from testers around the world to help me catch unused opcodes or the like.

The number of public releases is merely a reflection of how many times I was wrong about perfection, not the number of times I felt like updating everyone with an interim improvement. I would have still expected everyone to compile it on their own meanwhile.

But to jump back to your question, I am not done committing more improvements to the RSP plugin, but have just not had the time yet.



That just means it's segfaulting, and Project64's catching the access violation with its own exception checking (and its own error message).

I cannot test since I don't have Windows anymore. I have Linux.

I tried to send you an old new (yes that's correctly typed) rsp.dll file I had from my Windows partition, but PMs on this forum are broken. zilmar needs to fix his server thing. I don't do AIM or Skype or any of that crap, although you're welcome on IRC.



No, because you would first have to establish that it was RSP-related to begin with.

It's not possible to respond to an issue saying "try changing plugins" for the reason of seeing if a different RSP plugin shares the same issue (no change at all from switching DLLs) without knowing the RSP plugin was causing it.

You would have to first suggest to change plugins for the reason of seeing if it's a RSP plugin issue to begin with before you could even pose the question of whether other RSP plugins share the exact same issue or already know ahead of time that it was his outdated build causing it.



He would want to / could compile it on his own if he was using a better operating system.



I thought the reason for asking him to switch was to see if Project64 also had the bug inside its own RSP like you said, not because it was convenient for him to switch to builds he already has installed. Make up your mind.



Yes, I do know that.

If I wasn't aware of that I'd be sitting here wondering why theboy181's vagina is as sorely penetrated as his ass.

HAHA.. This was pointed out to me. If you are going to insult me please write it at the top of your posts. I seldom finish reading the garbage you write.

[wildgoosespeeder]

Here's a more recent binary I mirrored from HatCat's original download just in case it expires or something:
http://rctaddict.adryheat.net/HatCat_RSP.7z

[HatCat]

Up high.

Down low.

Originally Posted by theboy181

HAHA.. This was pointed out to me. If you are going to insult me please write it at the top of your posts.

Everything has to be pointed out to you below.

[wildgoosespeeder]

OK, throwing myself back into the fray and I have another issue running a specific game, Mario no Photopi. Yes, I read the manual and set the RSP plug-in accordingly, but nothing still displays. Graphics plugins changes don't fix it, changing game settings doesn't fix it. Nothing I do seems to fix it. Unless the game is broken again under v2.3, I got nothing.

A clean install of the emulator does seem to do the trick, but I don't know what is different.

[oddMLan]

With Semaphore lock on only, Doom 64 shortly crashes during the intro. Who's at fault here? The emulator or the RSP? Or even for some reason, the gfx/audio plugin?

Only seems to happen when the RSP is functioning in HLE gfx mode though (Send DLs to gfx plugin).
EDIT: If DLs are also being sent to the audio plugin, there's no crash. Why is MLE crashing here?

[Vardius2985]

I was noticing that an updated version of the RSP was linked a few posts back and have a question. I'm using PJ64 1.6 updated with the 1.6.1 patch and UoRDB 4.23 and would like to try out the new RSP update. How would I go about installing it into v1.6. I remember it being pretty easy, but want to make sure to do it right? Also keep up the good work. I look forward to future updates for this plugin. Thank you.

Edit: Nevermind. Last night when I was trying to view the manual on my phone it wasn't wanting to cooperate. When using my PC I'm able to view it no problem. You can disregard this post. Thanks again Hat Cat for continuing to develop this fine RSP plugin for us to use. Cheers.

[squall_leonhart]

All your links are dead.

[theboy181]

You are mostly correct, but I have a feeling that your or also wrong.

[ExtremeDude2]

Source code!!1!

https://github.com/cxd4/rsp

[masta ike]

Originally Posted by HatCat

I ran out of attachment upload slots using this post, so I'll be trying something different from now on.
Currently I'm going to stick with FileSend to be able to count downloads, in my lack of education about better options.

Available versions for download:

• public release 6
• public release 5
• public release 4
• public release 3
• public release 2
• public release 1

Remember to READ THE MANUAL (not all of it) for any specific concerns pertaining to your use of this software, either before or after running into any issues, but not after complaining about something in a deficient way. This HTML2 help file is provided within the download archive for the latest version.

As you can see by reading the manual, I have named this software Static Interpreter because it was designed to use optional branch elimination and other unusual, slick simplifications of a normal algorithm to a standard CPU execution loop with the fetch-decode-execute pattern. It was designed for the purpose of proving that an interpreter can be just as fast, if not even faster, than a quality re-compiler plugin such as Jabo's MMX re-compiler extension to zilmar's Project64 interpreter, although the goal of surpassing its speed was not uncontestedly met in most games.

hello i cannot download this for some reason..id like to could you send me a link please?

thanks!