WH_Thor

Good news! A reinstall did fix the problem. I guess the old install finally got tired of new things. Problem resolved.

Ok, thanks for your response Bignewy. That's what I'm currently doing, I'm on standalone so it's taken me a while to get it all downloaded again. I'll update again when I have all my modules reinstalled. Thanks again, Thor

Hello! First time posting a bug report. I cannot get the supercarrier module to load at all. Without fail it crashes during load. I discovered this while I was trying to update a simple mission for CASE 1 practice in the mission editor. I suspect this may have something to do with deck crew, because while I was playing around with it I found I could duplicate the same crash by opening the Personnel section under static objects. The same crash does not occur in a mission containing the default Stennis. I've tried several DCS repairs thinking maybe I was missing textures or something, and reinstalled the Supercarrier module itself. Neither solved the problem. My PC specs should be in the DXDiag included, but for those who don't want to search thru it: CPU: Intel i7-8700K OC 5.1GHz GPU: 2x Nvidia GeForce GTX 1080 Ti (SLI forced off or on at the driver level made no difference, currently running in single GPU render mode) RAM: Corsair Vengeance DDR4 2133MHz PSU: Corsair RM1000X OS: Windows 10 Pro Update 1903 DCS Storage Medium/OS Drive: 2x WD Black NVMe 250GB SSDs in RAID 0 Really at my wits end. I'm guessing at this point it's not something I can fix. I've updated drivers, ensured Windows was up to date, played with SLI settings, played with other graphics settings. It just dies when it tries to load. Hopefully ED can learn something from my logs. Cheers! dcs.log-20200528-123631.zip dcs.log-20200528-121301.zip dcs.log-20200528-115745.zip

I'm located in the US, Colorado. this is the output of the tracert results, assuming the IP is still at the previous IP I had: C:\Windows\system32>tracert [Removed For Security Purposes] Tracing route to [Read Above] over a maximum of 30 hops 1 <1 ms <1 ms <1 ms DHHOME [192.168.1.1] 2 16 ms 10 ms 8 ms 76.25.16.1 3 8 ms 10 ms 7 ms xe-9-0-1-0-sur03.fortcollins.co.denver.comcast.n et [68.85.107.49] 4 8 ms 12 ms 9 ms ae-10-0-sur02.fortcollins.co.denver.comcast.net [68.86.103.106] 5 11 ms 13 ms 12 ms ae-33-0-ar01.aurora.co.denver.comcast.net [68.86 .103.117] 6 14 ms 16 ms 13 ms he-0-5-0-7-cr02.denver.co.ibone.comcast.net [68. 86.93.149] 7 28 ms 28 ms 34 ms be-11317-cr01.dallas.tx.ibone.comcast.net [68.86 .84.229] 8 26 ms 28 ms 26 ms he-0-13-0-0-pe03.1950stemmons.tx.ibone.comcast.n et [68.86.86.154] 9 24 ms 41 ms 25 ms 50-248-117-6-static.hfc.comcastbusiness.net [50. 248.117.6] 10 57 ms 50 ms 49 ms 10ge5-3.core1.mci3.he.net [184.105.222.9] 11 43 ms 46 ms 49 ms 10ge4-1.core1.mci2.he.net [184.105.213.37] 12 43 ms 43 ms 44 ms joes-data-center-llc.gigabitethernet3-2.core1.mc i2.he.net [184.105.19.134] 13 44 ms 43 ms 46 ms 96.43.134.170 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. C:\Windows\system32>

Hey I was wondering if someone could help me with my problem? For the last several months I've been unable to see the 104th in my master list. I've tried pinging the server's IP several times in cmd, and also tracing the connection, but each time it times out. Does anyone know of a solution to this problem?

The one I have installed currently is linked in the OP, that's the first one the OP uploaded.

Hey guys, the screens look amazing, but I'm having a slight problem with the mod. Do any of you know the cause of the effect being so dim?

