Hipster

Good luck with your card! I was hoping for the same. I had suspicions about the power supply (500W) not being up to the job so upgraded that a week or so ago. Running some benchmarks and I started to notice crashes happening that rapidly became more and more frequent and affected DCS too. Since the whole pint of the PC is to run DCS I had to bite the bullet and swap out the 1080. I now have an RTX 3060 Ti which provides a slight improvement over the 1080, but at a cost. Luckily Santa Claus came early for me...

Attributed to a hardware issue - my GTX 1080 Ti has expired. RIP.

Thanks for the quick reply and advice. Mods disabled, repair performed, page file adjusted. Crash after about 15 seconds. Log file attached. I've fitted a 750W PSU instead of the old 500W unit so power shouldn't be an issue any more. Thnxdcs.20231213-194548.log

After a long time without any issues my game has started to crash. No hardware changes, and although I suspect running my system on a 500W PSU isn't helping, it was working okay until a day or so ago. I have tried Flappies troubleshooting guide but drew a blank, so would appreciate any insights anyone may have? Notes - DCS loads and I can select "instant action" and an F-15E Nav mission. I noticed a "stutter" during the splash screen at "world load 1/60"...this normally just races through to 60/60 but stalls at about 20/60 for a second or two. Once into the mission the screen will be filled with gobledegook after about 30 seconds, and then there will either be a hard crash (system restart) or a DCS crash (system resets to desktop). On the last DCS crash I have attached the log file. Tried running Passmark and had issues at 3D Graphics benchmark so I suspect a hardware problem? dcs.log-20231213-073810.zip

Ticked select in VIACOM and switched off "easy comms" and that seems to have fixed whatever the issue was...all my Caucasus freqs. work as they should do. Probably just an odd combination of settings I had selected.

Thanks - will give it a try. Also switched off "easy comms" to see if that makes a difference...

I get the "U" and not the "V" on Radio # 2, but I also have this issue where, on a manual setting, whatever I enter in the scratchpad (e.g. Batumi on 110.30) when I transmit it sends on 127.50. Manual setting, asterix in the correct box. I use viacom so have a PTT switch set up...using the "comms menu" and F5 for ATC the settings look correct e.g. Batumi is highlighted and I can interact through that menu correctly, it's just on the radio on the UFC. Am I doing something wrong or is it a bug? thnx

I had the livery folder set to F-15E. From you post I changed it to F-15ESE and there they were! Many thanks for the reply.

I'm trying to download some F-15E liveries. Once I extract them and add them to the x:\saved games\...\liveries folder they look like this and don't work: Previous liveries show the x.dds files as thumbnails but these ones don't. Tried various things, such as: - virus on/off whilst downloading/extracting - livery folders in x:\dcs\openbeta\bazar\liveries and or x:\saved games\...\liveries\F-15E, etc. Managed to get some F-15C liveries downloaded and they work fine, so the "method" seems okay, just unable to get the F-15E ones to work??? Random issue or incompetence? Any ideas?

FWIW - I have been flying the F-15C for at least a year...at the start I could barely crash it very well! However, after a lot of practice, lots of training videos and a lot more practice, I reckon I am pretty good at getting an F-15C down without bursting a tyre or bending the U/C. Not bad since my PPL was on C-152/172 and getting on for 40 years ago. Moved onto an F-18. The basics were there, and after a lot of familiarisation, I could make a decent pass at a dry landing, and just about get away with a CAT-1 carrier trap. Not pretty, but not bad. Then, the F-15E comes along. Now I LOVE the F-15 with a passion that isn't altogether healthy, so if course I had to get it... The basics are still there. I am still in the familiarisation phase. I haven't crashed or bent her on landing (yet). I can just about get her to 21 AOA, maintain around 170Knts, and manage my sink rate so that I can make the landing work. I find A/B is optional depending on flare/travel down the runway etc. I really struggle with the base turn into final from an overhead break: I cannot seem to coordinate the descent and turn so that I line up nicely on the C/L with a few hundred feet to go. I think the "simplification" of the F-15C model is more apparent when compared to the F-15E (in my case at least) and it feels like big difference is that the "weight" of the F-15E is there whereas it isn't in the F-15C (apologies - subjective but that's how it "feels") so there is a lot more momentum and "physics" involved. More practice is needed. Once comfortable with the basics I plan to practice some more until I can get it polished, and then I'll practice it some more. (Maybe not that helpful but useful therapy for me, and I feel better getting it off my chest - thanks for listening.)

I agree - until a month or two ago I was happily seeing decent FPS (60+) using GTX 1080 and DCS MT. @MbR2XgD - can you confirm if you are GPU limited? Your video suggests you're not maxing it out.

Sure thing! See also -

Self healing software

Didn't need to un-install it...logged on to do that but everything was working fine!

Hi - until very recently I was using a GTX 1080 (with i5-9600k, 32GB RAM, 1440 monitor, in a fairly low-end system) and getting high 60-70 FPS with higher in-game settings than you have set. Then suggest you check out the various YT videos on how to optimise settings (Spudknocker has a particularly good one which includes NVidia Control Panel settings) but there are plenty of others. More recent ones include specific settings for multi-thread to ensure your system is making the most of the new MT. Then it's a question of experimenting to get the best "sweet spot" for your system vs game settings. IMO you should be able to run reasonably high settings with FPS in the 40-60 range with a GTX 1080 in MT as that's what I was getting. It did take a bit of research and "tweaking" to get it working like I wanted it. Good luck and happy experimenting!