Jump to content
RealModScene

twinvipers

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About twinvipers

  • Rank
    RMS Freshman
  1. I have tried that with no luck. I also tried to do the separate ports with separate protocols so "3071 to 3071 enable TCP and then a second line for 3071 to 3071 enable UDP" and then the same for 3072 and no luck. I have also tried to change port numbers/range and i also moved the Xbox to a different IP within my network and no luck. Any other ideas that I can try? I have kind of hit a wall?
  2. A little help here would be great... I have followed the Tutorial for set up but can't seem to get "PASSES" every where. Here is my set-up.. F3Plugin- Enable Link: Always On (ticked) Enable UPNP: (ticked) Data Port: 3071 Broadcast Port: 3072 DashLaunch- DevLink: enabled PINGPATCH: enabled Linksys WRT610N- UPNP enabled: Port forwarding: During the "TEST" Pass - UPNP FAIL - Both TCP and UDP in Data Port Status FAIL - Both TCP and UDP in Broadcast Port Status Pass - JQE360 Status While in a game (BO2) I can go to Guide/System Link and see rooms and also join rooms. But when i try to load a room in game it shows nothing and refreshing changes nothing... Help Please..
  3. so you think updating the TUs for BO2 will help? also any ideas on now that i have updated dashboard to 19167 i cant seem to FTP transfer any .xex files? like if i transfer dashlaunch it create the folders but the .xex dosn't move? i can transfer back and forth any files or folders as long as its not a .xex?
  4. Well as I mentioned in my post I have Dashlaunch 3.04 and COD BO2 in NOT working?
  5. Ok I’m trying to update to Dashlaunch 3.04 so I can use BO2 but having some trouble. First thing I did was update my dashboard to 16197 using Nand Flasher 360 & J-Runner. And it’s been a while since my last update and let me tell you with J-Runner it was a breeze. Never the less that part worked perfectly. Now I didn’t know J-Runner also loaded Dashlaunch until after and I could seem to find/update the launch.ini so I reflashed the unit with J-Runner but turned off the Dashlaunch option. Now that all look good once done. I then loaded Dashlaunch 3.04 onto a USB and installed that way as I have done it that way in the past (I have also in the past used FTP to transfer the installer and run the .xex but I will get back to that in a minute) So I ran the .xex from the USB, installed Dashlaunch, changed one option the path for default dash to FS2, saved the launch.ini to HDD, and also saw an option to install DL3.04 to HDD so I did that as well. Restarted the system and it booted right into FS2 Great… But when I try BO2 it goes to a black screen and doesn’t move? I then restarted and thought I would run the Dashlaunch .xex from HDD and try to unload Dashlaunch and then see if BO2 worked but the default.xex was not in the installer folder that was created by Dashlaunch? I then tried to FTP the Default.xex into the file but the transfer fails? I even tried to transfer from the USB but it fails? It only seem to run off the USB? And Running the Dashlaunch from USB and Unloading Dashlaunch didn’t help ether the BO2 just gives me a black screen? Any ideas????
×
×
  • Create New...