woofer15

Tried that, thanks! No luck unfortunately- are they force disabled in the campaign? Not tragic because it's easier to spot vehicles in the desert but still - missing some action I think :(

Hi there! Campaign is awesome so far but a bit difficult in parts because I cannot enable labels during any of the missions. Any trick to this? Labels work fine in any other NTTR/DCS2 mission.

I am having this issue - labels fine in 2.0 except for RedFlag - any resolution? (edit: sorry for cross post I am in A10C RF.)

I found a good high-res Sectional chart of Las Vegas that you can overlay onto this excellent layerset Stuka provided: Download TIFF here: http://www.soaringdata.info/aviation/sectionals/TIFF%20Format/Las%20Vegas%2096.tif Size and place in Google Earth using these coords: http://www.soaringdata.info/aviation/jpgInGe.html

Pardon me if this happens to be an inappropriate post location or for those that may have already seen this...but felt compelled to share this epicness: This Mini A-10 Warthog Will Regulate Your Lawn With Its GAU-8 Nerf Cannon http://foxtrotalpha.jalopnik.com/this-mini-a-10-warthog-will-regulate-your-lawn-with-its-1785087184

Thanks for the replies, all! So I actually figured this out after much trials and tribulations. It turns out to be a very interesting and unexpected scenario. Just thought I'd post here for posterity. The Rise of Flight crash turned out to be a red herring (I couldn't repro the crash) but it led me down the path chasing RAM settings. I bumped up the CPU-NB voltage from 1.1V to 1.2V and bumped the DRAM to 1.55V (was 1.50)...and that fixed it! I guessed that it may have simply been an instability issue - I also tried dropping the clocks to 1333 instead of 1600, but reverted after upping the power and DCS worked fine. My OC'd system must have been just on this side of stable and DCS (circa 2016 but not 2013) seemed to push it over the edge where no game has gone before! Now I'm at 60fps and everything's gravy again. Thanks! PS - I should also add that I think the -repair along with wiping the User folder helped get things squared away after potential corruptions from the repeated crashes and the big migration from my 2013 version of DCS over to 1.5 and 2.0alpha.

Hoping to get a response but posting for posterity for others. I tried rolling back drivers to 368.22, which many claim to be relatively stable compared to latest 368.39. No dice. Onto looking at my RAM timings and speeds more closely...here we go memtest.

Update: Tried: chkdsk /r (no problems) sfc /scannow (no problems) Still crashing regularly so I tried another sim...and Rise of Flight crashed (never seen that before either...may have been a fluke/coincidence, of course). This makes me think it might be the latest Nvidia Drivers (368.39) -- the reviews on these drivers have been horrific from the community. Do we have a recommendation on stable drivers for Nvidia XFX Geforce GTX 970 FTW+ ACX 2.0? I'm praying this is the issue....

No official response yet but scouring the forums has me attempting the following, in order: 1) Attempt to re-install or verify install of DX11 (MSoft only lets me run DxDiag and cannot re-install or repair - so I'll presume this is OK). 2) Verify Virtual Paging Memory set to Automatically Managed (it is - currently at 16GB on top of my 16GB RAM). 3) Remove/delete the old DCS Saved Games folder (tried this then did repair below). 4) Attempt "repair" option for DCS (didn't know this was a thing now!) Observations: The UI loads in a much snappier way...will update if this lessens crashes else I'm out of ideas! Seems my thread is similar to: http://forums.eagle.ru/showthread.php?t=148443 Would appreciate any insights!!

