English Amiga Board - Want to try builds of the new FS-UAE 4 & Launcher 4?

English Amiga Board (https://eab.abime.net/index.php)

- support.FS-UAE (https://eab.abime.net/forumdisplay.php?f=122)

- - Want to try builds of the new FS-UAE 4 & Launcher 4? (https://eab.abime.net/showthread.php?t=106562)

For some strange reason the Linux Launcher linked in Post #1 (4.0.109) downloaded FS-UAE 3.2.11-beta and now claims everything is up to date. Thought this is to try FS-UAE 4 like the thread title says?

Quote:

Originally Posted by midimax (Post 1572831)

Instead of the links in the first post, for the Linux version, I downloaded the latest master version (4.0.122) directly from the automated builds page, I think that is most updated one, right?

4.0.122 does the same thing ( I rolled it back to 3.1.68/66 because my Workbench 3.2.1 HDF that worked with 3.1.66 did not work with 3.2.11-beta )

Quote:

Getting list of updates...
Got result, doing calculations...

Available updates:
FS-UAE: 3.1.66 => 3.2.11-beta (Linux_x86-64)

But I also downloaded FS-UAE 4.0.71-master from the Page you linked and will give it a try this weekend.

Thank you.

Quote:

Originally Posted by guidobartoli80 (Post 1572747)

I noticed that on FS-UAE-Launcher/Master/ the latest 4.0.122-master build is from 2021-11-21 following a steady series of updates about a week apart. I was wondering if by chance development had paused for any particular reason or simply because a new build with more updates was on the way.

Hi, it's a bit of both. I have a pending update in progress, updated code in a private repo. I haven't published it yet because the update changes quite a lot of code internally, and it's not fully stable yet.

And in addition to that, I have very little spare time for the time being, so progress is slow. This will also be the case for the next few weeks also.

But don't worry. Nothing is wrong. Except I started on a (too big?) internal upgrade, and then got problems with too little time to complete it :)

Quote:

Originally Posted by midimax (Post 1572831)

I finally "fixed" this today. There is a bug in the Launcher where it picks the beta branch updates instead of the ones from master. I've "fixed" this temporarily by removing the beta versions from the updates files.

Thanks

And I figured out why my OS3.2.1 HDF does not work anymore.
The Launcher 4 ignores my custom/3.2.1 Kickstart that my 3.1.68 made config file points to (Kickstart resides in "~/Documents/FS-UAE/Kickstarts/", the config file contains no path just its filename) and (re-)sets it to "default" every time i load said config with Launcher 4.

Edit: btw. Launcher 4 had successfully updated itself to 4.0.133-master but totally ignored that there is a FS-UAE_4.0.78-master.
At the moment I (try to) use FS-UAE_4.0.78-master together with Launcher 3.1.68 anyway because every time having to set the correct Kickstart file manually gets quite annoying.

Hi there!
I am new to EAB, so hello everybody.

I tried out the new version of FS-UAE-Launcher,
but FS-UAE is missing. It downloads just the recent version of the launcher and the plugins, but no FS-UAE.

What can I do?

(I am using a Mac with macOS 12.6 (Monterey).

Thanks a lot,
Michael

(BTW: FS-UAE is a great piece of software!!)

Quote:

Originally Posted by Experiment466 (Post 1578098)

What can I do?

While the (newest) Launcher 4, like guidobartoli80 pointed out, probably can be found at https://fs-uae.net/files/FS-UAE-Launcher/Master/
FS-UAE 4 is at https://fs-uae.net/files/FS-UAE/Master/

But I am not sure about MacOS 12.6 and the specific installation details there.

Does anyone know if there are plans to integrate Drawbridge / Floppybridge support into FS-UAE?

Hi ! I have been using version 4 for quite a while without problems, but I would like to know if it was possible in the future to include the possibility of mounting a floppy disk without necessarily declaring it with "floppy_image_x =" in the config file. It would be cool with a requester to open a window in the emulator, choose an adf and presto! mounted!

Thank you :)

Quote:

Originally Posted by Foul (Post 1594424)

I second this, would like it too. I think it was mentioned to happen sometime.

I've tried 4.0.133-master on OSX for a bit and I think you can add the following to the known issues:

- Saving of whdload game archives (i.e. load, play, save, then use quit key) does not work. Each time you restart a game via the launcher the saved data is gone and nothing is written to the save states folder like it is with the 3.x series.

- Screenshots and covers for custom configurations do not work. I have some saved for a workbench config that I use with 3.x and they don't show up.

- Shaders don't work.

In general I prefer the 3.x style single window launcher settings pane instead of the individual icons and windowed settings in 4.x. I know the icons are more Amiga-like but it is a chore to go through several different settings windows to quickly change or check a few things.

Hi !

Since i am not able to enter the "CyberstormPPC boot menu" by pressing ESC in
FS-UAE 3.1.68
... (by the way: is this normal ? does this happen to other users to?) ...

I just tried out FS-UAE Launcher 4.0.133 & FS-UAE 4.0.78:

Ok ... now entering the "CyberstormPPC boot menu" works for me !
But i am not able to mount a CD-ROM in FS-UAE 4.
I can add/select the .img in the Launcher but it will not be mounted (CD0= empty)
Mounting it in F12 menu does not work too, when i try to mount it, i see the .img
but i am not able to select it by pressing enter !!!

Saving configs does not seem to work too !

anyone here with the same problems ?
or could anyone help please ?

.. i am on:

macOS Ventura 13.2.1

Hi!

I tried both the pre-made execs and also compiling from the main sources, I end-up with a segmentation fault error (MacOS Ventura).

If run with --stdout, these are the last lines of the output before the program crashes:

Code:

[UAE] [000] PAL mode V=50.0804Hz H=15625.0879Hz (227x312+0) IDX=10 (PAL) D=0 RTG=0/0

[UAE] [000] PAL mode V=50.0804Hz H=15625.0879Hz (227x312+0) IDX=10 (PAL) D=0 RTG=0/0

[UAE] [000] 000:000        draw outwidth/height = 752x574

[UAE] [000] 000:000        draw outwidth/height = 752x574

[UAE] [000] Buffer size (752*574) Native

[UAE] [000] Buffer size (752*574) Native

[UAE] [000] 000:000        [DRAWING] init_aspect_maps

[UAE] [000] 000:000        [DRAWING] init_aspect_maps

[UAE] [000] 000:000        [DRAWING] init_row_map (maybe)

[UAE] [000] 000:000        [DRAWING] init_row_map (maybe)

[UAE] [000] 000:000        [DRAWING] init_row_map rowbytes=3008

[UAE] [000] 000:000        [DRAWING] init_row_map rowbytes=3008

[UAE] [000] 000:000        reset_custom_limits

[UAE] [000] 000:000        reset_custom_limits

[UAE] [000] RTGFREQ: 312*50.0804 = 15625.0879 / 50.1 = 312

[UAE] [000] RTGFREQ: 312*50.0804 = 15625.0879 / 50.1 = 312

[UAE] [000] 000:000         -- stub -- updatedisplayarea

[UAE] [000] 000:000         -- stub -- updatedisplayarea

[FSE] [AUD] Resume audio (FIXME!)

[FSE] [AUD] Resume audio (FIXME!)

[UAE] [000] 000:000        gfx_set_picasso_state monid=0 on=0

[UAE] [000] 000:000        gfx_set_picasso_state monid=0 on=0

[UAE] [000] 000:000        [DRAWING] init_aspect_maps

[UAE] [000] 000:000        [DRAWING] init_aspect_maps

[UAE] [000] 000:000        [DRAWING] init_row_map (maybe)

[UAE] [000] 000:000        [DRAWING] init_row_map (maybe)

[UAE] [000] 000:000        [DRAWING] init_row_map rowbytes=3008

[UAE] [000] 000:000        [DRAWING] init_row_map rowbytes=3008

[UAE] [000] 000:000        reset_custom_limits

[UAE] [000] 000:000        reset_custom_limits

[UAE] [000] Autoconfig board list:

[UAE] [000] Autoconfig board list:

[UAE] [000] END

[UAE] [000] END

[UAE] [000] 000:000        VM: uae_vm_alloc(4096, 256, 7) mmap failed (2)

[UAE] [000] 000:000        VM: uae_vm_alloc(4096, 256, 7) mmap failed (2)

[1]    25444 segmentation fault  ./fs-uae --stdout

the reason for me to try this version, is because I wanted to use VSCode + the fs-uae fork that allows debugging. If I try to launch the version bundled with the VSCode extension, I get a blank window but the app seems still to react to keypresses, however nothing seems to get drawn. I have to manually kill it.

Both the latest version 4.0.78 or building from sources result in a seg-fault.
Any ideas? The stable version 3.1.66 works just fine.

EDIT: I tried a few earlier version, and *once* I managed to see the interface rendering (version 4.0.15-dev). I wonder if this could be some sort of race-condition between threads that happens on slower CPUs? My Mac has an Intel Core i5-3210M.

EDIT 2: everything works as expected in Monterey. So this seems to be an issue with Ventura only.