Post a new comment to participate in the discussion on how this
game should be configured, or to add relevant information regarding
the use of these configurations.
Posted by
TCD at
2013-03-12 08:13:23 (Updated 2013-03-12 08:13:36):
It seems that you can't set it this way right now. Once "kickstart = 3.0+" is set A1200 is automatically chosen. Very rare case this one... Will talk about it with Frode later. For now please let them stay like they are
You can download SetPatch from http://os.amigaworld.de/index.php?lang=de&page=37 for free, so it should be no problem to use this in FS-UAE. An idea could be it to implement in all WHDLoad games by default, but I don't know how it interact with lower Kickstart version than 3.1
TODO: Hi @thevoice As I spoke with Frode about the guidelines for graphics in the database I understand now the rules. So if a game have a specific resolution, we only crop black borders but not force resize images to 640x400. So the game have a specific resolution of 646x552. I've checked that there are no borders up and bottom, but right or left I have no idea. So @Frode, can you check this out?
As I spoke with Frode about the guidelines for graphics in the database I understand now the rules. So if a game have a specific resolution, we only crop black borders but not force resize images to 640x400. So the game have a specific resolution of 646
OK, then my best guess is that running SetPatch is needed to get the system set up correctly before WHDLoad starts (or something else is needed in startup-sequence). The SetPatch is not automatically included because I assume it is not freely distributable. It is possible to require that the user must provide this, if that's the conclusion.
i think its not 17.1 related issue as i use 17.1.5206 on my hdd setup also. i also can confirm the slave works on a real a1200 2/4mb ram. so i also suspect the problem in the way you create the "virtual" hdd to launch the slave.
Weird.. this WHDLoad issue should be investigated further. Possible reasons include: SetPatch is not run in the launcher startup sequence, and perhaps this affects something. Alternatively, perhaps a problem with the 17.1 WHDLoad release.
Regarding screenshots: FS-UAE saves two screenshots - one which matches the crop rectangle you see on screen, and one which is uncropped. If the cropped one is perfect, then you upload that, if not, you must manually crop either the "cropped" or "uncropped" version. Alternatively, borrow screenshots from another source -but the guidelines must still be followed of course.
i stumbled over the silly memory issue on the aga whdload slave also. but it seems to be launcher related. i tried out the aga slave under my fs-uae hdd setup 2mbchip/8mb fast and it starts like expected. even 2mb/4mb worked.
i think i do something wrong with screen capturing xD. if i have fs-uae in default resolution screens come out 640x512 cropped. if i change the resolution to 640x400 in deluxe galaga for example the screen get zoomed so much that your spaceship is out of the screen .
Moved chip_memory = 2048 to the "WHDLoad, v1.1" entry. Another issue: "WHDLoad, v1.1, AGA" seems to complain about memory problems with "sane" combinations. It seems to require > 2MB chip memory.. (?), and also a lot of fast memory, so fast_memory = 16384 is used to force 32-bit fast memory, so 4 MB chip memory can be specified.
It is possible already! Set chip_memory = 2048 for the WHDLoad variants if the WHDLoad version otherwise works fine with A600. Alternatively, set amiga_model = A1200 if there are other problem with A600. Just test first by manually changing config in FS-UAE Launcher.
The A600 model has 1 MB chip memory. Documentation for the slave says: required Chip Memory 1024 KiB ($100000). One possibility is that the slave requires 1024 KB free chip memory, and that this is not possible with only 1024 KB to begin with (?)
puzzle time. the ecs version moans about to low memory for preload. amiga model is set to amiga 600 with 8mb fastram. so i guess we need more then 1mb chip for this slave. does the amiga 600 preset have 1mb chip at all or just 512kb ?
It seems that you can't set it this way right now. Once "kickstart = 3.0+" is set A1200 is automatically chosen. Very rare case this one... Will talk about it with Frode later. For now please let them stay like they are
it seems all the v2.6c variants want kickstart 3.0 but ecs chipset. so is it ok to set them like that ?
screenshoots replaced with proper ones
You can download SetPatch from http://os.amigaworld.de/index.php?lang=de&page=37 for free, so it should be no problem to use this in FS-UAE. An idea could be it to implement in all WHDLoad games by default, but I don't know how it interact with lower Kickstart version than 3.1
Yes, that is no problem (and then run it from Startup-Sequence), just a bit shame (less user-friendly) if it can't be solved automatically.
so can we bypass legal reasons by having setpatch installed by the user in /FS-UAE/WHDload/C/ ?
Testing indicates that running SetPatch is necessary -and specifically that the "Memory Pools" patch is needed :-/
TODO: Hi @thevoice As I spoke with Frode about the guidelines for graphics in the database I understand now the rules. So if a game have a specific resolution, we only crop black borders but not force resize images to 640x400. So the game have a specific resolution of 646x552. I've checked that there are no borders up and bottom, but right or left I have no idea. So @Frode, can you check this out?
(in my last post the half post was cutted >:0( )
Hi @thevoice
As I spoke with Frode about the guidelines for graphics in the database I understand now the rules. So if a game have a specific resolution, we only crop black borders but not force resize images to 640x400. So the game have a specific resolution of 646
TODO: Identify what's needed to get the AGA WHDLoad slave to run without weird memory setup when started by the Launcher.
OK, then my best guess is that running SetPatch is needed to get the system set up correctly before WHDLoad starts (or something else is needed in startup-sequence). The SetPatch is not automatically included because I assume it is not freely distributable. It is possible to require that the user must provide this, if that's the conclusion.
i think its not 17.1 related issue as i use 17.1.5206 on my hdd setup also. i also can confirm the slave works on a real a1200 2/4mb ram. so i also suspect the problem in the way you create the "virtual" hdd to launch the slave.
Weird.. this WHDLoad issue should be investigated further. Possible reasons include: SetPatch is not run in the launcher startup sequence, and perhaps this affects something. Alternatively, perhaps a problem with the 17.1 WHDLoad release.
Regarding screenshots: FS-UAE saves two screenshots - one which matches the crop rectangle you see on screen, and one which is uncropped. If the cropped one is perfect, then you upload that, if not, you must manually crop either the "cropped" or "uncropped" version. Alternatively, borrow screenshots from another source -but the guidelines must still be followed of course.
i stumbled over the silly memory issue on the aga whdload slave also. but it seems to be launcher related. i tried out the aga slave under my fs-uae hdd setup 2mbchip/8mb fast and it starts like expected. even 2mb/4mb worked.
i think i do something wrong with screen capturing xD. if i have fs-uae in default resolution screens come out 640x512 cropped. if i change the resolution to 640x400 in deluxe galaga for example the screen get zoomed so much that your spaceship is out of the screen
.
Guidelines for screenshots and covers here: http://fengestad.no/fs-uae/database-images
@thevoice: Please upload screenshots in size of 320x200 or 640x400. Also don't upload screenshots with watermark. Your last one had watermarks of HOL.
Moved chip_memory = 2048 to the "WHDLoad, v1.1" entry. Another issue: "WHDLoad, v1.1, AGA" seems to complain about memory problems with "sane" combinations. It seems to require > 2MB chip memory.. (?), and also a lot of fast memory, so fast_memory = 16384 is used to force 32-bit fast memory, so 4 MB chip memory can be specified.
ok checked chip_memory=2048 local and it works. so i changed it here aswell
It is possible already! Set chip_memory = 2048 for the WHDLoad variants if the WHDLoad version otherwise works fine with A600. Alternatively, set amiga_model = A1200 if there are other problem with A600. Just test first by manually changing config in FS-UAE Launcher.
looks like it. so we kinda need a possibility to give a600 2mb chipmem too and chenge that when its up and running
The A600 model has 1 MB chip memory. Documentation for the slave says: required Chip Memory 1024 KiB ($100000). One possibility is that the slave requires 1024 KB free chip memory, and that this is not possible with only 1024 KB to begin with (?)
puzzle time. the ecs version moans about to low memory for preload. amiga model is set to amiga 600 with 8mb fastram. so i guess we need more then 1mb chip for this slave. does the amiga 600 preset have 1mb chip at all or just 512kb ?