Swizzy

It's likely a problem with the game being unable to read a file that iy needs, possibly due to connectX being kinda slow... this results in the console having a fatal crash, your dashlaunch settings are probably setup to shutdown the console in the event of a fatal crash...

Sounds more like a issue with the bootanim.xex plugin if it's only happening when you believe the FSD plugin is loaded first, or are you loading that with Dashlaunch? Aurora loads the FSD Plugin otherwise during startup, it's not a separate entity unless you explicitly did that yourself which is the wrong way of loading it...

You didn't search enough... and no need to be all pissy about not being spoon fed answers

Might be something i implement as a PC tool (similar to my Asset Editor or possibly even as a feature within it) rather then on console, or something that gets implemented as a utility scripts, it's not likely to be added as a specific Aurora feature...

The .assets files contain only the image data, therefor you can't get all of it from there... however... we can probably make exporting features for you that lets you export a Aurora assets to the Asset Importer format/structure

hddalive only stops the drive from turning itself off when not in use, while playing a game or running Aurora the HDD shouldn't really be anywhere near inactive to have this issue (it's done by simply overwriting the file at the specified interval)

Depends on the game, a game with many small files take a long time to rip to XEX and is fast as GOD while a game with few large files may be faster as XEX then GOD

Less files in some cases, some games may or may not work in XEX format due to long filenames/pathnames, but in general all games work as GOD to some degree, installers don't work in either format usually

I believe they were moved with 0.6b tho, to the same location as scripts...

That'd just be a ready-to-go installer made using the installer generator found here: https://sourceforge.net/projects/libusb-win32/ there's nothing special about it other then having the VID/PID setup with a friendly name, i did the same for JR-Programmer The installer created self-signs the drivers during the install which allows them to run on Windows 7+ without having to disable driver signature enforcement

Another possibility that i didn't mention in the PM you sent me is that on USB (external) you use FAT32, while on the internal you use XTAF, they're not the same and may have different path restrictions, i believe the maximum path on XTAF is 240 characters or something around there... that may be why it's not working from internal as XEX, if you use it as GOD it should work tho...

I would suspect your HDD is no good seeing as you're having lag with XBLA games which i assume you're running from the internal HDD?

The only way to solve it is to get a different version of the game... patching the xex is a really bad idea

No idea what happened there, but unlikely to be related, what happens if you remove your internal HDD?

Use quickviews, they should be able to change both the coverflow layout and filters at the same time...

Subtitles, Filters, Sort scripts are all LUA scripts, they're as of 0.6b stored in "aurora:\User\Scripts\"

You can do a NXE install (via the original dashboard, followed by converting to GOD) or through the 0.6b installer utility script that converts it into a GOD container...

You need to make sure you don't have stuff colliding with the trainer such as other trainers (dashlaunch ones, or TU ones)

Probably, once we find the time to fix things

As long as you don't connect to Xbox Live and have atleast Liveblock enabled in dashlaunch, you are safe

Not without using stuff we do not support on this forum

Use Xbox Image Browser, made by the same guy, specifically for extracting ISO's, Xbox Backup Creator is done to rip games using the 0800 firmware and can extract ISO's aswell

Well, the server was going through and upgrade that failed, we had some downtime, and managed to restore most of the functionality, a few configurations were lost and hasn't been put back yet...

They're possible... anything is possible... reading the kinect camera input is possible, and sending it to a server not very difficult... Deleting files from the filsystems, easy... deleting/corrupting the nand? easy... ransomware? unlikely but possible...

No idea, maybe it was just a server glitch and it never got posted?