FS-UAE 1.3 Development Series

[FrodeSolheim]

Originally Posted by AmigaOnline

Same problem with the two computers (i've uninstalled Python)
Error: "The Application has failed to start because incorrect configuration. Reinstalling the application may fix it"

Have you tried installing the vcredist I linked to? If it does not help, I will try on a clean installation of Windows; will probably be able to reproduce it.

But the keyboard problem is more of a mystery.. -Same problem on the third computer also? Does it work properly when FS-UAE is launched without the launcher?

[AmigaOnline]

Originally Posted by FrodeSolheim

Have you tried installing the vcredist I linked to? If it does not help, I will try on a clean installation of Windows; will probably be able to reproduce it.

Don't worry, issue fixed by installing vcredist

Originally Posted by FrodeSolheim

But the keyboard problem is more of a mystery.. -Same problem on the third computer also? Does it work properly when FS-UAE is launched without the launcher?

FS-UAE works like a charm without the launcher.
It's not only a keyboard problem, but the emulator is somewhat unusable when started using the launcher (window only/not resizable/no menu...).
Will try with the third computer asap

[AmigaOnline]

Originally Posted by FrodeSolheim

-Same problem on the third computer also?

Same problems (i didn't expect something else in fact )

I've fixed the vcredist issue with the third computer

[FrodeSolheim]

Originally Posted by AmigaOnline

Same problems (i didn't expect something else in fact )

I got it reproduced in a virtual machine, thanks for testing

[AmigaOnline]

Originally Posted by FrodeSolheim

I got it reproduced in a virtual machine, thanks for testing

I just suppose that this could be useful for all Windows XP users
Finally, i have a good GPU

[AmigaOnline]

Hi!

Another suggestion: a dedicated config file for this launcher with:

-the default pathes (floppy disks, kickstarts...)
-additional default options

Thx

[FrodeSolheim]

Originally Posted by AmigaOnline

@Frode:
-When a game has been started, it's not currently possible to switch to full screen (alt+tab) or to access the usual FS-UAE menu. Is it a normal behavior? The keyboard doesn't seem to work either (emulated joystick).

The problem disappeared when not initializing pygame in the launcher, so some conflict there. Removed it, which unfortunately also removes the joystick functionality from the launcher for now..

Originally Posted by AmigaOnline

Hi! Another suggestion: a dedicated config file for this launcher with:
-the default pathes (floppy disks, kickstarts...)
-additional default options

Yes, there will certainly be a dedicated config file for the launcher, which will also be more "hidden away", since you will alter the settings in the GUI instead.

[AmigaOnline]

Originally Posted by FrodeSolheim

The problem disappeared when not initializing pygame in the launcher, so some conflict there. Removed it, which unfortunately also removes the joystick functionality from the launcher for now..

Thanks for all your efforts anyhow

[Speedvicio]

Hello Frode
The selection of the theme is restricted only to a sub folder of fs-uae?

[FrodeSolheim]

Originally Posted by Speedvicio

Hello Frode
The selection of the theme is restricted only to a sub folder of fs-uae?

Themes (theme folders) are located in either:
- share/fs-uae/
- (My) Documents/FS-UAE/Themes/

Perhaps I should move the bundled themes into share/fs-uae/themes/, so it will be easier to iterate over / find available themes.

[Speedvicio]

Originally Posted by FrodeSolheim

Themes (theme folders) are located in either:
- share/fs-uae/
- (My) Documents/FS-UAE/Themes/

Perhaps I should move the bundled themes into share/fs-uae/themes/, so it will be easier to iterate over / find available themes.

It might be a good idea to choose the themes from any folder, just specifying the path.

[FrodeSolheim]

Originally Posted by Speedvicio

It might be a good idea to choose the themes from any folder, just specifying the path.

I can make it possible to specify a full path for "theme" in the next version, it is trivial and quick to add!

[FrodeSolheim]

Version 1.3.10:

• Properly close hdf file stream in hdf_close_target function.
• Compile with _FILE_OFFSET_64_BIT defined.
• Use 64-bit ftell/fseek functions for hdf support where available.
• Call fflush(NULL) to flush other remaining file streams on exit, if any.
• Less video latency in full sync mode, but also requires a more powerful computer for smooth scrolling. Use new boolean option low_latency_vsync to enable.
• Can alternatively specify path to theme folder with theme option.
• Warn when using deprecated SUPER model. Use A4000/040 instead.
• Use simplified framewait function in custom.cpp.
• Merged WinUAE 2.4.2beta2 + compatibility patch.
• Fixed a RTG screen mode change crash (pointer to resized buffer not set correctly).
• Disabled OpenGL debug checking, which was accidentally enabled in the latest development releases.
• fs-uae can be started with –list-joysticks to just print names of connected joysticks to stdout and then exit.
• (Launcher) Automatically set amiga joystick port mode when selecting host device.
• (Launcher) Clear (rest of) floppy image list when multi-selecting floppies.
• (Launcher) Automatically select first joystick for input port 1 if a joystick is connected.
• (Launcher) Add window/fullscreen mode selector.
• (Launcher) Replaced some text buttons with bitmap buttons.
• (Launcher) Detect connected joysticks by running fs-uae –list-joysticks.
• (Launcher) Removed joystick configuration from launcher (for now) due to a pygame / wxpython conflict.

http://fengestad.no/wp/fs-uae/download-beta

[FrodeSolheim]

Originally Posted by AmigaOnline

It's not only a keyboard problem, but the emulator is somewhat unusable when started using the launcher (window only/not resizable/no menu...).

Now, joystick information is retrieved by executing fs-uae --list-joysticks instead of using pygame, so this problem should not be present anymore. Joystick configuration tool is removed for now.

Originally Posted by Speedvicio

It might be a good idea to choose the themes from any folder, just specifying the path.

Implemented in 1.3.10, just use the same "theme" option by specifying the path to the theme folder.

[Philantrop]

Frode, looks like you forgot to upload the source tarball. :-)

[FrodeSolheim]

Originally Posted by Philantrop

Frode, looks like you forgot to upload the source tarball. :-)

Yes I did -it's uploaded now

[Foul]

yeah ! no more reason to use WinUAE for me now

[AmigaOnline]

Originally Posted by FrodeSolheim

Now, joystick information is retrieved by executing fs-uae --list-joysticks instead of using pygame, so this problem should not be present anymore. Joystick configuration tool is removed for now.

Good Will try this (working) launcher asap
About the launcher: All new features/options/buttons are welcomed

[AmigaOnline]

@Frode:

Launcher: a way to start a game without an official kickstart file would be nice (AROS). Of course it's currently experimental but this should be appreciated by some new users

[FrodeSolheim]

Originally Posted by AmigaOnline

Launcher: a way to start a game without an official kickstart file would be nice (AROS). Of course it's currently experimental but this should be appreciated by some new users

Yes, and in the same vein, I was also thinking about bundling a small and freely distributable game or two (compatible with the AROS kickstart) with for instance the Windows installer so new users can just install and try it out. I like the shareware game "Cybernetix", for instance -But in any case, AROS kickstart (and custom kickstart for that matter) will be an option.