QUOTE(tk_saturn @ Mar 19 2011, 08:31 PM)

You need the Nxemini option set to true to use dashlaunch via the miniguide, the installer does ask you this.
My Ini:
[code][QuickLaunchButtons]
BUT_X = Hdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_A = Hdd:\FSD2-1044a\default.xex
BUT_B = Hdd:\Freestyle\FreestyleDash.xex
BUT_Y = Hdd:\FSD2\default.xex
LBump = Usb:\Applications\xellLaunchHDMI\default.xex
Default = Hdd:\FSD2\default.xex
[Settings]
nxemini = true
pingpatch = true
contpatch = false
fatalfreeze = false
fatalreboot = true
regionspoof = true
dvdexitdash = true
noupdater = true
I have mine set to auto signin, and haven't encountered any issues with 2.11 or any previous versions.
That's wierd because Dashlaunch via the Miniguide does work for me even though I haven't got the nxemini = true setting. In fact I just checked the info_launch.ini that comes with Dashlaunch and it says it defaults to True. I don't recall Dashlaunch install asking me about it either, only whether I wanted to update my launch.ini, which I always say Yes to.
However, it was useful seeing your launch.ini as it made me realise I don't even have a button assigned to FSD2, I've just set it as Default. Then again, it says in the info_launch.ini that it should use the Default when no buttons are pressed. I think it does sometimes, but I've found it doesn't work when I'm in NXE, which is a pain.
I also have never had any troubles with boot/signin before 2.11, so I thought a bug might have crept in there. I did update my flash recently to use thermal settings for the fan, rather than setting it to 70% in FSD2, but I wouldn't have thought that would cause any problems.
This post has been edited by doveman007: Mar 21 2011, 01:18 PM