@kdfrawg I recall the last time I looked at stuff for Flight Simulator X, it was almost impossible to lay hands on. Particularly the custom radio panels and throttle quadrants.
Expensive hobby, too. You can have many thousands of dollars invested in that stuff.
// @streakmachine
@streakmachine All of those things sound more appealing to me than software development.
@streakmachine The new release, Horizons, isn't available for Mac and I don't think they will support it going forward. It's just too graphically intensive for the Intel HD stuff Apple puts in their machines now.
EDIT: You can play it on XBox One so there's a cheaper alternative than decking ourt a gaming PC, at least.
@streakmachine I don't even want to think of the time I wasted in the original, 1984 version.
All I can really do in this one is exploration as I can land on a planet and switch to doing actual work. I take off again when I need a breather or have long builds going.
My destination will probably take months in real time to reach at this rate and that's fine. :)
I find it relaxing.
Oh..Not dead.
Office has been hectic and my home-time has been spent with a vim session on RHEL 6 on display #1, Microsoft Code on display #2 and this on display #3
Porting old code to modern Linux, working on a new release and departing on a 65,000 light year journey (plus doing things like mow the yard, fix the screen on the porch, etc) have left little time for chit chat :)
@nitinkhanna 3.2 Ghz i5, 16 GB RAM, GTX-960, Saitek X52 throttle and Stick, TrackIR head tracker.
EDIT: Gaming sure got expensive. Used to be "Commodore 64 + Atari 2600 Joystick you didn't ruin by playing Decathalon"
@nitinkhanna Because they are barely capable of turning a computer on.
// @kdfrawg
I've done the following..
#vim Makefile.am
Enter things like -lm -lstdc++ -lssl -fpermissive and such I've not needed in the past
:wq
..more than I care to think about, today.
@kdfrawg The only trying part of the day was talking a French-Canadian through mounting a logical volume in single-user mode and running fsck on it.
# vgscan —mknode
# vgchange -ay
# fsck.ext3 -y /dev/VolGroup00/LogVol00.
Relaying that was a lot harder than it looks.
Edit: Having them read the output of the second command off so I knew what to have them type in the third one is the bugger.