nr5

This is incredibly embarassing. I have spent _hours_ on the issue. The first thing I had tried was of course re-uploading the entire package, and I did that one more time at some point but evidently I messed that up. Fixing those modules absolutely did the trick, and to really make sure, I just redeployed the whole package. Thank you for your help. I'm so sorry for wasting your time. As a side note, is the source code for Aurora available?

Hey, Sorry for the late response. Unfortunately I didn't get the issue fixed yet. (on the other hand, your DNS hook did get my FSD to stop crashing in the meanwhile, so that's very nice!)

Unfortunately, I already did, and it didn't help. I used the very last revision from the website. I found out Aurora keeps logs file, I'm attaching the ones from my most recent attempt to launch it through DashLaunch. Seems like Aurora is accessing some virtual address out of its domain and the hypervisor is getting angry about it 20221005081914.crash.log 20221005081914.crash.log.callstack debug.log

It's an RGH3 that came with FS3 3.0b Rev775 and Aurora, a local guy did it. It came with DashLaunch 3.18 (as far as I understand it's a thing that patches your NAND to do various things, among which starting a different dashboard by default) but through some reading I determined that it was better to update it to 3.21, which I did. It's running kernel 2.0.17511.0. Now, I also have a couple problems with it. Should I update my kernel? Like, should actually, not just to get the warm and fuzzy feeling of having the last one. While FreeStyle seems to work ok (except for the occasional FSD error), I can't launch Aurora. It gets stuck on the bootscreen when launching it directly from DashLaunch (launch.ini), and it just freezes the console when starting it from XEXmenu and FreeStyle. I tried both whatever version the guy put on my HDD and the lastest version from the website. What do?