did you created a issue on Hekate's repo?hmm, blue screen when boot to "semi-stock" from Launch on Hekate6.1.1. HOS18.0, reboot to OFW still ok though
NVM, forgot to put atm1.7.0 pre-release into sd card at the same time.
did you created a issue on Hekate's repo?hmm, blue screen when boot to "semi-stock" from Launch on Hekate6.1.1. HOS18.0, reboot to OFW still ok though
NVM, forgot to put atm1.7.0 pre-release into sd card at the same time.
nah, someone else did but figured same mistakedid you created a issue on Hekate's repo?
[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100
[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_payload.bmp
[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0
CTCaer nor GBATemp Condone nor give support on piracy, sorry, there is no so much help we can give you. There IS NO SETTING OR WAY to lower the FW needed by a game because the game itself was build using the libraries and code of the SDK it needs. period.@CTCaer I changed from "payload=bootloader/payloads/fusee.bin" to "fss0=atmosphere/package3" with latest hekate sigpatches from @impeeza post and even his hekate_ipl.ini but now games that are above my FW don't run while using payload fusee even when I was on FW15.0.0 I could play most FW17 required recent games.
Currently I'm on Atmosphere 1.6.2, Emunand exFat as SD files and FW 16.1.0.
I even tried a clean atmosphere 1.6.2 + latest hekate + impeeza latest hekate sigfiles and his config with 0 content added and same exact result.
Is there a setting in hekate to make games to play on a lower FW than required or some kind of atmosphere setting that I have to force for hekate to load that you could be overriding it's default behaviour?
while using Hekate Fusee payload I don't have to do anyrthing not even use sys-patch, nothing, games equiring FW17+ just install fine with tinfoil and run fine without modding or changing anything.
ps: I also don't want to use sys-patch... And also I removed the game tickets and deleted them and reinstalled with hekate sigpatches with fss0 but same exact result as soon as I put something requiring FW17 it throws a error to go back to home and then shows as corrupt and just putting the fusee payload back the game verifies OK and plays fine...
My hekate_ipl settings:
Code:[config] autoboot=0 autoboot_list=0 bootwait=0 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp
And I'm using atmosphere exosphere.ini:
Code:[exosphere] debugmode=1 debugmode_user=0 disable_user_exception_handlers=0 enable_user_pmu_access=0 blank_prodinfo_sysmmc=0 blank_prodinfo_emummc=1 allow_writing_to_cal_sysmmc=0 log_port=0 log_baud_rate=115200 log_inverted=0
I'm not directly talking about piracy but rather playing a game on lower FW than I have and always work fine with atmosphere fusee payload so it definitely is something that Hekate is overriding to atmosphere settings since it uses its own settings...CTCaer nor GBATemp Condone nor give support on piracy, sorry, there is no so much help we can give you. There IS NO SETTING OR WAY to lower the FW needed by a game because the game itself was build using the libraries and code of the SDK it needs. period.
you can upgrade your setup to FW 17.0.1 without problem, that FW has been full tested with all homebrew an any trouble has been corrected time ago.
I used the latest @impeeza posted Hekate signatures and checked the patches.ini and atmosphere 1.6.2, my FW 16.1.0 both fat and exFat are there and any newer FW was there both Fat and exFat.Probably missing a signature patch needed.
You could just stay on FW17+ and the previous builds of Atmosphere.
Yeah DBI will help, but you must also to check you have Atmosphère's debug enabled:
No idea why you want them, the loader.kip is not finalized yet and I'm using versions above the OC suite since that's outdated, his latest stuff is more private on discord probably because of the persion with a "LION" avatarCan you post your exosphere.ini and your loader.kip?
[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0
Nop, I tried even on a full clean atmosphere 1.6.2 with latest Hekate + latest Hekate sigpatches with 0 content added, not a single thing on contents folder, nothing and games above my FW still would throw a error when using Hekate fss0 boot method and just going back to fusee payload method every 17+fw required game works fine on my FW 16.1.0...I think that your "issue" is related to the loader.kip or maybe the atmosohere that are you loading...
Hell no, I'm not updating atmosphere either, 1.6.2 will be my atmosphere for quite some time cause it's either going to FSS0 boot method on Hekate and having to update FW breaking stuff everytime a new game needs a new FW or having to trust someone to mod the fusee payload which not being official anymore it's likely to not be as stable as when SciresM officially had the feature that we could load sigpatches.Have you tested the 1.7.0 pre release?
If it doesn't work, thats some ips in your patches (as AMS has parsing patches disabled).
If it works, it's a Hekate "issue"