{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib6uniyjm7jqjddbt22w5a37owucnkewoe7hcz5dbjlzboi6guupm",
    "uri": "at://did:plc:npppinc2x6on5fmrcemn2p5o/app.bsky.feed.post/3mhsqoqbcgwa2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreigdwoj7v3esvtvct7wumj66ssuvtkttgon5jipqngnvatmdvzhr2y"
    },
    "mimeType": "image/jpeg",
    "size": 28077
  },
  "path": "/post/811974525684170752",
  "publishedAt": "2026-03-24T13:34:10.000Z",
  "site": "https://tumblr.sztupy.hu",
  "tags": [
    "randomsporefacts",
    "an interesting tweet by twitter user Dynabroth:",
    "technical explanation in the comments"
  ],
  "textContent": "randomsporefacts:\n\n> learnt about an interesting tweet by twitter user Dynabroth:\n>\n>> One of the strangest Roblox bugs of all time in my opinion is this one recorded by Hackerhunter100, in November 2009.\n>\n> “whenever you play roblox and spore at the same time the files mix and everything glitches”\n>\n> twitter user wiredmjx also left a technical explanation in the comments as to why this could happen\n>\n>> Remarkable rendering bug. It’s caused by two processes: XPDM (basically the thing that manages WinXP graphics) and DirectX 9. Essentially, XPDM allows both Spore and Roblox to access the same memory, while DX9 was a lot more lax with how it handles reading & writing memory. 1/x\n>\n> First, Spore writes its graphics into the memory, the specific image you’re seeing in Roblox is the depth buffer (which is a greyscale image that indicates how close objects are to the camera). Roblox then asks for some memory to write its own graphics (a cubemap skybox) to. 2/x\n>\n> DX9 hands over that memory WITHOUT CLEARING IT because it expects the programmer (whoever wrote the Roblox renderer) to do so. Roblox however also fails to clear that memory. It uses data still in that memory block (Spore’s depth buffer) and puts it on the cubemap. 3/x\n>\n> Now, the Roblox renderer doesn’t know whether this is valid data or not, it doesn’t check at all what the data is. The remarkable part is that it just so happens it IS valid data! So instead of getting a crash, you get this Spore monster in the skybox :) 4/x\n>\n> This bug was likely fixed around 2010 with the Roblox renderer now correctly clearing the skybox cubemap texture memory prior to use. This kind of issue is now extinct on modern computers, as the modern equivalent of XPDM doesn’t let programs access eachothers memory anymore. 5/5\n>\n> other people in the comments have struggled replicating this same bug from what i saw, but other people have reported that this happened to them as a kid\n>\n> it also seems like textures got carried over bertween the two. spore had these weird graphical issues (left i stretched back into shape but i cant tell what this is)\n>\n> and theres some ui elements here in roblox. this appears to be graphics_atlas~/NoGroup_ScrollFrameVerticalGeneric-00.png",
  "title": "learnt about an interesting tweet by twitter user Dynabroth:"
}