There are a lot of ways to fix this (like replacing the thumbstick with one from a more comfortable gamepad), but here’s what I settled on.
Originally, I didn’t want to make any permanent modifications, so I packed a joystick cover full of sugru, and smooshed it on top of the existing joystick, and let it cure for a day.
Because of the shape of the joystick cone, it couldn’t fit completely inside the cover, and rather than having sugru completely wrapping around the joystick top, it was only adhered to the top.
Despite that, it lasted about 7 months under heavy use (enough to wear down the
nubs on the cover) before falling off yesterday.
Since I was out of sugru (and didn’t want to wait another 24 hours for it to cure anyway), I decided to use thermoplastic (instamorph, polymorph, etc.) instead.
To allow it to fit in the cover and to adhere better, I removed the rubber tip from the G13. There doesn’t appear to be a good (read: reversible) way to do this,
as mine was both glued, and too inflexible to pull off of plastic shaft without damage, so I just removed it with a craft knife.
Like the sugru, I filled a new cover with thermoplastic, pushed it onto the joystick, and used a small pokey tool ensure that the thermoplastic wrapped around the top of the joystick (now flat), and let it cool.
Here’s the thermoplastic, having been molded to the inside of the cover.
I have sometimes wanted to run git bisect on all of the files in a single commit to determine which file caused a given issue.
While this isn’t supported by git (for good reason), it’s easy enough to fake.
This happened recently when I made a global typography change in a rails project, causing a feature spec (which depended on a specific
string format) to fail.
# Create a new branch, based on a working commit
git checkout -b bisect-debugging <working-commit>
# Apply the changes from the broken commit
git cherry-pick <broken-commit> --no-commit
# Unstage the changes from the commit
# Loop through modified files, adding and committing each# To include new files, you could also use `git ls-files -om --exclude-standard` for file in$(git ls-files -m); do
git add $file
git commit -m $filedone# Begin bisecting for your new commits
git bisect start <working-commit> HEAD
# Use the failing spec to determine whether this commit is good or bad
git bisect run bundle exec rspec spec/failing_test.rb:123
I’ve released Wheeler, an Open Broadcaster overlay.
Wheeler is designed to replace pedal cams (sock cams) in racing games for streamers. It displays configurable racing wheel, pedal, shift and handbrake input and plays nicely with multiple input devices.
Wheeler is priced at pay-what-you-want, but all support is appreciated.
After some trial and error (and error, and error, and error), I’ve managed to get DiRT Rally telemetry data to
display on a TM1638 display module, and have released both the arduino sketch I’m using and the python script used for communication here: https://github.com/Billiam/pygauge
The python script is also available as an all-in-one exe. You can download gauge.ziphere.
Here it is in use:
I started with X-Sim and this guide, but ran into a few problems. X-sim required Dirt’s extradata option to be set to 1, and didn’t seem to be aware of each cars rev limit. In the linked guide, the rev limit has been hardcoded to 9,500, which is pretty far off of some of DiRT Rally’s cars. The Use automatic maximum adjustment setting partially resolves this, but it won’t know what the maximum rpm until you reach it at least once.
X-Sim is extremely flexible and powerful, but is very configuration-heavy and felt like overkill for this project. If you’re already using X-Sim to drive your sim rig/gauges, I’d recommend sticking with it.
Additionally, if you’re interested in using this LED module for other games, including Assetto Corsa, iRacing, Project Cars and rFactor, check out http://batrako.blogspot.com/ instead.
An arduino. I’m using this one: dx.com $7.84 but I believe this one will work and is a bit cheaper as well: dx.com $4.99
(optionally) Some jumper wires: dx.com $2.96.
I just soldered wires directly to the arduino pins, but if you plan to reuse your nano for something else in the future, this may be a better solution.
Connect the Arduino to your machine. You may need to install these drivers to recognize the USB serial device: http://www.ftdichip.com/Drivers/CDM/CDM%20v2.12.00%20WHQL%20Certified.zip
Install the Arduino software. Here is a helpful getting started guide: https://www.arduino.cc/en/Guide/Windows. Download the TM1638 library and extract the TM1638 directory to your Arduino library folder (ex: C:\Program Files\Arduino\libraries).
Verify that you can upload sketches by uploading the blinky light Arduino example (see guide link).
You will need to connect arduino pins to the LED module. One for ground, one for power, and 3 to control it. If you plan to daisy chain multiple modules, you’ll be using additional pins.
Both the Arduino and the LED module pins are labeled on the PCB. Connect the Arduino 5v to the VCC input pin on the Arduino, connect ground to ground. I’ve wired Strobe 0, Clock and data to D3, D4 and D5 respectively.
If the TM1638 library was installed correctly, you should have a TM1638 menu in the Arduino app under File > Examples. Upload the tm1638_one_module_example sketch to verify that you can communicate with the led module. You may need to update the data, clock and strobe pins used, depending on how you wired them together.
In your DiRT hardware configuration, <Documents>\My Games\DiRT Rally\hardwaresettings\hardware_settings_config.xml, set the motion_platform udp enabled attribute to true and extradata to 3
Ran into an issue this weekend with httparty, and an API (mapquest) that was sensitive to query parameter order. Specifically, when batch geocoding locations, mapquest expects a query string like: ?location=foo&location=bar&location=baz, and will return geocode results in the order received.
I noticed the issue when an api call for a US city returned a result in Ireland.
Httparty has two methods of encoding query parameters. The default, rails-friendly, way converts
This can be disabled by calling disable_rails_query_string_format, which replaces the default query string normalizer with this proc
Different version of ruby (even different 1.8.7 versions) will sort the result of
differently. A sort was added at the end of the normalizer proc to ensure that the query string is consistent across versions, likely for testing. This works, but has the side effect of also shuffling the order of array value elements.
Presort query parameters to avoid surprises,
use an alternate proc for query normalization (I just removed the sort entirely in my app),
submit request as json (or other format)
or wait until it’s fixed upstream.
Httparty pull request can be found here: https://github.com/jnunemaker/httparty/pull/245
Recently discovered Chocolatey, which I’ll be using for basic software installation on new machines.
Chocolatey both suffers and benefits from its community-driven packages. While there are a large number of packages available, especially compared to similar windows tools, several packages I tried are were not functioning and seem abandoned.
My current install script and package lists can be found here.