Print

[Darknior]

QUOTE(YRUSirius @ May 5 2010, 02:09 PM)

VIDEO SETTINGS
Flicker Filter: 1
Soft Display Filter: Disabled
Texture Filter: Linear (can be changed to anisotropic perhaps)
Vertex: Mixed Vertex (seems to be important)
Skip Frames: No

EMULATOR SETTINS
Emulator: Project64
Video Plugin: Rice 5.3.1
Audio Plugin: LLE RSP
Max Video Memory: 4 Mbytes

Dynarec Memory: 10 Mbytes
Paging Memory: 10 Mbytes
Perhaps someone can verify the "Counter Factor" change to 3 and its performance improvement?

-YRUSirius

EMULATOR SETTINGS can be add to the surreal.ini
And i will add them after test if it is great ...

But for VIDEO SETTING do you know if it is possible to change them in an file for the game use these setting alone ?
Because it is impossible to write it in an NFO the guys must read before playing ... it must be automatic !
Like you speak about the COUNTER FACTOR ?

If you have some solution, PM me please for we speak about that ... or write here

Thanks
Bye

[YRUSirius]

Well my main modification was to edit the "Counter Factor" to 3 in the Project64.rdb manually. One could provide this new and improved Project64.rdb file to download or one could just edit it in manually (open it with notepad, search Donkey Kong 64 (U) and change "Counter Factor" to 3) and release it with the next Surreal release, so that the user does not have to care about this.

