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

[HatCat]

SSE3 is "Streaming SIMD Extensions 3", and the extra 'S' in SSSE3 means "supplemental".

Anyway by the next release of this plugin, neither should be of use anymore. The primary reason for SSSE3 was shuffling, secondary being better auto-packing and unpacking from ANSI code in the multiplies, which were quite optimized for what appears to be vectorizing compilers developed beyond what GNU gave us. Since I'm half-assing (ass as in inline-ass[embly]) by using the intrinsics from <emmintrin.h>, both of those problems can be eliminated anyway.

[oddMLan]

In other news, Microsoft made Visual Studio free (for non-enterprises):

http://www.neowin.net/news/microsoft...e-for-download

[Olivieryuyu]

I have a bug with this RSP plugin in Harvest Moon

[RPGMaster]

Originally Posted by Olivieryuyu

I have a bug with this RSP plugin in Harvest Moon

According to his commits, he fixed a bug in harvest moon (not sure if it's the same one you presented).

You can compile his latest source if you wish to see if it's currently fixed. The latest binary release has bugs in a few games, so it's best to compile anyway. Latest source is also more optimized.

[Olivieryuyu]

Hmm small question

I have constantly this when using the plugin with PJ64 plugins?

Any advise? Config is never ever save, so I can use in LLE without any options

[RPGMaster]

Originally Posted by Olivieryuyu

Hmm small question

I have constantly this when using the plugin with PJ64 plugins?

Any advise? Config is never ever save, so I can use in LLE without any options

I recommend you put sp_cfgui.exe in the same directory as your emulator exe. Once you do that, when you click config in the emulator gui, for RSP settings, the gui should appear and will create a config file if it did not already exist.

It's quite unfortunate, because the public binary one has glitches in a few games. But the latest source uses a different type of configuration and there's no public gui for the latest version. His latest source is also incomplete, so there's no way to config it. It's easy to fix the source, but I still haven't been able to compile with GCC due to some weird issues. I'd rather not use MSVC at this point.

[fallaha56]

Hey guys some of you may have seen this already:
gliden64.blogspot.ru/2014/11/lle-is-here.html

LLE on Glide64 is imminent -HatCat is this using your RSP I wonder? if not why not?!

[RPGMaster]

Originally Posted by fallaha56

Hey guys some of you may have seen this already:
http://gliden64.blogspot.be/2014/11/lle-is-here.html

LLE on Glide64 is imminent -HatCat is this using your RSP I wonder? if not why not?!

For LLE, there are multiple RSPs and each RSP may have its pros and cons. You don't necessarily have to stick to using only 1 RSP.

[HatCat]

Originally Posted by oddMLan

In other news, Microsoft made Visual Studio free (for non-enterprises):

http://www.neowin.net/news/microsoft...e-for-download

Awesome, thanks for sharing. I believe it broke down when my laptop connected to the internet and changed to saying I had X days left in my free trial, but I hope this is just a bug and what you posted really is free. Guess I'll find out/try again when my trial runs out.

Originally Posted by Olivieryuyu

I have a bug with this RSP plugin in Harvest Moon

Yes angrylion reported this to me a while back.
I'd sent him an e-mail linking to this patch to my source code, + an updated binary from that month which should fix your issues.

Originally Posted by Olivieryuyu

Hmm small question

I have constantly this when using the plugin with PJ64 plugins?

Any advise? Config is never ever save, so I can use in LLE without any options

Yeah sorry about the whole config directory relativity/absolution ambiguity. That along with the separation into SSSE3 build will be merged into a newer system when I want to post a new release.

[HatCat]

Originally Posted by RPGMaster

Edit: went back and fixed the rsp config. I just added in

(mode[0] == 'r') ? OPEN_EXISTING : CREATE_ALWAYS,
(mode[0] == 'r') ? FILE_ATTRIBUTE_NORMAL : FILE_FLAG_WRITE_THROUGH,

That's not something I'm sure whether I can commit.

The modes for fopen are things like "rb", "wb", "a", "r", "w", and many others. Generally to my understanding of the concept, the first letter must be either a 'r' or a 'w','a'.

You're saying if the first letter of the mode[] is 'R'EAD, then the Microsoft CreateFile() mode should be OPEN_EXISTING, and also use FILE_ATTRIBUTE_NORMAL. Otherwise if it's 'W'RITE (or 'a'ppend) then open via CREATE_ALWAYS, and later use FILE_FLAG_WRITE_THROUGH. These don't have a very analogous appearance with each other...

I think the current method is more readable.

...
(mode[0] == 'r') ? GENERIC_READ : GENERIC_WRITE,
(mode[0] == 'r') ? FILE_SHARE_READ : FILE_SHARE_WRITE,
...

If mode is read then GENERIC_READ. If mode is 'w'rite then GENERIC_WRITE. I can't understand your code, so if it's fixing something that's broken you could at least provide an explanation on why you picked a completely different macro from GENERIC_WRITE.