In RSP interpreter, it is DisplayError and I feel like it's an important
message, so it should be DisplayError in RSP recompiler as well, in my
opinion.
the & 0xFFC was missing, which caused it to return true when it should
have returned false. This means that LLE audio should be more optimized
now.
I also made it do delay slot, incase the delay slot instruction writes
to accumulator. Minor optimization here.
As for JAL, I made it do break instead of return FALSE because in Battle
For Naboo, it actually does come back and continue an existing
calculation. I think it is only an issue if you do a separate analysis
for the Low Accumulator and Mid/High Accumulators. It's still better to
be safe, just incase I or someone else actually implement a separate
analysis for the Accumulators later down the road.
Due to the newer spec design in PJ64 2.x, CloseDLL() doesn't get called
as often. So there are instances where it calls AllocateMemory()
multiple times without ever calling FreeMemory().
sizeof(wchar_t) is a size of 2 (or 4 if in a Linux environment). With the previous code, it would be trying to insert the null terminator at index 511 on Windows, which is incorrect.
Interpolated Platform and Configuration values to avoid case-by-case
condition validation.
(This could allow for future configurations and platforms without
additional modifications to VCXPROJ files).
I previously made a commit to fix a reordering issue, but did not
realize it needed that COPO_MF_Instruction flag for branching. This
should fix the Ogre Battle issue.
This fixes the losing audio after loading a save state issue with
certain plugins in certain games. I was hesitant to submit this, since
the fault is the audio plugin itself, but this also fixes bad save
states. This will not fix games like Top Gear Rally.
Any plugin that initially had this problem, can still lose audio at any
given time, due to flaws in the audio plugin itself. It is best to
simply use a plugin that doesn't have this issue to begin with, for such
games.
Did she give me a detour kind of "short cut", or did she just cut off my balls?
If we prefer not to say "shortcut", then at least say "short-cut". This way, the adjective "short" is co-joined with "cut" to indicate that they are connected. This guarantees that the "cut" is associated with "short", and not whatever word comes after.
If you don't have a colon between the "Frame Rate Display" and the combo box, then it just looks like the combox box is randomly placed there and unrelated to the checkbox you just checked/unchecked.
If "fullscreen" was a valid word, it would be an adjective, not a noun. You cannot "go to" an adjective because adjectives are not places, people or things. So it should be "enter" as in "enter a mode" (such as a full-screen mode), not "go to".
"Use high-level-emulated audio" does make sense, but seems a tad bit strong (and people could mistake the "high level" to mean extra/better emulation without any scientific HLE understanding). So I think "Audio HLE" looks better.
Either say "Percentage", or just drop the '%' since this symbol of unit is not relevant to what the menu item should convey to the user. What we're really trying to do is show the CPU usage statistics...most likely the users would see for themselves what unit it comes out as (percentage, fraction, whatever).
"On" is a preposition shorter than 5 letters long. Standard title case does not ever capitalize short prepositions (unless they are the very first word of the title, then usually). You can see this logic in the Visual Studio 2008 IDE itself: It has menu items such as "Attach to Process" and "Find[/Replace] in Files", in which the prepositions "to" and "in" are, correctly so, not capitalized by Microsoft in the VS2008 menus.
After some testing, I've concluded that software depth is better on by default than off. Testing every single game would be too time consuming, and the problems it fixes can be obscure. Enabling FB by default just seems like good sense. A few games need it disabled, but I'll fix them case-by-case.
zilmar