FS-UAE <= 2.9.x development series

[FrodeSolheim]

Three new releases has been made without announcement here, so here is a combined release annoncement for all three

Changes in FS-UAE 2.1.7dev:

• Merged updated emulation core from WinUAE 2.5.0beta27.
• (Launcher) WHDLoad support in combination with online database.
• (Launcher) Updated translations: it [Speedvicio], pl [grimi].

Changes in FS-UAE 2.1.6dev:

• Updated bitmap font with additional characters for Portuguese.
• (Launcher) Fix a bug where missing files stopped the scan process (when
  using the database feature).
• (Launcher) Fix path expansion when using ADFs from archives.
• (Launcher) Updated translations: fr [Foul], de [nexusle].

Changes in FS-UAE 2.1.5dev:

• Use Windows API function to prevent display from going to sleep.
• Added translations: pt [Treco].
• (Launcher) Initial online database support.
• (Launcher) Can download screenshots / covers on demand from server.
• (Launcher) Added translations: pt [Treco].
• (Launcher) Updated translations: pl [grimi].

http://fengestad.no/fs-uae/download-devel

I use FS-UAE 2.1.6dev ......

swap_ctrl_keys GUI function is missing?
For enable it?

[nexusle]

Have you tried 2.1.8dev??

You'll find it unter "Settings" (cogwheel) third point left and the last point right

Thanx.....is it all ok!

[yesplease]

Hi Frode,
how to emulate the mouse, with keyboard ? It seems the game "impact" lets you only control via mouse. But to control it with mouse doesn't feel comfortable. I like to have buttons, so I thought I set Port0 from mouse to keyboard-device and then set the keyboard to mouse-mode. But I can't control it with direction keys and the fire key that is my right alt key doesn't work either. Surely the best would be that impact itself would accepts joystick as controller but it doesn't. I used already the 2.1.8.
Any chance to get it work with controller or keyboard? If not I can live with the mouse as controller then ;-) FS UAE is so great !

[FrodeSolheim]

Originally Posted by yesplease

Hi Frode, how to emulate the mouse, with keyboard ?

FS-UAE does not yet have this feature (*). Mouse emulation via gamepad analog control at least is planned.

(*) There are actually some custom actions which you can map -which may work (feature inherited from WinUAE, haven't tested actually) - http://fengestad.no/fs-uae/input-actions. You can map keyboard keys against mouse events. No "official" support for this currently though, either it works or it doesn't.

[bcripon]

Frode,

I just downloaded FS-UAE 2.1.8. Unfortunately, I get the same "Python requires X11" message when I attempt to configure the joystick buttons as the earlier poster. I do have XQuartz on my system (the only X11 option for 10.8), but that does not seem to be enough.

From the earlier message, it sounded like it would be corrected in 2.1.4. However, at least for me, this does not appear to be the case.

I was just wondering if the Joystick Configuration program is working on OS X yet.


Bob C

[FrodeSolheim]

Joystick Configuration works on 10.6 at least, but X11-support is installed here. It looks like pygame (which is used for joystick support) may have some dependency on X11. Will have to investigate some more.

[bcripon]

Originally Posted by FrodeSolheim

Joystick Configuration works on 10.6 at least, but X11-support is installed here. It looks like pygame (which is used for joystick support) may have some dependency on X11. Will have to investigate some more.

Thanks.


Bob C

[bcripon]

Frode,

I also noticed that the Kickstart scan doesn't see a Kickstart for the Amiga 500 or Amiga 4000. I have all of the Kickstarts on the Amiga Forever 2012 DVD so I am pretty sure it should detect an Amiga 500. It does see an Amiga 500+ though.


Bob C

[FrodeSolheim]

Originally Posted by bcripon

Frode, I also noticed that the Kickstart scan doesn't see a Kickstart for the Amiga 500 or Amiga 4000. I have all of the Kickstarts on the Amiga Forever 2012 DVD so I am pretty sure it should detect an Amiga 500. It does see an Amiga 500+ though.

I understand what the problem is when you say 500/4000 . Short background: Amiga Forever does not really come with the Amiga 400/4000 kickstarts but slight variants. amiga-os-130.rom is for example the Amiga 3000 rom, but this is only differs in 3 bytes compared to a common Amiga 500 rom. So to make it easier for different people to join net play games whether they have purchased Amiga Forever or extracted an A500 rom, FS-UAE now patches the Amiga Forever rom by changing the three bytes. FS-UAE Launcher knows about this and in the file database, the checksum stored is the final decrypted/patched checksum. But what I forgot is that if the kickstarts are scanned with an earlier version of FS-UAE Launcher, the checksum stored in the database is the old A3000 rom checksum, and so the A500 rom is not found.

So you need to refresh the information in the database. One trivial solution (if the rom files are located in the standard FS-UAE kickstarts directory):
- Move the kickstart rom files to another (temporary directory) and start FS-UAE Launcher. This should erase the information from the database.
- Quit FS-UAE Launcher, move the rom files back, and start FS-UAE Launcher again so it can rediscover the kickstarts.

[nexusle]

Originally Posted by FrodeSolheim

amiga-os-130.rom is for example the Amiga 3000 rom

This would be new! A3000 started at Kickstart 2.0. Only Beta Machines had 1.4.

BTW: I have also the complete AF ROMs and have all icons green...

[FrodeSolheim]

Originally Posted by nexusle

This would be new! A3000 started at Kickstart 2.0. Only Beta Machines had 1.4.

BTW: I have also the complete AF ROMs and have all icons green...

I only know is that the decrypted amiga-os-130.rom has the same checksum as the following entry from the TOSEC dat: "Kickstart v1.3 r34.5 (1987)(Commodore)(A3000)[!]"

All Amiga Forever ROMs should work, but the problem can probably occur if they are indexed with Launcher < 2.1.3, and the Launcher is then updated afterwards because I didn't think of this case (haven't double-checked, but it is an reasonable explanation).

