-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XML overwrite necessary for Nebulus2_v1.6_1713.lha #125
Comments
@NoobieMaks ~ I'll address this here as it's the best example of things you need hold in consideration, when requesting any changes to the XML file ;)
With this in mind, any slow running emulation you find, will directly relate to the platform you're using...ie; if you state the title runs 'extremely slow' on RPi3, that is very much not the case with most x86-64 platforms (and apple CPU machines or RPi4/5 hardware)....I know, I checked =)
The list of available options is here -> https://github.com/BlitterStudio/amiberry/wiki/Structure-of-the-whdload_db.xml-file As you will note, there is no XML option to control the setting of
The setting of Therefore...as the XML doesn't cater for this setting, and the option itself is not applicable to all amiberry versions, no change of the XML is 'valid' (holistically) for this title --- the preferred route here, is to create an associated config.uae for this title in such a situation. Don't get me wrong here ~ I do appreciate your (and anyone's =) verve to improve amiberry, but to succeed in that endeavor you really do need to be aware/considerate of 'the big picture' --- it is that 'picture' I'm attempting to draw for you here in words, so that your valuable input might be honed to the cutting point of being actionable =) HTH Edit: Turns out that in amiberry
Result: Wrt to amiberry v5.7.3, the On this x86-64 rig, enabling The fact Conclusion: -The XML does not contain a (*)YMMV... dependent on actual hardware being used, and the Amiga machine/software being emulated ;) No change of the XML is warranted ~ this would be more a case of 'low powered platform tuning' when it comes to using that sort of hardware with amiberry v5.x and previous. In this specific case, the effective fix is to create an associated config.uae file for this title, that contains the required setting. We spent a lot time getting this working as expediently as possible, using the Amiberry GUI ...ie; if you load and start an Amiga software title, and then discover you need to change something for that title, hitting F12 -> change something -> Configurations panel -> Save , is all you need to do...the 'Name' and 'Description' fields are automatically filled with the correct values, you CANNOT change the Name field, but you are free to change the Description...Hint: change the name of the Amiga software file first, to how you want the associated config.uae to be Named (and appear in the GUI =) //I might hang out here at Horace's for the afternoon, and triage your other tickets ... |
Thanks @giantclambake - a well thought out and sensible answer. if, in checking through the tickets you find anything requiring a critical change to the script itself, you are always welcome to nudge me on Discord as I haven’t made much time for this recently but would be happy to do so. i think I did look at some new chipset options to be added but didn’t complete them, based on similar conclusions to your comments above |
No worries...
nudge -> fix Apidya
nudge nudge --> BlitterStudio/amiberry#1362
//comment 14
nudge, nudge, wink wink...(a nod's as good as a wink =)
…On Sun, Jun 23, 2024 at 9:02 PM Horace And The Spider < ***@***.***> wrote:
Thanks @giantclambake <https://github.com/giantclambake> - a well thought
out and sensible answer.
if, in checking through the tickets you find anything requiring a critical
change to the script itself, you are always welcome to nudge me on Discord
as I haven’t made much time for this recently but would be happy to do so.
i think I did look at some new chipset options to be added but didn’t
complete them, based on similar conclusions to your comments above
—
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR6M36M3X6HEY6QMUMTJTNTZI2TOHAVCNFSM6AAAAABFUVLOEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUHE2DINBSGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No doors are visible! So it's not playable.
To solve this only one change is to do:
ONLY this one Cycle Exact Mode!
If (Full) is also enabled my Pi3/ the game is extremly slow.
But the (DMA/Memory) alone already solves the door showing problem.
Tested with:
The text was updated successfully, but these errors were encountered: