TAW_Impalor

(SPOILERS) Flying it now. Killed everyone in compound, but vehicles count 30/36. I guess three are the surrounded tracks, don't wanna shoot them so as not to kill any blues. I need to find the remaining 3 vehicles on the map? My superman wingman does not see them either. Heli was shot. The yacht was interdicted, should I sink it? Was not ordered, but boats count 1/2... Flying like this for half an hour, nothing is happening. Progress 70%... Help!! ))) Ok. got it ))

Hi nuuthei500! Did you use DDU in Safe Mode to clean up your old driver? I have GTX 760 but with 2Gb, and it runs at VRAM limits. So 1.5 may be not enough. Try lowering visibility, preload radius, no Grass and minimal Trees, also try No Tree Shadows mod. One more thing, I noticed old driver 332.21 works better for our "old" card. I get significantly lower FPS in the "clouds" start screen with any newer driver. You may want to try it! And do use Display Driver Uninstaller when changing drivers))

No, if you put the ram.cmd in Startup folder (just drag it to Win Key - All Programs - Startup) it will create drive T automatically on boot. No need to do anything once it's set up once.

Sure. I found the idea on this very forum. It helped me with an earlier version of DCS, but I still use it. Even with lots of RAM the game (and now NVidia driver too) write some temporary files to a TEMP folder, usually on c: drive. Even with SSD this takes some time and creates micro stutters. The idea is to allocate some RAM as a virtual hard-drive and direct system variables TEMP and TMP to it. Now any software that needs to work with temporary files will do it super fast. The added benefit is that on reboot the "RAM-drive" is created anew, so all this crap gets deleted instead of accumulating on your system drive. Here are the steps: 1) google and download "imdisk", install it 2) take the attached ram.cmd file and put it in some folder (I had to zip it to attach) 3) create a shortcut to this ram.cmd and put it in your Startup folder 4) Reboot, see that T: drive is created. 5) Go to Control Panel - System - Advanced System Settings - Advanced - Environment Variables and change TEMP and TMP variables in _BOTH_ locations (system and for your user name) to T:\TEMP (see the picture) Now you can delete contents of your regular c:\Windows\Temp folder and enjoy more space on your c: drive. I do hope this helps you! ram.zip

I had stutters in DCS while ago, which I cured by moving TEMP folder to a RAM drive. I use imdisk via .cmd in Startup folder.

Hi guys/gals with HMDs. One quick question. I read that zooming keys don't work in VR, but how about snap views? I use them with A10 to work with radios and CDU even on a monitor. Would be useful in VR too...

@tiborrr: Thanks for your effort! I totally agree with your conclusion that for multiscreen and VR there is some bottleneck in the engine. In fact, this bottleneck was discussed half a year ago in relation to A-10C FLIR/MAV bug, and I ran some tests: http://forums.eagle.ru/showpost.php?p=2552722&postcount=212 That was with 1.5.0 and 1.5.1 versions of EDGE. Today I ran a similar test to yours to see if my ad-hoc solution still works. I.e. "load DCS with MINIMAL settings and then change them to high in game and launch the mission". I used a 3-minute track of my A-10C flying and used FRAPS, like you did. Here are the results (Min/Max/Avg): 1. DCS launched on HIGH/Usual settings, then I set all to LOW/NO and ran the track: 72/159/107 2. DCS re-launched on LOW/NO and I ran the track with these settings: 138/228/187 (75% gain!) 3. Set all to HIGH/Ultimate, re-launched DCS (important!), ran the track with these settings: 17/56/32 4. Now, set all back to LOW/NO, re-launched DCS(!), set all to HIGH/Ultimate, ran : 39/82/52 (60% gain) I know the settings took effect with no rebooting - based on texture quality, shadows, visibility range etc. So, some people's claim that you must always reboot after each change is groundless. I was not surprised to see these results again, as I did 6 months ago. I am surprised nobody else noticed this. I am now going to open a bug ticket and see what the devs have to say about it! So, there is a BIG difference (on my PC) whether DCS is launched with HIGH System settings or with LOW. I can't explain why it matters, but please go ahead and check on your side! Thanks! PS. I use an "old" NVidia driver 332.21 for my MSI 760 OC 2Gb, as all newer ones give me 10x(!) lower FPS on the "clouds" main screen. I see many people have this problem too... UPDATE: Turned out MFDs resolution only applies after reboot, so the high FPS was with 256. Well, I can live with 512...

Not sure if to post it here or in a Wish List. All knobs in all planes move in reverse to my mouse wheel (DiNovo Edge trackpad). Can it be fixed by a setting or a mod?

works great, thanks!

Hello. I use ButtKicker to feel the stall coming, and it used to work great in 1.2. But no more ((( The cabin shakes on the TV, but LF sound track is no different to that of a normal flight. I tested with P51 and Dora, but this must be a global bug. Please fix this! Steals the realism... Edit: Ah, ok, I had Diveplane's sound mods installed before. Got them back, all good. Only MiG-21 is properly buffeting without the mods...

Yep, thanks! Trying to optimize spotting vs. quality...

Seems to happen after the recent update, or I did not notice it before. Runway texture is "out of focus" until I am really close or zoomed in. I tried all the settings, can't get it right. Other static textures look fine...

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

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?

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

My game displays black screen with DCS logo, and then crashes (( Logs.rar

sure, but it's a bug. did not see it before...

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...

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

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.

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!

this is not what I see! setting low, restarting, setting high, launching the mission gives me hiqh settings with no bug!

Pagefile on ramdisk?? Why not just disable the pagefile - will be the same effect! ))

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!!!

Could you post a screen of your settings page, please?