Jump to content
RealModScene

drocker

Members
  • Content Count

    54
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by drocker


  1. Ok, first let me confess that i am unaware of this error called f3000. And, by the sound of it it seems to be an ip conflict. Try to put the an static ip in xbox dash network settings. Secondly, open your router page settings and see whats the "start ip address setting" which should look like 192.168.1.2 to either 50 or 100 depends different router models ( its something that your router assigns ip addresses in sequence to all those systems which are configured to assign ip address automatically. Once you find the settings make a note of the last ip you router supports and assign it to your xbox in network settings (for instance, 192.168.1.1 is your routers setting up address and 192.168.1.2 ..3..4..5 and so on would assigned to other systems which are configured to assign ip automatically).

    See if it helps.


  2. So my exams are finally over so was just passing by to say THANKS once again to those who helped me out with the problem i had with LINK....i finally got my console to show the System Link as before it was greyed out problem i guess it was the firewall being enabled but due to some reason it still didnt show afterwards so i just reinstalled FSD today and its working fine now :D

    glad to know you have all sorted :)

    Happy Linking :)


  3. So ive been trying to setup link so far ive seen 2 tutorial this is by far the best though im not able to see the link option even though everything is setup correctly according to me....that darn thing is always grey'd out when i run a game for ex. cod black ops IIMy dashboard version is 16203Dash launch version 2.07FSD version 3 rev 735when i test everything passes i tried with different ports as well other than 3071 & 3072 - ive also enabled DMZ with the xbox's ip address and still its greyed out - i have password remembered on jqe360 - any suggestions?

    bro ur problem is very simple :) ; u need to update your FSD to 775 and ur dashlaunch to 3:10. Once you have done that, follow the dashlaunch setup section and u should be "LINKED" :)

  4. Yah its COD

    What Dashboard setting u wana know?

    The error was Fetal crash corrupted

     

    cod will always remain strict no matter what. This matter was discussed by users and Link devs during the initial days of LiNK. Although cod's NAT is strict, but it shoudnt be of any problem to play and connect on LiNK.

    and as for dashlaunch, folllow tis guide:

    Dashlaunch setup

    -- The new F3 update has the devlink, pingpatch, and conpatch integrated in F3 systemLiNK. to access it, put a game on e.g. black ops 2, press the center button and navigate to networks and you should see dashlaunch settings there.

    -- But for a permanent solution, you still need to set those settings on or off in dashlaunch

    but if you want to do it the old style, then follow the guide below.

    Download the newest dashlaunch put it on usb, plug the usb in your xbox and open it with file manager in F3 dash. Install it where ever its convenient for you either usb hard drive or HDD1; I prefer my F3 and dashlaunch installed in HDD1.

    Next, open dashlaunch by going to the respected folder where you have saved it FS#'s file manager, go to networks enable ping patch and "DISABLE dEVLINK" , save your setting by clicking the RB trigger once and press X on whichever drive you have saved your dashlaunch (usually where ever your dashlaunch is saved there is a green mark on it). Done, now press B to exit.


  5. Thanks for ur guiding first .. Still strict :( and also its says fetal crash error and back me to dashboard

    what game are you trying to play? if its call of duty, then it will always remain strict in link and there is no way around it. even though, u can play that game without any problems.

    what about your dashlaunch settings; could you tell me what settings are enabled?


  6. Its okIts direct through wireless

    1- after enabling NAT in your router, restart it.

    2- in NXE, system settings, network settings, the ip address is same as in your router's port forwarding page.

      - in NXE, system settings, network settings, default gateway should be the same ip address as your routers default address; for instance, if you type 192.168.1.1(this is a commonly used ip address for most of the routers, yours could be different) to access your routers setting page, then type the same ip address for the default gateway in your NXE.

    3- this usually does the trick for many i have noticed - you dont have to use FS3's default ports; you can actually assign any port to it. the port im using are 4777 instead of 3071 and port 4888 instead of 3072. you are free to use these or any other if you like.

    let me know if it helped.


  7. Update to beta version ? I think this one the latest one am i right ?

    no; the last one is 2.0.16203 dash version.

    follow this guide its one of the easiest out there or you could either google it or youtube it.

    http://www.realmodscene.com/index.php?/topic/413-quick-and-easy-way-to-update-your-jtagrgh/

     

    my personal advice - youtube "How To Update Your Jtag/RGH To 16202 or 16203",  watch two or three videos  and get yourself familiarized with the process so you know what you are doing. dont worry  :) its not as difficult as it sounds. frankly, its quite easy once you get the hang of it. once done updating, you "MUST" install avatar and kinect data for link to work.

     

    http://www.realmodscene.com/index.php?/topic/347-how-to-install-avatar-kinect-data-on-a-jtagrgh-console/

     


  8. I didnt understand what u mean by clean install .. I just done install the Freestyle 3 and this my first game run ..So its cleaned ^^

    sometimes on rear occasions it doesnt install properly. try deleting fs3 completely from your system and reinstall it.

    also, what system update version u are on in nxe?

×
×
  • Create New...