FS-UAE <= 2.9.x development series

[yesplease]

Thanks for your answer Frode! I thought so. This little thing can render 1080p h264 movies without any problems, a task for which most standard computers in 2005 maybe wouldn't be sufficient. But CPU wise it is five years weaker, maybe comparably like a computer in 2000.

[FrodeSolheim]

A new development version has been released. Changes in FS-UAE 2.5.0dev:

• UAE core code updated from WinUAE 2.7.1b9.
• FS-UAE can use 256 kB chip RAM (and also 128 if you *really* want to).
• Inhibit screen saver / power saving when running FS-UAE on OS X.
• Allow short-hand –video-sync(=1/0) option
• Use floating point control register, output compiler warning when not.
• Added flush_log boolean option to flush log output after each log line.
• New UAE Native Interface (via built-in uaenative.library).
• Enforcer / AHI interface is added (but with a dummy AHI backend).
• Support for old WinUAE-style native calls.
• Code cleanup in UAE code to reduce the number of compiler warnings.
• Removed some unused source files from the source archive.
• Auto-generated source files are now auto-generated when compiling on all platforms, and not cached in the source archives any longer.
• Fixes to allow FS-UAE to be compiled with the lastest MinGW version.
• Updated translations: it [Speedvicio], es [albconde], da [tomse], nb.

Changes in FS-UAE Launcher 2.5.0dev:

• Windows portable version didn’t store relative paths.
• Properly locate A500 kickstart on first startup when it exists.
• Don’t refresh the online database when running the file scanner.
• Game database changes for better forward compatibility.
• Adult filter for game database, enabled by default.
• Use search term tag:adult to show adult games.
• New option database_show_adult to show adult games by default.
• Can search for quoted words to require exact word match.
• Fixed some translated strings used incorrectly.
• Updated translations: pl [grimi].
• Fixed multiple file selection when using PyQt.
• Added 256 kB chip RAM to the chip memory selector.
• Updated translations: de [jbl007], es [albconde], it [Speedvicio], da [tomse], nb.
• (Arcade) Fixed missing ext rom problem when starting CD32 games.
• (Arcade) Fixed repeat problem when navigating with joystick hats.
• (Arcade) Fixed a bug related to non-ASCII characters in joystick names.
• Fixed a bug preventing hd_requirements = workbench from working.
• Fixed a bug which is also a syntax error with Python < v2.7.
• Fixed a potential startup problem when PATH has non-ASCII characters.

Notes:

• Several of the changes are from the stable series, but new since the latest development version:
• For some reason, openSUSE build service won't built this (RPM) version, no useful information about the problem in the build logs, so no RPMs are available yet.

New development versions will be forthcoming more regularly I'll also make a post on what to expect of changes (short-term).

[tomse]

awesome work frode :-)

[Retroplay]

I have a quick question regarding 7-Zip.

I added 7-Zip (9.25 x64) to my path in Windows, scanned the directory containing my 7z compressed adf images (one file per 7z), but they still don't play ball in FS-UAE launcher.

Isn't that the correct way or did I forget something ?

[FrodeSolheim]

I think it should work in Windows too provided 7z.exe is on the path (quick test works). But a couple of notes:
* It only works to satisfy disk requirements / files for the online database, you cannot insert a .7z file in a floppy drive (nor use it as a hard drive).
* There's no clever logic, so if you have scanned the .7z files before adding the 7z-executable to the PATH, you may have to delete the file database (Cache/Files.sqlite) and rescan.

[Retro-Nerd]

Allow short-hand –video-sync(=1/0) option

Can you explain this a bit more, Frode?

[FrodeSolheim]

Originally Posted by Retro-Nerd

Can you explain this a bit more, Frode?

It's just a very minor thing, you can start FS-UAE from the command line with either --video-sync or --no-video-sync (easier to write and remember than --video-sync=off/auto).

[Retro-Nerd]

I see. Thanks for the info.

[Retroplay]

Ok I deleted cache and did a rescan, but I still can't get any of the adf or ipf games to work.

Also when I scan for 7z archives, the command box pops up for each archive it scans.
See this screenshot: http://imgur.com/sGnRxKe

It's practically rendering the PC "useless" while the scan is in progress.
Is there a silent mode, perhaps a commandline switch to prevent this from happening ?

It only works to satisfy disk requirements / files for the online database, you cannot insert a .7z file in a floppy drive (nor use it as a hard drive).

So you're saying 7z files are useless in FS-UAE, even though 7-Zip is added the path ? E.g I can't actually play the games ?

[amigafreak68k]

Originally Posted by FrodeSolheim

• Adult filter for game database, enabled by default.

How to disable it?

[rofl0r]

is there a specific reason you dont follow the upstream (==WinUAE) version numbering system?
imo that would make it more clear.

[FrodeSolheim]

Originally Posted by Retroplay

Also when I scan for 7z archives, the command box pops up for each archive it scans.

