Dubious Penguin

Note - I was able to get a resolution over on the VKB forums. Hopefully this will be useful to someone! http://forum.vkb-sim.pro/viewtopic.php?f=25&t=7713&sid=2dad8744ae44f6b3f756e573ecfdd6c0

Hi there, I am wondering if it's feasible to connect a Thrustmaster grip directly to a MK2 BlackBox (Without gunfighter base)? I have all the parts to connect it to the S-Bus of the MK2 BlackBox but am having issues with "detecting" the grip? I believe that this is feasible with a VKB grip but am concerned this approach may not work with a TM F18 grip alone? Full setup info: 1. Grip: TM F18 (With VKB TM adapter installed) 2. Extension: VKB 200mm 3. Connector: VP Force VKB Adapter (See attached image, Extension to BlackBox) 4. MK2 BlackBox 5. T-Rudder Pedals Mk iv Only the rudder pedals appear when using VKBDevCFG-C and ZBootloader2.exe, even when they are disconnected from the BlackBox. Reason for this approach is that I am trying out a custom ffb base. I also intend to purchase the F14 grip if this approach works. Quite new to VKB hardware/software so any guidance is greatly appreciated. Thanks! null

So far, TAA seems to be the lone culprit for me on an AMD gpu. I wonder if it's best to start an AMD specific thread or if I should just leave this here?

Original Post: 19 - Oct - 2023 I think I am getting a similar issue myself. (Note the front landing gear is where it is most apparent) I am running a Radeon 7900 xtx gpu. No matter what variation of TAA/SSS and motion blur combination that I try, the "tearing/artifacts" are still there. I also disabled any features from Radeon adrenaline software. Update Post: 20 - Oct - 2023 I restarted my PC this morning and the issue appears to be gone. I'll investigate further. I intend to turn settings on and off and see if the issue persists when set to off. If issues persist after turning the graphics setting to off - I will restart DCS and see if the setting truly switches "off" Testing Notes: TAA appears to be the source of the issue. While in the mission, I open the system menu and enable TAA The tearing/artifacts return While still in the mission, I turn TAA off from the settings menu The tearing/artifacts persist I exit the mission and ensure TAA is set to off from the main system settings menu I restart the mission with no TAA, the tearing/artifacts are now gone Original Post: 19 - Oct - 2023 (Footage and settings) DCS_MT.exe - Shortcut_2023.10.19-22.19_clip_1.mp4

Hi NineLine I've deleted the contents of both those folders. I tried playing the third mission in the Hornet campaign. I've uploaded the latest crash log. dcs.log-20190109-190416.zip

Hi Nineline Thanks for getting back to me on this. I had reshade installed for a while but I'm almost certain I removed all the files. Other than reshade I hadn't tried any other mods. No overclocking either. It's the one thing that's come to mind. I'll go back and try to do a more thorough search of the folders for any residual reshade files. If you have any advice on finding those it'd be greatly appreciated. Is there any convenient way to compare my own install to a "clean" install? Thanks again

Further testing If it's of any use to anyone. I deleted the contents of my C:\Program Files\NVIDIA Corporation\Installer2 folder. I removed all of my Nvidia software and reinstalled only the most up to date video driver. I changed graphics settings SSAA from 1.5x to off and set water from high to medium. I did an initial test and was able to complete the second mission of the Hornet Task Force challenger campaign. I attempted the third mission tonight and got another crash a few minutes into the mission. A crash log was generated. I will try to test different aircraft on different maps soon. The most recent crash log is attached. dcs.log-20190107-213439.zip

In the hope that these are seen, I'll post them here. These are the crash logs that were generated today. There were more than three crashes but these are the crashes that generated logs. I have created an autoexec.cfg file in Config. The crashes occurred in the 2nd mission of the Hornet mini - campaign and in the cold start training mission for the bf-109 on the Caucasus map. I will try to test more but it's time consuming. Hopefully this will be of some help to bug fixers. The latest Nvidia drivers (gtx1080 - 417.35 drivers) are installed, no mods have been installed and I attempted a repair using DCS_updater.exe. I will try wiping and reinstalling my GPU drivers and see if that works. dcs.log-20190106-114843.zip dcs.log-20190106-125224.zip dcs.log-20190106-154419.zip

It's also worth noting that I'm not getting a crash log generated for every CTD I get.

Hi shar321. I too am getting crashes, it might be helpful for Eagle Dynamics's bug fixers if you include a crash log. You can find it in: C:\Users\Username_here\Saved Games\DCS.openbeta\logs. I am getting these CTD's as well, it seems others are also, I've seen some reports mention an ACCESS_VIOLATION error, mine does too. One of the fixers or mods may come along and help you. I'm running version 2.5.4 of the open beta.