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.
Technically it's not really required but it's handy to have. When each player takes their turn they are able to hit space to show the inventory. That's why it's the same key on both joystick. In the simultaneous 2 player sections neither player can access their inventory anyway.
On a side note this is one of the great hidden gems of the Amiga. An amazing game to play on a 4 player. Would be a great game to play over the internet as it is turn based with the exception of when 2 players choose to engage in combat with one another.
Posted by
FrodeSolheim at
2013-10-17 20:04:50 (Updated 2013-10-17 20:04:59):
@thundercato does both ports use the same "secondary action" (space) on purpose? I'll admit I haven't played this game
In some cases, game data may not be written to disk by the slave until it is quit with the quit key... I don't know of any specific example of this, but that would be a reason to use the quit key.... Anyway, using A1200 as default for WHDLoad games is planned.
Maybe not I suppose. It may be just a since my Amiga days, I've always closed WHD games before switching off the machine. I guess with PRELOAD set, there's no concerns with 'disk' access.
At a push, hitting F10 to quit is one less press than a combination to quit the emulator, or reaching out for the mouse. The only other slight improvement would be loading, the A1200 gets to the next screen/scene almost instantaneously, with the A600 having a pause, but nothing that causes too much grief since WHD is a MASSIVE improvement regardless.
Is there a specific reason that the quitkey (rather than closing the emulator) is needed for Moonstone? Not that it doesn't make sense to set the model to A1200, just wondering why the quitkey is needed when started from the launcher.
WHDLoad is the only version really worth playing in this game. My friends and I have played this for well over 100 hours over the years and the non-WHDLoad versions are very buggy and crash a lot! We never actually managed to complete the game until we used the WHDLoad version which fixes most if not all of the bugs and crashes.
the quitkey we are talking about is the one chosen by the creator of the slave which works fine when you use a1200 as machine but not if you chose an 68000 cpu config
You can WHDLoad arguments with "whdload_args" overwrite / set. Put simply there "quitkey=xxx" to specify a key of your choice. xxx stands for the ASCII code, which you have you looking for that key.
Some games are key to define which are only available on Amiga keyboards. That is why it will not work.
if you start the slave in fs-uae running a workbench the slave popup gives 2 checkboxes buttonwait and custom1 to select. running the slave from fs-uae dont show these 2 checkboxes in the slave popup.
i read up a bit about quitkey. it seems some slaves have nonworking quitkeys with 68000 cpu. even some readmes refer to fixed quitkeys for 68k. so it seems its slave related and we can't do anything against it.
well we ar elucky and have the buildin f12 quitkey anyway .
Seems like another case where the WHDLoad install does not work 100% with A600. The quit key (F10) seems to work when Amiga model is changed to Amiga 1200. Didn't understand what you mean by "buttonwait > custom1".
Technically it's not really required but it's handy to have. When each player takes their turn they are able to hit space to show the inventory. That's why it's the same key on both joystick. In the simultaneous 2 player sections neither player can access their inventory anyway.
On a side note this is one of the great hidden gems of the Amiga. An amazing game to play on a 4 player. Would be a great game to play over the internet as it is turn based with the exception of when 2 players choose to engage in combat with one another.
@thundercato does both ports use the same "secondary action" (space) on purpose? I'll admit I haven't played this game
A1200 is certainly nicer for the loading times and performance, I was just wondering about the quitkey specifically for this game
In some cases, game data may not be written to disk by the slave until it is quit with the quit key... I don't know of any specific example of this, but that would be a reason to use the quit key.... Anyway, using A1200 as default for WHDLoad games is planned.
Maybe not I suppose. It may be just a since my Amiga days, I've always closed WHD games before switching off the machine. I guess with PRELOAD set, there's no concerns with 'disk' access.
At a push, hitting F10 to quit is one less press than a combination to quit the emulator, or reaching out for the mouse. The only other slight improvement would be loading, the A1200 gets to the next screen/scene almost instantaneously, with the A600 having a pause, but nothing that causes too much grief since WHD is a MASSIVE improvement regardless.
Is there a specific reason that the quitkey (rather than closing the emulator) is needed for Moonstone? Not that it doesn't make sense to set the model to A1200, just wondering why the quitkey is needed when started from the launcher.
TODO: Can we amend the default machine to A1200 so the default quit key works?
WHDLoad is the only version really worth playing in this game. My friends and I have played this for well over 100 hours over the years and the non-WHDLoad versions are very buggy and crash a lot! We never actually managed to complete the game until we used the WHDLoad version which fixes most if not all of the bugs and crashes.
the quitkey we are talking about is the one chosen by the creator of the slave which works fine when you use a1200 as machine but not if you chose an 68000 cpu config
You can WHDLoad arguments with "whdload_args" overwrite / set. Put simply there "quitkey=xxx" to specify a key of your choice. xxx stands for the ASCII code, which you have you looking for that key.
Some games are key to define which are only available on Amiga keyboards. That is why it will not work.
if you start the slave in fs-uae running a workbench the slave popup gives 2 checkboxes buttonwait and custom1 to select. running the slave from fs-uae dont show these 2 checkboxes in the slave popup. i read up a bit about quitkey. it seems some slaves have nonworking quitkeys with 68000 cpu. even some readmes refer to fixed quitkeys for 68k. so it seems its slave related and we can't do anything against it. well we ar elucky and have the buildin f12 quitkey anyway
.
Seems like another case where the WHDLoad install does not work 100% with A600. The quit key (F10) seems to work when Amiga model is changed to Amiga 1200. Didn't understand what you mean by "buttonwait > custom1".
slaves quitkey doesnt work. also the slave should show buttonwait & custom1 while loading. neither is shown at all