My video settings may not even be very important for the performance increase (perhaps just the Vertex setting, but I'm not sure, needs confirmation), I just gave them so that we could be at the same starting point.

Don't forget to try out that counter factor thing and tell us.

Besides the usual Donkey Kong gfx glitch where the polygon models stretch out of the screen it is very playable on my xbox right now.

-YRUSirius

[cbagy]

[weinerschnitzel]

YRUSirius and Darknoir, We're all excited to see what you come up with to improve compatibility! I hope to hear more from you guys farther down line!

kitten42,
I am using a 720p NTSC display and I have no issues. I hear it boots fine with evox but not xbmc. Odd. Tell me a little about your xbox, what bios are you using have you tried any settings there?

[cbagy]

@weinerschnitzel.
I use XBMC, various builds, in 720p and have no troubles with booting Surreal whatsoever.
Still haven't tested my other machines though one of which is a 1.6.
Could it be down to the video chip type ?

[YRUSirius]

I think I might have found even better settings for improved performance for Donkey Kong 64 (U) [!] using 1964 with Rice 5.31 without hangups in the intro or story intro. Please note that I use a (U) [!] rom.

First find the entry for Donkey Kong 64 (U) [!] in the 1964.ini file in the Surreal directory. It should look like this:



[EC58EABF-AD7C7169-C:45]
Game Name=DONKEY KONG 64
Comments=Playable!
Alternate Title=Donkey Kong 64 (U) [!]
RDRAM Size=2
EEPROM Size=3
DMA=2



Then add this line to it

Counter Factor=4

so that it looks like this:



[EC58EABF-AD7C7169-C:45]
Game Name=DONKEY KONG 64
Comments=Playable!
Alternate Title=Donkey Kong 64 (U) [!]
RDRAM Size=2
EEPROM Size=3
DMA=2
Counter Factor=4



My other settings are this:

EMULATOR SETTINS
Emulator: 1964
Video Plugin: Rice 5.3.1
Audio Plugin: LLE RSP
Max Video Memory: 4 Mbytes

Dynarec Memory: 10 Mbytes
Paging Memory: 10 Mbytes



Anyone wanna test this and verify it?






Using this same method I was able to slow down Blast Corps (U) (v1.1) [!] (which played too fast for me in some levels) using PJ64 with Rice 5.10 and Video Memory = 5 MB.

Edit Project64.rdb, search the Blast Corps (U) (v1.1) [!] entry and edit the Counter Factor to 3 or 4 (4 is slower, but might be too slow for your preference).



-YRUSirius

[kitten42]

QUOTE(weinerschnitzel @ May 5 2010, 05:59 PM)

YRUSirius and Darknoir, We're all excited to see what you come up with to improve compatibility! I hope to hear more from you guys farther down line!

kitten42,
I am using a 720p NTSC display and I have no issues. I hear it boots fine with evox but not xbmc. Odd. Tell me a little about your xbox, what bios are you using have you tried any settings there?

It's a softmodded v1.6 xbox. The bios is stock 5838 as far as I know. 5.1 worked perfectly, and still works perfectly for that matter....

[weinerschnitzel]

YRUSirius I will definitely check these out thanks!

kitten42, are you using NDURE? I would try that out and see if you can do anything with the nkpatcher settings. If you can hop into #surreal64ce on EFNET I can help you troubleshoot it more there and we'll see where that takes us.

[YRUSirius]

I'm onto Goldeneye right now, perhaps we can get the multiplayer uncrashable by editing the other inis.

Think I should post the results of my experiments in the "Surreal 64 B5.1 Ce Compatibility And Settings List, Unofficial Game Compatibility and Optimal Settings"-thread. Phew.

-YRUSirius

[jaygriggs]

QUOTE(YRUSirius @ May 5 2010, 07:24 PM)

I'm onto Goldeneye right now, perhaps we can get the multiplayer uncrashable by editing the other inis.

Think I should post the results of my experiments in the "Surreal 64 B5.1 Ce Compatibility And Settings List, Unofficial Game Compatibility and Optimal Settings"-thread. Phew.

-YRUSirius

HELL YES!!!!!
I will begin experimenting tonight!

However one point I'd like to bring up, I know we're few and far in between but for my fellow 128mb users shouldnt there be a seperate Surreal/ini for settings?

It seems on certain games the settings are great for my 64mb xbox but I find that sometimes different settings on my 128mb xbox perform better.
The freezing problem on goldeneye happens on both my xboxes so its not a lack of ram issue

[Likklebaer]

Since changing the Counter Factor to 3 seems to fix speed issues with these games (and presumably others too). Is there any merit in just changing the Counter Factor to 3 by default or does it have a negative effect on some games too?

[YRUSirius]

Yes, it might have adverse effects on other game, it's a game per game decision, it's like fine-tuning the 1964 or PJ64 emulator settings for each individual game (and there are still some values left in the inis, that I don't understand how they work or affect the emulation). Other games might kinda "desynch" or stop working.

-YRUSirius

[YRUSirius]

I've got an edit to try out and test for Goldeneye in UltraHLE.

Open Ultra.ini in the surreal folder, ctrl-f search the entry for Goldeneye and comment out the following line osrange=80008000,80024000 so that it looks like this //osrange=80008000,80024000.

Before the edit I could reproduce the crashing in two player multiplayer with rocket temple default settings after 3 to 4 kills, after the edit I could complete the match and kill the second player like 7-8 times.

How reliable or reproducable is the bug? Does multiplayer crash every time after 3-4 kills on two player multiplayer with rocket temple default settings? Or do I have to test and test until the multiplayer might crash and I found out that my edit did nothing for the multiplayer?

EDIT: It just crashed with same map and settings and my edit. Anyway, does anyone know what that osrange means?

-YRUSirius

[jaygriggs]

osrange  - defines the area in boot image where there is code (speeds up
//            loading, by default 1MB is assumed). Not necessary.

ultra ini. basics
http://home.clara.ne...s/uhle/help.htm
http://home.clara.ne...rs/uhle/ini.htm

testing your settings now and ill edit this post with my findings
Goldeneye froze 1st game for me.
Also what rom version are you using? I use Goldeneye (U) (!)

[Darknior]

Hi

Me too ... it freeze in first stage

It is bad because on PC with 1964 1.1 it works very very fine !

I think we can't fix it without an update in 1.1 for 1964 !