tom_19d

It just shuts off completely, like someone held the power button and forced a shutdown, then it immediately goes into reboot.

Thanks but I have never overclocked any of the components and I haven’t touched any of the MB settings in a long time. I get the idea behind a longer stress, but that seems kinda weird to me since DCS isn’t pushing my cpu to near the level that the stress test does.

Bad news. Maybe. So the first time this reboot happened it was pretty deep into mission 2 of Georgian Hammer CA. I started that up again tonight , once again about 30-40 minutes in- I was watching a helo burn in when WHAM, sudden reboot. So same mission, roughly about as far into it when the total crash happened. I ran a DCS repair, played again. I caught some damage and had to RTB but this time ran the mission to conclusion with about 30 min of run time and no issues. I had GPU-Z going, nothing got even close to 65 C....so now I really don’t know what to think.

Alright everyone, thanks for all the suggestions. I complied with them this afternoon, put it back together, and ran a couple more benchmarks. I haven’t had another shutdown. I have a friend with a basically identical system (we built at the same time) and we are benchmarking essentially the same. I guess at this point I just have to play some more and monitor. On the good news front, while going through my documentation I found out that PSU has a 7 year warranty, so if I do have to RMA anything I am covered either way. Thanks again all. I will give an update if I make it a while without problems or if something happens again. This is a great community.

Fair enough, I think there are enough ideas here to warrant not pulling the trigger on a new PSU quite yet, particularly in light after considering @Bitmaster's point that a PSU failure probably wouldn't lead to an event log, that makes sense to me. I'll try all the given advice with regards to cabling. @Demon, with the pencil eraser, you were talking specifically about the contact points on the GPU card where it goes into the PCI slot, correct? (Pencil eraser makes sense to me, whether comm cords or headset plugs that has always been my go to.)

Each DLC campaign has its own forum section. Here is the one for the basic flight training on the A10 I’m sure someone there can point you in the right direction.

Thanks all. I am out of town this weekend but I think at this point I am leaning towards picking up a new PSU. I think there is merit in rechecking all the connections, and if I am going to go through that I would rather be just hooking everything up with new cables to a new supply. This way I can try to cover all the bases at once and won’t risk a bad PSU taking anything with it if it decides to really fail. I just don’t have time anymore to spend troubleshooting, if I can be by the rig I want to be flying, not cracking it open on the workbench. Also, since I have realbench now, does anyone have an idea what a baseline score (nothing overclocked) should look like, given my specs above? Maybe that could help point to a GPU issue if I am way off...

Post number 12 of this thread... Eagle I ran that conversion on the link against the example I laid out in post #6. Your website was indeed 30 feet closer to correct then my rule of thumb conversion. I am going to look at that site more and try to see how they source their conversions because now I am interested haha. Frederf, I hadn’t thought of using an EGI derived height, that could be interesting. My memory is that pre-WAAS GPS did a poor job of determining height/altitude but I admittedly don’t have any idea how the A10 handled it or perhaps more importantly how DCS models it, but I think it is worth exploring. Regardless, as it relates to the OPs question and bearing in mind that civil aircraft only have to have an altimeter that reads +/- 75 feet from a known elevation to be legal for instrument flight, until DCS implements something different I will stick with a method that I can mostly do in my head and only takes a working comm radio to implement...and least until a lot more missions require ILS approaches right to minimums.

Fair enough, but until we get an ATC that issues an altimeter setting for each airport, I don't know of a way to compensate (or at least a way that makes any sense to pursue in a cost v benefit sense). How can this knowledge be applied to the OPs issue?

I’m sorry nessuno, I do not know of anything off the top of my head. You could surely work out a proportion of mmMg over meters, but I am not sure if it would be quite as handy as the 1 inch per 1000 foot rule. Hopefully someone around has an answer!

Post 12 this thread Like I said...

