multi builder and dash patches: what does it mean?

[eyesonly]

Hi,

After glitching my falcon box with multi builder 0.4 (option 1: add dashlaunch patches), do I still need to install dashlaunch?

Don't really understand what the dashlaunch patches do that are installed in the nand?

Any thoughts?

 

[ball00]

Dash launch is a set of files that allows you to boot direct to whichever dash you choose nd sets how the dash acts. You may also set different launch paths attached to the buttons on your controller. Holding a would go to nxe holding down nothing launches fsd etc.

As well as allowing us to chose which dash to launch the setup files can be edited to do some useful stuff. We can block accidental updates, block connection to live to avoid being banned. It removes the ping limits set by microsoft an can alter how your mini blade acts (the menu that shows when you press the xbox button in middle of controller)

Dash launch is already installed if you chose the option in multibuilder. If you want to edit how dashlaunch acts then find the launch.ini file that is either on your hdd or usb hdd and edit the options through notepad and save it back to its original location.

 

[Martin C]

Just bear in mind that option #1 puts a copy of launch.ini into your FLASH area, so if you want to edit/remove, you'll need to enable advanced settings in FSD to access it.

IMHO I wouldn't do this - installing the actual patches to flash is enough while keeping the launch.ini on a removable storage should you ever need to edit it in future.

 

[eyesonly]

aah, thank you both.
So if I want to update to a newer dashlaunch, I have to update the one in the nand and cannot just put the files on my hdd?

 

[Martin C]

correct - to update dashlaunch in the future, you only need to run the installer.xex that comes with it.

 

[eyesonly]

correct - to update dashlaunch in the future, you only need to run the installer.xex that comes with it.

Now I'm confused:crazy:

So when I run the installer.xex with a newer dashlaunch, it should update?
As stated: I did option one, so the file is written into the nand. So when I put the .ini on my hdd, it will not see the file?

Second question: is it possible to bypass this without flashing the nand?

 

[Martin C]

Now I'm confused:crazy:

So when I run the installer.xex with a newer dashlaunch, it should update?

Yes - if there are any changes to the launch/lhelper.xex files in the NAND then it will update them for you on the fly.

As stated: I did option one, so the file is written into the nand. So when I put the .ini on my hdd, it will not see the file?

Then you've done something wrong with the ini file. Without knowing any more about it, I can't help.

Second question: is it possible to bypass this without flashing the nand?

Bypass what? Not sure what you're asking or whether you completely understand what dashlaunch is.

 

[eyesonly]

well, updated to dahslaunch 2.27 and now understand how it works. When updating the installer updates the part of the nand.

thanks

 

[Martin C]

Yep!