Karl Spackler

Same. On a 3770k processor and a GTX1070 lightly OCed.

That's all I'm really doing. But the stuff is so good. There are so many great instrumental players out there that will never get a look because there's really no money in that genre. The stuff is basically a vaginal drying agent, and when you follow the money in the music industry, that's where it leads.

More modern prog metal guitar... And this weird Japanese thing which is a fairly amazing modern proggy jazz in two chords...

SPOILER DISCUSSION CONTINUES OK if it's time to pick it apart after action style, cool. - Reverb, delay and pitch shifting. "trade-secret effects" my dyin' ass LOL - I do agree with a lot of the nitpicks. Klaiber's list of gripes alone equals an additional year and 50 million in fixes I especially agree about the fighter sequences. Chris Nolan could have gotten any number of people to consult on how to make these fight sequences more sporty. Instead we saw a lot of Han Solo maneuvers - drifting a little to the left, for instance. As I sat and watched I had to wonder if the guy getting shot at was even aware of the fact that he was getting shot at. In games we take this for granted but even after flying measly 160 and 180 hp Cessnas and Diamonds I often wondered if I'd even notice rounds going by if they weren't tracers. I know how I abused flight characteristics in IL-2 and even with those primitive flight models I realize how easy it must really be to snap stall those planes. Couple that with a lot of these pilots only having 30 hours in Spits flying against Germans with combat time against the Russians plus them trying to keep from running out of gas. Still they could have shown us how hard these guys were working when maneuvering against each other. Instead they portrayed it as this ethereal, fluid quiet world when really it's lots of G, gas and oil smells and cranking your head around to check six and making lots of position calls on the radio. The beach landing scene was exasperating to watch. Why ditch on the beach? Ditch in the water right in front of the rescue fleet for the love of all that's holy! If not that, then ditch on the beach toward the direction of the friendly force not the enemy force! He appeared to have plenty of energy to think about it for a second and then made the worst call in cinematic aviation history. Why would you give yourself to the Germans like that? And yeah if landing on that surface, landing gear would have caused the inevitable divot flip cockpit smash and he should have been paste. No flaps, no gear, nice and easy, bleed the speed off until you're slow, let it fly onto the sand and have it stopped right in front of Admiral Whatshisnuts just in time for tea would have been just the ticket.

That approach to character was very deliberate, and in my opinion for this story, an astute choice. Here's why: The events depicted were experiences shared by hundreds of thousands. How do you home in on one or a few protagonists, and in the case of historical events, specific people? Do you create 'composite' characters and give them names? How far do you develop those characters histories? How much time on screen do you spend on that? Making up representative characters to tell the story of hundreds of thousands of equally heroic people that remain nameless? You leave names and personal history out of it entirely. This seems to work especially well for that particularly British stoicism. For instance, the pilot that Tom Hardy plays is every pilot in the war. Instead of tagging him with the name of a real-life pilot captured that day, I sat in the seat and wonder if that was maybe one of the characters from The Great Escape. Maybe Ashey-Pitt or Cavendish. Those grunts on the beach are all named Smith. They could have been anybody. I thought it was a novel approach to a difficult problem.

Maybe it's a situation where you can decrease the noise gate? Possibly you're losing the first syllable to the software gate and that's causing the system to throw out the command. Try increasing the mic sensitivity/lowering the detection cutoff threshold if there is such an option. Mind wandering (because I've been doing calculus for the last 10.5 hours (minus a lunch break, so the best thing to do is start typing on the internet, right?): This is why you sometimes hear pilots with ANR headsets preface phrases with "and". They're getting past the noise gate, which doesn't interact with the PTT. Thew other reason is that some confuse what PTT actually stands for. It's "push-to-talk" not "push-to-think". They key the mic when they know it's their turn to talk (to ATC or other aircraft) but they didn't plan or know what they're supposed to say until the moment comes. Students actually get stage fright when they key the mic.

LOL you know I mean a "OMG HOW BADASS WAS DUNKIRK WHAT" thread. Forgot about that other thread. Year old dead thread necromancer is not a core skill set.

