Print

[scorp316]

Below is an updated Surreal64 B5.31 CE compatibility list.  Games include Madden 99-2002, Battletank, Mario Party 1-3, Diddy Kong Racing, NFL Blitz, NFL Blitz 2000 + 2001, Virtual Pool 64, and a few more.

Might want to check it out.  Read the top of the spreadsheet if you see that your game doesn't have settings....as it will indicate to use its default settings.


This time, I will allow you to edit my list......just in case there are better settings for a game.

Surreal Compatibility list 2

[Xboxer64]

Hi, I'm new here.

I'm very happy to see new Surreal releases. My favorite emulator

I'm having a problem with mempaks

I've been using Surreal since b5. The only way I could get a mempak to function properly was to set the default as rumble, then once in game switch to mempak. Now I can't get them to work at all. All games say mempak corrupted. I've deleted the surreal stuff from Tdata (not my game saves, but the ini ) and Udata and re-installed. Didn't help. Any suggestions?

Being able to actually adjust the joystick sensitivity has made GoldenEye playable. Some random crashes, but I did beat the game on 00 agent. Only used a save state on Control, "Protect Natalya" blah. Had to definitely rely on auto aim. Setting the sensitivity low enough to be able to move the cross hairs smoothly meant walking super slow. Even on the PC emulators, I can never get the joystick to feel quite right. Is it because the N64 controllers use an optical type sensor for the joystick? Modern controllers use pots. I have a 3rd party controller for the n64 that uses pots, can't aim with it either XD

[scorp316]

QUOTE(Xboxer64 @ May 29 2010, 08:30 AM)

Hi, I'm new here.

I'm very happy to see new Surreal releases. My favorite emulator

I'm having a problem with mempaks

I've been using Surreal since b5. The only way I could get a mempak to function properly was to set the default as rumble, then once in game switch to mempak. Now I can't get them to work at all. All games say mempak corrupted. I've deleted the surreal stuff from Tdata (not my game saves, but the ini ) and Udata and re-installed. Didn't help. Any suggestions?

Being able to actually adjust the joystick sensitivity has made GoldenEye playable. Some random crashes, but I did beat the game on 00 agent. Only used a save state on Control, "Protect Natalya" blah. Had to definitely rely on auto aim. Setting the sensitivity low enough to be able to move the cross hairs smoothly meant walking super slow. Even on the PC emulators, I can never get the joystick to feel quite right. Is it because the N64 controllers use an optical type sensor for the joystick? Modern controllers use pots. I have a 3rd party controller for the n64 that uses pots, can't aim with it either XD

Your problem with the mempak can be easily resolved.  When you start a game, it might say that it is corrupted.  Then it might give you a choice of repairing the mempak, if so press A on "repair mempak"....it should work by doing these steps......This was also common on the N64 console.

[Xboxer64]

Thanks for the response. I wish it was that simple. Although I can choose the repair option and play the game, it never saves after the repair. I would like to be able to actually use mempaks. Example: If I set the default pak as mempak in New Tetris, each and every time I start the game I get corrupted mempak warnings. I repair it for all 4 controllers. If I set the default pak to none, I still get corrupted mempak warnings (no mempak should even be inserted). With default as rumble I don't get any warnings, and go straight into the game as usual.

