Flaminek

been away for 3 months and only just updated to F3 v483 from F3 first release. Ran the Link test and failed some aspects of it. However Link still worked. Was loving it when I ran Blops2 and selected system link to be met by a load of peeps also on Link and could hear some chatting.Wow awesome work guys. Wish more people would go on Blur racing though haha.

i got a jasper jtag and if i turn my fan setting to auto in fsd3 settings it tends to stay around 60c fpr gpu/cpu. this is what the machine would do as default if on retail out of the box.i generally have fans set to 65 or 70 and it cools me down to 45c for cpu/gpu.i'd imagine this would eliminate any possiblity of RRoD. 60c i think is pretty much default for all machines including pc/laptops/

so excited about this development,can't wait for release.

yep just ftp the default.xex inside the installer folder and boot it to update. i thought jtag/rgh was security free more or less.so was it some new code embedded in the game that originally stopped this playing with (the first game to ever do that) dashlaunch3.03?would love to know how this worked. cheers to coz

yeah baby can't wait.

just updated to kernel 16197 on my jasper jtag all good.fsd3 still running smooth.the download latest dashlaunch option in fsd3 installer is wicked.

; when set to false, ejecting a dvd video or game returns you to your default item, set to true to auto exit to NXE; if not present this is set to FALSE dvdexitdash = false launch.ini in root of hdd.

deffo a hdd fault then.might be best to borrow a ext hdd move everything to that and reformat ya hdd in nxe then move the stuff back.or if u happy with fsd3 from usb stay like that. to add to jpizzle's comment goto fsd3 settings and check it says plugin loaded.mine didnt at first.i test out my plugin by booting deasd space 2 disc 2 and then choose to launch a single player game from scratch and if plugin is working in will flash the message please wait (like it was about to ask for disc 1) then just boot single player normally.

i may be wrong but some peeps couldn't get it to work on trinity internal memory so thanks for clearing that up and letting them know it does boot from trinity int memory.

just try launching it from a usb stick for now with the fsd3 folder and launch.ini on your usb stick pointing to the usb to boot the dafault.xex. if it dont crash then then, then its a corrupt hdd.you may have to reformet the hdd and start again

Dashlaunch 3.03 : 16197 kernel, corona 4GB and new features added The famous Xbox 360 developper cOz release today a new version of the 360 master application : Dashlaunch. This new version bring (of course)the support of the 16197 dashboard but as always some new features and bugfix (check the changelog). The new features are : - Corona 4GB memory support - autofake option, when enabled fakelive functionality is enabled during dash and indie games only (thanks BioHazard!) - nohealth option, disables kinect health pseudo video at game launch - nooobe option, disables setup screens when settings already exist - Fakeanim option, to set a small video to use as bootanim - farenheit option, to use farenheit unit instead of celsius just added this as read a few posts from people who can't get fsd3 to boot from there 4gb int memory.it's always been possible

i used to get a little of this randomly on fsd2.2.have you tried removing the 1 game that duplicates 10 box arts (i.e deleting it) then reinstall it and see what happens (maybe do a complete rescan too beofre coying it back). i used to own a 4gb RGH slim with fsd2.2 that launched from Internal memory unit so the answer would be yes. have a quick look at all your xbla and dlc wih xm360 and count the number it gives you for each.then compare that to ehat's in fsd dash.if they compare then that aint the problem.also set scan depth to 2 or 3 see if any change. create a Emulators folder (or what ever you want to call it) put your emu's in that ect then set the scan path to that folder. go to http://covers.jqe360.com/ create a profile.then with this profile input them to fsd covers settings in fsd3.then connect your xbox to your router and it's all automatic. i wouldn't as your be booting and using fsd2.2 as you change the files around.just create another folder,place fsd3 in that.then change your launch.ini to boot the new fsd3.once that boots then delete fsd2.2 in fsd3 file manager. there are only 6 new skins available for fsd3 at themoment as it's a fairly new dash.-http://spiffy360.com/themes.php

try clearing your database and do a full rescan

post your launch.ini here.

just install it to a usb stick for now.i take it you want to launch games from ext hdd?also try installing to hdd as i think your int memory is like a hdd.

does the cd installer not offer the option to install fsd3 to the internal flash memory.i know it can be done with fsd2.2 as i had it done for me on a slim i once owned.i know in dashlaunch you can select the paths to the fsd3 default.xex then save the launch.ini to where ever you want.

