sepruda

What would you recommend if you havent bought a base yet, sounds like Ultra is still the way to go?

That is a very smart use! I have used a long Virpil Desk mount which I've clamped to the baseplate with the 200mm extension. It works very well, but I'm now missing options to properly mount panels/ufc etc in front of me (current mainly held in place with velcro tape), and I would like to purchase the simgear F16 ICP and properly mount it on a center plate, and then add the MFDs someway... So this might be a solution to have the stick extension without drilling or welding stuff. My current dream setup is this, but that is a DIY solution... I do wish Next Level had more accessories to the chair (which I love the look of)

Seems I can't override the campaign settings and toggle immortal. Of course I realise this is not realistic, but when being shot down by the MIGs in mission 15 for the 10th time, I would like to skip the start-up and holding please!

Unfortunately I crashed into the deck. The marshall point confused me, the text said Chig entered it as a nav point - I flew towards it but before reaching it Chig calls out established, I kept flying toward it but could then see the carrier lights. I proceeded to head out on the 183 radial, establishing myself 22 dme from the waypoint and pushed on time. But the carrier looked far away still, as Chig called platform. Suddenly though I was almost on top of it, and I lost patience and tried for the landing anyway but hit too hard. Would the correct approach have been to set a course from the wp?

I only fly in the A-10CII

