Teej

Heh. Which vid? I've seen a couple of vids out there with real world radio chatter dubbed in.

Yes. My Droid will keep charging in S3 state. Plugging it in or unplugging it will pop the computer out of S3 also. Gotta see if I can change that.

I don't think you can narrow it down like that. There are hundreds, if not thousands hooked up to a variety of motherboards and we only know of somewhere around 10 people, give or take a few, who have had problems. You name the situation and I've done it to mine...unplugged, plugged, PC off, PC on, USB hub, motherboard port, USB2, USB3...mine's seen it all. Some have had problems, but I don't think there's any actual indication what makes the problem more likely/less likely...and there's certainly no evidence of anything guaranteed to make it fail or not fail. Fly it. Have fun. If there's a problem, they'll take care of you.

OK...since I've commented before on the fact that my throttle lights shut off...I did a bit more putzing today and stumbled across this little tidbit... My throttle shuts down when the computer does (or goes to S3 sleep)....but only when plugged into a USB3 port. It doesn't go dark when the keyboard/mouse do (plugged into USB2 ports)...but only when the system actually "shuts off" (fans quit). This is usually several seconds after the KB/mouse go dark. Plugged into USB2, it stays lit like the holiday lights.

Heh. I should look into whether I can do something interesting with my new Droid. :D

Did you get a white screen for several minutes the first time you launched it? If yes, it applied. If not...no. If that's not good enough...just wait a few days or so for B5.

Any sounds, "good" or "bad"? Quick flash of the 5 LEDs when inserting the plug? See any change in windows game controllers when you insert/remove?

I was amused by the fact that it looked like one continuous sine wave going across all 4 cores...especially 2 seconds before I took that screen shot when cores 0 and 1 were more closely lined up. Look across from left to right - it's like you could draw one continuous line....

re: trackIR not detected after 5.1b2 I had this issue as well. In my case r/r from same port didn't do it. I plugged it in to a different port and it reloaded drivers...then moved it back to the original and it continued to work fine. (reason for going back - normal port is on monitor. Used port from m/b to get it to redetect but that's inconvenient for normal use)

Heh. the 'big white screen' is putting a load on more cores than the sim itself does. :D dahell? Why is the load spread across 4 cores like a sine wave (was even better about 2 seconds before I took the screenshot...)

Do you mean your "HOTAS Warthog" has lost its default profile? That's not possible. If you're not running TARGET to set the stick up from DCS (and you really shouldn't be) then the "default profile" is 100% contained within DCS. So the patched DCS may well have reverted some changes you'd made but the fix will lie in tweaking DCS, not the TM Warthog.

I had sent him some of my thoughts a while back (days, maybe a week) but was just working on the thing you pointed me at, LD.

Dunno how they do with shipping up to the arctic, but newegg has that card, Mower (470 SC) for $250 after $20 MIR...like ~ $8 shipping here in the states. Again, dunno if they screw ya sending it up there.

See, that's just full of crap. The worst thing for electronics is the power on surge and heat cycles. A "surge" in the mains _shouldn't_ get past the power supply, if you have a decent surge strip and power supply. Kinda depends on what your target audience is though. For home users that use a system frequently (daily), the more it's left on, the longer (calendar) it will last. Fewer heat cycles = fewer chances for a drive/fan motor to get stuck and fewer times the motherboard heats/cools stressing solder joints. The problem with that in an office environment is if everyone leaves their systems on, not only is it wasting a ton of power but then when you have a power outage, you suddenly have 30 systems that won't power up instead of 1 every week or two.

I'm not sure what the deal is. I know theoretically there shouldn't be performance difference, but for a while I was seeing one, running 32/64 back to back. I used to gain 3-5fps on 64bit. I no longer do.

Well I was about to tell you where it was but apparently I didn't have to do that with A-10....or I did the equivalent and forgot about it. If you look in (game)/config/graphics.cfg about 20-22 lines down you should see a line referencing 'sync'. 1 = locks max FPS to your refresh rate. 0 lets it float. At '0', I often see 100+ (obviously not looking over an airbase full of jets, but you know what I mean). With it '1' I never see over 60, except briefly as it compensates. Thus, it keeps the GPU from running hot needlessly.

Also...it looks like other aircraft are the chief culprit at this point. I created a mission for practicing some weapons employment based out of batumi and my FPS pegs at 60. Drop a few F-16 on the ramp and the FPS drops to around 50. Change those out for A-10 instead and bam, goodbye FPS (down into the 30s, like the t/o training mission)

@power: I never mentioned it in this thread, but I have in others -I set maxfps to 60. There's no point in trying to render faster than the refresh rate of my monitor (2408 WFP)

Not a problem. As to AF...well...I'm pretty sure it benefits more from multi cores than the DCS engine does. As for the graphics...of course it's not gonna tax current cards. The graphics engine is really a mix of 8-12 year old code. Despite its faults, there's still nothing that can touch AF for online campaigns. You can get better looking single player setups. You can get more feature packed multiplayer TEs. But stable, flexible multiplayer campaigns? No competition. Put another way...there's girls you date...and girls you marry. :D

To find your most severe bottleneck...I'd suggest the following. Download/install/run MSI Afterburner (Yes, even if you don't have MSI video cards). It will graphically show you GPU utilization and video memory and a few other things. Leave that running. Now fire up windows taskmanager (start / run / type 'taskmgr' or you can select it from ctl-alt-del ). Put it on the 'performance' tab. Now start A-10 and load the 'takeoff' training mission. Don't throttle up, just unpause and sit there at the end of the runway basking in what may be a slideshow framerate. Let it sit there for a good 30 seconds. Then alt-tab out and look at the utilization graphs (CPU, GPU, GPU memory). See which one is pegged. Though to be honest I'm not sure how some of that might look on SLIed cards - I've never run an SLI setup so maybe someone else can chime in and improve my suggestion here. Once you've done that and taken some notes, alt-tab back into A-10 and actually take off and fly away from batumi a bit. Preferably over land. Note your framerates there and then when it seems it's hit the highest number it's going to hit (when actually looking at ground and not sky/water) alt-tab again and see where the above utilizations are. That should give you a pretty good idea whether you are currently CPU or GPU limited. Of course, fixing one may suddenly reveal a weak spot in the other. Hard drive speed / SSD would tend to help with stutters more than FPS. And keep in mind...this _IS_ unfinished code. Optimizations will be made. That alone may improve your performance or even reverse the current location of the bottleneck! I myself am definitely GPU limited. My CPU will trot along at ~ 50% of one core while the GPU (even overclocked) is pegged on the end of runway portion of the test. GPU memory will appear maxed out initially, but alt tabbing out and back in tends to free up some that was allocated but not actually used.