Thanks Bitmaster, I ran a Realbench 15 minute stress first. All passed OK, 62C max on GPU, 58C max on CPU. Restarted, waited a bit, and started Prime95 (I did the in place large FFTs since it said it would have max power consumption) and then immediately started the Realbench 15 stress test. Realbench said all OK. All 8 windows on Prime95 showed no issues/no warnings. CPU maxed at 65C, GPU at 63C. From my Event Log from last night, 2 events seem to have precipitated the restart, both with an Event ID code of 1074. "The process explorer.EXE has initiated the power off to computer GAMERIG on behalf of user GAMERIG\GAMERIG for the following reason: Other (Unplanned). Reason Code 0x0. Shutdown Type :power off -2 Seconds Later "The process C:\Windows\system32\winlogon.exe (GAMERIG) has inititiated the power off of computer GAMERIG on behalf of use GAMERIG\GAMERIG for the following reason: No title for this reason could be found. Reason Code: 0x500ff. Shutdown Type : power off After that the log shows a cascade of services stopping, then the shutdown.

Eddie said it all - when you take off you want the altimeter showing airport elevation and when you return you want the same thing. The reason you can't get zero to show on the ramp (not that you want to) in some situations is because western aircraft aren't designed to use QFE so mechanically they aren't able roll down that low. The fact that you were able to apply the 1 in/mg to 1000 feet rule and, using the ATC QFE setting, get your altimeter to show field elevation proves that the method works, at least well enough. However, if you are just starting on the ramp, what is actually easiest would be to adjust your kollsman window until the altimeter shows field elevation - then you have QNH. And someone can correct me if I am wrong, but I believe in the DCS world, unless you have dynamic weather on, QNH should be a constant across the map (so you only need to get it once...and it is usually available in the briefing). Thanks for this Eddie. I have seen this explained in 1A-10A-1 but heard in other threads it wasn't fully implemented. Glad to have this confirmed by a SME.

Morning All, I have seen this around but nothing too recently and this was a first for me so I thought I would pick the collective brain. Two nights ago I upgraded from my old twin 970s to an EVGA 1080ti. Prior to this, the system has always been rock solid. i7-4790K 32GB Kingston HyperX RAM Samsung 850 EVO SSD Asus Z-97A Corsair H100i water on the CPU Corsair HX750 PSU After installation I was only able to screw around for about 30 minutes, things looked good and everything was running very cool, I am struggling now to remember exactly but I believe the GPU maxed at 68 C. Last night I had a little more time, I was flying the A10 for a little over an hour, getting ready to call it a night, when the machine just completely rebooted. At first I thought maybe our electricity flickered at the house, but nothing else had any issues from what I could tell. I haven't had a chance to try to look at the Windows event log, but that is my next move. My immediate thought is power supply. The Corsair PSU in there is 3.5 years old. I know 750 watts should be plenty for this rig, so I would guess maybe age is taking its toll? Regardless, are there any other logs I can try to access to see what the problem might have been? Are there any GPU issues that anyone is aware of that would cause a sudden reboot, as opposed to a blue screen, game crash, ect? Thanks

i missed this the first time around but it was great, thanks for waking this one up!

AveWhiteGuy -- I can try to sum up. This is strictly a rule of thumb type calculation, but it can be done in your head, and gets you close enough for about everything we do in the A10...at least until DCS ATC starts issuing QNH some day, which would be great. It is generally considered that pressure decreases 1"/mg (i'm sure you know but the altimeter setting put in the kollsman window of the altimeter is measured in inches of mercury) per 1000 feet of altitude. Lets assume we set up a mission editor with the plane near Vaziani and leave standard QNH of 29.92. So you start airborne and head towards Vaziani, field elevation ~1520 MSL. You call Vaziani to land, they issue QFE of 28.34. Divide field elevation by 1000. Moving the decimal leaves you at 1.52. Add this correction factor (1.52) to the issued QFE (28.34) to reach 29.86. Put that in your kollsman window and land. Here we see why it is a rule of thumb - 29.86 is what we have set. 29.92 is correct. That 0.06 difference in in/mg will present as your altimeter being 60 feet off. It isn't perfect, but barring an ILS at absolute mins it is close enough, and unlike other methods it can be done mentally. It is how I deal with it until we get an ATC update...

