-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by BadgerFly
-
Hey TBone! Wow, thank you so much for sharing your experiences! It's always incredible for a non-military virtual pilot such as myself, who's always dreamed of flying a combat helicopter, to get a glimpse into what it was really like. From my limited experience doing SEAD flights with the Ka-50, I very much agree with your strategy of using cover and concealment as far as possible. I have found that even when a nasty SA-19 has you in its sights, using a hill or a building for cover can help to exhaust its supply of ready-to-fire missiles, and when it's reloading you simply pop it with a Vikhr outside of its gun range. The first time I flew with a new group on Discord I was No.4 in the flight, and when we got to the AO our flight lead directed the four AH-64s into a hover at 1500ft AGL - felt super exposed and uncomfortable! For what it's worth: Casmo made a video on the exact same topic around 6 months ago, so it's pretty epic hearing the same thing from two different, credible sources:
- 25 replies
-
- tactics
- survivability
- (and 4 more)
-
So I was just browsing around on this thread, and when I saw @okopanja's post about the Ka-50Sh and Ka-50N - just WOW! I absolutely give my vote to one of these airframes being modelled. Yes, it will be great knowing when someone's shooting at you, and yes it will be cool shooting down Apaches with the Iglas, but flying around in the dark with a FLIR-equipped Black Shark will just make my year, or even decade! ED, I love DCS and all that it is, if the international restrictions allow for it please give us a Ka-50 with a FLIR!
-
Crashing with DXGI_ERROR_DEVICE_REMOVED since 2.7.9
BadgerFly replied to BadgerFly's topic in Game Crash
Hey July Something I found (which may or may not be a valid/good way to do this) is to enable Debug Mode in the NVidia Control Panel. From what I've seen, it essentially removes the OC - as soon as I enable it, Zotac Firestorm immediately shows the 1080Ti GPU clock decreasing to 1480MHz which I believe is the base clock for this card. So far, I've had limited positive results by enabling Debug Mode. As they say, your mileage may vary! I believe some more of my positive gains have been achieved by lowering my SteamVR Super Sampling - essentially lowering the workload on the GPU. (The screenshot below shows a Quadro P1000 - this is my work laptop) -
Crashing with DXGI_ERROR_DEVICE_REMOVED since 2.7.9
BadgerFly replied to BadgerFly's topic in Game Crash
Thank you Raven for your reply, I will see what I can get right with OCCT. Hey July, thank you for your post, it's bittersweet knowing someone else is also seeing the same thing happen. I reckon the writing is on the wall for me at least - it might be time to retire my 1080Ti. -
Crashing with DXGI_ERROR_DEVICE_REMOVED since 2.7.9
BadgerFly replied to BadgerFly's topic in Game Crash
Hi Raven Thank you for your suggestion! Can you please recommend a VRAM benchmark for me? I've tried several, and I can't seem to get one to work - OCCT tells me I don't have an OpenCL compatible device, - memtestG80 tells me I don't have a CUDA device - Video Memory Stress Test just won't run. Ah, I see. My RAM is set at 3600MHz, Cl16, it is a G.Skill 2 x 16GB kit rated for this speed. Sadly, DCS has been crashing without being able to write crash logs, but I did attach a DCS log to my original post. Hmmmmm. Temperature could be a possibility - The card is around 4-5 years old now. FPS VR tells me that the card never exceeds 70C, but there might be a hotspot somewhere that's not being reported. The core and video memory frequency are now sitting at stock 1080Ti speeds - in the NVidia Control Panel I enabled 'Debug Mode' - this seems to drop the frequencies to stock accross the board. Thank you for your help, I will do some more testing on my own and play with some of the settings some more. -
Crashing with DXGI_ERROR_DEVICE_REMOVED since 2.7.9
BadgerFly replied to BadgerFly's topic in Game Crash
Hi Maximov, Flappie So I ran the TechPowerUp memory test, and after 20 minutes and 6 loops it showed 0 errors, so that's at least one thing ruled out. To answer Maximov's questions: The crashes do not happen in 2D with the same settings. The crashes do happen in Singleplayer after about 5-10 minutes (not sure if I should be trying with a pre-defined mission, I'm just flying around after creating a basic mission in the ME). I set the game to the default "Low" settings, and I did not experience any crashes. My FPS shot up to 65, but I could almost not make out what was going on on the HUD! So it seems from these questions that my system (or at least, my GPU) cannot handle very high settings - I suspect the crux of the matter might lie in my desire to have Textures set to high. My question is then: If I am happy to fly with 40-42 FPS in VR with High textures, why does my system crash? I mean, it clearly handles my desired settings for around 5 minutes or so, but then suddenly decides that it's had enough! Do you think that I'm just being too optimistic in terms of what my 1080Ti can reliably sustain? And then, why has this changed with the recent update to 2.7.9? Can it be possible that my GPU might be giving up the ghost? Thank you for your time. (I have attached my settings below. I also use SteamVR SuperSampling at 160%) -
Crashing with DXGI_ERROR_DEVICE_REMOVED since 2.7.9
BadgerFly replied to BadgerFly's topic in Game Crash
Hey Maximov, Flappie Thank you for your replies! I'm currently at work, but I will see if I can run a memory test this evening, and also do some more testing so I can get you some more answers. Thanks again! -
Crashing with DXGI_ERROR_DEVICE_REMOVED since 2.7.9
BadgerFly replied to BadgerFly's topic in Game Crash
Hi Flappie Thanks so much for the reply! I have not tried that, no, can you recommend a suitable method to me / where can I find out how to do this? -
Hi Everyone! Since end December last year (since the OB 2.7.9 patch was released) I have sadly been getting repeated and repeatable crashes to desktop with the DXGI_ERROR_DEVICE_REMOVED every single time I fly. This has not always been the case. After reading up on the error on the Eagle Dynamics and r/Hoggit forums, here is what I've tried so far: - I am running WMR and SteamVR without the latest open betas. - I have the latest nVidia drivers, my Windows is up to date and I have re-installed my nVidia drivers after using DDU. - My GPU Shader Cache is set to 10GB. - My motherboard BIOS is running the latest version. - I have tried running DCS Slow Repair, the sfc /scannow utility, and re-naming my Saved Games/DCS.Openbeta folder. - I have tried underclocking my GPU, reducing the power limit to 80%, and running it in nVidia Debug Mode (lowers everything to stock settings). - I have tried to swop around the 8-pin 12V power rails on my PSU. - My CPU and GPU temps never exceed 65 - 70 degrees Celsius - My Windows Pagefile is set to 64GB - I have tried removing the only Mod I have installed, fholger's Reshade, and this has not made any difference. - I have tried adding the TdrDelay and related registry keys into Windows. - I have tried lowering all my graphics settings, but this has not helped either. Essentially, what happens each time is that I load into DCS, load into a multiplayer server (or singleplayer, same thing happens), and load into an F-16, AV-8B or Ka-50, and after about 5-10 minutes of flying DCS crashes. Sometimes it crashes 'well' and writes a proper crash dump, other times it just crashes to desktop and writes to the DCS log. I absolutely love DCS World and am incredibly grateful for all the amazing work that the ED team constantly does to make our dreams come true! I am simply getting desperate, since I am at the point of not being able to fly for more than 5-10 minutes before everything crashes. Does anyone have any ideas of what else I could try, or do I have to face the fact that my graphics card could be on its last legs? Thank you in advance for your time and help! dcs.log