Jump to content

Scratchy

Members
  • Posts

    140
  • Joined

  • Last visited

Everything posted by Scratchy

  1. There's a vid from the Grim reapers which demonstrates this being a problem with the shadows. (I think the new trees and their shadow maps.) The solution is to use Flat Shadows. There's 2 spots in configuration where this is set. If this has already been posted elsewhere, sorry. I found that my FPS is halved flying low, until I changed to Flat Shadows.
  2. I'm new to the Viggen as I bought it during the current sale; so I'm not a vet on flying characteristics... Something changed with the last update. The aircraft flies as if the rudder is deflected. This is new. I started hot on the runway. It tracked the centerline during the takeoff run just fine. As I rotated, the yaw became off and as I leveled off the nose drifted hard right. Correcting with rudder caused a marked dutch-roll. I tried the flight again and it was normal. There's something not getting initialized correctly, i guess. I didn't touch the trim either time. I haven't tried a cold start since the update. So, I don't know what that might bring.
  3. Thank you. Your guides are wonderful.
  4. No shots from me. But, this seemed like a good place to say: "Wow, DCS dudes/dudettes". The map looks super. I think you guys have really hit your stride. By far, the best looking map in the set. Congratulations ED
  5. Thanks very much Sham03. This has helped my single-player problems quite a bit.
  6. I tried that. The results are interesting and hopeful. I haven't froze up since using these settings, but that probably doesn't mean much, since reproducing freezing is a random event. However, setting Process Lasso to Single Core Performance effectively turned off hyper threading. Meaning, only the primary cores are being used and the virtual cores are not. The other Process Lasso settings are probably useful too. Anyway, I've had one studder without a crash in about 6 hrs of flying missions since these changes. This includes flying the A-10C which seemed to be the worst offender for studdering while flying missions. Thanks to the primary poster for the document. Your results will vary, but for me, this has helped.
  7. I'm still getting the freezes after the latest update. This last time, I simply glanced down to my lap and that caused the shudder for 2 frames or so followed by the freeze. As I've mentioned before, it seems to be caused by rapid head movement (my head, with TrackIR in use.) I had only one monitor enabled. I was flying Piercing Fury mission. This seems to only happen while flying missions, but who knows? I guess I'll have to stop using TrackIR for now, if I want to fly any missions... FYI
  8. My game freezes are less frequent after changing Pre-Rendered Frames to 3. But, it still will happen. What seems to trigger this freeze, for me, is sweeping my view around too rapidly/vigorously. I use Track IR. Checking my 6 caused a freeze last night.
  9. Better, now I haven't had any more freezes after I set PRF = 3 in the nVidia control panel. I also changed the FOV to 120, but I have doubts that was a factor; I use one screen and no VR. FWIW
  10. Same here. I get game freeze and have to use task manager to kill the DCS process. It seems to get out of sync. I get 1 or 2 more frames at increasingly long times till it finally stops. There's still activity judging by the activity on the various cores of the CPU. I have 2 monitors, but am running DCS on one only. As far as I can tell, it seems to happen to me during missions when something new getting spawned gets triggered. Example: Mission 1 for Piercing Fury after I get the 9-line and the 'red' smoke is to be popped. Edit: Anther way to cause the freeze, in my situation: Use Active Pause. When I've used Active Pause and then un-Active Paused, I can count on getting a freeze a few minutes later.
  11. Speaking of documentation... I'm a bit fuddled. I have the FTQ installed. I see there's a download for various maps and so on and these download as a MIZ file. How do I 'use' these? The files are named DCSWA10C_CMPDOC01.V1.5.miz and DCSWA10C_CMPDOC03.V1.1.miz. I downloaded them through a link to the user files portion of the DCS site. Thanks.
  12. I am running as Administrator. I didn't make it clear I guess. I'm error free at last! I was able to complete a couple of campaign missions last night, including the very long 1st mission for the UH-1H campaign. Thanks for looking.
  13. Update for the curious It's been a long and dismal journey, but I made it! TL;DR: My memory data rate/frequency was causing the problem. The Story: After a long period of not being able to fly for more than 10-12 minutes before a "DCS has stopped working." error message, I have finally solved the problem. This post is a history of the problem and how I finally tracked down the solution. I have a fairly hefty system (my specs are in my signature) but nothing special. I've been running 8Gb of DDR3 memory for some time (few years) with a data rate set at 2133. With this setting I'd been running DCS without any issues. Then, problems began after some point. What triggered the problem was unknown. A Windows 10 update? Driver update? DCS update? I couldn't pin it down. I tried rolling back video drivers. I cried on the DCS forums, hoping for some kindred spirit would point me in the right direction. Clean installs of DCS versions. Nothing helped. I gave up. What does one do without DCS to enjoy? Play other games. In my case: Factorio. But, you can only swat bitters and spitters for so long, so I started playing other games. And to my dismay the games using Unity or directX 10 also crashed after 10 minutes or so. Ah ha! One more bit of information is needed at this point: I added 8 Gb of memory; doubling the total amount to 16 Gb. After all, I needed to get ready for the Red Flag campaign. All I did was add the memory, check the BIOS settings and verify the memory was detected and running at the same data rate. I also ran benchmark and stress tests (RealBench). There wasn't a add memory and experience crashes event. The crashes began some time after adding the memory. Back to the story: Crashing regardless of the app running. That's the clue I needed. I ran extensive memory tests over-night. No problem. I did clean install of old nvidia drivers--still crashing. So, it must be the memory, right? It was. I toned down the memory's data rate to 800. All is well and everything runs fine. I moved the data rate to 1600. A modest but acceptable data rate. Still A-Ok. I can't tell a difference between 1600 and 2133 data rates. I may take it (the data rate) up to the next setting (1866 maybe? Not sure) and see what happens. Long story, I know. But some might find it helpful or interesting. Summary: 16 Gb of memory with a 2133 data rate on my motherboard is a no-go. Theory: As you may or may not experience with DCS and other high performance open-world applications, there are instances where it is necessary for additional data to be fetched into memory. It may be a predictive algorithm or maybe it just happens when you approach a chunk border. Dunno. However, this instant causes a slight hiccup on my system. Further, this is where my crashes were occurring. This data fetch into memory exposed the problem with my system's configuration.
  14. My favorite changes as time goes by. The one I return to again and again is the A10-C. It is the first fixed wing aircraft in the DCS series and is great fun in that it is so varied in the roles it can play. Kinda like your first love: always will be a place for her in my heart. Over the last year or so, I now have a 'thing' for roto-winged critters. The Ka-50, Huey and Mi-8 are great. Having spent my entire aviation hobby in fixed wing aircraft I initially found helos obtuse and impossible to fly. However, with some study and video watching, followed by some practice, I'm able to make helo flying happen. Ka-50: Very cool, Russian and it can bring the pain. Huey: Vietnam. Super flight model. Mi-8: As heavy an airframe as is presently available in DCS. (may not have the highest MGW, but flies heavyish) My roots are in heavy airframes. I really enjoy all the modules, but these are my favorites at present.
  15. Thanks for the explanation Abburo.
  16. I have also had 'DCS has stopped working' crashes since January. I've all but stopped flying DCS. I suspect it's some issue with DX11/drivers and DCS's DX11 library; new API: new problems. It may not even be on DCS's side. Could be root problems in the graphic driver's implementation of the DX11 standard. Perhaps the way DCS uses this standard exposes the problems. Anyway, I'm not getting why one would suspect a USB power issue as the problem. If that was the case wouldn't there be sudden reboots and blue screens? Also, crashes regardless of application running? (as USB devices are powered when plugged in) Not trolling--just curious.
  17. I too have seen the blue screen crash with 2.0 since last nVidia driver update. The Windows 10 blue screens show the name of the offending service---it was a video driver message. With the driver(s) before this, I was seeing "DCS has stopped working" crashes. I'd take this over blue screens any day. :( I don't think there'd be any logs/tracks with a blue screen? I was simply doing the Instant Action on the UH-1H and had been flying about 10 mins.
  18. I can't really help, but let you know you're not alone. I've tried many things (reinstall, roll back driver version, reduce graphics settings, running as administrator, reinstall VC++ runtime, etc) and I still get what you're experiencing: "DCS has stopped working" messages after some variable amount of time flying. This rules out doing missions, obviously. I'm sure DCS will eventually fix this problem. In the mean time, I have to resign myself to short flights and wait for the next update. Good luck.
  19. With the last update to DCS world, I'm still seeing crashes (DCS has stopped working). I've been staying with 1.5.x and flying the Mi-8 and UH-1. Both will crash (stop working) after a few minutes. [DCS is so vast now, with so many modules and mission, it's hard to pin down a way to reproduce each time it crashes] Lately, I've been flying the 1st UN Pilot mission. I've repaired DCS. Removed all mods. Checked VC++ runtime. Rolled back vid driver to prior version. After this last update, I can go longer before the crash, but still have crashes. About 15 -20 mins. I'm sad. Questions: Is this a module issue? Would flying only the A-10C solve my crashing? Would a clean install help? Would any devs or interested individuals like to see my latest logs etc? Anyone else having this issue? [adding logs] Logs.zip
  20. Chiming in. Each time there's an update, I have to use an activation. This only occurs on this module. My solution is to uninstall the MiG-21 before I use up all the activations.
  21. I've seen crashes in both versions (1.5 and 2.0) after flying for some variable amount of time. This rarely happens. Both time in cruise flight. No weapons being used nor conflicts with AI. It is single player. I think it might be related to toggling mirrors on/off...maybe. I've attached the crash dump and log. This is from a flight in the Mi-8. dcs.logs.zip
  22. Here's the post about using command line options. Including the repair option.
  23. That's correct. If you want to use the open alpha version (2.0) you will have to purchase the NTTR terrain. The DCS World version (1.5.x) is free with the 2 free aircraft.
×
×
  • Create New...