Another example: Mario Kart. With the default pak as mempak it is always corrupted or full. Can't save ghosts. If I set the default as none my ghost data is available again, which is odd because there shouldn't be a pak inserted (I didn't use the key combo). If I use the key combo to swap from mem to rumble or none it doesn't seem to work properly. Once I do the key combo and cycle through, my ghost data never comes back..... unless I reset the rom.

At one point I went into Tdata and deleted all the mempak files that had been created. That didn't help either

[DarthMingus]

Hello,

I have an upgraded 1.4ghz XBOX with 128 RAM. I have the newest Surreal XXX loaded on my XBOX and all the roms, except for Super Mario 64, just boot to a black screen. I tried this with 1.4ghz 'patched' XBEs as well as unaltered with the same results.

A number of users with this upgrade at 1emulation have had the same experience. Would it be possible to look into a fix for this? I'd be will to do any testing necessary to make it stable for users with an upgraded Xbox.

Let me know if you need any additional information to isolate the issue.

Thanks!

[DarthMingus]

Update: Some games do load, however, others such as the two Zeldas, go to black screen.

Any suggestions?

[weinerschnitzel]

128mb support is fixed in B5.4, if you would like to test it some before it releases (please do) hop into IRC when freakdave or I are available and we'll set you up.

The mempak issues will be looked at at a later time.

[DarthMingus]

Tried logging on tonight, but you were idle. Could you PM me?

[Xboxer64]

QUOTE(weinerschnitzel @ Jun 1 2010, 09:10 PM)

The mempak issues will be looked at at a later time.

No rush, I was just hoping someone would read my problem before it got lost in the thread.

Ha, is anyone else having mempak problems? I've been searching for someone else who had a prob in hopes of seeing what they did to fix it, but I didn't have any luck.

I'm probably doing something wrong.

[scorp316]

QUOTE(Xboxer64 @ Jun 1 2010, 09:24 PM)

No rush, I was just hoping someone would read my problem before it got lost in the thread.

Ha, is anyone else having mempak problems? I've been searching for someone else who had a prob in hopes of seeing what they did to fix it, but I didn't have any luck.

I'm probably doing something wrong.

To me...it seems that your problem is unique because I don't have a problem with the mempak on Mario Kart 64.  It saved my ghost quite well....my only problem is that I can't see the ghost as well as it is on the N64.

I have a 64mb xbox.  Are you using the 128mb xbox?  If so, I believe there are a few problems with Surreal64 b5.31 CE on the 128mb xbox, which freakdave and weinerschnitzel are working on resolving this issue at this time.

If it is a 64mb xbox, you might want to reupload your surreal64 b5.31 ce onto your xbox.  It can also be your download.....but I doubt it very much.  Might want to check surreal.ini....as a final resort.

[Xboxer64]

I have a stock 64mb xbox. I downloaded surreal from xbins, should be legit. To properly update surreal all I have to do is delete the ini and copy over the new files right? I deleted the ini in Tdata as well. I help my friend with his xbox, he is having the exact same problem I am...... more evidence that I'm doing something wrong.

I've tried multiple versions of surreal over the years. I always have had the mempak problem. When I updated to b5.31 I ftp'd the entire emulator folder over, then copied over my screenshot and roms folder from the other version before deleting it. Then I went to Tdata and deleted the ini there. I formatted x,y and z as well. Is there a step I'm missing?

About you not being able to see your ghost the same as on the actual 64, do you mean you only see the shadow on the ground and their exhaust? I think if you use the default plugin (rice 5.60) that the ini suggests that is what happens. Try Rice 5.31, the track textures will look slightly different (more grain), but ghosts show up properly. I prefer the slight track grain over the invisible ghosts. I just noticed that the plugin I suggested matches the current release version, 5.31

[DarthMingus]

Hello,

I seem to have issues with particular games. For instance, Mario Kart, Mario 64 and Castlevania launch without issues. However, games like Conkers and both Zeldas just hang at the black screen.

Could my BIOs have something to do with it? I'm using the 5035 Xecuter.

Also, for us upgraded Xbox users, should we max out the RAM settings in the config menu or would that cause issues?

Lastly, is there documentation on the different Rice plugins? I can't seem to see much difference. For instance, in Mario 64, I used Rice 5.1 and textures looked good and the frame rate read at 87-90 FPS. When I tried Rice 6.1 the framerate dropped to 30 FPS and the textures pretty much looked the same. The weird thing was the actual gameplay looked the same - IE. 30 FPS ran as smooth as 90 FPS.

Are there any online resources that show what the proper frame rate should be for these games? I know a lot vary from 30 - 60 FPS.

Thanks!

[scorp316]

QUOTE(Xboxer64 @ Jun 2 2010, 07:39 AM)

I have a stock 64mb xbox. I downloaded surreal from xbins, should be legit. To properly update surreal all I have to do is delete the ini and copy over the new files right? I deleted the ini in Tdata as well. I help my friend with his xbox, he is having the exact same problem I am...... more evidence that I'm doing something wrong.

I've tried multiple versions of surreal over the years. I always have had the mempak problem. When I updated to b5.31 I ftp'd the entire emulator folder over, then copied over my screenshot and roms folder from the other version before deleting it. Then I went to Tdata and deleted the ini there. I formatted x,y and z as well. Is there a step I'm missing?

About you not being able to see your ghost the same as on the actual 64, do you mean you only see the shadow on the ground and their exhaust? I think if you use the default plugin (rice 5.60) that the ini suggests that is what happens. Try Rice 5.31, the track textures will look slightly different (more grain), but ghosts show up properly. I prefer the slight track grain over the invisible ghosts. I just noticed that the plugin I suggested matches the current release version, 5.31

I also have a 64mb xbox.  I noticed that you deleted the ini from Tdata.  I deleted my "ini" folder from the "Surreal64" file, but not the ini from Tdata.......probably that could be the root of the problem.  Might want to reupload b5.31 ce to your xbox and try it.

Also, if you're playing South Park Rally....it has a problem where it fails to detect the controllers that are not plugged into the xbox controller port when you are using the "Mempak" or "None" option.  Might want to disable the controllers you will not be using.

I've also noticed that some games fail to repair your Mempak problem.  The game that fixed this issue...I believe was Superman...which is very odd.  Although it repairs your Mempak, it will still say "corrupted mempak" when entering other roms, but this time it will successfully repair your mempak.  Might want to try this as well.

[Xboxer64]

I've tried deleting everything and starting over a few times now. Thanks for trying to help me

Aside from screenshots and roms, I deleted the entire contents of the surreal folder, which of course included the ini folder. Since I was still having problems I cleared out the surreal folder in tdata, aside from gamesaves.

It was my understanding that since there is no way to edit mempak notes in surreal, each separate game (and each controller) would create it's own mempak save file. All the mpk and numbered "m" files in tdata show this. Attempting to repair a mempak in one game should have no effect on the mempak used in another. Right?

[scorp316]

QUOTE(Xboxer64 @ Jun 2 2010, 02:50 PM)

I've tried deleting everything and starting over a few times now. Thanks for trying to help me

Aside from screenshots and roms, I deleted the entire contents of the surreal folder, which of course included the ini folder. Since I was still having problems I cleared out the surreal folder in tdata, aside from gamesaves.

It was my understanding that since there is no way to edit mempak notes in surreal, each separate game (and each controller) would create it's own mempak save file. All the mpk and numbered "m" files in tdata show this. Attempting to repair a mempak in one game should have no effect on the mempak used in another. Right?

Correct.  Some games may have a problem with mempak....in this case disable the mempak on the controllers you will not be using.