mine boots straight to fsd3:)without that line it won't load up multidiscplugin for me.yours works without that line in launch.ini (i.e it says plugin loaded in fsd system settings?). gotta get connectx (also in fsd system settings.to say its loaded up) to work yet there is no file for that but suppose it will come later with rxe.

be carefull you don't have 2 x Default = IntMU:FSD3default.xex paths as this will stop it booting.this is a mistake i made.copy/paste my launch.ini above and alter the 2 lines to IntMU: thanks mate.but you do need this path with fsd3 as it won't say the plugin is loaded in settings else.fixed this now.the problem was dashlaunch created a launch.ini with the lineplugin1 = Hdd:PluginsFreeStylePlugin.xex and i didn't spot this so altering it to- plugin1 = Hdd:FreeStylePluginsFreeStylePlugin.xex and all good now.i go to fsd3 settings and it say plugin loaded.

i think you can use xex menu or even fsd2.2 if you still have it and then go to file manager and copy FreeStyle folder to your ; internal slim 4G mu IntMu:then change your launch.ini to- IntMu:FreeStyledefault.xex it's freezing because it can't find your launch.ini not 100% but think dashlaunch on the fsd3 cd installer plays a part too. got my multidiscplugin to work in the end.had a noob moment.this launch.ini got me going- Default = Hdd:FreeStyledefault.xex [Paths] BUT_A = BUT_B = BUT_X = BUT_Y = Start = Back = LBump = RThumb = LThumb = Guide = Power = configapp = dumpfile = [Plugins] plugin1 = Hdd:FreeStylePluginsFreeStylePlugin.xex plugin2 = plugin3 = plugin4 = plugin5 = [Externals] ftpserv = false ftpport = 21 calaunch = false [settings] nxemini = true pingpatch = true contpatch = true fatalfreeze = false fatalreboot = true safereboot = true regionspoof = true region = 0x7fff dvdexitdash = false xblaexitdash = false nosysexit = false nohud = false noupdater = true debugout = false exchandler = true bootdelay = 30 liveblock = true livestrong = false remotenxe = true hddalive = false hddtimer = 210 signnotice = false autoshut = false autooff = false xhttp = true tempbcast = false temptime = 10 tempport = 7030 sockpatch = false passlaunch = false fakelive = false nonetstore = true shuttemps = false devprof = false devlink = false autoswap = false

i agree on fsd2.2 multidiscplugin just worked (there was a multidiscplugin.xex file in plugin folder though in fsd2.2). with fsd3 however when you go to fsd3 settings it says if plugin loaded up or not and you can set the path to the plugin in dashlaunch settings. this alters the launch.ini to include a path under [plugins] to the file in plugins folder. i test it out by launching disc 2 of dead space 2 and start a new game and it should boot game and no change disc messages. yes i done all the Hdd1:xbox 360deadspace 2disc1 Hdd1:xbox 360deadspace 2disc2 stuff. like i say it worked the otherday but today it don't.i even checked the dashlaunch settings in dashlaunch and it's retained the path to plugins so must be a glitch.

something wrong again with multidiscplugin.not loaded up when check system settings.fsd2.2 seemed to do it automatically but fsd3 needs the path in launch.ini. i got it working yesterday but upon turning jtag on today it not loaded up?

yes i am on kernel 15574 and all good.

just letting people know there are 5 new themes available for fsd3 ayr is quite good:) http://spiffy360.com/themes.php

installing fsd3 only means you got to set your paths again and settings and let it download the covers again. yes i think. Change dashlaunch setting to look for launch.ini in IntMu: instead of Hdd:or change the line in launch.ini with notepad on pc from Default = Hdd:FreeStyledefault.xex to Default = IntMu:FreeStyledefault.xex with the fsd3installer i am sure you can change the path to internal memory to install fsd3 to it. sorry about mixxed answer. Got it working thanks for that tip.changed my launch.ini a little to include-[Plugins] plugin1 = Hdd:FreeStylePluginsFreeStylePlugin.xex plugin2 = plugin3 = plugin4 = plugin5 = that loaded up my plugin and it works. I've now deleted FSD2.2 completely and can't fault fsd3.cheers FSD team.

thanks will try and report back:)