Hi, after a long consideration I finally decided to get a Buttkicker, on the recommendation of many in here. I am however struggling to set it up properly, I have had it working sort of, with the HaptiConnect software using the new DCS mode, which worked ok. But reading that the SimShaker Aviator and SimShaker Sound Module surpasses the native software, I decided to buy a license for that. And now I'm not sure how to go about setting it up properly, I sometimes lack some sound elements (only voice/no voice) and sometimes lack the rumbling. In my setup I use the HP Reverb G2 VR HMD and as mentioned I have the Buttkicker Gamer Pro with amplifier. I only have an onboard soundcard at the moment. According to this post an external soundcard is not required, and the poster recommends using both the HaptiConnect and Simshaker software. My current configuration which doesn't really work - The Buttkicker is connected via USB and I also have the Y cable go into my sound output on my machine (though the MB port in the back didn't work, so plugged it in on top) - In the SimShaker software setting, I have the output mode to SOUND and to automatically start the Sound Module. I see the DCS modules I've tried to fly with, having this open. - In Sound Module I have selected my onboard soundcard as Dedicated Sound Card. Rest is default - In HaptiConnect ButtKicker Input is connected, the outputs are the Buttkicker and my G2 headphones - My Windows sound selection in my onboard sound card - I leave all apps running when starting DCS - In DCS I've tried selecting both the G2 as audio and the onboard as audio Really confused what to select for all of these options, I hope someone can give me or point me to good step by step tutorial.

I know this is an old campaign, but still, it's still for sale in the shop. Wingman is garbage, I've never had him engage anything, and believe me I've tried. He starts popping flares at some point and usually crashes into the ground. The second JTAC doesn't respond with anything. The coordinates from the kneeboard seem precise enough, but those pillboxes require a direct hit. I had two near hits and one miss, on direct hit. Leaving me not enough explosives to complete the mission. I have yet to see a wingman doing anything in this campaign, besides calling out SAMs. Skipped.

In any case Davy shouldn't call out warnings as well

I seem to recall the MWS also sounding of, I wasn't aware that AT missiles triggered it, that could be the issue then

I was flying mission 16 yesterday, and everything was going pretty well. After attacking the secondary target, I got a bunch of SAM calls from Davy, I did not get a visual, but popped a lot of flares trying to dodge them. Later after taking one of the JTAC assignments and going in on a gun run, I was shot down, my flare expenser empty Watching it on TacView, I can see that there was no sams when Davy was calling them out, instead it seems to correspond to the anti-tank missiles being fired by the ground forces. I can share the file and track if you want.

Hi there, Phenomenal work as always. I'm very much enjoying the challenge of the campaign. I did wonder though, why you would pack LGBs when it's clouded... I couldn't go through all my search points, cause I got damaged trying to get in for the kill with rockets. Really missed more standof weapons, like 4 mavs, instead of 2.

Thank you so much for the campaign. In M15 I launched my JSOWS from a high altiude but unfortunately I only got 2 hits, and was missing a primary target, so I aborted the mission and flew home. I was cleared to land on 23, but when I got down that runway was littered with Tornados (aggro flight), that I crashed into.

What do you mean with computer error calculation? And how do you apply an offset? Thanks for sharing

Just a short update, got a new Corsair Gold 850W and everything is working perfectly now. Thanks again.

Thank you for the breakdown. The issue seems indeed from the PSU, but not from too little power, but the PSU overheating due to a faulty fan (it doesn't run at all). I will however get more voltage when I return it (I bought it just a couple of months ago). So once again, like the other threads PSU is at fault! Thank you very much everyone for all your suggestions

On the contrary, now I can RMA it and maybe improve w

I don't believe it! Pulled the PSU out and ran the test again, the fan has zero movement! Seems I've found the culprit Of course it has zero RPM mode, so I'm gonna keep the test running and verify that it never starts up.

Oh of course, yes I already upgraded the BIOS to the latest one, that was required before installing the 5950X.

Thanks! If my next round of tests prove it's a power issue, I'll definitely look at your suggestions And if it comes to that, I'll look at your MB recommendations, though I'd rather not spend any more time installing components right now I don't think I have looked at upgrading the firmware for my MB, wasn't aware that was something you could, so I'll look into that. I have some more steps I can try: - Reset BIOS to failsafe - Look into deactivating one CCD in bios I don't mind not having 100% value of the 5950X, I will some day upgrade my MB, preferable just not right now

Guys, thank you for taking the time to try to help me, it's really frustrating not having my dose of DCS @LucShepThank you for your thorough analysis. I know I'm pushing my MB with that processor, but I'd rather upgrade my MB than downgrade my CPU Maybe it's possible to see the VRM temps in one of those programs I am running (?). The 750w should be enough, my dealer assures me, but I'm also skeptical that that is really the case. I will try Hiobs suggestion "MSI Afterburner you could try to limit the Power draw of your GPU to - let's say - 200-250W", and see if that solves it.". Next step will be turning down the speed of the RAM as you suggest. I will try to run GPU-Z as you suggest Hiob. I don't mind buying a 850w PSU (even though I just upgraded to the 750w ) - but would like some kind of verification that power is really the issue.

So I ran Cinebench multi core test and hwinfo and CPU temp peaked at 63. Afterwards ran the MSI Kombuster stress test untill shutdown, latest CPU reading from hwiinfo says 64, max GPU is 63. Doesn't seem like a heating issue Of course it's possible that hwiinfo didn't record a spike just before shutdown..

Correct, I installed two additional fans on top, though I only did that after the shutdowns I have three fans in front (intake), two in top and one in the back (outtake). I did have to disable one of the top fans though since it was hitting something on the Noctua I did remove the plastic piece on the cooler, but I will try to remove the cooler and install it again, making sure it contacts properly with the CPU. I think I'll also follow your advice and remove the top fans. Though first I will try to monitor the CPU heating in DCS again, wish there was some software that recorded the highest temperature since the time might vary quite a bit.

I used MSI Kombustor to run a stress test, and after I came back to the PC in about an hours time, it was shut off again. So does indeed seem to be a cooling issue of either the CPU or GPU. I have monitored the temperatures before while playing DCS, however not just before the shutdown and also using a different tool. I guess there are different paths for me now: Try to provoke the heat issue like you described, or check the installation of the CPU cooler and the thermal paste. I bought a Noctua NH-D15 CPU cooler, which was almost to big for my MB, it's pushing slightly towards the graphics card, don't know if that could be an issue.

I was beginning to hope that switching PSU sockets had solved it, but unfortunately I gotta another shutdown after 53 minutes cold and dark on the tarmac. I've looked in the event log, but not sure what to look for. I have one critical "kernel-power" error, just around the shutdown, but doesn't really tell me anything. I've attached the logs around that error. I've only just noticed you writing about the temperature in post 3 @Hiob I've applied the thermal paste and installed the CPU cooler myself, so might be a possibility that I did something wrong. Is there a way to track what the highest temperature was before shutdown? I had the cabinet open for my last round of testing, which lasted longer than before, so I guess a cooling problem is still a possibility.. I will try to run the stress tests you recommended. log.evtx

To be clear, my GPU was not connected to those two sockets, I've moved them there (currently running the game for testing again). Will look into the event viewer and stress test if the issue persists.