That should be fixable (added https://github.com/FrodeSolheim/fs-u...ncher/issues/6)

Originally Posted by Retroplay

So you're saying 7z files are useless in FS-UAE, even though 7-Zip is added the path ? E.g I can't actually play the games ?

What I mean is that it will only work with the online database a.t.m. (It was really only a small feature added on request, but this is the problem with adding small features on request without doing it thoroughly )

Originally Posted by amigafreak68k

How to disable it?

Advanced settings:

database_show_adult = 1

(it was too late to create an UI control for it for 2.4.0)

Originally Posted by rofl0r

is there a specific reason you dont follow the upstream (==WinUAE) version numbering system?
imo that would make it more clear.

FS-UAE and WinUAE does not have any coordinated release cycles, so FS-UAE version numbers based on the emulation core from WinUAE makes little sense to me. For reference, FS-UAE 2.1.x (>= 2.1.13), 2.2.x, 2.3.x and 2.4.x all use the same emulation core (from WinUAE 2.5.x).

[Goingdown]

Originally Posted by FrodeSolheim

For some reason, openSUSE build service won't built this (RPM) version, no useful information about the problem in the build logs, so no RPMs are available yet.

Hi,

I tested to compile fs-uae from source on my Fedora 20 (64-bit)

Make install fails with:

install -d /usr/bin
install fs-uae /usr/bin/fs-uae
install: cannot stat 'fs-uae': No such file or directory
make: *** [install] Error 1install -d /usr/bin
install fs-uae /usr/bin/fs-uae
install: cannot stat 'fs-uae': No such file or directory
make: *** [install] Error 1

Will need to investigate more - this seems strange because /usr/bin/fs-uae is there.

EDIT. False alarm. I think I had something wrong with that compile. Recompile did fix the make install

[Retroplay]

Originally Posted by FrodeSolheim

That should be fixable (snip)

Excellent, thanks.

[SnakeCoils]

Hello Frode,
could you please modify the makefile to let the compiler use SDL=1 if the architecture on OSX build is PPC? I do this manually since the SDL=2 was the default for OSX but would be nice if the script do this automatically :-)
A last word: I still believe that audio problems on audio samples playback (for floppy sounds and CD32 tracks) on ppc builds are not related to lack of speed but to big/little endian format handling. Could you kindly take a look about this issue? May some of the other Mac developers here team up with a suggestion or a fix?

[FrodeSolheim]

Originally Posted by SnakeCoils

could you please modify the makefile to let the compiler use SDL=1 if the architecture on OSX build is PPC? I do this manually since the SDL=2 was the default for OSX but would be nice if the script do this automatically

Well, I could, but... I'm contemplating going all in with SDL2 very soon. That will probably mean SDL1.2 support either disappearing completely, or bit-rotting because I don't wan't to reguarly maintain / test the SDL1.2 code. There is also quite a few hacks to work around issues in SDL1.2 I could remove if I only need to support SDL 2.0.

Is there a problem getting SDL 2.0 to work on OS X / PPC?

Originally Posted by SnakeCoils

I still believe that audio problems on audio samples playback (for floppy sounds and CD32 tracks) on ppc builds are not related to lack of speed but to big/little endian format handling.

I just posted a patch you can try here: http://eab.abime.net/showthread.php?p=945851#post945851

[FrodeSolheim]

A new development version has been released. Changes in FS-UAE 2.5.1dev:

• Merged code from WinUAE 2710b12.
• Support for .scp floppy images [keirf].
• Drive sound and CDDA fixes for big-endian platforms.
• Fixed left trigger = toggle autofire.

Changes in FS-UAE Launcher 2.5.1dev:

• Case insensitive kickstart scan on startup.
• Added support for Greek language.

[SnakeCoils]

Oh my God, it works! It's ALIVE! :-D Thank you so much! Reallly THANK YOU! Both floppy drives and CD32 tracks now sounds beautifully on my PowerMac G4 MDD! Excellent work!
About the SDL 2.0 question seems that this major release will not more support the PPC platform so the last available revision for it will be the 1.2.15
I feel also the MAME team is going to move, sooner or later, to SDL 2.0 environment but things must evolve and the PPC era is slowly going to its sunset... but as for present situation I am more than HAPPY to see all this life still going on in this ten years old technology! :-)

[FrodeSolheim]

Just a short update on what's going on (except for spring influenza, etc ):

The next development version is dragging out because I'm replacing quite a few components:
* SDL2 is used by FS-UAE on all platforms - might fix high-DPI resolutions on Windows as it did on OS X - as well as allow for some nice improvements in the longer run.
* FS-UAE Launcher / Arcade is migrating to Python 3 (from Python 2). A main reason is Python 3's sane split between str (unicode) and bytes, which should prevent those unicode-related bugs showing up from time to time.
* As a consequence of the above point, pygame must also be replaced, and FS-UAE Arcade is being ported to (Py)QT instead.

In short, some short term pain for long term gain. This stuff is more or less done. Some more tweaking, fixing and testing remains

[yesplease]

Nice. 256Kb memory selector. Cool stuff.