[Hard core Rikki]

Report on compatibility with games here.
Differentiate between Xebra and Arbex, and state which released version of either was used.

The general guidelines for reporting compatibility apply. Detail your hardware, settings used, mention if games are fully playable from start to end, only go ingame, hang anywhere or display glitches, and share screenshots.

One separate post for every game (same for every separate region, as compatibility can differ between US/EU/JP releases).

 

[TBx]

Chrono Cross - US Region

Screen goes blank black and freezes (sound repeats in a loop/stutters) when the game has to load a new screen/section (pass through a door in the map, go to the status menu that shows the 3D models of the characters)

Xebra 1-7-11

Video Output:
Stretch with OpenGL +
Stretch +
Whole Frame Buffer -
Nearest +
Progressive +
Cycle(1) = 0
Cycle(2) = 0
Cycle(3) = 0

Sound Output:
N = 0


CPU: q8200 3.33GHz
MOBO: Gigabyte GA-EP45-UD3L
RAM: 8GB OCZ DDR2 5-6-6-18 @ 478MHz
GPU: PNY 9800GT 1GB
SC: Built in Realtek HD
HDD: 300GB Seagate + 1TB WD Black
OS: Windows 7 Ultimate x64

(Sorry, I was too lazy to change the multi-color-ness of the specs from my sig)

 

[hattori]

Chrono Cross : Menu/Run/Misc/Blank

 

[Ilya-v]

hattori.

Are you DR. Hell?

 

[hattori]

No.
This information was reported in Japanese anonymous bulletin board

Å‹­‚̃Gƒ~ƒ…ƒŒ[ƒ^[iPS•ÒjšXEBRAŒÀ’èš

 

[drhycodan]

So you must goto Run/Misc/Blank everytime the game has to load a new screen?

 

[Ilya-v]

Aparently from Hattori's explaination from previous posts
the lower the "I Cache Rate" the faster the emulation recieves
commands from the emulated ps1 CPU, making the emulation more accurate.

You can lower the "I Cache Rate" setting to 8 (click 10 then -1, and -1 again).
wich will make Chrono Cross work without needing to press Blank everytime.

I saved a Simulation by the name of XEBRA.INI with this setting so that
Xebra will load this setting by defaul.
You can also edit the XEBRA.INI file with SIM.EXE and change the I Cache Rate
to "E".

I don't see any slow downs with lower settings, on the contrary it is smoother.

Cheers.

 

[drhycodan]

Wait, first you said it was 8, then E? So which is it?

 

[Ilya-v]

Its E in the SIM.exe editor.

10 -1 -1 = 8.

but the editor shows E.

 

[drhycodan]

But there's also an 8 in the editor.

 

[Ilya-v]

E in the editor (SIM.EXE)

You don't have E in Xebra, the minimum is 10.
Therefor you have to click -1 (its in the same menu), and once more -1.

but in the editor it shows E NOT 8, wich way lower.


Cheers

 

[TBx]

Thanks guys! Using the Menu/Run/Misc/Blank worked, as well as setting "I Cache Rate" to "E" in SIM.EXE.

 

[drhycodan]

But E in the editor does not equal 8 in the emulator. If you save the I Cache rate at E in the editor, it is also E in the emulator. You can see so by going to simulation/show values.

 

[TBx]

I guess what Ilya-v was saying was that if you go down to 8 within Xebra.exe it will fix the Chrono Cross issue. However, in the Sim.exe you can lower the I Cache Rate LOWER to E, which is even faster/"more accurate" than 8? In any case, setting it to E did work for me.

 

[drhycodan]

But setting it to anything below 18 causes a transition error from town to world map in Xenogears, so lowering the I cache rate doesn't necessarily mean higher accuracy.

 

[TBx]

So lowering it to 8 fixes Chrono Cross but breaks Xenogears?

 

[Ilya-v]

forget about 8 its to low.
E is two values below 10.

I'll report to Dr. Hell about the need to change the "I Cache Rate" values.

 

[drhycodan]

Yes, thank you! If he could make Xebra autodetect the Simulation settings for each game, it would make it so much more easier to use, not to mention a lot more convenient too, and one more step towards perfection.

 

[Ilya-v]

There also seems to be big problems with cheatings cds (gameshark, pro action, etc..)
these don't even go past the PS logo.

I'll let him know about this too.

 

[Ilya-v]

Dr. Hell about "I Cache Rate":
The frequency of PlayStation CPU is 33868800Hz.
Therefore many people think PlayStation executes 33868800 instructions per second.
However, there are actually a lot of factors to obstruct the execution, and it stops very often.
Not only CPU but also GPU, SPU and any other peripherals stop each other,
because they compete by the access to main storage.
To emulate these factors is very very heavy.
Probably, future Core-i7 10GHz might be power shortage.
Therefore, almost every game emulators cannot help adopting an approximate method "SIMULATION".
(some emulators have the part where even neither the emulation nor the simulation are done.
It is natural that some games never work on them)

"I Cache Rate" is average time to fetch one instruction from I Cache
(it is expanded to 16 times to deal by integer and written in hexadecimal number)

Haven't you ever heard?......
If Pentium and Celeron have same clock frequency, Pentium will be faster.
Because Pentium has bigger I Cache, so average i-fetch time is shorter.

In the same principle, the fetch time of refined program is shorter than that of non-refined.
Even in one game, refined code and non-refined code exist together.
There is no all mighty setting.

-----------------------

I think we'll have to live with changing this setting by hand.


cheers.