Fallout 3 review copy leaks


Recommended Posts

I hate to break it to some of you guys, but nobody's going to get banned for having Fallout 3 achievements. Why?

Think about it, you can transfer your profile to any 360 at any time. You don't even have to be online to do it, you can just plug your hard drive in another 360 and off you go. Who's to say that the pirates didn't just plug their hard drive into a moded 360 to play the game, but uploaded their score via a clean, safe 360? It might have even been their friend's 360, which could own a perfectly legit console - should they ban him just to try to get the pirate?

Sure, the achievement details might also state which console they were earned on, but that's unlikely and more to the point - unproven.

Plus, if ONE "review" copy has been sent out, then chances are SEVERAL review copies have been sent out and Microsoft can't just ban them all, nor can they keep track of the reviewers' IPs or whatever, it's just not possible.

So when it comes down to it, Microsoft has a choice - do a lot of guess work and attempt to ban anything "suspicious" and almost-certainly instigate a PR nightmare (And really, do they want to risk banning actual journalists who are likely going to mention it in some high-profile magazine?), or try to use their tried-and-tested methods of backup detection and only ban the ones they KNOW are pirating the game for sure.

I'm guessing they'll be going for the latter, as plenty of people have escaped the banhammer thus far, despite playing games ridiculously early.

There's another point I'd like to make, though - nobody is actually sure if this is a "review" copy or a retail leak, or both (i.e. it's the final code, but it's been sent out to review) and what's interesting is that it does actually work on retail consoles. Often, reviewers (at least the ones that review games before they come out in retail) have to use a special 360 that'll play backup disks and, more importantly, unsigned code. If this were unsigned, it wouldn't work on retail 360's at all and although it's a hell of a leak, it's still not so early that it couldn't be from a pressed, final disk (I believe it takes 2 weeks from Gold to print all the disks needed for the launch of a game - factor in that they'll likely have some leeway here and there, plus it's a hugely anticipated release and it comes together quite well).

Microsoft hasn't banned anyone in nearly a year now, either they'll given up (or simply can't) detecting them, or they're getting ready for a big-ol banfest right before Christmas. I'm going for the latter, but I still wouldn't expect many people to get banned because of this game alone and I'd still expect only the "stupid" pirates to get banned.

Christmas ban-fest to boost console sales :p

You're right but, so much guess work involved with playing copies/modded firmware.

A bad CRC will get you banned for sure (bad rip), but no one can really explain claims of people getting banned where they say all their games check out.

That's the risk involved with piracy and I doubt MS will ever make their methods of detection fully clear.

I hate to break it to some of you guys, but nobody's going to get banned for having Fallout 3 achievements. Why?

Think about it, you can transfer your profile to any 360 at any time. You don't even have to be online to do it, you can just plug your hard drive in another 360 and off you go. Who's to say that the pirates didn't just plug their hard drive into a moded 360 to play the game, but uploaded their score via a clean, safe 360? It might have even been their friend's 360, which could own a perfectly legit console - should they ban him just to try to get the pirate?

Sure, the achievement details might also state which console they were earned on, but that's unlikely and more to the point - unproven.

Plus, if ONE "review" copy has been sent out, then chances are SEVERAL review copies have been sent out and Microsoft can't just ban them all, nor can they keep track of the reviewers' IPs or whatever, it's just not possible.

So when it comes down to it, Microsoft has a choice - do a lot of guess work and attempt to ban anything "suspicious" and almost-certainly instigate a PR nightmare (And really, do they want to risk banning actual journalists who are likely going to mention it in some high-profile magazine?), or try to use their tried-and-tested methods of backup detection and only ban the ones they KNOW are pirating the game for sure.

I'm guessing they'll be going for the latter, as plenty of people have escaped the banhammer thus far, despite playing games ridiculously early.

There's another point I'd like to make, though - nobody is actually sure if this is a "review" copy or a retail leak, or both (i.e. it's the final code, but it's been sent out to review) and what's interesting is that it does actually work on retail consoles. Often, reviewers (at least the ones that review games before they come out in retail) have to use a special 360 that'll play backup disks and, more importantly, unsigned code. If this were unsigned, it wouldn't work on retail 360's at all and although it's a hell of a leak, it's still not so early that it couldn't be from a pressed, final disk (I believe it takes 2 weeks from Gold to print all the disks needed for the launch of a game - factor in that they'll likely have some leeway here and there, plus it's a hugely anticipated release and it comes together quite well).

Microsoft hasn't banned anyone in nearly a year now, either they'll given up (or simply can't) detecting them, or they're getting ready for a big-ol banfest right before Christmas. I'm going for the latter, but I still wouldn't expect many people to get banned because of this game alone and I'd still expect only the "stupid" pirates to get banned.

Thank you!, what I've been saying the past few days now :yes:

The only way I see bans coming out are if the review copy is watermarked and can be traced.

They won't ban for achievements, many people play games early through owning a game store/knowing friends/etc.

I legitimately played MGS4 about a week before it was out. It's just too much of a guessing game for MS with achievements.

Unless of course the achievements are somehow not final :p

Christmas ban-fest to boost console sales :p

You're right but, so much guess work involved with playing copies/modded firmware.

A bad CRC will get you banned for sure (bad rip), but no one can really explain claims of people getting banned where they say all their games check out.

That's the risk involved with piracy and I doubt MS will ever make their methods of detection fully clear.

I don't actually know how they do it, but the "experts" in the "scene" monitor XBL communications and are usually able to pinpoint what information is being sent back to Microsoft. After the last banning, they discovered a bug in their ripping process that could give off a weird result (I don't know the full details and I want to keep this post on the side of "Lets not ban Kushykins for discussing piracy in too much detail") in some cases, but not others. It was a bug, but not one that always appeared and even after a backup had been burned, didn't always appear, but when it did, Microsoft could detect it (Which is why a lot of people were confused after the last time, since it would appear that SOME people got banned, but others got away with it). A few weeks later, a new firmware appears that fixed this tiny little bug and nobody's been banned since (apparently).

What's interesting to me, however, is that NOBODY has been banned since last Year. Could the pirates have really "won?"? I find it hard to believe that nobody has been using bad rips in all this time, but you have to ask why Microsoft is waiting. It's possible they're waiting until Christmas so they can boost sales a little, but it's also possible they really can't detect the "safe" pirates and are holding off so they get lazy and slip up.

Oh well, we'll see what happens.

I don't actually know how they do it, but the "experts" in the "scene" monitor XBL communications and are usually able to pinpoint what information is being sent back to Microsoft. After the last banning, they discovered a bug in their ripping process that could give off a weird result (I don't know the full details and I want to keep this post on the side of "Lets not ban Kushykins for discussing piracy in too much detail") in some cases, but not others. It was a bug, but not one that always appeared and even after a backup had been burned, didn't always appear, but when it did, Microsoft could detect it (Which is why a lot of people were confused after the last time, since it would appear that SOME people got banned, but others got away with it). A few weeks later, a new firmware appears that fixed this tiny little bug and nobody's been banned since (apparently).