Hello all, sorry for the late replies. Actually, this CPU replacement was enacted to address the exact issue you pointed out (that is, a hardware failure). Yes I have a feeling it was indeed a software problem (not, as I have found, directly DCS related, I'll detail further below), although it was originally introduced by a hardware failure, I suspect (PSU went out some months ago and took the old ASUS motherboard with it). Yes, I did some benchmarking before I started this thread to see if I could determine that as the problem. As I said in my original post, the CPU core seemingly assigned with processing the simulation events wasn't pegging over 60% usage, and my GPU was giving similar utilization even at highest settings, only topping out at around 70% usage, and never rising above about 50°C. This I found incredibly odd given my in-game performance. Yes, the current UEFI version I have is the most up to date I could find from Gigabyte. Actually, I'm a big fan of CPU-Z. No need to recommend, already have it installed. No, this is no where near a new build. This build is from Feb. 2012, although you couldn't tell by looking at the parts now. The only thing that's left from the original build is the case and CPU cooler, and (until last night) the disk image. No chance I forgot thermal paste, I'd never be so daft with a computer, lol. Got a good healthy amount of Arctic Silver 5 under the hood. Throttling was not a problem, and my 620 has no problem meeting the TDP of this new FX-6350, as well as my old 960T. See as above, I was getting abnormal utilization for my in game performance. Upgrade. So, enough foreshadowing. One critical aspect that I had failed to mention or even take into account, and you may have extrapolated from reading above, is that the disk image I was using was, until last night, almost 4 years old. Also, the performance impact seemed to be growing greater, and affecting Windows as a whole. After scanning for malware, looking for rootkits, and clearing as much digital cellulite as I possibly could, I gave up. I had deduced that the problem most likely lie in years of code built over code, then half washed away and built back up again. The digital catacombs of my hard drive were most likely so filled to the brims with skeletons of programs past that it had finally run out of CPU overhead to give the rest of the computer while active applications ran. So I did what any one sensible person would do. I nuked it all from orbit. I backed up what I cared to keep, got out my Win 7 disk, formatted the HDD and the SSD, and reinstalled Windows. Thus far, it's going great. Unlike before, performance is on par with what you would expect from a hex core, 8 gig, mid-range card, purpose built gaming tower again. I pull a constant 30 FPS in Arma 3 with vsync on, and am very happy to report that the framerate on DCS is once again playable. At moderately high settings I pull between 30 and 50 fps now. Thank you all for your help, I have squashed this one thoroughly.

Already tried windowing the game, didn't change a thing. That's how I tested the lower resolution to see if it would make a difference, it was windowed at 1440x900.

No, the graphics settings have seemingly no effect on performance. I suspected this was the case, my graphics card is having no trouble with the work it's being given. It seems that something is drastically reducing the amount of performance my CPU can give to DCS, which I find odd. I'm going to try reinstalling it and see if that fixes it.

Hey guys, so I'm having some weird and very frustrating issues getting DCS to just be playable at this point. I recently got a new CPU and memory hoping to increase my performance and decrease the incredible amount of stutter I was having. Instead it seems to have made the issue worse. Here's my current system specs: AMD FX-6350, Nvidia GTX 650 Ti Boost, Team Vulcan 8Gb DDR3 1600 RAM, Gigabyte GA-990FXA-UD3 Motherboard, 2 Tb WD Black HDD, 128 Gb Crucial SSD Setup as a cache drive to the HDD, and an Antec Kuhler 620 in push/pull I constantly see FPS between 4 and 14, peaking at 22 for very short periods, and stuttering almost constantly. Resolution has no effect on frame rate or stutter, as it's the same result windowed at 1440x900 or full screen at 1680x1050. Looking in the task manager under the Performance tab when DCS is active, the CPU core tasked with handling simulation events never rises above about 60% load, which I find odd. Does anyone have any ideas?

Yeah, I got the same results as you on the route trace and the ping request. My route timed out one hop after Joe's data center, so practically identical results. What's strange is that you can connect without problem, while I cannot even see the server.

Hey, have you guys made any progress solving the seemingly blocked IP? I don't really like the idea of trying to use a VPN just to play on the server, but I know of no other way to circumvent such a problem if there isn't a workaround.

No, I still can't see the 104th. At this point I'm thinking it's something external that I can't fix locally. I heard they recently changed server hardware, I'm wondering if the new server is in a location where a data center along the way is blocking the IP for some reason. Although, if you have any other ideas I'm up for listening to them.

Doesn't look like that fixed it. Thanks for trying to help, though.

Hey guys, so I just created a profile here to talk about a weird problem that showed up about 2 weeks ago. For some reason I can't see the 104th anymore. I can't see it in the server browser, and direct IP connection doesn't work either. Does anyone know what the cause of this problem is? Thanks in advance, Thor.