Its not a bug. DCS ATC reports altimeter setting in QFE. You are looking for a QNH setting. This thread covered it in depth , I am sure there have been others.

I had never actually clicked on the modifier button in controls to see the switches option, but that looks handy. Thanks guys, learned something new.

Hi gents. I looked at this a little more at other fields with just one ILS; Batumi in the Caucus and Groom Lake in Vegas. At both places, I was unable set a wind condition that would turn the ILS off. Tailwind, calm wind, light headwind, strong headwind, the ILS at those two places stayed on regardless. At Creech however, the problem remains. I believe this might have something to do with the "phantom" ILS to 13 at Creech on 108.5. It shows on the ME, but I haven't seen it published anywhere else, nor have I seen it turn on. I'm not sure if ED is planning on activating a second ILS there or what the deal is with the second ILS, but since this particular issue of a one-ILS airport turning off the ILS only seems to be happening at Creech, I am willing to let this one go for a bit to see if we hear anything from ED about the second ILS there...

Thanks Peaches

I didn't know that was possible Rob but that sounds great -- is there a mapping in DCS that lets you set a toggle like that, or did you have to use a 3rd party solution? In the attached screenshot I had my mouse cursor right over the crossing of the two runways, but the screenshot function masked out the mouse. Regardless, at the bottom you can see the MGRS readout circled in red. I'm not sure how familiar you are with MGRS so hopefully this isn't telling you something you already know, but a six digit grid will get you within 100 meters of a point and is generally plenty close for what we need. So in this case GG 323 360 would be your entry. As I think I mentioned in another thread I have been out of the A10 for a long time, so someone can fix me if I'm wrong, but I believe the entire Caucus map lies on the 37 T map sheet so you don't ever have to use those letters and numbers, just the two letter grid identifier than the string of numbers.

Hi Scuby, The F10 map works fine for me for finding coordinates for waypoints as well as elevations if needed. I find using MGRS grids to be much easier than lat/long. Write down the points you need, plug them into the CDU as waypoints, and off you go. TACAN is always an option too depending on where you are on the map, although line of sight limitations can be problematic if you are going someplace while staying down in the weeds and it makes complex courses harder to manage.

Ugh. I think both Eldur and Victory have it spot on correct. Mariner maybe you should tell us what RL type ratings you hold? As I said before...the book says the F18 stops shorter with antiskid on...why are you arguing against the AFM?

I'm not going to buy that argument mariner. If data is available that clearly shows ac performance under a given set of circumstances doing one thing in reality and in the sim it does another, there is no reason not to point it out. And the issue isn't brake fires, the issue is that standing on the brakes during rollout on a dry runway with the AS off should shred tires almost instantly, or at the very least should not allow for shorter stopping distances than landing with AS on. Since the data is available, the RL hornet drivers you speak of would probably say the same. I certainly don't consider this a game breaker or anything like that, but if people start using the "it's a game" excuse instead of pointing out issues that can clearly be defined in the frame of available data, I don't think that is a positive direction for the community or the devs. DCS seems like a special community to me and I would hate to see that change.

Sorry sir, I'm going to disagree here (at least for aircraft). By this logic airline captains should disable their antiskid if their factored landing distance is really close to the landing runway distance available. After all, they are by the very definition the "professional" operators you cited and this technique would allow them to stop shorter if that is true. I would like to see a source on the primary function of antiskid on an aircraft being directional control. I agree that AS systems are all about threshold braking, and when it comes to preventing tire blowout or flatspotting during maximum effort braking I will trust the computer every time. When it comes to contaminated runways, even more so to prevent wheel lockup. But if antiskid really did start out as a measure to prevent direction control loss on landing or RTO, I'll be happy to admit I'm incorrect. And thanks Victory, that explanation makes sense to me.