Swizzy

Check in NXE if it installed the TU properly and that the download was done correctly... if it doesn't show up there and you know it's not a cache type TU it means Aurora deletes it because you've instructed Aurora to disable the TU, if it shows up with a exclamation mark as icon, it means the data is corrupt

It is, but, a user room is user controlled... they decide what rules apply to that room, they decide who are welcome and who are not...

Aurora doesn't ship with a custom HUD skin and it uses the FSD Plugin...

It's because they didn't want you there for whatever reason... do you think we just allow people to get kicked and instantly rejoin? that makes it pretty redundant to allow kicking...

That means you are loading the plugin with FSD and not Aurora, that's what causes it to launch FSD instead of Aurora

Did you try the 68nF cap i mentioned? I'll see if i can find the install pics i made in the past, i can tell you i used AWG32 for all connections except for VCC/GND which i used AWG28 (old IDE/ATA cables) for...

That means you need to look in the event log for windows... filter on .NET errors and search for last error that mentions the app

Well, i'm the rude one i'm more used to people wanting to sell me xboxes etc. Or having me fix and sending back... since i don't live nearby and shipping being generally expensive to send a xbox to sweden i'm curious as to why, obviously if you simply want to know what you did wrong (if there is something you can do differently in the future to prevent the issue) you can just send me pics of your install, or remind me to send you pics of mine... I just don't want ppl to send me consoles expecting something in return, besides what i already give everyone for free (or a possible answer to a tricky question etc. Even if i've thus far not encountered a jasper, falcon, trinity or corona that i failed to hack one way or another i can never give a 100% guarantee i can fix every issue, not to mention the fact that i don't have a heap of spare time to offer these days for hardware fixes etc.)

What's the catch?

The issue was that the plugin was loaded by fsd, and yes you can change it, there are custom hud skins for that...

I live in sweden, shipping here tends to cost a fortune

Make sure you are using the same emulator as they did in that video, possibly check your roms aswell...

It means you need to build a new nand that have the nofcrt patch enabled, or disabled if it was enabled...

Jasper isn't "unglitchable", infact... RGH 1.0 is super stable on Jasper if you install it the correct way, i used a 68nF cap between GND and CPU_PLL_BYPASS and had boot times that were faster then retail quite frequently on Jasper

Sounds to me like you may have the unofficial Dashlaunch installed on your system... but as Gavin said, update kernel etc. to the latest version and these issues should go away

Server upgrade that forced a update to everything making the old skin become incompatible

Press RB or LB and you'll bring up "Quick Views" which allow you to quickly switch between filters, otherwise you can press B to bring up the view settings menu where you can manually set the filters to use (here you can also edit/add Quick Views)

I don't remember what caused that issue, but, i remember it being mentioned before... Regarding XeLL not finding it - you need it in the root of your usb drive named "xenon.elf"

Same as all other DLC, you find it on google and just transfer to your console followed by making sure they're unlocked (xm360 on console)

Whatever works best for you It's a pretty simple/basic file to edit...

You need to download and install the compatibility pack(s)

also, one thread is enough, no need to make 2!

Run Dashlaunch Installer, it'll tell you on the bottom right if it's a Corona or Trinity, you can also use Simple 360 NAND Flasher, if it talks about MMC you have a corona, otherwise you have a Trinity... likewise, XeLL will also talk about MMC and say that it skips updflash.bin

It's being fixed, caused by a recent server issue...

I would appreciate if you could mention the exception messages you had, otherwise i can't fix it in the official build in case we add more information to it...