Badass1982

Do you know what DOES work?

OK I'm new to LUA scripting but I've read up on this thread and I'm still struggling. What I'm trying to achieve is to create a viewport for my knee board on my second monitor (atm the f14 but preferably most aircraft). My 1st monitor is a UWS 3440 x 1440 monitor and my second is a dell 2048 x 1152 resolution monitor Total combined resolution is 5488 x 2592 and if im not mistaken the aspect should be 2.1172839506172 I'm realy struggling to get my monitor config file setup up correctly if any of you bright sparks can help it would be much appreciated included the lua code i have tried so far. thanks in advance. _ = function(p) return p; end; name = _('KNEEBOARDTEST1'); Description = 'One main monitor + Kneeboard on second' Viewports = { Center = { x = 0; y = 0; width = 3440; height = 1440; viewDx = 0; viewDy = 0; aspect = 3440/1440; } KNEEBOARD = { x = 300; y = 300; width = 300; height = 300; } UIMainView = Viewports.Center GUI = { x = 3440; y = 0; width = 3440; height = 1440; } GU_MAIN_VIEWPORT = Viewports.Center

I stand corrected , so far the WebGUI is holding up for me (the remote control bit i mean)

Not for me. Its still the same.

"Web GUI is currently on maintenance" I get this error when trying to remotely access my computer from another PC other than the server it is running on withing my LAN I can access the WebGUI from work and from the computer thats running the server , but NOT from any other PC's on my LAN which is the same as the network the server is running on.

I had loads of trouble today until I made a bunch of new firewall rules in windows firewall to allow all the ports needed to run my server to be opened.

So I don't want to tempt fate, but I was able to just fly a DCS 2.5 open beta Bear Trap mission with my F-15 without a single black screen or crash, the only thing that has changed on my system is that my GPU is now being water cooled and thus the temps are a LOT lower. Under load (in DCS the GPU doesnt get hotter than the mid 30's C). I will report back if this happens again but so far so good. Oh this is WITH the card overclocked past factory settings.

I've just installed my GPU water block so I'll update this thread if I find out anything new. (Under Water my GPU is 22c idle and 31c under load lol)

Mine isn't going above 65 Celcius so it's not that for me.

Do you have the same hardware. This is the only application that does this: Graphics benches don't even crash when heavily loading the card, DCS barely even loads my card.

My DCS Log Part 2 OK so after all that I reverted to the latest stable release went to start my F15-C engines and again the same crash . I have included the latest log.zip for the devs review. dcs.log-20190103-035833.zip

I tried a fresh install into a directory which is different to where the previous installation was done. No change. Ruled out re-shade causing my issue. Or Mods. Or the Shader folders as It was newly created shader folders. Running the latest 2.5 BETA build. Still have to try with the stable build.

My DCS Log. Just tried again , I managed to reproduce it shortly before take off. No artifacting just game froze and if I pressed escape it would stop in game sounds, pressing escape again would continue the games sounds with a stuck picture on screen of my f-15 taxiing. Looks like the game has been paused but it hasnt then after a couple of seconds crashes out to the DCS splash screen. I'm including the log file. I have deleted the folders suggested by the user above and launched the game again so the shader folders are rebuilt and I deleted the mods folder (and DCS savegames folder too). I did in the past have RESHADE installed so I'm doing a fresh install (though this wouldn't explain why it doesn't crash when not overclocked on the smae install). dcs.txt

I haven't had a chance to check it yet but I will in the next few days and I'll attach my crash dump thing too.

Mine wasn't giving ANY ARTIFACTING overclocked or not, just a black screen crash. This is a DCS engine error, I have already uploaded my crash dump through the auto thing but i can add it to this thread as I can reproduce it every time. Artifacting is usually but not always due to an unstable overclock (also extremely unlikely on a factory overclocked card to be to do with the overclock as it is stable) Not one of my other games (or benches crash when running my card OC'ed or not) I use a LOT of GPU and CPU benches in my daily life and none make my hardware fail. Its such a cop out to say "it's your overclock".

flyer49, nope no solution/fix and no response other than yours to my post. It's definately a DCS issue though as opposed to Graphics/Driver/Overclock issue. I have tried EVERY other game and benchmark I own at those overclocked settings and EVERY single one works flawlessley except DCS beta/stable at those settings. The ONLY workaround I have discovered so far is having two saved OC profiles for my GPU in Afterburner, one at stock clocks and 1 at my STABLE OC

I just wanted to give my 2cents on this issue. This is Not an issue with someone's faulty GPU and is 100% to do with DCS (at least in the open beta version) not liking overclocked RTX cards. I have tested this in depth and every other game I have installed (I have over 20 games installed) works flawlessly with my RTX 2080ti (when set to stock clocks) which currently has an overclock of +150 on the core and +500 on the vram. As soon as I set this to the default clocks: I have the evga ftw3 version, so my default boost clocks are slightly higher than a stock version. It runs flawlessly at stock clocks but doesn't like overclock at all. Like I said this is the only game that does this I have many beta versions of different games and None exhibit this behavior when overclocked except DCS 2.5 BETA. I have already submitted many auto bug reports when the game crashes (note the game doesn't crash to desktop but it causes a black screen hang with a game crash error) I have yet to see if this still crashes when running the "stable" version of DCS but I can reproduce this every time on the Beta version. I will test this in the stable version when I get out of work tonight. I should also add that I don't get any artifacts at all. Just crash to black screen with DCS ERROR message, nine line told me to post it here. Update: I have since tried on the "stable" version of DCS and get the same issue, definately a software issue , not a hardware/overclock one IMO.

Its really about the software, I have Track IR5 but I'm curious if the opentrack software works with the Track IR 5 camera as I would like to try that instead of the track Ir software.