Lava

Lightning, that works pretty well, people can get GPS fixes in airplanes. I have a wrist-mounted GPS that works perfectly in a car, under trees, clouds, etc. Haven't tested it in a plane but I've read of people who have. I'm sure a slightly larger model with maps installed could be used in a fighter/bomber's canopy. The question might be if such electronics are -allowed- in the cockpit. Electronic emissions concerns? If A-10 pilots use binoculars, a GPS might be a valuable addition (in real life). I know I miss the ABRIS!

I noticed the effect in BS as well. FC2 is a bit more pronounced. Setting autopilot and zooming in closely on the monitor helps boost usability and FPS... but it's still annoying. I think it's because the engine suddenly has two windows it has to render scenes in - the normal window, plus the shkval/tv monitor... so, twice the workload at least.

In the G940 Throttle column, Joy Y corresponds to the Left throttle, and Joy X corresponds to the Right throttle. They both work, no patch needed. In fact, the G940 seems to work well in general for FC2, so far.

This says it all! I hesitate to touch BS again until I have the time to re-learn it, but I think FC will be easy to put down for a week or two when I get busy, then pick right back up.

I tried it as well - my tracks on restricted view servers only had the airfield view.

FC2 just checks for a previous installation of LO/FC, no disk required. Since you have it installed, the answers to 1 and 3 are "Just install FC2, it should work". I don't think any settings are moved from LO to FC2. They changed the config system to match DCS:BS, so things are all different. Shouldn't take you long to pin down video settings at least, and several people report FC2 runs better (?!?) than LO.

I gave up and started learning SEAD with the SU-25T. It has nice, shiny radiation-homing missiles!

I saw a quote in another thread (have no link though) from either an ED member or tester that stated FC2 does not require LO etc except during install. There's a check done during install to see if you have LO and FC (not sure if it's one or the other or both), but after that you do not need LO + FC. Also, uninstalling LO + FC removes the starforce drivers, which is generally considered good. (edit) Figures, official word gets posted while I was typing this :)

Hmm, thanks! Apparently I was so careful around buildings I never found out they were solid :)

Hello everyone, I was flying an SU-25T earlier and I slammed into a power line tower, crashing my plane in a rather terminal fashion. If I remember, in DCS:BS the buildings weren't solid. Did this change? Or is it just the power line towers? I'm NOT meaning to start a flamewar or begging for solid buildings, just curious how FC2 implements them. It'd be wonderful if they were solid. I can't hop into FC2 right now and try it out, at work.

If you bought the game, you can find the documents and key reference cards in your install directory: LockOn Flaming Cliffs 2/Doc

I dusted off my G940 for this. Seems to work pretty well. The stick moves with the autopilot, which I like. Had an odd problem changing the radar scan elevation on a hat switch; it would only issue one keypress even when I held the switch. So, I just set it to a high repeat rate in the options for those commands. Other hat switches and commands don't have this problem. The separate axis/commands for the different aircraft within FC2 will drive me nuts. Having to enter axis info for each aircraft is a pain in the butt, trim and zoom in particular. At least 96% of the commands are similar across aircraft. That, btw, makes life a lot easier for profile programming. I'm doing most of the control setup in the profile.

Thank you ED! Been lots of fun flying this weekend, got all my gear set up and planning to re-learn BS for the eventual patch!

Did you try recalibrating it? Mine drifts a tiny bit from time to time, since I calibrated it, but a quick tap on it stops the drift. (edit) Actually I end up using the HAT below the mini-stick for SKHVAL most of the time.

I wonder if it didn't explode because it broke in two on impact? That sure looked like an explosion coming when it was plummeting from 400 meters @ 270 KPH :)

Alec, this crash started after Logitech patched in shift buttons to work across all devices. Didn't have any problems before, and at least one person has contacted me via PM with the same problem. What OS are you running?

There's a survivable crash, and then there's a crash you can walk away from. BS currently doesn't model the trauma to the pilot from an incredibly violent crash. Instead the copter explodes. Hey, maybe you got thrown free and survived with 50% of your body burned and spent the next year in the hospital and the rest of your life crippled! Or maybe you got thrown onto the stick, or the HUD shattered and glass flew in your face, or debris slashed open your chest. Instead of ED modeling all that, I'm happy with the compromise of exploding the chopper when, in real life, they'd say "This chopper is completely useless for us now." You can think it's 'survivable' all you want. Ask yourself, though, how many real life pilots would have ejected earlier, fearing for their lives? Or perhaps not even pulled that maneuver in the first place :) All it takes is one bad injury and you can never fly in the armed forces again. Think of it as "BOOM! No SANE pilot would have pushed it this far, and this is too unpredictable to accurately say if you will survive or not!" edit: Perhaps the most fundamental reason the game doesn't have more accurate crashes: Where would you get the data from? How do you know it's accurate? You'd need a lot of data to put together an accurate helicopter crash model. A poster above pointed that out in a joking format.

I still have a computer-crashing bug in the Logitech software crippling my shift-button capability. When a shift button (S5) on the stick is pressed, and a throttle button is pressed, a hard computer crash results. Vista x64. Anyone else?

Best -practical- tip for me (aside from stuff like upgrade) was setting Shadows to 0 in the options.lua file. ["shadows"] = 0, Really did wonders to keep my FPS above 30 and towards 60.

Twoarms, in my wholly subjective opinion, it's great, slight software problems aside. Read any of the dozen G940 threads in this forum to form your own :)

I haven't done much in TIR's software. What are you guys doing with the curves, increasing the angle to make it respond faster as the input is more extreme?

Yep try taping over the sensor, it's the upper hole on the right side of the stick, just above a screw-hole.

LOL I think we have a winner!

Hm, out of curiosity, do you have a basis for comparison aside from the way it looks?

The TrackClip Pro is a pretty useful gadget. If your wallet is really tight, perhaps go for the 4 and the Clip. No hat to wear, just the usual set of headphones for me.