Jump to content
RealModScene

JPizzle

Administrators
  • Content Count

    2203
  • Joined

  • Last visited

Everything posted by JPizzle

  1. You have to be in a systemlink enabled game for the Systemlink menu in the HUD to become active.
  2. Make sure both consoles are using different ports for link and that they are running the same TU version.
  3. We are upgrading our server very soon and it will have twice the capacity as the current server.... Unfortunately it is also twice the cost. We pay for the server ourselves so that everyone in the community can enjoy playing games together on their JTAG/RGH consoles but donations are always appreciated. You can send VIA PayPal to donations@realmodscene.com
  4. Originally posted on Engadget.com Microsoft's white employee-only Xbox One could become a little less exclusive. The snow-colored console is rumored to appear alongside the cartoony shooterSunset Overdrive this October, and a 1TB version of the hardware might release in November according to a NeoGAF thread that's been confirmed by The Verge's sources. What's more, Microsoft's latest console may also see worldwide release this year sans Blu-ray drive for $399. With the annual DICE Summit and Game Developers Conference not far off on the horizon, it might not be long before we see these rumors publicly confirmed. We've reached out to Redmond and will let you know if we hear back. Update: The source of the NeoGAF thread also says that a Limited Edition Titanfall console is on the way too, posting what he says is an image of the special console's design.
  5. update F3, FreeBOOT and Dashlaunch.... check out the tutorials section.
  6. The reason for this issue is because GTA V is a two disc game, one disc being installed o the HDD and the second meant to be run from disc. F3 is checking for a TU for the disc that i meant to be run from disc as that is how you are running the game. The TU's for GTA V are assigned to the disc that is installed on the HDD. This is why F3 is not finding a TU for the game and why you need to manually install them.
  7. Scan for new games in the F3 settings area and it will scan for new games and then new TU's.
  8. make sure both consoles are running the latest TU for the game and also update both to the same version of dashlaunch
  9. maybe nobody wants to play with you
  10. go into the stock MS dashboard and check your network settings, set everything to automatic.
  11. JPizzle

    Weather and FSD 3

    untick the box bellow the arrow
  12. Your F3 plugin is not loaded, update to the latest version of F3 v775 @IrishDave Nice tutorial
  13. PS Vita hacking community member Katsu has released details of his POC(Proof Of Concept) hack for the PS Vita over at wololo.net. The hack allows a user to boot into a previous kernel, essentially performing a downgrade. For more information CLICK HERE
  14. Originally posted on http://wololo.net/ It didn’t take long for Yifan Lu’s investigations to become useful for other hardware hackers! Our community member katsu, guided by Yifan’s precise description of the Vita’s NAND pinouts, was able to hack his PS Vita in order to boot from a previous firmware, technically performing something very similar to a downgrade. Check the video below, it’s cool and full of “electronics porn”, like your favorite cyberpunk movie. What katsu did was dump his firmware 2.12 (on the NAND), probably using Yifan Lu’s technique. He then copied that Firmware dump to an SD card. In the meantime, he upgraded the PS Vita to firmware 3.01. On the video, you see him inserting his SD card in a reader connected to the Vita. The Vita then reads the content of the SD card (the firmware 2.12 he dumped earlier) instead of its own 3.01 NAND. What the hell does all of that mean? First of all, that Yifan Lu’s little experiment in the hardware world is proving successful, by providing inspiration and documentation for other talented hardware modders. Secondly, that downgrading a PS Vita is a possibility under certain conditions: what the experience proves here is that technically your Vita is able to go back to a firmware that was previously installed on it. This might sound obvious, but it means that installing firmware 3.01 did not “change” anything that would make the Vita backward incompatible with its previous firmwares. That’s something that eventually Sony could change, but for now this is promising.Now don’t get me wrong, this doesn’t mean downgrading a Vita will become mainstream overnight! The hardware modifications required here are pretty big for now, and more importantly, this would only work with a NAND dump of your own Vita, as it is very likely that the NAND encryption key is specific to each console. One wouldn’t be able to downgrade to someone else’s firmware. What this means though is that today, someone with cheap hardware and the required skills could dump their Vita 3.01 NAND, upgrade to Sony’s next firmware to get all the benefit of the PSN, and boot from firmware 3.01 again whenever they feel like running Total_Noob’s Custom Firmware again. Here again, I am making this sound a bit better than it really is. Katsu did not prove it was possible to write anything back to the NAND, just that he is booting the firmware from an external reader, which according to him takes 10 minutes. Not something very practical for now. Nevertheless, this is pretty exciting, and could be the first (second?) step in some cool Vita hardware hacks. Let’s see how this develops! Source: katsu on /talk
×
×
  • Create New...