[bcripon]

Originally Posted by FrodeSolheim

So you need to refresh the information in the database. One trivial solution (if the rom files are located in the standard FS-UAE kickstarts directory):
- Move the kickstart rom files to another (temporary directory) and start FS-UAE Launcher. This should erase the information from the database.
- Quit FS-UAE Launcher, move the rom files back, and start FS-UAE Launcher again so it can rediscover the kickstarts.

Frode,

That fixed the problem. Thanks!


Bob C

[nexusle]

@Frode

in last dev build the Launcher doesn't store general custom options. Can you have a look at it?

[FrodeSolheim]

Originally Posted by nexusle

@Frode

in last dev build the Launcher doesn't store general custom options. Can you have a look at it?

Please give a detailed example (steps to reproduce) and also attach Launcher.log.txt file after trying to store the options (quit the Launcher first).

[nexusle]

Tried to set zoom mode for all games to 640x400.
have added the line:
zoom = 640x400 in custom settings
after closing an reopening the settings, this option is gone

AHHH...
Forget everything from "good morning"
The Launcher have options for this under "Filter & Scaling"
My fault

[FrodeSolheim]

Originally Posted by nexusle

The Launcher have options for this under "Filter & Scaling"

Yes, the options with GUI controls are not shown under custom settings This setting may not be ideal for all games btw, since this zoom mode sets a very specific crop rectangle, and some games will not be centered in this. The autoscale algorithm can be overriden in the database on a per-game basis when autoscale does not work properly. Just add a comment to the game in question and I can look at it.

[nexusle]

Hi Frode,

I've a problem with the ESC Key on WHDLoad Games. His function exists

Can it be, that the default quit key for WHDLoad/FS-UAE in WHDLoad-Mode is ESC? If so, this is no good idea! In some games with the ESC key you can skip intros etc...

Can you/I fix this?

[FrodeSolheim]

Originally Posted by nexusle

Hi Frode,
I've a problem with the ESC Key on WHDLoad Games. His function exists

Can it be, that the default quit key for WHDLoad/FS-UAE in WHDLoad-Mode is ESC? If so, this is no good idea! In some games with the ESC key you can skip intros etc...

Can you/I fix this?

Yes, you are right, FS-UAE Launcher creates a "default" WHDLoad.prefs file. I've checked and it does have QuitKey=$45 set I copied the defaults from somewhere, but I don't remember where. This should probably be something else...

You should be able to override it without a new Launcher version by creating the following file:
Documents/FS-UAE/WHDLoad/S/WHDLoad.prefs
(it can probably be an empty file), and it will be copied over along with the WHDLoad key - overwriting the WHDLoad.prefs file created by the Launcher when you start a game.

For reference, here's the WHDLoad.prefs file that the Launcher creates:

;ButtonWait            ;wait for button pressed (slave must support this)
;ChipNoCache            ;disable cachebility of Chip-Memory
;CoreDumpPath=T:        ;path for coredump files
;DebugKey=$5b            ;rawkey code to quit with coredump (debug)
;ExecuteStartup=rx offline.rexx    ;command to execute on WHDLoad startup
;ExecuteCleanup=rx online.rexx    ;command to execute on WHDLoad exit
;Expert                ;selects expert mode
;FreezeKey=$5d            ;rawkey code to enter HrtMon/TK
;MMU                ;use MMU (for 68030)
;NoAutoVec            ;ignore unwanted autovector interrupts
;NoFilter            ;disable audio filter
;NoFlushMem            ;do not flush memory
;NoMemReverse            ;do not allocate memory reverse
;NoWriteCache            ;disable the disk write cache
QuitKey=$45
;ReadDelay=150            ;wait after reading from disk (1/50 seconds)
;RestartKey=$5c            ;rawkey code to restart
;ShowRegs=SYS:Utilities/MuchMore W WL=80 WT=80 WW=582 WH=700    ;command for Show Regs
SplashDelay=0        ;time to display splash window (1/50 seconds)
;WriteDelay=150            ;wait after saving something to disk (1/50 seconds)