Jump to content

Aluminum Donkey

Members
  • Posts

    1088
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Aluminum Donkey

  1. I wouldn't worry about that, how bad could it possibly be? The worst you'll have to do is re-create your custom missions from scratch It's still DCS World, and if 2.7 can't cope with existing missions, then how will it deal with the massive amount of work that ED (and others!) have put into existing modules? AD
  2. It isn't a bug. When you speed up time, more stuff has to happen in the sim for each frame. So, you get fewer frames per second of real time. Makes sense? AD
  3. Sounds great, I wouldn't mind being able to fly WW2 dogfights without my screen turning into a rectangular disco ball. Peace AD
  4. You'll need a much heftier graphics card, and probably a new motherboard and CPU with an unlocked multiplier that can run at well over 4.0 GHz on all cores. AD
  5. I know people like new stuff, and I'm looking forward to the Typhoon myself. But, I think it would be in ED's favor to not bother with new content and improve the simulation engine instead. Fix all the graphics bugs! Flashing clouds, flickering WW2 propellers, the infamous yellow/orange/black flashing, and generally improve performance (Vulkan API!!) and just polish the sim engine overall. There are enough bugs that people are irritated by it, and that's just no good for a video game that people have spent over a thousand bucks on over the years! AD
  6. You could put the pagefile on your 120GB 840 EVO, and use it for nothing but that. Put the Windows Environment Variables on that drive as well. That way when it wears out, a replacement is cheap AD
  7. Connect your two boxes with an Ethernet cable and rip DCS from the old drive to the new one. Then copy your Saved Games\DCS folder to the new machine. Should work just fine--DCS isn't tied into Windows in any way and its copy protection doesn't have anything to do with your old machine or old Windows install, so you should be able to just copy it over and you're ready to rock 'n' roll. Peace & happy warfare AD
  8. Hmmerhead, In my own experience installing DCS on both SATA3 and NVMe drives, it makes very little difference. NVMe is best for tranferring very large files, but makes little difference in gaming. Load times for missions are about the same. If you don't have much room left on your NVMe boot drive, get a SATA3 SSD for DCS. It works just as well. A great improvement can be had in DCS with more and faster memory (system RAM), though. By the way, "performance" (framerates, FPS) are NOT affected by the storage device you use. Just loading times and texture streaming in-sim as you fly around the map. I run mostly high settings and find a SATA drive fine for this. AD
  9. Taz1004, Thanks so much man, much better than the bleach-blonde default trees in the sim AD
  10. That's true. It's just that I've never had much luck with cluster weapons in DCS anyway. The explosion effect looks cool, but doesn't do much of anything to the targets that you hit. AD
  11. Yeeaaaahhhh... Noticed that myself. Just use the C version (single warhead) and hit each aircraft (or tank, or other ground targets) individually with one bomb each. That seems to work. AD
  12. Klabo, Did you try down-clocking your GPU? The "DXGI_ERROR_DEVICE_REMOVED" message means your GPU is crashing. That's why your system is crashing to desktop instead of giving you a Blue Screen. Messing around with reinstalling/repairing DCS isn't gonna help with that and neither will re-installing Windows and/or changing graphics drivers most of the time. If it's always, always doing it, and muffing about with graphics drivers, Windows settings, repairs/reinstalling, different brand of beer, different swear words etc. aren't helping, it's probably an excessive GPU clock--even if you haven't overclocked your GPU. It's very common for GPUs to be factory overclocked excessively right out of the box. Great benchmark scores, but lousy stability. Reduce GPU clock speed and fly a while, see what happens! AD
  13. The Kurfurst was a tough bitch to smack in real life too, especially a later version with 2,000 HP on tap at 2.0 ata supercharger pressure (not modelled in DCS.) It had other-worldly flight performance for its day and could out-fly just about anything the Allies could throw at it. It probably also enjoyed certain "benefits" such as a short engine life at full power, and short range due to other-worldly fuel consumption AD
  14. +1 I've got a bunch of empty beer cans kicking around here, I wonder if they'd let me trade 'em in for the Syria map
  15. Klabo, Down-clock your GPU. Crashes to desktop are often, if not usually, causes by excessively high GPU clock speeds. Graphics cards are often heavily overclocked right from the factory, so even if you have not overclocked yours, it might be running much too fast already and it isn't quite stable. The GPU crashes and the sim dumps you to the Windows desktop--that's why you're getting the DXGI_ERROR_DEVICE_REMOVED error. Down-clock your GPU by maybe 200 MHz or thereabouts and try again. Once it's stable, bump the GPU clock up again in small increments until you find a nice, fast speed where it's still completely stable. Worked for me. AD
  16. I bit the bullet (and ate the cash) for a 32" 1440p screen a while back. Now I wish I'd gotten a 40" 4K one. But, then I'd want a 60-80" 8K one and a GPU that can drive it at acceptable framerates. Then I'd want... You always want a bigger screen with higher resolution, and then you always want higher framerates. You know how it goes AD
  17. I remember buying my first SATA SSD just for DCS and nothing else. It's DCS so it has to be fast, so an SSD is good--but, it's still DCS, so I better get a HUGE one. That way, I'll never run out of room, plus I'll have some extra space for Windows and some other things. 240 GB. I'll NEVER fill all that space up AD
  18. For VR... Well, the answer you expect Wait it out for that RTX 3090. It'll be a pain in your arse to wait for, and a pain in the wallet to pay for, but that'll be it. Then you can just run the dang sim with a minimum of BS. I'd consider that 1080 you have to be marginal for DCS, and woefully inadequate for VR. AD
  19. In all fairness, you could probably do that in real life no problem at all. The manifold pressure (supercharger boost) was pretty low, only 1.4 ata, so it wouldn't really have been a big deal to fly an entire flight on WEP. It would have shortened the engine lifespan, and of course it burns fuel more quickly than lower throttle settings, but WW2 engines running at almost 1.4 ata continuously weren't uncommon. They just didn't like it because it wore the engine out faster, but I don't see why there would be any catastrophic failure at 1.4 ata continuous. AD
  20. I'm using the BU0836A 12-Bit controller. 8 analog axes, 32 buttons. I'm pretty sure that's the maximum number of each type of input you can have on one USB port with DirectX, so if you want more than that, you need to use two of these boards. They have *really* high analog input resolution, great if you want to fly helicopters, but great for everything else too. I'm not sure what you mean by "emulation mode". The BU0836A just plugs into a USB port, and Windows detects it right away--no driver or anything. AD
  21. Hey, I use one of those too! The factory-built TM Cougar is an absolute pile of crap. The stick gimbal is total crap, the buttons are cheap crap, the electronics are crap. Oh yeah, I almost forgot to mention, the stick gimbal is pure unadulterated crap. Did I mention that the stick gimbal is crap? That's a lot of crappy junk for $600 if you bought it new. I bought mine used for about 200 bucks, acutely aware of the fact that it was mostly a pile of junk, and ripped out the stock electronics and replaced them with Leo Bodnar's excellent USB interface board. The stock gimbal is still crap, but I replaced the cheap potentiometers with Hall effect sensors, and re-worked the gimbal and pivots bearings to eliminate as much of the slop as possible. It was an awful lot of work to put into a pile of junk, but it's now, actually, a pretty decent flight stick & throttle. The total cost of all mods was about $60 including the Leo Bodnar control circuit--plus a hell of a lot of work. $260 for a decent HOTAS isn't bad. The all-original TM Cougar is atrocious, and I spent more time overhauling it than any sane person should. But, it's decent now, and the cash cost was half-decent. Terrible, TERRIBLE product, though, and Thrustmaster charged an outrageous price for this pile of garbage with its low-quality components and atrociously shitty design and workmanship--it was ready for the garbage pile when it left the factory. Terrible, low-quality product that even 1980s China would have been ashamed of. It only becomes decently usable after a lot of work. If you don't have a lathe and a milling machine, you're sh!t outta luck--don't waste your time on the Cougar. But... That's what I use Peace and happy warfare AD
  22. Obviously they did it that way to avoid getting sued. Why else would they do it? It's blatantly obvious...
  23. Go into Options, Special, for the Hornet. Set your Afterburner Detents to Always Off. That way, the burners light up when you push the throttle forward far enough. Otherwise you'll have to bind a key or a button to "Cycle Afterburner Detent" to toggle the detents every time you want to use the burners. AD
  24. Ok, I've had this happen too and it only happens in DCS, rarely in anything else except Metro. For me, and a lot of other people, it's caused by default GPU clocks being much too high. You graphics card and motherboard have a feature called GPU Boost, and it ramps up the GPU clock speed to much higher than the original manufacturer's recommendation under heavy load, which can cause graphical glitches/artifacts and crashing to desktop. In your crash log it says "ERROR DX11BACKEND: DX device removed" which mine did too, meaning a GPU crash. Obviously you didn't actually remove your graphics card while it was running! It just quit working and DirectX couldn't detect it anymore, and crashed to desktop. The solution for me was to slightly down-clock my GPU. It took about 60-65 MHz downclocking for me, not very much, but if your GPU is running at close to 2000 MHz then it can be a problem, because these chips are actually designed to run at closer to 1700. I can attest that the 460.89 driver is very good, that's not the problem. Try using MSI Afterburner (or something similar) to downclock your GPU and possibly VRAM, by about 200 MHz or so. Try DCS, and see if it runs properly. Slowly increase your GPU clock until it crashes again, and bump it back down. Have fun AD
  25. Because Nvidia drivers sometimes tend to be somewhat less... Functionally Graceful, shall we say, than their hardware, I've stuck with the Studio Driver for now, which is version 460.89. I've had good luck with it, it seems to perform well and be fairly crash-free. AD
×
×
  • Create New...