Danke habe gefunden
Beiträge von cardo
-
-
Ist ja einmal ein Ps4 spiel und das andere Ps5. Das ja voll doof.
-
Cloud zeigt er Ps4 Version nicht an sondern legt neu an beim Syncro
-
Gibt es eine Möglichkeit meinen Spielstand von der Ps4 Version irgendwie zu übernehmen?
-
Das solltest du besser über die CFW im sysNand machen, um einem Brick vorzubeugen! Dafür ist die Zeile "emummcforce=1" aus der "hekate_ipl.ini" zu löschen und dann der emuMMC unter Hekate zu deaktivieren. Zudem sind die FW Daten der Version 17.0.0 aus dem Link im Daybreak Thema erforderlich.
Hm. Ist es vielleicht besser noch zu warten bis der Fehler mit dem Brick behoben wurde. Muss im Moment nicht die OFW auf 17 updaten?
-
-
-
Ja, das kannst du. Allerdings stehen die FW Daten der Version 17.0.0 über den Firmware Downloader noch nicht zur Verfügung. Dieser lädt aktuell noch die FW 16.1.0 auf die SD-Karte herunter und das wird auch weiterhin so bleiben, solange noch keine Sigpatches für die FW 17.0.0 verfügbar sind.
Ok. Ich muss ja die Firmware nicht updaten.
-
Atmosphere auf aktuellsten 1.6.0 Build 3a8cffef5 aktualisiert.
Wie immer, ist dieser Build nur über das Online Update gemäß Spoiler Nr. 7 zu beziehen!
Changelog:
ncm: better detect + fix 17 brick after-the-fact
Datum der package3 Erstellung: 16.10.2023 13:05 Uhr mit eingebettetem amsPLUS-M Bootlogo.
Danke. Kann ich jetzt einfach die cfw updaten, ich bin in der ofw auch noch nicht auf 17. Games laufen in der cfw trotzdem weiter? Wollte die ofw später mal updaten.
-
Wo finde ich die Screenshots bzw wie kann ich sie mir anschauen? Wenn ich Album öffne lande ich ja im Homebrew.
-
-
-
Berichte mal ob es geklappt hat.
Ja es funktioniert
-
ok dank, wo kopiere ich die erstellen emuiibos hin?
-
emuiibo wurde auf Version 1.0.0 aktualisiert!
Changelog:
- This update's major milestone (among others) is to finally intercept nfp:sys service, AKA intercepting system settings/applet amiibo support - hence, many changes here are because of this
- emuiibo is no longer a pre-release, by the way
NOTE: don't forget to update to the latest nx-ovlloader/Tesla menu!
- The virtual amiibo format went through some major changes system-settings support required:
- Now area information is saved in
<amiibo>/areas.json
, which stores pairs ofaccess_id
andprogram_id
values. System settings support also requires knowing the program ID of the title using the area, which is why now area information is saved here - This JSON also contains a
current_area_access_id
field: system settings's option to delete an amiibo's save data conflicts with emuiibo's implementation of saving (real amiibos have a single game save data while emuiibo allows multiple), so this field contains the currently "selected" area, which consists on the area system settings will see and show info of/delete - In order to convert old formats to this new changes, the
areas.json
file will be created automatically, but since there is no way for emuiibo to tell the program ID of plain amiibo areas, it will set a certain ID by default (to be distinguishable from the rest, I opted for "Retain Interactive Display Menu"'s one, which is a debug program), and for the correct ID to be set on the area info, the user must use the amiibo with the game in question. I know this can be a bit tedious, but it's the best way to handle it - Now virtual amiibos with names longer than 10 characters are ignored and considered as invalid. Due to certain technical reasons (and Nintendo being too inconsistent with its formats) I originally thought the limit was at 40, but in certain contexts (like system settings) where the 10-char limit is imposed, existing virtual amiibos with longer names tend to cause weird/unexpected behavior
- The system settings formatting option will remove all virtual amiibo areas (won't unregister it like with real amiibos since virtual amiibos have no concept of being (un)registered)
- The system-settings game-save-deleting option will remove the selected amiibo area, which can be changed from the overlay. This selected area will also be the one system-settings always shows
- Now the random-UUID option has its own field in the
amiibo.json
file (use_random_uuid
), so that amiibos will have their own UUID which won't be cleared when random-UUID wants to be enabled (see related overlay changes)
- Now area information is saved in
- Old formats supported in older emuiibo versions (raw bin dumps and older virtual amiibos) are fully supported now! Backwards-compatibility has been reimplemented so that these outdated formats are automatically converted to the modern format on boot (for bin dumps, the dump binary file gets moved but not deleted)
- Criptography is now supported, so that if
/switch/key_retail.bin
is present, the encrypted sections of bin dumps will be accessible by emuiibo, so that the resulting converted amiibos will contain all the amiibo data present there (this includes game app-data areas, AKA amiibo game save-data)
- Criptography is now supported, so that if
emuiibo
- Compiled with latest libraries
- All the format changes above resulted in code changes to support it, of course
- The
emuiibo
IPC service (used by the overlay and other homebrew to control emuiibo) has some new commands reflecting the format changes. As always, the overlay is the best example of a homebrew using this service to control amiibo emulation - Some amiibo ID internal bugs were fixed (again, huge shoutout to Nintendo for being unnecessarily and heavily inconsistent with their amiibo formats across platforms), which would've previously caused some isssues with certain games (like Monster Hunter Rise, Splatoon, etc.)
overlay
- Compiled with latest libtesla/libnx
- A long-standing libtesla UI cleanup bug was fixed which may have caused crashes sometimes
- The UI was extended (following the new format changes) to show/toggle the currently selected area of the active virtual amiibo, as well as to toggle amiibos' random UUID option
- Listed amiibo/plain directory entries are now alphabetically ordered
- If the title is installed, it's name will be shown; otherwise, it's plain program ID will be shown
- emuiibo's version is now checked, so that an overlay will refuse to work with older/newer emuiibo versions and thus only work with the exact same version
- French language support was added
emutool
- .NET framework version was lowered to v4.5.2, hoping this may increase compatibility with certain systems
- Amiibos whose default name contains "/" are replaced with "_", and special characters are also replaced with their ASCII equivalents (like E from È) to avoid issues with system paths on virtual amiibo creation
Hi gibt es eine gute verständliche Anleitung wie ich das installiere und nutzen kann? Also wo welche Dateien hin gehören.
Danke
-
-
-
-
-