What's interesting to me, however, is that NOBODY has been banned since last Year. Could the pirates have really "won?"? I find it hard to believe that nobody has been using bad rips in all this time, but you have to ask why Microsoft is waiting. It's possible they're waiting until Christmas so they can boost sales a little, but it's also possible they really can't detect the "safe" pirates and are holding off so they get lazy and slip up.

Oh well, we'll see what happens.

They always ban in waves anyway, it's strange it's been as long as a year, but we'll see what happens around the time of NXE/GoW2.

Well MS could just ban anyone who has the achievements, and clean up the mess after.

Didn't play the game pirated game? unmodified 360 you say? well we'll have a look and if it's true we'll unban it.

That'd potentially hurt a lot of reviewers if they were logged in when playing and would maybe even make some think twice about running pre release MS games. I assume reviewers can play on their own accounts, maybe thats not the case.

From a PR perspective that'd likely do more damage than just copping the fact copies leak would...especially given it's the press you would be hurting most here and they are the ones that will make you look good or bad and influence millions of other customers out there.

Perhaps they should just design review copies in a manner that you MUST be online in order to play them. Just have a little toggle somewhere, a single bit thats on or off depending if it's a retail copy or not. If you try and play a review copy offline you get booted back to the dashboard.

I don't see the point of this topic? Games get leaked all the time, what makes this any different. Game is out soon anyway so looking forward to it :)

i have to agree with you on this one, even be it a Review copy, this is nothing new, in the last two months there have been REVIEW copys of other games.

and no-one really knows if you will be banned or not playing a Review copy, even states this in the .nfo....

price you pay for being inpatient, or just get two xbox's :p

MS has pretty much stopped banning as of late and people are wondering when they will do a massive ban, or just plain start up again.

The market for actual "mod chips" that have external switches to enable players to turn them on and off to avoid detection has dropped significantly and more and more people are simply modding their firmware which is riskier since other then not going on live you have no way to truly hide the fact that your running modified firmware.

The above wouldn't have happened if not for the long lull in bans.

I don't think the 360 has ever had a mod chip with a switch to deactivate it?

.. yeah i dont think there was on you could actually turn off, there was a chip called NME that had a fair bunch of features.

- one chip for all drives: Samsung ms25 and ms28, Hitachi/LG 46,47,58,59, 78 FL/FK, 79 FL/FK, all BenQ drives!!!

- Added logic to support possible future Hitachi/LG versions as well

- 100% Auto detection of Backup or Original on Samsung and Hitachi drives (BenQ requires manual switching)

- boots stealth and non-stealth backups - optional: Power Led will turn off when a Backup is detected

- optional: disables the network when playing backups

- optional: disables the rear USB connection when playing backups (for disabling USB Wlan)

- no DVD writer model issues. Works with all DVD writers

- now working with pioneer 111d and Pioneer based burners as well as all LG burners.

- 100% Firmware Stealth, when MS tries to read the Firmware then it replies as 100% original unmodified. No error code E66.

- optional: 100% Live secure when playing Backups

- the result of 1000s of hours of research and programming

- based on Actel Logic for most possibly stability

- manufactured with highest quality Logic, PCB and components. Made in Europe.

- complies with RoHS directive (lead free). Gold plated solder pads, for easy soldering.

I don't think Microsoft CAN read the firmware anyway, a lot of the drives have a sort of "lock" on them that prevents this without some jiggery-pokery. The Hitatchi 79's are a prime example of this.

There was some routine within the drive's firmware that gave a checksum of the firmware, but that was found pretty early on.

It's well known that Microsoft cannot detect a modified drive (unless it's spoofed, but that's an ENTIRELY different matter), but rather it's bad copies they detect. I believe the purpose of that NME chip was to allow you to play bad copies without running the risk of getting banned (because it automagically disables the network adapter) but the scene is now mature enough that "bad" rips are pretty rare.

EDIT: In saying that, though, with the NXE update, it's very possible they'll be doing some firmware checking since they've reported that the installation will take a good while - plenty of time to do what's needed, while knowing the user isn't just going to power off any time soon.

Edited by Kushan
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!