Jump to content
RealModScene

Poffertjee

Members
  • Content Count

    21
  • Joined

  • Last visited

  • Days Won

    1

Poffertjee last won the day on March 8 2013

Poffertjee had the most liked content!

Community Reputation

3 Neutral

About Poffertjee

  • Rank
    RMS Freshman
  • Birthday June 15

Profile Information

  • Gender
    Male
  • Location
    Holland
  • Interests
    Webdeveloper, XBOXModder.
  1. You can actually set your target temperatures in Dashlaunch, the fan will automatically change it's speed to maintain the temps you set.Just make it run under 60s (: Don't forget to set it to auto is FSD.
  2. First of all, afaik theres no such bug. Your connection is not working. Uncheck the uPNP part in FSD. Try to disable DMZ, check you ip-adress and create the forward entries in your router like this: 1. Port: 3071 (or port range 3071-3071) Protocol: BOTH (UDP and TCP) Enabled: YES.2. Port 3072 (or port range 3072-3072) Protocol: BOTH (UDP and TCP) Enabled: YES. Run the check again. Your connection to LiNK will only work the right way if all the tests pass! See if it makes a difference (:
  3. To make things easier: you can hold RB while booting to go to NXE directly (: What you can do, is update your Dashlaunch to 3.07. After that, do a fresh install for FSD.
  4. Try starting the game through xex menu, if the problem still occurs, it's not fsd.
  5. Writing the NAND replaces the Core software of you console, if something goes wrong, the only thing to do is use hardware to fix it. Try to find a tutorial that takes you through all steps so you know what you're doing.Don't use the IP-functions in AutoGG. Also keep in mind that you don't have the hardware to correct if something goes wrong. You don't need NandXell, you only need to build a new NAND image.
  6. As you can see both your Dashboard (D) and Kernel (K) show a value lower then the 15572 i recommended. Assuming you never flashed your NAND before, i can recommend you to check out some tutorials. First you need to make sure you can boot to Xell to get your CPUKey.You can use "NAND Flasser 360" to read your current NAND to a Flashdrive.Use AutoGG to build a new Freeboot image. and use rawflash (through Xell) to write the new image. It's important for you te use tutorials, to have step by step instruction. Also try to find as much information as you need before doing anything (: Note that doing the writing wrong can break your RGH/JTAG.
  7. i recommend you to first check out your current dash version! Open your system settings and goto "Console Setting" and highlight "System Info".On the right a message will appear; what dashboard version does it show?
  8. Do you actually have a working internet connection on you console? (as you cannot ping the console)Does your console show an IPadress in the lower left corner?
  9. The "Game:" shows the content of what process is currently running, as the console handels FSD as a game, it will show the contents of your FSD folder. If you're in-game, it will show the contents of that game.
  10. First question, did you do the JTAG/RGH yourself or did you buy it pre-modded? You can use AutoGG to build a new freeboot image, based on your current nand, or a previous dumped one.Make sure to check the DashLaunch box in the AutoGG settings.
  11. Hi, Your problem sound like a kernel problem. Have you updated your NXE (Kernel) and dashlaunch?Try to make sure you are using Dashlaunch 3.07 and at least a kernel above 15572. Note that your Microsoft Dash a.k.a. NXE contains your kernel. Cheers
  12. I used Rev58 and Rev483 on both consoles. Both Rev's worked out well. Afaik, LiNK hasn't changed it's way of communicating and serving. I think the problem is inside the network, interesting.. You can try forwarding both incoming and outgoing connections for all ports, despite the labels in FSD. In your router's setting you can choose the type of forwarding per entry: TCP, UDP or BOTH. Try using the BOTH setting on ALL ports, this will forward both incoming and outgoing connections. After this, make sure the LiNK test passes on both consoles and try to host a game on console1 and join using console2.
  13. Could be because you're not in a room, did you try it while connected to a host and playing?
  14. Well, best way is to stay up to date, but in your case, assuming you're on 15574; it will work. Note that going to 16203 isn't a brash decision as you never know what a future update might require
  15. Yeah, update your microsoft dash aka NXE, that includes your kernel.You can update it using AutoGG, make sure to use the latest version.AutoGG allows you to update via Xell, there should be enough information on it, just google it. Everything above 15572 will do. Good Luck!
×
×
  • Create New...