Hi there! Just got back from a 3yr deployment and dusted off the old cockpit setup. Happy to be back and first thing I did was fire up DCSW after getting all the updates to 2.0 and 1.5, etc. Unfortunately, my experience has been disappointing so far :( Back in 2013, I never had any crash issues (just standard perf issues). Now in 2016, I'm getting solid 60fps with occasional stutters - seems these occasional stutters become catastrophic at some random point and always crash the flight 5-10min in (time varies). Would LOVE some assist to get up and running....I need some DCS action before I head out again. Crash observations: Occurs in both 1.5 and 2.0alpha Crash occurs sooner and with more consistency in 2.0alpha Graphic settings changes seem to delay but not entirely prevent crashes Max settings = crash more frequently, Min settings = lasts much longer...but still might crash Same system as 2013 - no changes except updated drivers and TrackIR Using TaskMan and GPUZ for running stats (image attached) RAM never exceeds 6GB used (10GB free) VRAM usage varies based on texture settings, but never exceeds 3.6GB at highest settings Paging file set to System Managed Crash error seems to vary each time (making me think it's somehow memory related...leak or otherwise). Crash occurs with or without TrackIR or other software running (antivirus, etc). Crash occurs with or without control peripherals My usual settings: Tex High TTex High Civ Low Water Low Viz Med Blur Low Shad Flat Only Rez 1920x1080 1 monitor MFD 256 MSAA 2X HDR Off DOF Off Lens NONE Vsync (on but I have to Alt+Enter to make it work w/ Track IR) Clutter 300 Trees 5000 Preload 150,000 Anis 16X Flat Terr ON Aero Disabled Full Screen = YES See specs in signature. Here are the latest crash dialogues (from 2.0 and 1.5) -- image of RAM & VRAM usage attached. Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 2.0.2.52658 Application Timestamp: 57235e7c Fault Module Name: DCS.exe Fault Module Version: 2.0.2.52658 Fault Module Timestamp: 57235e7c Exception Code: c000001d Exception Offset: 00000000002eb1b3 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: f3ac Additional Information 2: f3ac2eba13701109f6bdac83aba074c3 Additional Information 3: c75e Additional Information 4: c75e487283e8c90f945d3b1a4f02f0a9 Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 2.0.2.52658 Application Timestamp: 57235e7c Fault Module Name: dx11backend.dll Fault Module Version: 2.0.2.52658 Fault Module Timestamp: 570d5088 Exception Code: c0000005 Exception Offset: 00000000000197d3 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 77ec Additional Information 2: 77ecc5690d6ea245d839600395ff2e01 Additional Information 3: fd1a Additional Information 4: fd1a644786de4066a6434e8da125e79e Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.3.53279 Application Timestamp: 574703dc Fault Module Name: Visualizer.dll Fault Module Version: 1.5.3.53279 Fault Module Timestamp: 573c801b Exception Code: c0000005 Exception Offset: 000000000001f53d OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 3277 Additional Information 2: 3277a41819270cf2bac00bda6d5a2315 Additional Information 3: 1e74 Additional Information 4: 1e745f51ca116e7b673e672e166fef92 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.3.53279 Application Timestamp: 574703dc Fault Module Name: Cockpit_A10C.dll Fault Module Version: 1.5.3.53279 Fault Module Timestamp: 574703d5 Exception Code: c0000005 Exception Offset: 00000000000092fc OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: ae0f Additional Information 2: ae0f04302bbee204394599935b5fa811 Additional Information 3: 51c8 Additional Information 4: 51c89d9819d64c34aeb363f50997ca06 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 2.0.2.52658 Application Timestamp: 57235e7c Fault Module Name: Visualizer.dll Fault Module Version: 2.0.2.52658 Fault Module Timestamp: 571f6457 Exception Code: c0000005 Exception Offset: 00000000000272f1 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 3277 Additional Information 2: 3277a41819270cf2bac00bda6d5a2315 Additional Information 3: b992 Additional Information 4: b9927ba9aa15f8365670b5cf50a06832 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 2.0.2.52658 Application Timestamp: 57235e7c Fault Module Name: edterrainGraphics41.dll Fault Module Version: 2.0.2.52658 Fault Module Timestamp: 570d518d Exception Code: c0000005 Exception Offset: 0000000000033fb1 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 1587 Additional Information 2: 1587eb874b6884ad3dd0ab9e4875fdd7 Additional Information 3: dc24 Additional Information 4: dc2438212e9e3bc18d55e111250d8beb Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

