Jump to content

Aluminum Donkey

Members
  • Posts

    1088
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Aluminum Donkey

  1. Ok, it might have something to do with the fact that my team is set to a Runway Attack mission, not SEAD or Ground Attack. They also refuse to go after aerial targets, even though they're also carrying A2A missiles. AD
  2. I'm playing the 1989_OCA mission and I have equipped my wingman with HARM missiles. When the SAM site start showing up on my RWR as I get close to the target area (airbase with helicopters to blow up) and I order my wingman to "Engage Air Defenses", most of the time he says and does nothing. But, sometimes I get him to say "copy". After which, he just turns around and flies home without firing his HARMs! What's going on? AD
  3. Just adjust it in-sim. Load a mission, press Esc, click Options and play with the system settings. You'll see the effect that adjusting the detail has on cities/infrastructure and forests. AD
  4. I'm using the rig described in my sig, with a 1080 Ti... I have forest distance set to 100%. Forest detail and Scenery detail are both at 50%, which I find gives good performance down low (where it's worst, about 45-50 FPS minimum) and Clouds are set to Standard. I don't find it makes much difference what I set Clouds to, though. Setting Draw Distance (not Forest Distance, the one for ground objects like buildings) has a great effect. I like it on Extreme, but my 1080 Ti is showing its age One plan is to reduce Draw Distance, and crank up Scenery Detail, but I really like Extreme Draw Distance. And frankly, it could stand to be MUCH longer--about twice as much. I'd need to edit the config files for that. And I'd get maybe 10 FPS I'd really love a 3090, but if I had that kind of bread I could buy a really crappy vehicle hehehehe AD
  5. Nobody brought this up (it seems) but the new naming scheme for weapons in the ME is just awesome, now I can quickly get a clue as to what the 13,769 different weapons are instead of having to hunt through the encyclopedia Thanks so much for this ED! Peace AD
  6. Looks pretty good on Low. They are, after all... Clouds Anyone gotten a handle on weird effects near the horizon? AD
  7. Turns out that, when you find an area of the map that gives the lowest FPS, adjusting the 3 sliders (forest draw distance, forest detail, and scenery detail) allows you to scale the minimum FPS in real time So, find your lowest FPS, and then fiddle with these until you get the lowest FPS you're willing to deal with. I set the forest draw distance to max (always looks best), then set the detail levels so it still looks good and and I get good framerates AD
  8. That's cool, thanks for posting! Looks like it doesn't make a huge difference, at least not on your beast system. I always thought it would be great to have less forest and building detail in the distance, but much longer draw distances. I should fiddle with this a wee bit. AD
  9. If you're getting crashes on the second mission, do you have a fixed size paging file? That might be it. I had to drastically increase the size of my paging file to 32 GB. You could also try turning off the Disk Cache if you're using an Nvidia graphics card. AD
  10. Wernst, DCS 2.7 is stable! I had constant crashes too until I removed my VRAM overclock. Sometimes even default clocks (both VRAM and GPU) on a graphics card are too high--they do that a lot because it's good marketing, but it just isn't stable. Before you give up on 2.7 make sure you try under-clocking both your VRAM and GPU a couple hundred MHz. Try it out and see if it's stable. Mine is now! Enjoy the goodness that is 2.7 and then sneak up on stable clocks. 2.7 runs great! Even at lower clocks you'll have better performance overall. AD Bignewy, When people get crashing, you should remember to advise them to try under-clocking their graphics cards, both VRAM and GPU. It usually doesn't take a lot, and this has saved my bacon numerous times after messing around chasing after constant crashes. Default clocks on graphics cards are often just too high. They benchmark great--and crash when a heavy load is put on them. It's something to keep in mind. Oh yeah, 2.7 rocks! AD
  11. Ok everyone, Can confirm that it was my VRAM overclock that was causing the crashes in 2.7. Leaving it at default (11,200 MHz) solves it! I'm still running my GPU at a 65 MHz underclock. Running it at default caused crashing in 2.5.6, so that's where I left it. Maybe I'll try running it at default clock, about 2000 MHz. Card is a Zotac GTX 1080 Ti Amp Extreme Core Edition. If you keep getting crashes, try underclocking either VRAM or GPU (or both) and see if it helps! You can "chase" the highest feasible clocks later, once you get the sim running nicely. Looking good for me so far! AD
  12. Your system looks pretty deadly compared to mine, and I have great performance. You might want to double check everything on your rig--clock speeds under load, that sort of deal. DCS 2.7 kicks ass. AD
  13. ...The only thing that seems to work for me is removing a +145 MHz VRAM overclock I had. I have a GTX 1080 Ti and I had to down-clock my GPU (the GPU itself, not VRAM) by about 65 MHz to get it stable in version 2.5.6. So, it seems now that the +145 MHz VRAM overclock on my graphics card is what was causing the crashing. Seems OK now at 0 overclock on VRAM, and -65 MHz on GPU. If 2.7 is causing you constant annoying crashes, try downclocking your card--either GPU, or VRAM, or possibly both. Try one at a time first, of course. Graphics cards are notorious for being heavily factory overclocked. Reducing this may solve your crashes. Peace and happy warfare AD
  14. ED, Been fiddling around with 2.7 for a little while. I'm not a woman but if I was you'd be scrubbing my lipstick off your ass cheeks. Not only is the yellow/black flashing finally completely gone, but so is the WW2 propeller flashing, almost all of the stuttering, and various cloud shadow related lighting glitches. The flashing/glitching smoke trails from burning aircraft are gone too. Everything runs nice and smooth and performance is great even with all sorts of goodies turned on, even on my aging computer! This update is something that DCS has needed desperately for a very long time now. Kudos to all involved for a mighty fine job! Peace and happy warfare AD
  15. That's as good an idea as any--since 2.7 is a major update, it's a good plan to wipe out fxo and metashaders2 and let DCS rebuild them from scratch. Also, SLI has never gotten along well with DCS. I just don't think DCS is coded to make use of it. If all else fails, disable one graphics card and try again. Also, check for excessive overclocking of GPU and VRAM, which can cause this too. OP, keep us posted, I'm curious how it works out for you. AD
  16. Sounds like a killer system. If you're running your 4000 MHz RAM at only 3600, you can probably reduce the latencies by a clock or two and squeeze more performance out of it. You have some 'overhead' on tap because you're running it at below rated clock speed. AD
  17. Damn straight man. Let them work on something REALLY cool without bogging them down with other BS expectations. The F-4 had it's uses, just like school buses and garbage trucks have their uses. There's a good reason for creating a flight *simulator*. If you wanna fly crusty, rusty old jet fighters with more mileage on them than the Space Shuttle, move to Canada and join our Air Force DCS Typhoon is the ONLY thing I've looked forward to in this sim for many years now, besides DCS F-22 Raptor. Everything else is just bug fixes and eye candy. AD
  18. If you're buying a new GPU don't bother with the 3070. DCS needs all the silicon balls it can get, the 3070 is too wimpy for the price. It's not that it's a bad card--it's just that the price of any new GPU is gonna suck no matter what, so I'd get one that will have great performance and suit your flight simming needs for years to come instead of being a bit of a disappointment and always leave you wanting for more and wishing you could upgrade. Keep using what you have for now, save your bread, and get the 3080 instead. AD
  19. Dustbag, Hang on to your 9600K. I'm using an i5-6600K that I dug up along with some dinosaur bones. Works just fine, runs at 4.5 GHz without too much trouble. The 9900K with eat a bunch of bread that deserves to be sat on until maybe the 12th gen i5 comes out--or even quite a while after that. Your system looks really well-balanced and I'd just leave it alone, a 9900K is far too much cash to burn just for another 2-3 FPS! DCS 2.7 performs really well and you'll gain just about nothing anyway because all of those extra cores will just be sitting on their thumbs. DCS World is clock-speed dependent and little else. Overclock your i5 and enjoy. AD
  20. Don't care much, but it's getting to the point where equipment just to play video games costs as much as a good amount of flying lessons in a real aircraft. Imma stick with my archaic rig. The "good" new stuff is great until you realize it isn't--for the price, it's downright lousy. It's still just another consumer product, not a mansion with a late-model Learjet included in the price The 3090 looks like a neat toy, but this stuff is for people with money to burn. It's for Hollywood plastic surgeons and not machinists or welders. I'm old, I remember when CD players were $5000 and they were apparently pretty bad when they were new AD Bingo bango. I'm glad somebody gets it. If you're an electrician or a plumber you're probably not going to marry a supermodel. Private jets aren't for people who pump gas for a living. It's how the world works. Find something better to do than gaming AD
  21. Flashing, cloud shadow glitching, stuttering is all gone! Mission loading times are better too! It's been a LONG time coming, nice job ED!
  22. Can confirm 2.7 kicks ass No more yellow/black graphics flicker. Propellers look awesome now! Stutter-free. Great performance even with Ultra cloud settings and runs smoothly now even at lower framerates, so you can turn up your graphics settings if you like and it'll still fly great! VERY fine work ED! AD
  23. Woooow! Mine was only 15 GB. I have NTTR, Normandy and Gulf. Many modules. No idea why yours is so huge. AD
  24. What I meant to say (sorry for being a bit of a smartass) is that it's still DCS and you're probably not going to have any problems at all. I have a nagging suspicion that 2.7 isn't going to be much different aside from the way the clouds look, some wind/weather effects, and hopefully graphics glitch/flickering fixes. It's still the exact same game so all your missions should work exactly the same way. I wouldn't be concerned. Frankly, after the noise of the hype train has died down a bit, I wonder if they'll actually release 2.7 any time in the next few months. AD
×
×
  • Create New...