silverdevil

factory OC has sometimes been a culprit. try with nVidia DEBUG mode. this will remove factory OC for testing.

i see what you mean.

this is what i have in my defender. you should notice a faster opening time for DCS.

eh? interesting. have you had this controller issue ever before? in case you are interested, this little app is good for making backups of critical DCS files in your Saved Games folder. i do the "backup input folder" and "backup config folder" each time i make a change. it works with latest build too. https://www.digitalcombatsimulator.com/en/files/3315428/

@TJTAS reported! @Flappie merci beaucoup mon ami!

i read your message a second time and i realized what you were saying. this does seem like a bug. @Flappie have you seen this bug in an upcoming fix? thanks!

i suppose it is possible that your issues are the result of some other cause. i never really had the issue or it was imperceptible.

especially MP.

does the AV report anything being flagged? this DLL could be crashing because of a dependency being blocked.

huh? sorry i am confused. you may want to share a screenshot.

hopefully. i saw a few really old posts about and then recently your post and someone else's. like the problem was fixed and then it returned.

good to hear you are good. i have seen this mentioned in other posts.

since you are not sure if TIR is the issue, i suggest turning it off and testing. make a mission that you can use to test with. with and without TIR. i just updated to the latest version of TIR and have no issues ATM. also looking at your log and the graphics settings. below is a comparison with my settings annotating which may cause performance issues. bolded are the settings and red font indicates my settings. ['AA'] = 'MSAA'; SLAA DLAA ['forestDetailsFactor'] = 1; ['rainDroplets'] = 2; ['LensEffects'] = 3; ['box_mouse_cursor'] = true; ['anisotropy'] = 4; ['water'] = 2; ['motionBlurAmount'] = 1; ['BlurFlatShadows'] = 0; ['outputGamma'] = 2.2; ['aspect'] = 1.3333333333333; ['lights'] = 2; ['LODmult'] = 2; ['MSAA'] = 1; ['messagesFontScale'] = 1; ['canopyReflections'] = 1; ['width'] = 2560; ['visibRange'] = 'Extreme'; ['DLSS_PerfQuality'] = 1; ['useDeferredShading'] = 1; ['clutterMaxDistance'] = 1500;0 ['textures'] = 2; ['cockpitGI'] = 1; ['terrainTextures'] = 'max'; ['height'] = 1440; ['multiMonitorSetup'] = '1camera'; ['shadows'] = 4; ['defaultFOV'] = 60; ['shadowTree'] = false; ['chimneySmokeDensity'] = 10;1 ['secondaryShadows'] = 1;0 ['SSS'] = 1; ['fullScreen'] = true; ['preloadRadius'] = 150000;50000 ['scaleGui'] = 1; ['Scaling'] = 0.66; ['DOF'] = 0; ['clouds'] = 3; ['sceneryDetailsFactor'] = 1; ['Upscaling'] = 'OFF'; ['Sharpening'] = 0; ['motionBlur'] = 0; ['ColorGradingLUT'] = 0; ['SSLR'] = 1;0 ['effects'] = 3; ['SSAO'] = 1;0 ['maxFPS'] = 300;180 ['sync'] = false; ['heatBlr'] = 2;0 ['forestDistanceFactor'] = 1;0.5 ['flatTerrainShadows'] = 0; ['civTraffic'] = 'high';off ['ScreenshotExt'] = 'png';

not really any help but there are other posts concerning the similar type crash

I see you just updated BIOS in another thread. do you have a OC going on. Your DCS log does not show a crash. 2024-10-19 14:34:32.072 INFO APP (Main): application shutdown This is a normal shutdown. You sure you got correct log? Anyway, since you mentioned updating BIOS, it could be an XMP memory setting in BIOS. Just grasping at straws.

roger. thanks. i will give it a try.

ah thanks max. i did not realize they released this. BETA though. any problems? i trust you

hey max! what app is this you mention? roger that

i personally use experience for videos. others have noted they only use drivers because of problems it causes with their systems. i do not have any hardware for aorus and not sure what you mean by control center. talking about Alienware? my current driver is 561.09.

hello. first thing to do as always when one has troubles, is to post your latest dcs.log. it may contain clues.

correct. i found an old log that shows: 2020-09-27 18:33:31.909 INFO DCS: Device hotplug disabled! i do not believe this line will show in the log if the feature is set in the GUI. nor being in the autoexec file. i thought you were asking what file that code was placed.

sorry for the late reply. you have a lot of messages like the below. 2024-09-29 01:29:12.315 WARNING BACKENDCOMMON (2548): Need to reprocess [DDS] image '/textures/SpitfireIX_Wheel_rear_NM.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format have you cleared all the shader files? Saved Games\DCS\fxo and Saved Games\DCS\metashaders2 just go in the folders and delete all the contents.

that line was a 'stopgap' that was put into \Saved Games\DCS\config\autoexec.cfg

exactly. i could not find the link

if i understand. you are trying to get a gamepad useable in DCS using Steam? if so, and i have not done so in a while, is setup the controller in Steam. it just magically worked for mine in dcs. used in apache and honestly it was more controllable than anything i used prior. this is just one video of many discussing the process.