Jump to content

TAW_Impalor

Members
  • Posts

    722
  • Joined

  • Last visited

Everything posted by TAW_Impalor

  1. No, I surely know what fusing I use and I looked back long enough for the delayed ones. The mission file attached. Thanks for checking! bf109 bomb.miz
  2. I have a simple practice mission where I bomb ships with unlimited ammo. I only see some of the bombs explode (on target, on water or on the ground), with some 70% chance that they don't. I know how to fuse etc. Same bug happens online (ACG), which is a shame given only one bomb attachment and long hauls. I don't remember such a problem in 1.2, but I only tried bombing today in the 1.5... Showing the track is useless, as they no longer match what happened (( Anyone else noticed this?
  3. Two flights, two DCS crashes today, both on ACG WW2 server. Both times when I was shooting and hitting someone, the game froze and "restarted" to the black splash screen, but the engine sound continued. I see a lot of errors in the log file!! After the first crash I restarted and let the pilot sit on the ground idle for half an hour - no problems. Then took off and fought for 5 minutes - splash screen again and stop. This game is unplayable for me anymore, all these money I paid are down the drain (((( logs.zip
  4. My game displays black screen with DCS logo, and then crashes (( Logs.rar
  5. sure, but it's a bug. did not see it before...
  6. P51 quick take off mission. Screen goes dark when pointing the airplane in a certain direction, as if facing the sun. But the sun is set. Not a blackout, flying slow and easy...
  7. In quick P51 vs P51 I killed the guy and landed "dead stick" on a road, but the track shows otherwise! The other plane survives and I crash in the field, far from that road... And that's in a stable version. bad track.trk
  8. Must be easy to implement or to add an option. I hate to wait several seconds before I can reset the view to my default in quick combat missions.
  9. If you read through my post, restarting after setting High brings about the FLIR bug. Only restarting with Low settings and than changing to High without restart gives a solid predictable bug-free result!
  10. this is not what I see! setting low, restarting, setting high, launching the mission gives me hiqh settings with no bug!
  11. Pagefile on ramdisk?? Why not just disable the pagefile - will be the same effect! ))
  12. OK. Now I am completely baffled, but I got somewhere! * The "FLIR Bug" symptoms are: sharp drop in FPS and CPU utilization when turning TGP in WHOT/BHOT mode and/or IR MAV on MFD. Then done on both MFDs, the effect is cumulative. It does not matter if the MFDs are in the field of view(!) ** For all testing I used Instant Action "Easy - Russian Foothills - Fall" and put the mission in active pause right after the start. So, except for the wingman flying around, the conditions are always the same. I wiped DCS.openbeta folder, removed all mods and repaired the DCS before the tests. 1) Installed 8 Gigs of new memory to bring RAM to 16. NO DIFFERENCE at all! 2) Reduced all settings to NO/LOW (see attach). The bug disappeared!!! I.e. instead of FPS drop 100->44, it is now 130->110. On my old 8 Gigs this test earned no results (although, I only tried it once). 3) Now, one by one moving the settings back to High/Ultra as before (screen attached - I will call this setup "High", but it is not the High preset). Starting from the bottom, and restarting the quick mission after each change, I was trying to find the culprit. 4) After returning everything to High, I STILL SEE NO BUG. Base FPS is now at 120 (was 100) and dropping with FLIR+MAV to a decent 100. Double checked that all settings are back ah high, try again the mission. No bug!!! 5) Reboot - restart DCS to see if the bug is gone for good. All settings still at high. The bug is back!!!! Base FPS 120 - still higher than before the experiment (100), and drops not to 44 but to 50. I can't believe my eyes. 6) Now, instead of lowering all settings at once, going one by one from the top. Base FPS goes higher and higher, but there is still a sharp drop with FLIR+MAV. And only when I lowered the last parameter - Anisotropic Filtering from 16x to No, the bug disappered! 7) Is it the AF causing the bug? Upped everyting else to High/Ultra, except the AF - the bug is back! 128->48... 8) Again reducing other settings, one by one, trying to find at least one eye-candy I can use. 9) With only Terrain Textures at High and everything else at Low/Off, the bug is now extreme 136->36!! Never before it was 36. always 44 minimum. 10) ALL at Low/Off again and I ended up with the most severe version of the bug: 143->37 (((( 11) Restart DCS again, NO BUG at all Low (143->120)! 12) Moved all to High - again NO BUG (105->100)!!! 13) Restarted the mission - a little bit bigger drop (108->91), let's say no bug. 14) Restarted the mission again: 114->99. 15) Restarted the mission again: 114->99. Everything seems stable. 16) Now, re-launching the DCS. As you have guessed, the bug returned: 107->47. 17) Re-launching the DCS again. The bug is here: 115->49. 18) Re-launching the DCS for the third time. The bug is here: 106->47. 19) Now, reducing all to Low, OK, then back to High, launch. The bug is here: 105->47 20) Again all to Low, 140->66 21) Restart DCS, same Low settings - No bug now. 22) Restart DCS, and before launching the mission, I change all settings from low to high. Launched the mission: 100->87, NO BUG appeared!! 23) I ran a few more tries and reproduced the results over and over. I came to the conclusion: The only way to run A-10C on my machine is to set all settings to Low, re-launch DCS, return everything to where I want it to be and then play. It seems important with what settings the DCS launches - it must be allocating some resources one way or another. I don't know if 16Gb of RAM was important, but it is still nice to have them. I spent five hours today on these tests(!!!), but at least there was a result. (And I paid good money for all the modules I have.) I hope the Devs will get to the bottom of this bug. Please confirm you are reading and taking action! Thank you!!!
  13. Could you post a screen of your settings page, please?
  14. DCS writes quite a few temp files, god knows why. Worth a try!
  15. Great! I think the new drivers only cater to their newest cards, screwing up older models. To make you shop and is exactly what Windows/Intel and Apple crime syndicates are doing.(((
  16. Could you look in the task manager how much RAM does your DCS use?
  17. @raptorsim: My sig is clear: 8Gb DDR3 Ram, 2Gb vram, no SLI. I tested everything at low and reported earlier in this thread "no improvement". I also reported that looking away from MFDs in FLIR/MAV modes still bears FPS hit and that I see a significant CPU utilization drop when turning these modes on. So my conclusion is that the videocard has nothing to do with that. I have ordered more RAM, to up it to 16Gb and will report... and I don't see any memory leak...
  18. Did you try assigning your TEMP and TMP folders (both user and system variables) to a RAM drive? I did it ages ago, helped me with DCS stutters. It is also great to delete all the crap various programs leave )))
  19. What's your memory usage with DCS? Mine is 4.1 with 1.5 free, BUT pagefile at 6.7... UPD: Ok, that high pagefile usage was reported by MSI Afterburner. Windows PerfMon shows a mere 5% of 8Gb allocated. Still curious what others see... UPD2: Disabling pagefile did not make a differene to FPS. Afterburner still shows I'm using 6.7Gb of it (LOL), while PerfMon won't even allow to add the measure to the chart. I did order 8 more Gb of memory, will update when it arrives...
  20. Do all the guys who see improvement from 1.5.1 have 16 Gb of RAM?
  21. I further noticed that FLIR/MAV kill FPS even when I look away from the MFDs. I suspect that the bug is not video related, but some algorithmic bottleneck. CPU utilization drop may be an indicator of this.
  22. Funny thing just happened. I finally risked upgrading my video driver from 332.21 to 358.91. Yes, my driver was 2 years old, but anything newer was giving me random BSODs at the time, so I rolled back. This menu screen with clouds used to run at 130 FPS, but now only at 19! 19, Carl!!! In game FPS are 5-10 lower as well. I did a proper wipe with DDU, all video settings stayed the same. Way to go, Nvidia...
  23. Your pilot has cold! ))
  24. Nope! )) Same smoke happened in free flight mission...
  25. I did, nice! But I still like Diveplane's mod better...
×
×
  • Create New...