gaming, xbox comments edit

I bought the Xbox 360 premium package that came with a wireless controller. That same day, I bought a second wireless controller so Jenn could play. The controllers come with battery packs that take two AA batteries.

The batteries last for several hours, but of course, I was in love with the new gadget and played until the batteries ran out. That’s when I saw the rechargeable battery packs and the quick charge kit, which I also bought.

Something I noticed, though: When the AA battery packs were in, the controllers both behaved as expected. When the rechargeable battery packs were in, the controller that came with the Xbox 360 would turn off fine, but the controller I bought later would stay on - one of the LEDs around the Xbox Guide button would stay on faintly. Sometimes I could remove the battery pack and put it back in and the light would go off, but later it would turn right back on.

That worried me - if the controller won’t turn off, it’s going to just eat my batteries and I’ll be constantly charging just to stay ahead.

I called Microsoft support about it this morning and it turns out this is a known issue. Some controllers just leave one of the LEDs faintly on. They claim it won’t affect your battery life and you should just ignore the light being on - as long as the controller functions properly otherwise, the light being on shouldn’t be a worry.

I don’t see that documented anywhere. I found a forum where other people are having the issue and it sounds like it’s not just me.

Anyway, if it’s happening to you, Microsoft says it’s a known issue and it’s nothing to worry about.

I’m just coming across way too many cool things while cruising the morning news, so I’m going to share in a sort of random tech news aggregation thing.

First, it looks like Mark Miller’s introducing some cool stuff for the next version of CodeRush - Dynamic templates sound pretty awesome. I can’t wait for that.

Next, there’s an entry on the PowerShell blog discussing the grammar of the Windows PowerShell. The geek in me smiles while the rest of you look on in disgust.

Moving on to gaming, it looks like the stupid bat-a-rang controller for the PS3 is no more. Sony has released the real new PS3 controller. Looks a lot like the standard PS2 “Dual Shock 2” controller, but runs on Bluetooth and can detect motion (sort of like the Nintendo “Wii” controller). Of course, the new PS3 controller doesn’t have any vibration feature the way the other controllers do because it apparently messes up the motion detection. Hmmm. I guess that wasn’t the hugest part of gaming, but it did add a little something.

For folks that aren’t into that crazy Wii controller, I guess there will be a “Classic controller” that you can use. Just watch - you’ll have to have both controller types because some games won’t work with one.

Oh, and the Halo 3 trailer is out, so check it. It rocks. (My dad actually sent this to me before I got to it. Dad is stoked and he doesn’t even own a single game console. I think he’s just found his reason to get an Xbox 360.)

Okay, I think that’s it. For now.

downloads, vs, coderush comments edit

The new version is out with a few bug fixes:

Fixed rendering issue with table lists being wider than the window.

Fixed rendering issue where generics didn’t display correctly in syntax preview.

Updated minimum requirement for CR_Documentor to DXCore 1.1.58. Needed for syntax preview.

Cleaned up icons in the preview window toolbar.

Added CR_Documentor to the DXCore “About” box.

Go get it!

net comments edit

Greg pointed me to this pretty cool all-in-one API reference site. If you’re a developer, you’ll want to check this out: ~Got API?~

Update 2/1/17: The site has apparently gone out of business. Link removed because it turned into some weird porn spam thing.