I have basically have the same frame rates as you. Tried all the tweaks here and didn't see an observable, measurable difference. Seems most of these tweaks are GPU related though. I'm 100% certain that I'm CPU bottlenecked. I can up my settings without significant affect on frame rates. I can overclock my CPU and see a slight difference (3.4 to 3.9ghz) but no difference from OC'ing my GPUs...I only go to unplayable frame rates <20fps during the unit-heavy missions, like the campaign missions. there's no fix or tweaking for that. My 2-3 year old CPU just won't cut it on this 2-3 year old sim. I really look forward to playing it at killer FPSs 10 years from now, though! Kind like I do with Falcon 4 and IL2 now......sad as that is.

Hmmm -- doesn't seem too...but I'll take a closer look. Thanks!

Thanks westr, will give it a go. Do you notice any graphical anomalies (like the flashing clouds/TGP)? Which ATI card do you crossfire? Also, noticed you have Falcon 4 BMS installed. Do you have any graphical issues with it using 13.4? I fear driver updates, haha. EDIT UPDATE: Ok, so upgrading from CCC 12.8 to 13.4 gave a small, yet definitive increase in FPS of 1-2 frames during all scenes. Good news! I also did extensive testing with Crossfire setups before and after this driver update. Conclusion: Set Crossfire to disable (at least for me!). DATA on drivers 12.8: --Default, AFR Friendly, and 1X1 crossfire modes result in a decrease of 7 FPS (from ~30 to 23) consistently across the board. Notably, AFR Friendly results in flashing clouds and TGP/MAV while 1X1 and Default does not. --GPU load with xfire disabled: GPU #1 = 100% peak // 36% average & GPU #2 = 0% peak // 0% average; GPU #1 load with Default/AFR/1X1 = 100% peak // 35% average; GPU #2 load with Default/AFR/1X1 = 39% peak // 15% average --Crossfire status icon illuminates only for Default/AFR/1X1 when useing westr's settings and mapping to DCS.EXE --CONCLUSION: Crossfire DOES enable but does not "work" for me. I get 7 FPS hit regardless...GPU 2 is disabled when crossfire is disabled, yet when crossfire is enabled GPU 2 only peaks/avg 39%/15% while GPU 1 still carries peak/avg of 100%/31%. DATA on drivers 13.4 (slightly different, but same story): --Default, AFR Friendly, and 1X1 crossfire modes result in a decrease of 7 FPS (from ~32 to 25) consistently across the board. Notably, AFR Friendly still results in flashing clouds and TGP/MAV while 1X1 and Default does not. --GPU load with disabled GPU #1 = 89% peak // 35% average & GPU #2 = 0% peak // 0% average; GPU #1 load with AFR/1X1 = 34% peak // 3% average; GPU #2 load with AFR/1X1 = 35% peak // 9% average; GPU load with default crossfire GPU #1 = 89% peak // 35% average & GPU #2 = 0% peak // 0% average; --Crossfire status icon illuminates only for Default/AFR/1X1 when useing westr's settings and mapping to DCS.EXE --CONCLUSION: Notably, in 13.4 the Default Crossfire mode does NOT put load on the 2nd GPU (it stays 0%/0% peak/avg), yet the crossfire icon shows up in the corner. Also of interest, the GPU #1 load during crossfire went from peak 100% in 12.8 to peak 34% in 13.4 (this more closely mimics the GPU #2 crossfire loads)...but this did not result in FPS loss or FPS gain. NOTE: the peak load for 13.4 on GPU #1 reduces from 100% to 89% (probably accounting for the 2 FPS addition across the board with or without crossfire enabled).

Insofar as I understand it (I will likely need to be corrected), graphics.cfg is legacy and ED prefers that no one edit the graphics.lua (since it will be oft replaced automatically by updates and your changes will be wiped). Instead they recommend you create/use an autoexec.cfg in the USERS folder to execute commands to modify the graphics.lua, such as "max fps", etc. Since no one responded, I took his most recent (OP) graphics.lua and overwrote mine (after backing up). I then modified that "on-the-fly" using my new autoexec.cfg to cap the FPS. Of course, if ED overwrites the graphics.lua in an update, all non "max FPS" changes made will be defaulted again. And we won't know if this same graphics.lua will be compatible with the newest ED version.

Thanks for the effort, Skate -- good to know there's a few advocators out there. In your opinion, do you think I'd gain from moving to CCC 13.4 from last year's 12.8?