You are viewing our Forum Archives. To view or take place in current topics click here.
How to setup FSD 2.0 and Xlink Kai
Posted:
How to setup FSD 2.0 and Xlink KaiPosted:
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
[ Register or Signin to view external links. ]
Note: You will need the 30ms ping patch already installed
Download Section:
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
1. Extract the FSD 2.0 contents to a folder on your HDD. I suggest using a external HDD so you have more room.
2. If your using Dashlaunch (Should be everyone), Edit your launch.ini to point to the default.xex in the new FSD2 folder so it will auto-boot at launch. Once you have done that, reboot and confirm that it boots into the new dash. If it does, go ahead and delete your old FSD and FSDdata folders off your JTAG.
3. So now that you have the new FSD2 auto-booting, go to the "Utilities" section and then the settings tab and make sure you have "receive Update Notices at Startup" & "Enable Beta Updates" checked in the General settings window. Enter your Team FSD.com credentials if you are a member. Move over to the Content Settings window and under market place locale choose your location and click the "set Marketplace Locale" button. Now we need to set your game paths so click the "manage game paths" button just below.
4. Here we need to add the paths to all of your content so just click "Y" to add. Click the change path button and navigate to where your games are stored. Mine are in USB0:Games\ so I would navigate to that folder and press Y to select directory. Check off the box beside Xbox 360 or whatever content's path you are trying to set. You can leave scan depth at 2 or move it up to 3 just to be safe, it all depends on how many directories away from the set path the xex files are. Now click X to save and continue the same process for the rest of your content (XBLA, Homebrew, Emulators, etc.). It is going to take a long time to scan and download all art for your content so you might as well take a break.
5. OK, so now you have set your paths, your content's art and info is all in place. Looks great doesn't it ;) but you're itching to see what's up with that Xlink Kai section .... well let's get you setup then.
6. First thing you're going to need to do is setup Xlink Kai on your home network. For info on that go to [ Register or Signin to view external links. ] . Once you have Xlink downloaded and setup correctly on your network you will need to download the special Xlink Kai Engine Update for FSD2.
7. Download the package and extract it. Inside you will find "kaiEngine.exe". Move this file over to your Xlink installation directory: C:\Program Files\XLink Kai. It will ask you if you want to copy and replace. Say yes to copy and replace. Now start up Xlink. You should see the little Xlink Kai engine icon near your clock. Right-click it and go to configuration. Your web browser should open up a config page for Xlink kai and near the bottom-right there is a box beside the options that says "Allow Remote UI Connections ". Make sure that is enabled and save. Now Xlink is ready for FSD2!
8. Go to the Xlink Kai section in FSD2 and click the "Sign In/Out" tab. When the Sign in window pops up, either enter your Username & Password and click the remember me box or if your Xlink client is already set to auto sign in on your PC you can simply click the "Login using username/password stored with engine" box. There is a box that says "Live Status" if everything is working properly it will read "System attached to Xlink Engine...". Click the connect button and you're on Xlink !!
Thanks to Apathy from 7s for the original tut and download links
I found this video on youtube that shows FSD 2.0 and should help you out.
Note: You will need the 30ms ping patch already installed
Download Section:
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
1. Extract the FSD 2.0 contents to a folder on your HDD. I suggest using a external HDD so you have more room.
2. If your using Dashlaunch (Should be everyone), Edit your launch.ini to point to the default.xex in the new FSD2 folder so it will auto-boot at launch. Once you have done that, reboot and confirm that it boots into the new dash. If it does, go ahead and delete your old FSD and FSDdata folders off your JTAG.
3. So now that you have the new FSD2 auto-booting, go to the "Utilities" section and then the settings tab and make sure you have "receive Update Notices at Startup" & "Enable Beta Updates" checked in the General settings window. Enter your Team FSD.com credentials if you are a member. Move over to the Content Settings window and under market place locale choose your location and click the "set Marketplace Locale" button. Now we need to set your game paths so click the "manage game paths" button just below.
4. Here we need to add the paths to all of your content so just click "Y" to add. Click the change path button and navigate to where your games are stored. Mine are in USB0:Games\ so I would navigate to that folder and press Y to select directory. Check off the box beside Xbox 360 or whatever content's path you are trying to set. You can leave scan depth at 2 or move it up to 3 just to be safe, it all depends on how many directories away from the set path the xex files are. Now click X to save and continue the same process for the rest of your content (XBLA, Homebrew, Emulators, etc.). It is going to take a long time to scan and download all art for your content so you might as well take a break.
5. OK, so now you have set your paths, your content's art and info is all in place. Looks great doesn't it ;) but you're itching to see what's up with that Xlink Kai section .... well let's get you setup then.
6. First thing you're going to need to do is setup Xlink Kai on your home network. For info on that go to [ Register or Signin to view external links. ] . Once you have Xlink downloaded and setup correctly on your network you will need to download the special Xlink Kai Engine Update for FSD2.
7. Download the package and extract it. Inside you will find "kaiEngine.exe". Move this file over to your Xlink installation directory: C:\Program Files\XLink Kai. It will ask you if you want to copy and replace. Say yes to copy and replace. Now start up Xlink. You should see the little Xlink Kai engine icon near your clock. Right-click it and go to configuration. Your web browser should open up a config page for Xlink kai and near the bottom-right there is a box beside the options that says "Allow Remote UI Connections ". Make sure that is enabled and save. Now Xlink is ready for FSD2!
8. Go to the Xlink Kai section in FSD2 and click the "Sign In/Out" tab. When the Sign in window pops up, either enter your Username & Password and click the remember me box or if your Xlink client is already set to auto sign in on your PC you can simply click the "Login using username/password stored with engine" box. There is a box that says "Live Status" if everything is working properly it will read "System attached to Xlink Engine...". Click the connect button and you're on Xlink !!
Thanks to Apathy from 7s for the original tut and download links
I found this video on youtube that shows FSD 2.0 and should help you out.
#2. Posted:
Status: Offline
Joined: Jan 27, 201014Year Member
Posts: 1,631
Reputation Power: 70
Status: Offline
Joined: Jan 27, 201014Year Member
Posts: 1,631
Reputation Power: 70
yeah finally mate thanks this is what i was looking after so many hours
- 0useful
- 0not useful
#3. Posted:
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
Davidek1994 wrote yeah finally mate thanks this is what i was looking after so many hoursYeah man, no problem. Need any other tuts just shoot me a PM
- 0useful
- 0not useful
#4. Posted:
Status: Offline
Joined: May 24, 201014Year Member
Posts: 696
Reputation Power: 44
Status: Offline
Joined: May 24, 201014Year Member
Posts: 696
Reputation Power: 44
this looks way too complicated for me.. lawl
- 0useful
- 0not useful
#5. Posted:
Status: Offline
Joined: Jan 14, 201113Year Member
Posts: 10
Reputation Power: 0
Status: Offline
Joined: Jan 14, 201113Year Member
Posts: 10
Reputation Power: 0
No games pop up in system link : (
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Aug 09, 201014Year Member
Posts: 552
Reputation Power: 31
I tried to set it up on my jtag but couldn't connect to others, gave up in the end. maybe you should add a tut describing how to port forward, I might be wrong but I think everyone will have to do it.
Here's a video tut I followed. I take no credit for this, just helping out.
[ Register or Signin to view external links. ]
Here's a video tut I followed. I take no credit for this, just helping out.
[ Register or Signin to view external links. ]
- 0useful
- 0not useful
#7. Posted:
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
I just set it up on my falcon and didnt have to port forward. Maybe some routers have to, idk
- 0useful
- 0not useful
#8. Posted:
Status: Offline
Joined: Aug 09, 201014Year Member
Posts: 552
Reputation Power: 31
Colorado880 wrote I just set it up on my falcon and didnt have to port forward. Maybe some routers have to, idk
maybe that is my problem, does it work with 12625 and Dashlaunch2.22?
- 0useful
- 0not useful
#9. Posted:
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
mag00 wroteThats exactly what I used to setup my falcon. dashlaunch 2.22 and 12625Colorado880 wrote I just set it up on my falcon and didnt have to port forward. Maybe some routers have to, idk
maybe that is my problem, does it work with 12625 and Dashlaunch2.22?
- 0useful
- 0not useful
You are viewing our Forum Archives. To view or take place in current topics click here.