More actions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
| author = weinerschnitzel | | author = weinerschnitzel | ||
| website = http://surreal64ce.sf.net | | website = http://surreal64ce.sf.net | ||
| download = | | download = https://www.gamebrew.org/images/over100m/Surreal64_CE_B6_1_Beta_r342.rar | ||
| source = https://sourceforge.net/projects/surreal64ce/ | | source = https://sourceforge.net/projects/surreal64ce/ | ||
}} | }} | ||
| Line 57: | Line 57: | ||
Q: What does Range Fog and Linear Fog mean? | '''Q: What does Range Fog and Linear Fog mean?''' | ||
A: Range Fog is the default fog method and usually correct method | A: Range Fog is the default fog method and usually correct method | ||
fog. Linear Fog refers to depth based fog on a linear filter. It is | fog. Linear Fog refers to depth based fog on a linear filter. It is | ||
| Line 65: | Line 66: | ||
desirable artifacts may appear. Rice 6.12 only. | desirable artifacts may appear. Rice 6.12 only. | ||
Q: Software Vertex Clipper, what? | '''Q: Software Vertex Clipper, what?''' | ||
A: The Software Vertex Clipper uses code that also relies on DirectX | A: The Software Vertex Clipper uses code that also relies on DirectX | ||
features unsupported by XBOX. You can witness the missing side | features unsupported by XBOX. You can witness the missing side | ||
| Line 74: | Line 76: | ||
Vertex Processing" in Video Settings. Rice 6.12 only. | Vertex Processing" in Video Settings. Rice 6.12 only. | ||
Q: 1964 1.1 and PJ64 1.6 support cheats, what gives? | '''Q: 1964 1.1 and PJ64 1.6 support cheats, what gives?''' | ||
A: I never implemented a menu scheme to modify and activate cheats. | A: I never implemented a menu scheme to modify and activate cheats. | ||
In the meantime, PJ64 1.6 can load "permanent cheats" that correct | In the meantime, PJ64 1.6 can load "permanent cheats" that correct | ||
some big issues. (i.e. Zelda SubScreen Delay Fix, and Pokemon Snap) | some big issues. (i.e. Zelda SubScreen Delay Fix, and Pokemon Snap) | ||
Q: I am experiencing graphics glitches in X game. | '''Q: I am experiencing graphics glitches in X game.''' | ||
A: That's not really helpful. :/ The most common graphics issues | A: That's not really helpful. :/ The most common graphics issues | ||
result from Rice Video's lack of [Hardware] Framebuffer Emulation. | result from Rice Video's lack of [Hardware] Framebuffer Emulation. | ||
| Line 95: | Line 99: | ||
look into fixing it. Otherwise... Don't bother! :P | look into fixing it. Otherwise... Don't bother! :P | ||
Q: I am experiencing a crash after X in Y game. | '''Q: I am experiencing a crash after X in Y game.''' | ||
A: Make sure you are giving the emulator enough RAM, and try setting | A: Make sure you are giving the emulator enough RAM, and try setting | ||
Texture Memory to AUTO. Some games handle the auto texture memory | Texture Memory to AUTO. Some games handle the auto texture memory | ||
| Line 102: | Line 107: | ||
of plugins that worked in the past. | of plugins that worked in the past. | ||
Q: PJ64 1.6 doesn't play opening animations all of the time. Why? | '''Q: PJ64 1.6 doesn't play opening animations all of the time. Why?''' | ||
A: There are some changes to PJ64 where previous optimizations don't | A: There are some changes to PJ64 where previous optimizations don't | ||
work as gracefully. The result is that some opening animations get | work as gracefully. The result is that some opening animations get | ||
skipped at the cost of good emulation speed. | skipped at the cost of good emulation speed. | ||
Q: Turok Dinosaur Hunter doesn't work or crashes on me. Why? | '''Q: Turok Dinosaur Hunter doesn't work or crashes on me. Why?''' | ||
A: PJ64 1.6 won't boot it due to optimization issues. 1964 1.1 will | A: PJ64 1.6 won't boot it due to optimization issues. 1964 1.1 will | ||
only boot it with audioMusyX. Both emulators will eventually crash, | only boot it with audioMusyX. Both emulators will eventually crash, | ||
| Line 113: | Line 120: | ||
be needed to play this game fully. | be needed to play this game fully. | ||
Q: Players 2 and 4 are unplayable in Conker's BFD deathmatch. | '''Q: Players 2 and 4 are unplayable in Conker's BFD deathmatch.''' | ||
A: Sorry. Again, this is a core issue. | A: Sorry. Again, this is a core issue. | ||
Q: Can I tweak the speed of a game? | '''Q: Can I tweak the speed of a game?''' | ||
A: Yes. Adjust the Counter Factor value in the emulator's .ini or | A: Yes. Adjust the Counter Factor value in the emulator's .ini or | ||
.rdb. A lower CF value emulates closer to a real N64, while a higher | .rdb. A lower CF value emulates closer to a real N64, while a higher | ||
| Line 122: | Line 131: | ||
Xbox. Generally, adjusting CF will do a better job than Frameskip. | Xbox. Generally, adjusting CF will do a better job than Frameskip. | ||
Q: Load/Save States as well as the In Game Menu cause me crashes. | '''Q: Load/Save States as well as the In Game Menu cause me crashes.''' | ||
A: Yes, these bugs have been around since Surreal64 1.0. They are a | A: Yes, these bugs have been around since Surreal64 1.0. They are a | ||
result of the emulator and plugins running natively with the lower | result of the emulator and plugins running natively with the lower | ||
Revision as of 13:05, 9 February 2018
Compatibility list WIP
https://docs.google.com/spreadsheets/d/1oKgtu5GzvWCui-hb1Vlf481viAuodHec7HIhgnKGkDY/edit#gid=0
Changes/Additions
Core Updates
- 1964 1.1 added
-Starting in 2009, freakdave, Ez0n3 and schibo all gave their efforts to porting this to Xbox. I only finished what they started.
- PJ64 1.6 added
-Before the leak gained publicity in 2012, Mudlord and Squarepusher shared their discovery with me and the xbox port happened shortly after.
- UltraHLE updated to match UHLE Alpha codebase
-UHLE Alpha uses some larger buffers for sound and textures, and has very slight changes to syncing.
RSP Plugin Updates
- RSP Recompiler updated to 1.7.0.9
- HLE RSP Plugin updated with MusyX HLE
-MusyX will require use of "AudioMusyX" until a proper HLE audio plugin is ported.
Video Plugin Updates
- Rice Video 6.12 updated with several changes from mainline and some
backport fixes from Rice 5.60. -Near Plane Clipping hack for Zelda -HW vertex handling from Rice Video 5.60 -Pixel Shader combiner switched to PC version (faster and complete) -Software Vertex Clipper as an option for corner cases -Glide64 LOD fix for correct fog depth -Moveword insert matrix fix for SSB -Fill_Rect primColor fix for MK64 -Various renames/refactors and other less noticeable bug fixes
Input Plugin Updates
- Deadzone threshold decreased for better button-to-analog mapping
Frequently Asked Questions
Q: What does Range Fog and Linear Fog mean?
A: Range Fog is the default fog method and usually correct method fog. Linear Fog refers to depth based fog on a linear filter. It is less costly, but requires the Software Vertex Clipper, which itself uses more resources than the old hardware method. Linear Fog can create a more visually appealing thickness of fog, but some less desirable artifacts may appear. Rice 6.12 only.
Q: Software Vertex Clipper, what?
A: The Software Vertex Clipper uses code that also relies on DirectX features unsupported by XBOX. You can witness the missing side textures on treasure chests in Legend of Zelda. The rest of the functionality is enough to work, and it also corrects some bad vertex clipping seen in Conker's BFD in the level "Enter the Vertex." You can enable the Software Vertex Clipper by selecting "Software Vertex Processing" in Video Settings. Rice 6.12 only.
Q: 1964 1.1 and PJ64 1.6 support cheats, what gives?
A: I never implemented a menu scheme to modify and activate cheats. In the meantime, PJ64 1.6 can load "permanent cheats" that correct some big issues. (i.e. Zelda SubScreen Delay Fix, and Pokemon Snap)
Q: I am experiencing graphics glitches in X game.
A: That's not really helpful. :/ The most common graphics issues result from Rice Video's lack of [Hardware] Framebuffer Emulation. Garbled textures, missing effects, bad vertex clipping, and black/ missing textures can be a result of a plugin incompatibility rather than a port incompatibility. Check your PC for compatibility with the closest Rice Video plugin to determine if the bug is in fact a regression or something that can be fixed. Next, you can do some research to find out what type of bug you are encountering and if it can be fixed. Emutalk.net forums and BigHead's compaitibility list are helpful here. Gonetz' GLideN64 dev blog has great explanations for N64 HLE graphics problems here: http://gliden64.blogspot.com/ After that, report the game, tell me exactly whats wrong, what emulator and plugins you're using, include a screenshot, and I might look into fixing it. Otherwise... Don't bother! :P
Q: I am experiencing a crash after X in Y game.
A: Make sure you are giving the emulator enough RAM, and try setting Texture Memory to AUTO. Some games handle the auto texture memory trick better than others. If crashes persist, report the game, emulator & plugins, how to reproduce the crash, and any combination of plugins that worked in the past.
Q: PJ64 1.6 doesn't play opening animations all of the time. Why?
A: There are some changes to PJ64 where previous optimizations don't work as gracefully. The result is that some opening animations get skipped at the cost of good emulation speed.
Q: Turok Dinosaur Hunter doesn't work or crashes on me. Why?
A: PJ64 1.6 won't boot it due to optimization issues. 1964 1.1 will only boot it with audioMusyX. Both emulators will eventually crash, either randomly, or after the first key is recovered. Mupen64 would be needed to play this game fully.
Q: Players 2 and 4 are unplayable in Conker's BFD deathmatch.
A: Sorry. Again, this is a core issue.
Q: Can I tweak the speed of a game?
A: Yes. Adjust the Counter Factor value in the emulator's .ini or .rdb. A lower CF value emulates closer to a real N64, while a higher CF value will create a better experience on old hardware like the Xbox. Generally, adjusting CF will do a better job than Frameskip.
Q: Load/Save States as well as the In Game Menu cause me crashes.
A: Yes, these bugs have been around since Surreal64 1.0. They are a result of the emulator and plugins running natively with the lower level xbox functionality written into various parts of Surreal64. Most emulators for the Xbox include a simple App that the emulator is built ontop of.with Surreal64, when a problem occurs, the interface becomes inaccessible.