SniperRu

это про вас Воевода говорит на стримах у кирилла?

ok ran the test again, crashed maybe 5 minutes in. Logging did not catch any spikes, but since the whole computer crashes then it probably is a power issue Power Supply is an Antec HCG-750M bought new in 2015. Just spent 500$ on a GPU and now have to buy a new PSU as well Any recommendations are welcome

Downloaded GPU-Z, started logging 30 minutes later and 2 missions down still no crash.... murphy's law The whole time the power draw does not exceed 200W total from the PSU ports. Usually one is 100-120W and the other 70-80W. Temperature stayed below 80ºC Will try again tomorrow

How would you do that with the game running? Does this mean I have to choose between this GPU and playing DCS?

Seems to have helped a bit. The game kept running for about 30-40min (in mission time), but then the crash happened when I exited back to the editor. Same manner as usual - screeching sound and everything frozen Went through the logs, in the "System" logs, the only "critical" ones are due to The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Source : Kernel-Power Nothing in there about the GPU. Additionally I usually monitor the GPU temperature and it never goes above 74ºC in DCS. I also checked the required power supply on Newegg using my gear and it says 699W and my PSU is rated at 750W

So I just bought a new RTX 3060 Ti 8Gb to replace my old GTX 970. After installing it, there is now a consistent complete freeze of my computer (I suspect a BSOD but I can't see it) when playing DCS and DCS only. The only thing I can then do is a hard reset using the power button. Seeing as I mainly bought the GPU for DCS, this is really frustrating. I am running the latest open beta and disabled all mods. Things I've tried so far : Changing pagefile (all possible configurations) Reinstalling the GPU drivers (using DDU) Changing the graphics preset to medium Stress testing/benchmarking my GPU using a specialized app (no crash happened) I've tried running Arma 3 and Escape from Tarkov but they both run fine. However only DCS runs the GPU at full capacity. Other details on the crash : It seems to be happing after about 10 minutes in game The map, mission, planes, player in-cockpit or out, only AI on map - nothing seems to affect the BSOD and its timing When it happens, these is a screeching sound and everything freezes on both my screens dcs.log DxDiag.txt

I noticed the same thing a couple of patches ago. It (CCIP) used to be very accurate but now the bombs always land short/long.

No I noticed this issue while playing my own missions even before you posted this.

Can confirm, happened to me too (not on your track, on my own missions), seems inconsistent tho not sure how it is triggered.

I usually play as Red Coalition and I noticed that the GBU-38, when using TOO with the TPOD, misses the target almost always. Unrestricted SATNAV is enabled and I always wait for the bombs to align (get down to the 7:30min mark). I tried the same scenario with the coalition switched to blue and the accuracy is much better. See attached tracks. Still an issue as of the latest patch (Sept 23rd 2020). Am I missing something? F-18_Bug_POD_TOO_Red.trk F-18_Bug_POD_TOO_Blue.trk

Anyone has an answer to this one? I've been wondering for a while as well

I tried that and it did not help the accuracy. Plus by following a bomb using F6 and monitoring its altitude, from what I could see, it burst between 300 and 400 meters, which is between 980 and 1300 feet

Am I the only who can't get the CBU-99 on target in CCIP? They (bomblets) always fall long for some reason (Dive bombing with MFUSE set to VT 300). I've even set wind on ground level to 0 m/s... still no results

That solves it... I feel stupid. Thanks for the help everyone! now only the Potato quality IR video feed left to fix, too bad it didn't make it in today's update

I am doing the same thing with a waypoint (at altitude 0) designated as the target. The SLAM just won't dive... and my IR feed is consistently bad, even at night. I thought that the SLAM was showing a dynamic launch zone like the JSOW, so when I saw on the HSI that I was well in range I thought it would be no problem. Am I mistaken?

I just tried SLAMs for the first time and it is quite a disappointment. * First missile launched, well within range, flies at a high AoA and ends up falling into the sea far away from the target (TOO set by TPOD) * Second missile flies all the way to the target but does not dive towards it, making it extremely hard to direct with the DL pod * The IR video feed is horribly dark (same issue as IR mavericks) which make it impossible to find the target See attached track Am I missing something? or is this bugged? F-18_Bugs_SLAM.trk

You are right, my bad. I thought that on a hot start everything would be loaded already.

When starting hot from the airfield parking spot, the stores show up on the exterior model but inside the aircraft SMS shows as if there was nothing there, and the ground crew refuses to change the laser code on the bombs saying there is nothing on pylons. See attached track. JF-17_Bug_Stores.trk

This still happens to me, any fix on this? (Latest Stable Version)

bug still persists as of March 2019 :(

I'm getting the same kind of crashes (while cycling through external views) very often since the last patch. never had them before. Also I'm not running any mods, using the stable version.

I was going crazy thinking I was doing something wrong... this is so frustrating. Is there any hope of this ever getting fixed?

Ok I found the problem, the TrackIR Z-axis was mapped to the actual forward&backward head movement inside the cockpit instead of the zoom. Seeing as the Mig-29A/Leftwaffe don't have 6DOF cockpits it didn't do anything. Thanks for the help

I'm having a bit of trouble taking out tanks. Both the RBK bombs and unguided rockets seem to miss the target most of the time... any tips on this? and just to make sure, which RBK/rockets should I be using for armored targets?

For some reason the zoom axis (moving head closer/farther to the camera) in the Mig-29A doesn't work. However pressing the keyboard buttons : * and / works... Anyone knows how to fix this? PS: so far it's the only plane (still have to test Mig-29 Luftwaffe & the Western jets)