FS-UAE <= 2.9.x development series

[asapreta]

Guys, I'm really impressed with your work.
As a former Amiga owner I decided to get some of my stuff back running and got FS-UAE 2.7.7 dev. to my MacBook Pro.

I got some of my stuff running but then I tried to check some configs and features and I got this error while trying to run CyberStormPPC acc:

(Edit, I attached the figure)

The rom is on the correct folder (I presume) but it can be seen by the FS-UAE.

Can you help me?

[FrodeSolheim]

Originally Posted by asapreta

The rom is on the correct folder (I presume) but it can be seen by the FS-UAE. Can you help me?

Move it into the "Kickstarts" folder (which should be called ROMs", really). Also, this is not really a question specific for the development version.

[asapreta]

Originally Posted by FrodeSolheim

Move it into the "Kickstarts" folder (which should be called ROMs", really). Also, this is not really a question specific for the development version.

You are right about the development version issue, sorry.
But thanks for the tip, I'll give a try.

[FrodeSolheim]

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

• Disable use of fullscreen spaces on OS X by default. Use SDL_VIDEO_MAC_FULLSCREEN_SPACES = 1 (advanced settings or environment) if you want to re-enable it.
• Fixed a crash when using (experimental and) unsupported re-recording.

Changes in FS-UAE Launcher 2.7.8dev:

• You can add custom config on startup (--config:key=value). Especially useful when auto-launching games and you want to override config.
• You can start with custom settings (--settings:key=value). Note that the changed settings will be permanent / saved.
• Make distinction between Amiga device type and host device more explicit.
• Made launch dialog non-modal.
• Net play feature is enabled by default.
• Moved net play UI into a separate window.
• Clear search field when changing game/config list in dropdown.
• All .sqlite databases moved into Data/Databases.
• Some user interface adjustments.
• Quite a bit of code cleanup and some restructuring.

Changes in FS-UAE Arcade 2.7.8dev:

• Open FS-UAE Arcade as a maximized borderless window as default for now.
• Idle (stop rendering) when animations are done.
• Do not process joystick input in the background while running FS-UAE (Fixes problem where Arcade has disappeared when quitting FS-UAE).
• Do not run needless render loop in the background while running FS-UAE (Also fixes FS-UAE performance issue when running via Arcade).
• Alt+Return (Cmd+Return) can be used to toggle fullscreen, Alt+Q (Cmd+Q) to quit.
• Delay loading GL widget until window has been shown.
• Delay loading of PyOpenGL functions until first time needed.
• Possibly fixes black screen for some ATI users on Windows.
• Cleanup in the code base, removed some unused code.
• Updated PyOpenGL to 3.1.0.

Due to the number of changes in the Launcher and the Arcade, and the time passed since the last release, I wouldn't be surprised if there is a bug or two hidden somewhere. So don't be shy about reporting any new issues

Also, after starting this new version, you need to rescan files/games if you use the online game database.

[asapreta]

Hi, I just downloaded and tried 2.7.8dev and it won't load plugins already installed, even after rescanning files (on 2.7.7dev they work) .

They are on the default folders for Mac OS X.

I'll keep testing.

[FrodeSolheim]

Originally Posted by asapreta

Hi, I just downloaded and tried 2.7.8dev and it won't load plugins already installed, even after rescanning files (on 2.7.7dev they work).

Works for me. The most likely explanation is that you had 32-bit plugins and downloaded 64-bit FS-UAE (or the other way around). The CPU architectures have to match.

[asapreta]

Originally Posted by FrodeSolheim

Works for me. The most likely explanation is that you had 32-bit plugins and downloaded 64-bit FS-UAE (or the other way around). The CPU architectures have to match.

I'll check this.
I think I may have downloaded the 32 bit version of the FS-UAE without noticing.

Thanks for answering.

[edit]

You ware right. I downloaded the 32 bit version instead of 64 one.
Now it is working. Thanks.

Morning,

How can I migrate the database from fs-uae 2.7.7 to fs-uae 2.7.8?

[S0ulA55a551n]

Originally Posted by gorzka

Morning,

How can I migrate the database from fs-uae 2.7.7 to fs-uae 2.7.8?

Just do a file scan from the menu

[ztronzo]

Originally Posted by gorzka

Morning,

How can I migrate the database from fs-uae 2.7.7 to fs-uae 2.7.8?

If you are using the portable version, I just put the freshly downloaded portable 2.7.8 on top of 2.7.7
replacing everything inside the fs-uae/programs folder
Without running it before you do so (Its safer if you just delete the old fs-uae/programs folder and add the new one there)

When you run FS-uae it checks folders and files keeps all your original folders and settings.ini intact
and if it doesnt find them it creates a new settings.ini and database structure

That does'nt work. The database structure is not the same in 2.7.8 as in 2.7.7

[FrodeSolheim]

Originally Posted by gorzka

That does'nt work. The database structure is not the same in 2.7.8 as in 2.7.7

As S0ulA55a551n said, you genereally don't migrate the databases, you just let FS-UAE Launcher recreate them. If you have a specific use case where this is problematic, you should add more background information!

Originally Posted by gorzka

That does'nt work. The database structure is not the same in 2.7.8 as in 2.7.7

The folder structure in 2.7.8 has changed a little bit.

The Database files now go into "fs-uae\Data\Databases\"

The newly created files are:

Amiga.sqlite
CD32.sqlite
CDTV.sqlite
Files.sqlite
Launcher.sqlite
Locker.sqlite

The file "settings.ini" should be placed into the "fs-uae\Data"-folder.

This has been explained by Frode in his changelog for 2.7.8, already.

This question is for Frode:

I wonder why are there still 2 versions of fs-uae: portable and not portable.
Isn't it better to just have a portable version, only?

The file portable.ini is a zero-byte file which tends to be deleted by some system cleaning software very quickly.
Instead of having a zero-byte file wouldn't it make sense to have something written in it?
Just like:

.

[portable]
on

portable=on/true

...or something similar? We then would have at least 1 byte written in this file, and it wouldn't be deleted that easily.

Other projects do that, too with their portable.ini file.

If you write something into the portable.ini in v2.7.8, you'll get a list full of errors, which i didn't get in v2.7.7.

BTW: Some burning tools like Nero don't write zero-byte files...

[jbl007]

Originally Posted by FrodeSolheim

(–config:key=value) (–settings:key=value)

Looks like something (forum-software?) replaced the double dashes chr(45) with a long dash chr(8211)in your post. Works fine with

--config:key=value

--config:key=value

I wouldn't be surprised if there is a bug or two hidden somewhere.

Found none so far and Arcade seems to run a little smoother.

[Morrissey_de]

Hi there,

I´m using the latest portable Development Version 2.7.8dev with Windows10 and since then i have a problem with deleted Config Files.
When i delete a config file in the Configurations Folder, the Config
doesn´t disappear in the Launcher Config Window.
Before Version 2.7.8 it was necessary to quit the Launcher and Restart
the Application. The deleted Config was not in the Config Window anymore.
But now nothing helps. Even a complete System Reboot won´t change
anything. I tried both x86 and x64 versions.

Any suggestions?

Thanx and Greets

MOZ

[FrodeSolheim]

Originally Posted by wizzel

I wonder why are there still 2 versions of fs-uae: portable and not portable.
Isn't it better to just have a portable version, only?

One reason is "historical reasons", removing stuff is always harder than adding stuff Another reason is that the versions are not completely identical on all operating systems. For example, the portable versions (next release) move some data files out of the OS-specific directories, so they can be shared between Windows, Linux and OS X portable versions, while the non-portable versions have a simpler directory layout (more or less flat). So on OS X, the non-portable version is suitable to be dragged into the Applications folder, while the portable version is not.

But of course, fewer distributables means less stuff to test, so cutting down on the available versions is something to consider in the future.

Originally Posted by wizzel

The file portable.ini is a zero-byte file which tends to be deleted by some system cleaning software very quickly.

Cleaning software deleting files it does not know anything about? That's just incredibly stupid!

Originally Posted by wizzel

If you write something into the portable.ini in v2.7.8, you'll get a list full of errors, which i didn't get in v2.7.7.

It should work fine if it is written in ".ini syntax":

[foobar]
foo = bar

I can add some content to Portable.ini in the next release.

Originally Posted by wizzel

BTW: Some burning tools like Nero don't write zero-byte files...

More stupidness

Originally Posted by Morrissey_de

Hi there, ... When i delete a config file in the Configurations Folder, the Config
doesn´t disappear in the Launcher Config Window... [

Confirmed, will fix!

[FrodeSolheim]

Originally Posted by Morrissey_de

When i delete a config file in the Configurations Folder, the Config doesn't disappear in the Launcher Config Window.

Problem found and fixed (https://github.com/FrodeSolheim/fs-u...7f9c6e6f162576 - Scanned files were not stored with proper relative paths on Windows). Fix will be included in 2.7.9dev (coming soon)

[FrodeSolheim]

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

• Plugin layout changed – new plugins must be downloaded.
• Detect screen refresh rate for correct display with multiple displays.
• Simplified video_sync option (is a boolean now).
• Low latency vsync is enabled by default.

Notes:

• You need updated plugins for this version, the old ones will not work. The plugins are now found on the download page: http://fs-uae.net/download-devel#plugins, and the simplified plugin downloads include support for all operating systems (32-bit and 64-bit).

Known issues:

• Allocating 32-bit memory fails on some OS X / BSD setups. With 2.7.5dev+, 32-bit memory is avoided when JIT is not enabled, but real fix is needed for JIT. Problem (and cause) is known, just
• Amiga key sticks when opening/closing FS-UAE menu with modifier+F12 https://github.com/FrodeSolheim/fs-uae/issues/77

Changes in FS-UAE Launcher 2.7.9dev:

• Warn about old plugin versions, if detected.
• Detect ~/.wine/users/Public/Documents/Amiga Files, if present.
• Some changes to the settings dialog, video pages merged from 3 to 2.
• Scanned files were not stored with proper relative paths on Windows.
• New GUI controls for monitor, fullscreen mode, video sync and monitor info.
• New settings control for starting FS-UAE with full keyboard emulation.
• Fixed issue when you have a mouse with the same device name as a joystick.
• More compact binary distributions, far fewer data files.
• OS X: New skeleton .app launchers for portable suite.
• Windows: Proxy executables passes on arguments.
• CD-based games are now downloadable from OAGD.net locker (if the user has them stored there).
• Recognize .ccd CD variants from the online game database.

Notes:

• The file database in FS-UAE Launcher must be updated (full re-scan) due to a fixed bug – sorry!

Notes for the portable packages:

• The structure of the portable versions for different operating systems have been unified somewhat, and the versions are also able to share a lot of data files. You may want to remove the old program directories when upgrading to the new portable version.
• If you use the portable version, you should also delete the any FS-UAE Launcher[.exe|.app] or FS-UAE Arcade[.exe|.app] executable / script in the root folder. The new ones are called Launcher[.exe|.app] and Arcade[.exe|.app], and are – for all operating systems – simple “shortcut executables” / scripts. New in this version is that all the “shortcut executables” pass any arguments to the real programs.
• Portable.ini is no longer a 0-byte file.
• OS X Note: The .app bundles in the portable version are not self-contained, so you should not drag these to the Applications folder or similar. Use the non-portable version instead for this!

[Retro-Nerd]

Where are the shaders now? They are not in any of the new "Programs" subfolder.