Reksi-Erkki

Just to keep his legacy alive... he was such a great tutor to us newbies, and made some awesome music as well. RIP Blooze.

I have this problem as well... have to open the base tomorrow and check the wires. And apply some grease while I'm at it.

Yeah, 127.500MHz FM it is.

Blooze will always be in my mind. What a gentleman. And his music will live on.

i7-2600K from 2011 @4.4GHz because I don't want to stress the old lady too much... with the NZXT Kraken I've run her stable at 4.6GHz, but the performance gain is minimal compared to the almost 10C temperature rise. Meanwhile, the GPUs have changed from HD6870 to 2xHD6870 to GTX680 to GTX980. Sandy Bridge was - and is - indeed a very good processor family.

I had a similar crash with the latest alpha, but only once. Flying at the VA NTTR server. Their missions tend to love RAM to death... had to upgrade from 8G to 16G mostly because of that in the 1.2.x days. But 16 gigs is really a hell of a lot of memory; I'll post a log if it happens again. Now I'm all busy watching ladies play rugby.

It's a bug - the key to toggle the controls indicator (RCtrl+Enter) doesn't work in 2.x right now. See http://forums.eagle.ru/showthread.php?t=168816

Mine are the defaults (linear, 100% range) for everything except the Gazelle. She's so very very sensitive (in the open Alpha, at least), that I had to reduce the range (to 70%, I think), and apply a bit of nonlinearity (16?) for both X and Y. I have a 100mm extension for the stick, and it sure helps a lot with the helos.

I got mine from a local electronics supplier. http://www.triopak.fi/fi/tuote/huolto-ja-mekaaniikka/laitekotelot/supertronic/PP12N/muovikotelo-78x40x21mm-musta

Yep, ABRIS is definitely 1°1' too much to the West in Nevada. Can't say if the bug was introduced in the latest update, or earlier.

I just tested my G940 pedals, they work OK. At least the calibration values looked smooth enough, and I seem to remember the pedals worked quite fine in the sim as well. The pinout is different from the G25/27 pedals, though, so you'll need something like this between the pedals and the Bodnar cable. In the image, the pedals connect to the right, the Bodnar cable to the left. Here's the pinout for the converter box; those are the actual numbers printed on the connectors themselves. I double checked the connections, but the usual disclaimers apply... EDIT: my pinout seems to match your images - if you swap GND and +5V, the axes will be inverted, but that's not a problem since you can adjust for it in the sim. Pedals Bodnar 1 black 6 2 orange 2 3 green 3 4 yellow 4 5 red 1

I've noticed that assigning buttons or keys sometimes requires quite a few clicks, but I haven't seen any menu slowness.

I got the ILS audio signal and moving needles in the Huey yesterday, but didn't actually try to follow the path. I couldn't find any VORs, though... but there's probably something I didn't do properly.

RIP Blooze. He was a good man.

Sweet!

8/8 cloud coverage during the eclipse.

After the last update, I had to delete the Saved Games\DCS\Config\Input\C-101EB folder and recreate all assignments. Even the ESC key didn't work, I had to Alt-Tab out of the sim and kill it by fire. There are quite a few other controls that cannot be assigned, including labels, kneeboard, eject, engine start & stop, GPU connection... bank, pitch, rudder... Yeah, it's kind of messed up at the moment.

That's what I did... the handle clicks a microswitch three times. It's not pretty, though :music_whistling: I'm planning to use an AVR Tiny25 to pull the Bodnar board input down, so any old switch could be used.

At least I've used it in the Ka-50 campaign.

That's Gelendzhik... the Novorossiysk airport doesn't exist anymore, at least not according to Google maps :) I checked a few airfield coordinates (from the F10 map, using the airfield icon as reference) and Google maps places them either on the runway or very close. BTW, I just completed my Excel sheet for exactly the same purpose... the calculated distances are within 4% of the measured ones, and some of that is probably caused by my inaccurate measurements - I didn't bother zooming in so that I could have used the exact runway centerpoints. It looks like the acos formula would give better results, though. I calculated the average bearings between the initial and final ones. They seem to contain an error of five to seven degrees - suspiciously close to the magnetic deviation in the area! I wonder if the F10 map distance/heading tool actually shows magnetic headings?

Military prop/turboprop trainers with good avionics/navigation suites might be nice... T-6 Texan II, perhaps?

I see what you did there :lol:

Just run the multiplayer client, log in and find it from the list. Highly recommended!

Don't know if DCS can be configured like that, but have you tried any joystick emulators? A few links: http://www.makeuseof.com/tag/turn-your-mouse-into-a-joystick-for-pc-gaming/

I experimented a bit quite some time ago, but never got the touchscreen I ordered... The idea was to use a custom web server (http://desrat.lightning-bolt.net/TouchDown/) on the PC running the sim, and a set of pages with buttons / other controls that would, when pressed, generate a keypress to the sim. It did work in testing, but using a mouse wasn't at all practical. I also had some problems with Java(script) on the RPi. I've also thought of using Helios with RPi2 - hardware is in the mail, waiting for Microsoft :)