Nope. We're definitely straying far off topic here, but.... I will say this board does take a few extra seconds to get through initialization (particularly the 15 seconds prior to the video card POST message - that's definitely longer than many I've had) but there is nowhere after that where it just "sits and pauses" waiting for input / timeouts / device boots (I have nothing but the main HD as a boot option, no extra memory tests (there's nothing to select))...it's as clean as it's gonna get. As I said, I don't even see the vid card's post message until 15 seconds from power-on. During that time the mobo is running whatever checks it deems necessary (can see the status progress on an on-board LED display). That's on for a couple of seconds, then the bios info & proc ID pop up...3-4 more seconds and the RAM size/speed are displayed, a few more lines of text, then it clears and displays the Marvel controller info for a couple of seconds, quick flash to all the IRQ lines and such and before you know it it's hit 35 seconds and 'starting windows' pops up. Now like I said it takes ~ 20 seconds from that time until I get my login prompt and I can be at a "stable" desktop at just over 60 seconds from power-on. But again, that's not what I was talking about when I said over 2 minutes. From that point I need to start everything else I'd just leave "running" on an S3STR...trackir, browser with a couple of email accounts and a couple of forums, etc. Firefox starts in like 1s if I just start it up clear....but if I have those tabs open it takes a while to fetch/refresh from the interwebz. Why go through all that when I can just tap a key, count to 3 and my system is "fully booted". I generally run a pretty tidy computer. Not counting crashes caused during overclock attempts/tweaks, I often go months without a true "reboot" and have done it that way since win95. My crap just _works_. Never been a victim of those strange freezes/lockups/crashes that so many seemed to complain about over the years. My buddies with macs bitch about their systems more than I do.

Right. I know EVGA makes good stuff (or I wouldn't have bought an EVGA mb. hehehe). Kinda funny...I can't remember the last time I had to use a warranty, and now within a week or two I sent a camera lens in for warranty and now my GTX275.

I use Firefox. It saves my tabs. But it still takes time to load and refresh. And yeah, I'm using a ~ 2.5 year old HDD as my boot drive. Heh. And on one hand, I probably overtimed the boot since my "main" tab was on yahoo mail which stalled...everything else might've been done first. And on the other hand...20 sec to boot win7 ain't bad. Heh.

OK, so here's the deal. I'm running a nice fresh Win7 install with no excess crap getting loaded. I'm at about 9 seconds from sitting in my chair to checking email when I use S3STR. From a cold start it takes 15 seconds before I see the video card POST. I don't get "starting windows" until about 35 seconds. I get my login prompt at 57 seconds (After 20 years in IT, I don't leave a computer without a required login...and I force the one my wife uses to have a required login as well). Then to load trackir and my browser with the 7-8 tabs I usually leave open...I'm at about 2:10 before I see my emails and can do whatever else. That's on a machine running at 4ghz w/ 6GB ram. 2 extra minutes isn't a huge deal but it would get really old, really fast if I had to waste that much time every time I STR instead.

Time it, with a stopwatch, from poweroff until the time you're ready to actually use it. Do include anything you would normally have running if you were simply to have stepped away for a minute. (Browser, TrackIR, etc). It's not simply a matter of how fast you get to the desktop. It's not like we're talking 10 minutes...but with S3STR, I'm up and running before it would even post if I'd done a shutdown.