Teej

What sort of flying are you doing when it crashes? I've not flown any of the missions/campaigns at all. My flying has generally been familiarization and a few weapons practice sorties. Totally unstructured but that's how I tend to absorb material. ;) The only crashes I've had in the sim have been when flying multiplayer and the host shuts down while I'm in the pit. Game locks up tight and I have to end-task it. I figure I don't want to "ruin" the experience of the game too much while it's still in beta. Hehehehe.

As anyone who knows me knows, I'm always game for a bit of semantic hair-splitting, but that's going too far for me. Yes, in one sense (generally relegated to compilers) that's what optimizing means. In a more general sense, and for anyone who lives outside the world of compilers, optimizing means making the best use of resources. Lots of things get "optimized" that have nothing to do with streamlining loops. :D

This game engine is weird. There seems to be minimal benefit to a 4xx card (in geforce speak) over a 260+...AT THIS TIME, and in these sims... GHz does dominate over cores, all else being equal. Between C2D / C2Q, the higher clock speed will probably prevail. However, an i7 at the same clock speed as a C2D/C2Q will outrun it. Based on a small sampling size in terms of # of people I've discussed it with...SLI/xfire seems to be pointless in the DCS engine at this point (at least in terms of frame rate. If you're driving additional displays, that's another matter). Well...not weird...just not optimized for top end technology (cores, sli)

... "Taking off 4 - 1 and 1!" "2!" "3!" "4!" "5!" "6!" "Taking off for the high show!" (snicker) "dude. He said high."

Having TARGET open will do absolutely nothing to DCS. I've done it many times. Running a profile may make your stuff not work right while the profile is running....but as soon as you 'stop' the profile, the stick should go back to working as default with A-10.

My CPU, OCed, stays below about 10C above m/b temperature in FC2 & DCS. Good enough for me. Current setting is 3.7ghz (23 * 160) with memory at stock 1600. Both sims are difficult to get below 60fps now. In A-10 with the takeoff training mission, I start out at 25fps on the runway...as I roll down the runway it's up to 50 around the time I lift off. I can fly back down the batumi runway and not see under 50. Certain angles will drop to 40 if I'm touching dirt with the retracted wheels. High tex, med scenes, low water, med distance, 1920x1200 full screen, 16x aniso, 16x AA That's with a single GTX275 card.

No particular reason. Not sure it would've made much difference for me. Sitting here at 3.9ghz running windows apps, I see: System: 31C CPU: 24C Cores are all showing under 40C Maxed out the cores all stayed below 70C. They barely rise at all in FC2. Cores all below 45.

I'm running an H50 cooler on an i7 950. I've really only just begun OCing and am looking around at the best way to do it. Right now it's running at 170 * 23 = 3.9xx but needs some RAM tweaks. In FC2 I'm getting high frames but more microstutters than at stock (133 * 23) w/ the ram at a more optimal speed. Running 4 * Orthos (1 w/ memory, other 3 for CPU) didn't get any core over ~ 68 and the "CPU" temp stayed waaaaay below that. like...50C....) Still work to do. Heh.

Don't neglect the time needed to grow the trees. ;)

Had some issues w/ FC2 & TIR recently...thought I'd throw this out there in case someone else runs into it. I recently built up a new machine and all was well. Have a TIR4pro, using TIR5 software. Since the last time I flew FC2, I had: Uninstalled our VTB mod & installed the VFAT race mod Reversed the above Threw on the beta TIR software hoping to get x64 TIR (before Wags posted up) Then when I tried to fly last night w/ VTB crowd, if TIR software was running (any...tried several un/reinstalls) I could not unpause or do anything else. Worked fine without TIR running. TIR worked fine without FC2 running (shrug) Sounded a lot like the posts of problems with Newview (whatever that is). Although copying over a backup FC2 folder might've helped...I didn't have one (I do now...heheh...). I had to deauth, uninstall FC2, reinstall FC2 and reauth. All is working now. (shrug) keywords for searchers: fc2 can't unpause keyboard no response trackir

Wouldn't it need to be slightly cheaper, too? :)

Back in the day I burned through 2 X-45 sets flying choppers in the "desert combat" mod for Battlefield 1942. They were "cheap"...but they creaked and groaned, buttons only worked half way, it has the world's tiniest spring (figuratively) on the rudder rocker, etc. That was about the time I started shopping for my Cougar and FCC mod....and then got back into Falcon with AF.

Glad it's working. I'm pretty confident you'll be able to control the lights eventually. They are awfully bright compared to where I have my MFD lights set to. :O

I don't have any MapKeyR commands. Try this: MapKey(&Throttle, FLAPU, PULSE+Flaps_Up); MapKey(&Throttle, FLAPM, PULSE+Flaps_Up_Down); MapKey(&Throttle, FLAPD, PULSE+Flaps_Landing_Position);

Didn't fly one stock enough to form an opinion. Bought a used one...5+ years ago (sn 4491) and had an FCC mod in hand before I got the actual stick. It had a spiking throttle pot in it when I bought it and also had that replacement in hand before I got the stick. Flew it on a regular basis with no other changes until I started flying Warthogs back in May. Lots of Falcon time in it, along with VTB time.

No hang, runs in 32 bit...but no blue in 64 bit and no TIR section in the options.

Don't lie to us. We know you're just gonna meet up at a "coffee shop". :D Well, at least that should tell us if it's certain units that have issues...or certain pilots. (And I mean no insult by that - perhaps there's something that just plain bugs Frazer more than it does me, LD, Grab, Yskonyn and MTF.)

Have you installed the latest (RC2) TARGET?

Yup.

No arguments there. But you are one redneck russkie. :D That's awesome man. :thumbup:

That so needs to go on http://www.thereifixedit.com :D

If I had the tricks to rebooting your stick, I'd let you know. I've not been told of any ways around it. Have you contacted TM? Page 1 of the doc for the firmware updater states "If after many attempts the devices are still not enumerated correctly, please contact Technical Support which will guide you through the necessary steps." My advice to you would be limited to unplugging the sticks, doing a full power-off shutdown (actually disconnect from the mains) of your computer and restart....plugging the WH parts back in once it's booted up. As to the 'risks'...well...this is just my interpretation, but since TM released this publicly I personally would interpret that as acknowledgement that there's a problem with firmware corruption on units in the wild. As such, since there's no warning limiting it to certain conditions/OS/motherboards...while you may have had a problem (and I'm sorry to see that)...there's a very real chance that the average person has better odds updating their firmware now rather than waiting for a problem. But that's just me spitballing. I agree it would've been nice for someone to post up and say "Hey guys...this is out, if you wanna try it go ahead" or "Please run this ASAP" or whatever their internal feeling is on the issue.

You realize that by the time someone "needs" this (by your definition) it will no longer work...right?

Make sure you don't have any flight controls mapped to axes on more than one device in A-10. Classic example is with my Warthog and pedals. The system doesn't know the pedals are "pedals" and by default will map the 3 axes (rudder & toe brakes) to a completely unusable set of axes...one of the pedals gets mapped to pitch until I unmap it in FC2/A-10/whatever, for example. Aside from that, no, there's nothing about the Warthog that would "interfere" with anything else any more than any other controller. Remember - it's just a plain ol' DirectX input device. The stick doesn't have any special functions or programming.

Don't have a G15, but I'm not surprised the sticks work plugged into it. I'd be concerned about the power if I was trying to charge something or use USB powered "toys" from the keyboard...but operating the sticks, even with LEDs, should be extremely low power.