majapahit

same problem here 4 monitors T-setup

My 2500K @ 4.5 GHz and 1866 mem, BLK @ 100, had to underclock DDR3 to 1600 my 8600K @ 4.7 GHz and 3200 DDR4 mem, BLK @ 100, slightest OC (3333) won't boot (stable at factory 3200)

Same here after update, horrible trees, crazy stutter on 4 screens. Set MSAA to OFF If NVidia you can choose to set FXAA ON, or any other NVidia special AA That solved mine (took hours and help from this forum), trees now look ok (like in Rudel_chw's image), them trees now, you hit 1, you go boom ...... how great is that 6 screen resolution render / 4x 1080p monitors in T-setup / 8600K / Asus GTX 1080 gives 30-50 FPS in Caucasus, but smooth, enough (1.5.8 would do 75-100 FPS with 4x 1080p monitors)

Someone already came up with a solution Set MSAA to OFF, imm Nvidia Inspector set FXAA to ON Fixed

I experienced problems when from 1 screen to 4 screen rendering (4 FPS). Someone pointed out that you need to disable MSAA in DCS and and use NVidia Director to switch on FXAA (perhaps something comparable if AMD), after which DCS 2.5 worked fine. Maybe you can try also this if your DS setting crashes DCS

Wow, that actually works. Who would have thought, thanks you saved the game (Measly 30FPS, smooth and solid)

With 1x 1080p screen (a 60Hz TV) on 8600K and Asus GTX 1080 I (barely) get 40 FPS with DP, which apparently is normal (I tested all possible settings, DS, HDR, shadows etc.) Trees look stupid light green blobs, no detail in the trees, and I think these just don't render as is intended (CPU 40% GPU 80-99%). When I change to my regular setup, 4x 1080p screen in T-formation, @ 5760x2160, which is 6x 1080p, DCS 2.5 starts an unbearable 4-7 FPS crawl. Fortunately I still also have my DCS 1.5.8 running, 4 screens, silky smooth and 70-85 FPS CPU 40% GPU 99% and actually - Caucasus - terrain way better looking then DCS 2.5 So, now what? (I won’t fly with 1 screen)

with 1 screen FPS ~40, landscape quality ok-ish with my 4 1080p screens, HORRIBLE 4-9 FPS, stutters, with 'HUD only' 20FPS, horrible trees render Trees, horrible 'sprite blobs', seems shadows or some textures are not making it to render. (1.5.8 smooth as silk, sharp, great shadows) On new 8600K & Asus GTX 1080 what the hell?

No Oculus here, but mayor stutters after upgrade 1.5.8 to 2.5, not in 1080p/1 screen, but when I extend to my 4x1080p screens (5760x2160) It's the cockpit rendering with 4 screens, when I switch 'HUD only' view, the stutter disappears, HDR Trees look horrible by the way, might be I have a shaders problem I uninstall and wait till the severs get less busy and try again

'racket' @ 800 RPM? That seems not right, worn bearings? Try another fan / buy a replacement PWM fan Perhaps try to grease you fan, Google 'repair CPU fan' see if that makes a difference

Cheap aftermarket 30euro 'best buy' ARCTIC Freezer i32 (changed the 3 pin fan to the 4pin PWM Cooler Master fan from my old 2500K box)

FYI new rig Intel 8600K startling numbers, 8600k @4.5Ghz CPU load 36% GTX 1080 load 99% DCS 1.5.7 A10-C flying Caucasus FPS 60-85 FPS (5780x2160 - 4 screens) graphics options maxed ASRock Extreme4 Z370 with 4.5Ghz ‘Optimized’ OC setting & CPU “voltage offset” 16GB DDR4 - 2x8GB 3200 Corsair Vengeance LPX Asus GTX 1080 Nvidia drivers 390.65 Nvidia Profile Inspector Antialiasing for DCS: SuperVCAA_64X_4x12 8600k @4.5Ghz 8600k CPU max load 36% 8600k CPU max Volt 0.62V (<- how about that) 8600k CPU max Temp 47°C (<- how about that) Asus GTX 1080 max load 99% sustained Asus GTX 1080 max Temp 65°C 4x screens 1080p 5780x2160 (T-setup) Thrustmaster WH, Logitech 940, PSU 750W Cooler Master How cool is that (pun intended)

FYI new rig Intel 8600K startling numbers, 8600k @4.5Ghz CPU load 36% GTX 1080 load 99% DCS 1.5.7 A10-C flying Caucasus FPS 60-85 FPS (5780x2160 - 4 screens) graphics options maxed ASRock Extreme4 Z370 with 4.5Ghz ‘Optimized’ OC setting & CPU “voltage offset” 16GB DDR4 - 2x8GB 3200 Corsair Vengeance LPX Asus GTX 1080 Nvidia drivers 390.65 Nvidia Profile Inspector Antialiasing for DCS: SuperVCAA_64X_4x12 8600k CPU max load 36% (<-- not breaking a sweat at all) 8600k CPU max Volt 0.62V (<-- how about that .. stock 1.15~1.25V ) 8600k CPU max Temp 47°C (<-- and this) Asus GTX 1080 max load 99% sustained Asus GTX 1080 max Temp 65°C 4x screens 1080p 5780x2160 (T-setup) Thrustmaster WH, Logitech 940, PSU 750W Cooler Master How cool is that (pun intended)

you prob want to define the GUI to the Left-most screen for the resolution af that screen (I've been doing this for ages now with 4 screens, because DCS won't fix it)

just try it sometimes DCS changes the format and it doesn't, even in between versions seperately you highlight a changable binding and then you load the profile of that column So sometime this doesnt work, again because sometimes apparently DCS just changes everything Also if per occasion your devices get assigned different USB ID's (per the Windows hardware plug and play), that will create a fresh new default ID profile, and you have to recover your old one. Also, the Modifiers.lua "..\Saved Games\DCS\Config\Input\A-10C\modifiers.lua" per plane in the root of the profile(s) you need to copy manually, or you will have <errors color> for all the inappropriately assigned modifier bindings

I discovered the hack that adds 128 (or 68 ) additional DX definitions to the standard TARGET profile, normally its limited to DX 32 which is way to few for TMWH, so your 'virtual TMWH' runs out of UI assignments at the throttle pretty quickly (button 6 or something), adding DX128 makes all/most TMWH 'positions' (also 'OFF") accessible through the UI So, you load a target .tmc profile with the additional DX assignments, "C:\Program Files (x86)\Thrustmaster\TARGET\scripts\targetdx128.tmh" edit the .tmc header "include "targetdx128.tmh" // (use expanded targetdx128.tmh instead of target.tmh - default Thrustmaster function code) have targetdx128.tmh in your target script path <"c:\Program Files (x86)\Thrustmaster\TARGET\scripts"> et voila many more TMWH ON/OFF accessible through the normal DCS config UI (still takes some effort though till you've figured this out) find the thread of the original poster about this, hidden deep, but its still confusing (but I use it though) target dx128 128 DX BUTTONS.zip

download USBDeview, UN-install all used USB connected devices/driver per the listed unplug and re-plug keyboard so you can restart windows windows plug-and-play re-installs your USB connected after restart this works for me always use the same port for a specific device - until the port assignments clog up again and repeat

My experience with additional software and plenty of USB devices, the USB assignments f**k up. I use JoyIDs to check the ID of the joystick, USBDeview to clean out the USB assignments and start over, I've notices with many USB devices you can only use a certain sequence of ports or things go haywire, which is trial and error and then never change a successful way of assignments sequence. I have a TMWH and a Logitech g940 together, Trackir and a MCPCombo, and a assortment of keyboard pads, race wheels etc. Windows 7 x64 When I would attach my G940 (FFB) to another USB port, things won't work. I tried Win10 when it was introduced, what bad USB management that was, Win 8.1 better but not so stable USB management as slower Win 7. I'll try Win 10 again when I upgrade to a new motherboard, and hopefully it has improved.

Use TARGET TARGETGUI.exe to set up you commands per button per the manual. Create 'new', use 'basic' otherwise you'll have those 5x 'shifted' states unless you want that, assign which controllers you want to use, assign Axis (leave default), assign commands to buttons by double click the button and then type 'Event Name' (f.i. 'gear up AND down' which would involve not just 'Pulse', but rather both a 'Press' and a 'Release) Add Event and Save Event which then shows up in the right column 3. of events 'SAVE' (bottom left) this script TARGETGUI script so it is actually a file for safekeeping 'RUN CONFIGURATION' to test the script when OK (save again if you forgot) do VIEW SCRIPT this is the TARGETScriptEditor.exe version of the commands file (you need to learn the TARGETScriptEditor syntax which is much quicker) you now have 3 options 1 - always load though the TargetGUI and "Run Configuration" 2 - or, run the script translation created by 'VIEW SCRIPT' with TARGETScriptEditor 3 - or, you run the script translation created by 'VIEW SCRIPT' a .tmc file that is a definitions batch as a command line with TargetGUI simple what? (yep Thrustmaster did a horrible job) So to set up a KA-50 script, you - test an define starting with TargetGUI (and save f.i. as <KA-50.fcf>) - then you create a .tmc file by 'VIEW SCRIPT' that you can run with TARGETScriptEditor (and saved as <KA-50.tmc> - then when all is tested and running nicely you can run the .tmc <KA-50.tmc> as a command line with TargetGUI in for instance a setup batch file, as in my KA-50_setup.bat that loads my trackIR etc and has the line rundll32 shell32.dll,ShellExec_RunDLL "k:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r "i:\TEKST\My Games\DCS\TMTARGET_profiles\KA-50.tmc" after you have learned the syntax of the .tmc file, that's a lot quicker.

nope

1.5.7.8899.335 Labels way off in multiscreen (vertical) mode NOT FIXED yet

thx (i'm dementing)

haven't got around to a proper setup yet, this 3 minutes contraption works now, plank, 1 yogurt bucket, 2 glue clamps shows G940 FFB for KA-50, but can swap with TMWH

Stream Deck 120+eu keypad from ebay driven by remapper 3-4 USD free shiping duh

K-041 Targeting system power switch Ins Targeting Mode Controls Panel PVR Power OFF Targeting Mode Controls Panel PVR -- > switches off HUD? after new setup, powering off PVR also blanks HUD is this normal (can't recall) I use Shkval LEFT-MFCD onscreen and powering off frees screen of Shkval when RTB