WinUAEX Amiga Emulator port for XBox v1
http://xport.xbox-scene.comhttp://www.winuae.net/Thanks to J-Red for another great skin!
Features :
- Emulates Amiga
- Excellent compatibility - ported from WinUAE 0.8.27
- ZIP support
- Cheat system - Search/Create your own cheat codes (see notes)
- Favorites list
- Save states
- Virtual Keyboard - go to Controller Configuration / UI Mappings to select
the button combo that will bring up the Virtual Keyboard while in-game.
- Real keyboard support
- Real mouse support
- Hard drive files (HDF) and hard drive directory support
- Lots of WinUAE customization options
- Fast forward/throttle
- Resizable game screen
- Skin-able :
- Backgrounds
- Sounds
- Background Music
- Sprites
- Text position (right/left/center, top/bottom/center)
- Text color, select bar color
- Font
- Fading speed
- Screenshot position
- Can specify 2 sprites to surround the selected menu option
- Option to have a transparent select-bar color (from select-color menu)
- Can flip sprites horizontally/vertically
- Can set motion_x and motion_y variables for sprites
- Sprites can loop continuously or just once
- If you want to change the way something looks in this new UI,
chances are that you can change it via the Configuration menu.
- Save Game management - delete save game files
- Text file viewer
- ISO9660 support
- User definable save directory. If you don't like the default of
E:\SAVES\WINUAEX you can change it via the menu
- Take in-game screenshots and display them on the game selection list
- New UI feature - auto-screenshot capture mode. When enabled, the emu
will start taking screenshots at a user-defined interval. Useful for
ripping sprites/animation.
- Hardware filtering options : Point, Bilinear, Trilinear, Anisotropic
- Record/Playback feature - record your gameplay in the emu and then
play it back again. Record up to 10 minutes of gameplay.
- Every single in-game command is fully customizable on any of the
four joypad controllers.
- Map any emulator or UI command to a single button or a combination of
two buttons. (e.g. RTrigger+LTrigger = Save State)
- Autofire capabilities for any emulator button on any controller
- One-button combos (define a series of emulator commands to be played
back when you press a user-definable XBox controller combination.)
(E.g. Press RTrigger+LTrigger to execute the command string
A,B,A,B,Up,Down,Left,Right)
- Traverse any directory on any drive ( Continue selecting the parent
directory entry on the file selection list to get the drive selection
list. Selectable drives are C, D, E, F, R, X, Y, Z, and SMB.
R is the CDROM drive. SMB is the samba share you have defined in your
WINUAEX.ini file.) Press Y from any file-listing screen to go up one
directory level.
- All UI commands (save state, load state, screenshot, etc) can be
invoked from the Options/Pause menu as well as in-game via your
customized joypad mappings.
- Can be invoked from a command-line to directly run a game from a front-end
or dashboard and bypass the user-selection screens. (Only if the frontend
or dashboard supports this feature.)
- Can return to the launching program *if* the launching program supports this
feature. For example, if the custom-launch routines are incorporated into
a new frontend, that frontend could launch WINUAEX and when you exit
WINUAEX, that frontend can be automatically reloaded.
Default ROM dir is D:\AMIGADISKS
===============
Important Notes
===============
--------------
Kickstart ROMs
--------------
You need to put the following ROM files into the D:\ROMS directory:
KICK12.ROM
KICK13.ROM
KICK20.ROM
KICK30.ROM
KICK31.ROM
These are the so-called "Kickstart" ROM images that are REQUIRED in order for
WinUAEX to be functional. Search google for "kickstart roms" and I'm sure you'll
find them.
--------
Cutbacks
--------
WinUAE eats up a LOT of memory. I had to remove the following:
Software graphics filters (2xSai, AdvanceMame2x, etc, etc)
MP3 playback
Network sharing (Samba, Relax, netplay)
Hi-definition modes (720p, 1080i)
If you put a different skin on, I don't recommend using any sprites or sounds
because if you add too much, it may prevent WinUAEX from being able to load
any games.
I don't think these restrictions will be really disappointing to people, though.
-------------------------
Using Disks + Save states
-------------------------
When you change disks while playing, the configuration of the game is updated as well.
For example, if I start a game with DISK1 and then during the game I change the disk
in drive 1 from DISK1 to DISK2, then the configuration of the game will now state
that the disk in drive 1 is DISK2. When you start the game again from the main menu,
it will try to boot off of DISK2. This is intentional. Save states for multiple disk
games requires that the disks present in the drives when the state was saved are there
when the state is reloaded.
If you are playing a game where you have to change the disks during gameplay, then
I strongly suggest these tips:
- Turn on auto-loading of save states
- After you have changed a disk, wait until the game has finished loading whatever
it needs and then save the state. Always remember to save the state after
each disk swap. If you do this, then when you exit the game and restart it in the
future, the disks will be set correctly in the configuration screen, the state will
automatically load, and you'll be all set.
-----------------
Weird Speedup Bug
-----------------
There is a strange bug that has popped up a couple of times during testing that I have
not been able to find. If you notice that the game you are playing is going way too
fast, then simply exit out of it and restart (or save the state and immediately load the
state again.) It should be fine after that.
-----------------------------
Save States + Hard Drive = No
-----------------------------
Saving states while using hard drives is not supported in WinUAE, therefore it is not
supported in WinUAEX. You can still save/load the states, but there is no guarantee
that it will work with hard drive images. I've had it work fine for me in some cases
and in other cases it has crashed.
------------------
Game Configuration
------------------
The default configuration will work with most non-AGA games, but some games do require
tweaking. For AGA games, I suggest using KICK31. There are lots of tutorials,
docs, and forums about configuring games for use in WinUAE. I suggest you read
them first if you are having a problem getting a game to run. I have found that
just about every game will work if you fiddle with the settings enough. There are
also different versions of various games. If one does not work, try to find another.
In the few cases that I couldn't get a game to work, I found that it also did not work
in the Windows version of WinUAE.
Here are some general configurations that have worked well for me:
#1 - This is good for standard A500 games, including Shadow of the Beast
68000
Kickstart 1.3
512k Chip Mem
defaults for everything else
#2 - This is good for some more advanced games (A1200)
68020
Kickstart 3.1
2MB Chip mem
defaults for everything else
#3 - This is good for AGA games
68020
Kickstart 3.1
2MB Chip mem
AGA Chipset
defaults for everything else
--------------------------
Amiga Controllers Defaults
--------------------------
It seems the normal configuration that many games expect is for a mouse to be
plugged into port 1 and a joystick in port 2. The default configuration for
your controller is as follows:
The following buttons apply to the controller assigned to port 2 which is
defaulted to an Amiga Joystick:
XBox DPAD - Port 2 Up/Down/Left/Right
XBox A - Port 2 Button 1 (Joystick Button 1 or Mouse Left Button)
XBox B - Port 2 Button 2 (Joystick Button 2 or Mouse Right Button)
XBox X - Port 2 Button 3 (Joystick Button 3 or Mouse Middle Button)
The following buttons apply to the controler assigne to port 1 which is
defaulted to an Amiga Mouse:
XBox Y - Port 1 Button 1 (Joystick Button1 or Mouse Left Button)
XBox Black - Port 1 Button 2 (Joystick Button 2 or Mouse Right Button)
XBox White - Port 1 Button 3 (Joystick Button 3 or Mouse Middle Button)
The XBox Left Thumbstick will always control the mouse cursor regardless of
the port to which it is assigned. (The same thing applies to a real mouse
if you have one connected.)
Stella, Gnuboy, SMSPlus, FCEUltra, HUGO, NeoPop, DGen, Bochs, HUGO-CD,
FMSXBox, Bliss, WinSTon, Gens, Z26X, StepmaniaX, PCSXBox, XBoyAdvance,
DOSXBox, AtariXLBox, MirrorMagicX, KoboX, MaelstromX, MarblesX, Vice64X,
Vice20X, VicePETX, KegsX, XPired, AdamX, WonderSwanX, BeatsOfRageX,
PowermangaX, LynxBox, BlueMSXBox, GladiatorX, AmphetamineX, StarfighterX,
PachiX, BlobWarsX, OdysseyX, ArnoldX, X68000X, WinUAEX...
what's next?
Enjoy!
