Amarok_73

Just an ordinary crash to desktop, I was unable to send it from the game (pressed Esc while error report was prepared), and now only log.txt file is available, while zipped version seems to be broken. dcs.log dcs.log-20200617-221718.zip

False alarm. In the UI Layer this button was mapped, and it seems, that this mapping group has higher priority than airplane specific.

Hello, I'd like to report, that there's some issue with joystick button number 4 in Logitech G940. Tested on multiple different airplanes (A-10C, Ka-50, Su-27) and all of them having this button mapped to some functions seems to be not responding to this button. In the Logitech profiler, the button have no any special assignation.

So I've got to the point, where I am desperate to find the reason of TDR errors, that I am receiving regulary, practitcaly every mission I start. I read the sticky thread in this subforum, all what is said there applies to my situation, so I downloaded the dx11backend.dll file that USSR_Rik suggests to use, and was very keen to see what extended information it will return, but... this dll seems to be somehow broken, or obsolete, as the application hangs on startup, then in the log following entry appears at the end of file: ['preloadRadius'] = 60000; ['height'] = 980; ['terrainMapMFD'] = { ['distance'] = { ['mapLodDistance3'] = 200000; ['mapLodDistance2'] = 100000; ['mapLodDistance0'] = 25000; ['mapLodDistance1'] = 50000; }; }; }; 2020-05-31 17:42:31.250 INFO GRAPHICSVISTA: renderer: 'dx11backend.dll' 2020-05-31 17:42:31.251 ERROR GRAPHICSVISTA: Can't load render backend 'dx11backend.dll'. Reason: Nie można odnaleźć określonej procedury. === Log closed. The text "Nie można odnaleźć określonej procedury" means "the specific procedure cannot be found". After last about two weeks when I have my new computer and started to fight this inequal fight, reading dozens of game, hardware, system related foum threads, the question to developers is if You're indeed interrested to resolve this issue, or define what is the ultimate reason of this problem (hardware or drivers related). If the answer on above is positive, then next is if there's anything we can do to support You on this issue? If this is neccessary, can You provide updated version of this dx11backend.dll file? If there are any testing scenarios that could help You in this investigation? As Bignevy declares this is not possible to reproduce the case on his computer so perhaps it would be wise to employ the people that encounter the same issue to collective work over it, define testing screnarios, specific reporting rules to follow, where it would be defined what kind of outcome should be observed and reported, specific system behavior, additional error messages. max values from specific sensors reported by GPU-Z, or OCCT, etc?

+1

That may be the tip for the developers if any of them have noticed dozens of crash reports I've sent already testing all possible combinations of drivers, software managing my hardware, underclocking and game display settings i could imagine. :-)

So I am not the only one, who recently started to have this problem. For some reason I feel much better now. Perhaps because it means probably and hopefully, that not my hardware is the issue... :-)

Hi Branli, could You share update? What did You do to eliminate the problem, and what is the current situation?

After all these days, full of testing and changing display drivers, and all the other activities, that's also my suspicion. Point is, that i did not overclocked anything so far, and the overclocking options in my motherboard UEFI are so complicated, so it's hard for me to evaluate, what parameter could be changed by seller in the process of preparation and stability testing. So far, i've found site where are told PBO parameters optimal for my hardware, set it up, and first and only flight after this change was undisturbed. Also I've decided to use XMP profile for my memory instead of hard setting 3200 MHz... So far I wonder if clearing CMOS that will set default settings can be assumed also as most safe in regard to stability. I'll continue "doctorization", and if I'll get promising setup, I'll share what did I set, perhaps someone will benefit from such feedback.

Well, there's something concrete... I've started GPU-Z, enabled logging to the file, started DCS and flied for a while, then the crash occured, and it seems, that this happened exactly in the moment, when GPU clock raised from about 1700 MHz, to above 2060, what seems to be higher than default values for my graphic card. The time signatures from the crash log and GPU-Z log for this event are almost the same (difference is about 3 seconds). I am attaching GPU-Z screenshots showing the info screen and sensors page with max values of all measured parameters. Now, the question is, how to limit the GPU clock so it will not get higher than stock values, and how to investigate what actually cause such behavior?

Playing Arma3 I have encountered error that seems to be of the same origin as in DCS. The screenshot of this error I am attaching to this post. Now the question comes, as it can be that the graphic card becomes unstable because of stock overclocking, how can I get the information if my card is indeed stock overclocked, and how to get it to the base settings?

And now the same happened again in the same mission, with the same settings, flying A-10C. :( Tell me please if should I stop posting the Crash Log files as they probably contains the same information, so there's no benefit in it.

Well, I have praised too early. It still occurs. Nothing changed since last successful test except this time I was flying in Harrier instead of Ka-50 and A-10C. dcs.log-20200524-211950.zip

Well, so far - so good. I've deleted these modules, started pretty dense mission on max'ed graphical settings, and no any issues noticed. :thumbup:

Well, I have done what You suggest in troubleshooting advice, tried multiple combinations of graphic settings, and in every of them, sooner or later the crash ocured. I'am attaching the reports from these moments, but I assume, there's no really point in publication of these here and instead I should just use the function of reporting the crash that is integrated in the game? Logs package.zip

Hello, I'd like to report crash that aparently seems to be related to water settings. On low settings there's no problem with game stability (so far), but raising it to any higher value causes the CTD soon after mission start. I've searched through this subforum and see that there's some advices to delete files from fxo and metashaders2 directories in saved games, i did so, but th effect is the same. Also there is some advices to turn down overclocking of graphic card, but my card is set to defaults. In system event viewer I can see, that the issue is somehow related to the DX3D11.dll. I attach exemplary crash logs. My hardware (bought about week ago) specification is: AMD Ryzen 5 3600 AMD Radeon RX 5700 XT 32 GB Ram dcs.log-20200520-194343.zip dcs.log-20200522-170710.zip

Indeed, Backspace - Return to Search. Thank You all for help!

Hello, I'd like to confirm if indeed, there's no button availiable for unlocking target? Edit: Sorry, this question was meant to be put in SU-33 subforum.

On 1.5, I've done today two touchdowns (one missed), and no problem noticed with wires...

I've had it some time ago, but it was hardware problem - my G940 rudder pedals was sending peak signals, since potentiometer was stiff mounted.

+1

+1 Also, NVG brightness is not working. When rotated, it'snaps' to brighter value than default, and stays locked in that position. Tested with the same result in different missions, both - in single and multiplayer.

It can be, You've been flying without radio assist.

sc_neo, If You're using for instance A-10C, then You can install Ricardo's HD texures, so with medium/low all other textures, cockpit will be razor-sharp. :-)

No worries, You're not crazy. As I already wrote in previois posts, there was a time, when there was... let's name it "simplified" version of MWS, which was working same way as in Su-25T, so there was just vocal warning about missile in the air.