-
Content Count
252 -
Joined
-
Last visited
-
Days Won
9
Posts posted by Flaminek
-
-
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 NXEOne little nagging problem remains. Whenever I am playing a game and depress the Guide button on the wireless controller to quickly exit the game I am presented with what appears to be the standard (non-F3) dashboard which has the following displayed:
Xbox Guide
Xbox Home
Join Xbox LIVE
Open tray
If I hit the Guide button again it reboots F3. I assume that something in the configuration (INI ?) file is wrong and I probably caused it. How do I fix it and how to I get to the launch.ini file to edit it assuming that's what I need to fix?
As always many thanks for the invaluable assistance,
outofwork
; if not present this is set to FALSE
dvdexitdash = false
launch.ini in root of hdd.
- 1
-
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.It ended up crashing two more times, first while scanning the XBLA folder and then while downloading the assets, but since then it hasn't crashed once. Here's hoping it remains stable now, I really like how much faster I can access my games now.
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.First of all, I love the new build. CoverFlow looks awesome!
Now for my problem.. I was able to install FSD3 over top of FSD2 via the install CD. All my games and everything still exist. I mapped the folders exactly how I had them before (I wrote them down). However, my Emulators all seem to merge into the Homebrew tab of the library instead of the Emulation tab. Not a huge issue currently, as I hardly ever use them. Just thought I'd mention it incase somebody else has a similar problem so the dev guys can take a look and fix it with an update patch.
Also, I'm curious as to how the whole disk swap thing works. On games like Rage where it's just a straight progression from disk 1 to 3, do we still just hide disk 2 and 3 and FSD takes care of swapping on its own, or do we need to do something else to enable it or make it work?
Great work guys, can't wait to get some hard use out of it!
-
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.You wrong.
Before of this version of dashlaunch on corona 4GB was impossibile install it and autoboot
In trinity 4Gb always was possible and it work
-
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 againThen please tell me what I'm doing wrong. I manually copied the files to a new folder on the HDD, changed a few settings to match my FSD2 setup, and added all my folders. That's when it started crashing over and over again. I then burned the ISO and installed it from there to yet another new folder checking the box to download updated files. Changed options again, and then added just my 360 game path on my external drive, no Originals or XBLA because there were several people reporting crashes after scanning 100+ XBLA games. I then took a shower, came back to find it had crashed again. So, please tell me what I've done wrong. I just added the XBLA path now and it is scanning, we shall see if it crashes 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 too have this exact same issue but it is only with my xbla games. Many of the covers in my xbla games are duplicated. I even have one xbla game cover that has 10 duplicates. I do not understand why there are so many duplicates and why it is just my xbla games. I have 2 more problems besides this one as well. When I try to delete a game path the symbol that lets you know that fs3 is busy just hangs there and never deletes the path. I have also tried to clear the data with resetting FS3 but it does not remove a thing. Now when I try to deleted a game path and I am connected to the internet fs3 will not allow me at all to do so. I get a message from fs3 that says please wait until scanning is done but it is not scanning a damn thing.
i used to own a 4gb RGH slim with fsd2.2 that launched from Internal memory unit so the answer would be yes.Nobody had reply at an important question.
Is possible autoboot on corona 4 GB??
Or maybe we should wait next dashlaunch?
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.I have re-installed FS3 at least 6 times and still get the duplicate coverart in my xbla games every time. I have no idea what in the hell can be causing this issue but I have also seen other people post with this exact same issue elsewhere. After a new install and the database is through scanning I have even cleared the database and when it scans I get the same damn results. One of my xbla games has 10 duplicate coverarts and others have anywhere from 2 to 6 duplicates but only in xbla games. I have also tried to delete game paths in FS3 and it says to please wait until operation is complete but that screen just stays there and it never deletes the game path. Sure wished I knew how to get rid of the duplicate coverart for my xbla games because manually removing 100 of them is just insane. Anyone that has had this issue and resolved it please post your findings. Personally I believe this is some kind of bug in FS3.
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.Hey guys. Awesome work!
I'm having an issue getting emulators to show up though. I've got them in Content0000000000000000Emu and I've scanned that folder but I they're not showing.
Genesis360 show's up as a homebrew?
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.will it show the covers automatically? or i will need to connect my xbox to the internet,, I don't know how to connect my xbox,
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.I still haven't upgraded. Lol.
If I already have FSD2.2 install can I just simply rename that folder via FTP and then transfer the F3 folder in via FTP with the same name as the previous FSD2.2 folder?? And expect it to work?
there are only 6 new skins available for fsd3 at themoment as it's a fairly new dash.-HELP!!!! I have installed the new dashboard to my hd and it started automatically when i turned the videogame on, but today i tried to change my skin to a portuguese one that is attached below (Brazil) cause mine was in spanish. So i copied the archive to the same file of the old skin through FTP (filezilla) and when i selected it on the freestyle3 menu, it all turned black and my freestyle doesnt work anymore...only the menu of xbox. WHAT DO I DO?????
Would be glad if someone helps me. Im a light usuary so i dont understand much of installing this kind of programs.
Thank you so much.
Onborges
-
try clearing your database and do a full rescan
-
post your launch.ini here.I delete my FSD 2.2 from IntMU and copy already FSD 3 in such path: IntMU:FSD3, so then i copy DashLaunch 3.02 on my flashdisk and launch xbox with flashdisk and i automatically go to DashLaunch interface on a startup, i correct default path there as IntMU:FSD3default.xex so it right path and save such launch.ini at my IntMU. But when I restart my console again it freeze again and when I use DashLaunch again it says - default: none path O_o But I save it already О_о I'm not first, who meet this kind of problem.
-
just install it to a usb stick for now.i take it you want to launch games from ext hdd?Nope. I rec FSD3 installer Demo on my flashdisk and launch it under NXE. So it does'nt see my IntMU path, only USB and i guess HDD path (i don't have internal SATA HDD, so i can't check it).
Please, guys, fix that problem with installing to IntMU on XBOX Slim 4gb consoles. Thanks!
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.I have ONE string - Default = IntMU:FSD3default.xex in my launch.ini. And I have logo freeze on startup.
-
mine boots straight to fsd3:)Delete all that in launch.ini and launch into F3 by default and you will see that it loads fine if you haven't touched anything. If not, do a cold boot ie power off completely one time.
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:I delete my FSD 2.2 from IntMU and copy already FSD 3 in such path: IntMU:FSD3, so then i copy DashLaunch 3.02 on my flashdisk and launch xbox with flashdisk and i automatically go to DashLaunch interface on a startup, i correct default path there as IntMU:FSD3default.xex so it right path and save such launch.ini at my IntMU. But when I restart my console again it freeze again and when I use DashLaunch again it says - default: none path O_o But I save it already О_о I'm not first, who meet this kind of problem.
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 lineNo you don't need the path in launch.ini. Launch.ini is Dashlaunch's ini file not F3s. Start directly into F3 and the multidisc works.
plugin1 = 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:So, how to autoboot FSD3 from IntMU path? Does anybody knows? I have XBOX 360 logo freeze at boot then i change path to IntMU:FSDdefault.xex
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.
Later this evening I'll have to try a 2 discer game and see what happens. Will post what happens for me (fresh FSD3 install - 14719, DL 3.01 beta...no other changes made other than the new fsd install)
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.Hi will this install on dash 15574
Any info much appreciated
-
just letting people know there are 5 new themes available for fsd3
ayr is quite good:)
-
installing fsd3 only means you got to set your paths again and settings and let it download the covers again.Hello to all, i am new here. And have the following question.
What does the Database mean? i have the 2.2 version and want to upgrade to the new version. i have a xbox360 with a 1TB internal disk full of games and content like DLC etc.. So what happens if i want to upgrade? does this remove al my games? or only has it to rescan the content for covers?
cheers!
yes i think. Change dashlaunch setting to look for launch.ini in IntMu: instead of Hdd:I reapeat my last question; is possibile install FS3 on corona 4Gb in OnboardMu and start it on boot? Or we should wait dashlaunch patch for do it?
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-There's your problem. It loads 2.2 multidisc plugin into memory or something, blocking F3 from loading it. Boot directly into F3 and the plugin will work!
[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:)There's your problem. It loads 2.2 multidisc plugin into memory or something, blocking F3 from loading it. Boot directly into F3 and the plugin will work!
Freestyle 3 inlcuding LiNK BETA mandatory update
in FreeStyle Dashboard Releases
Posted
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.