Exactly what made it so good (for me). All the extra baggage that would normally be there in a WWII flick from the 50's and 60's (The Longest Day, Devil's Brigade, and so on) or even today (Fury) is taken out of the picture (excessive character development, chatty dialogue, heavy handed feelings/emotions, coming of age, conflict resolution, what happened to lead up to the moment the movie begins, and so on) and we're given the people, the full weight of the situation they were in and how they dealt with it. We're inexorably forced deal with it with them, deftly enabled by maybe one of the most tense soundtracks ever, and a pace that kept me in it the whole time. I've become pretty jaded about movies, especially war flicks, and the this film was effective. Usually there's some point where my mind wanders or there's a part in the middle act where I become aware of my bladder. Not so this time. There's not a wasted minute of the 1h46m run time.

The movie was everything I'd hoped it would be. I will be buying it on iTunes the minute it comes out, despite the fact that I know it'll be on HBO 10 times a week and on demand.

Warthog is great. That said, everything breaks eventually. I had to replace my Hog joystick two years ago because I tried to update the firmware and I bricked it. I replaced my throttle block two months ago when the USB buttons on the (EDIT) right stick no longer functioned. The right throttle HOTAS is critical as it has all the hats, boat switch, china hat switch, speed brakes, two directional hats and the HID mini-mouse. The left one just has the lights and an autopilot button. Original purchase was when it first came out (Fall, 2010). I'd say I got my money's worth out of the original set and I wouldn't use anything else if I had the choice. Here's to another 6 years!

Further refinement: All this does is force the pixels to x2 if the software tries to downgrade it. With DCS you have that slider that goes from 0 - 2.5. If you set it to 2.5 this should theoretically downgrade it 2. However, it may be placebo effect but I really feel like I saw an improvement sitting in the A-10C cockpit. The environment outside the cockpit on the other hand, not so much. I don't think this is Oculus' fault. That's on Eagle Dynamics. Elite Dangerous does not have a pixel density option, only resolution options that only apply to the main screen, and when running VR really only affects the size of the window on the screen (if running in windowed mode). Here I think is where this tweaker functionality has more value. Lastly, the changed debug value is not a permanent setting to the video card (Brit, like high speed data loggers, autopilot tweakers, etc - yes I still remember LOL). You have to do this prior to every session.

In the quest for more clarity of image in Oculus Rift VC1 I did some google sleuthing and found this: https://uploadvr.com/super-charge-oculus-rift/ However, this: https://forums.eagle.ru/showthread.php?p=3196626#post3196626 Long story short, the debug tool is already installed per the ed forum thread post, so don't bother trying to install any SDK's, it's unnecessary. Change the "Pixels Per Display Pixel Override" parameter from 0 to 2 and hit enter (you know it's set when your 2 changes to 2.000000) I recycled the Oculus software that starts up automatically, and rechecked the debugger to confirm it was set to 2. I did immediately notice improvement in E:D and the A-10C. Much less fuzzy. I will test some more after GoT.

Been into the proggy metalz lately. Plini: Intervals Plini and Aaron Marshall (Intervals) Sithu Aye

You should be on a 64 bit OS at this point too. If you are, 32 GB is the max. Lots of headroom, won't have to worry about RAM for a good long while. Look at your motherboard specs and see what the fastest memory is supported as far as DDR level, CAS latency, channels, voltage, etc.

This guy absolutely ruled.

This week is all Allan Holdsworth. He passed on Sunday. RIP Allan. You were a genius. Caution: jazz fusion guitar content.

If there's looping Command and Conquer-like music that would be siiiiick braaahhh LOL

I don't even see the code anymore...

Must've been even more difficult considering the extra weight of and physical space needed for his GIANT BALLS. https://www.youtube.com/watch?v=oEPJzEpWJTc

Requires Chrome I believe. 360 panning on YouTube doesn't work in Safari https://www.youtube.com/watch?v=ZQ9m3iaTCMY

Sorted. Might delete this thread so no one gets the wrong idea just from the title.

Well I just reinstalled 1.5.5 and still having the same problems. License/key issues with the MiG-21bis, TrackIR not showing up in the list of devices in controls. That's even after uninstalling everything, cleaning the registry with ccleaner, deleting old install files.

The trick is to be re-trimming as you make adjustments. The thing I do (and I don't really know if it's a legit technique) is hold down trim as I make my maneuver, heading change, whatever, and when I'm done and the helicopter is doing what I like, I release trim. Keep an eye on those little green lights. When it's time to be super dynamic I neutralize the trim and fly it by hand, no trim at all. You, know, like a helicopter.

I found that when I tried to run 2.0 I got the same litany of issues. It would makes sense that what I was seeing was the module keys got corrupted (they are shared by both installs) after the update. Shouldn't have happened, but that's life in the big city.