Crysis 2–weapon stuck in semiautomatic mode.

So I was playing Crysis 2 and hit a random button on my xbox controller and my weapon went into semiautomatic mode. I could not for the life of me figure out what I had done or get it to switch back. Apparently I’m just dumb but it was so frustrating I tried to search google but came up empty.

Turns out later I discovered it was the “under barrel” option and that you can switch firing modes with the left d-pad.

So if anyone out there is as dumb as me, that’s how to get your Scarab out of semi-auto mode.

Snow Leopard Time Machine Tweaks

Sparse bundles created by Time Machine in the latest versions of Snow Leopard are created slightly differently than they used to be. It used to be that Time Machine would create a sparse bundle with a name like “machine-name_001122334455.sparsebundle” where the “001122334455” part was your main ethernet port’s MAC address. Now it creates just “machine-name.sparsebundle”. So how does it associate a machine with the sparsebundle?

Well, it turns out they added a new file inside the bundle. Now, alongside “Info.plist” there is a new file called “”. Inside this file is some info:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "">
<plist version="1.0">

The “” is where the MAC address is now stored, but there’s one other extra field: “”. This value can be found by launching “System Profiler” (hold down the option key while selecting the Apple menu to get there quickly). On the first page (titled “Hardware Overview”) is something called “Hardware UUID”. This is what goes in the HostUUID field.

So if you ever need to create a Time Machine sparse bundle from scratch, you’ll need to make this file and fill out those 2 fields. There are some other fields in there but I have no idea what they do. I think they have to do with when “fsck” was last run on the sparse bundle and whether or not the bundle is valid, but I haven’t explored it yet.

Last Modified on: Dec 31, 2014 18:59pm