MadDog-IC

I would say there is a major issue with your graphics card driver, there is a mass of DX11backend "DXGI_ERROR_DEVICE_REMOVED failures in the log file. I noticed that you have windows 10 and 390.65 of nvidia graphics driver, I had major problems with that version with my GTX-780 (made my complete windows unusable, so I would highly recommend that you once again uninstall the graphics card driver and run version 388.71 and then do the standard DCS cleanup and repair. Helped this guy with similiar issues. https://forums.eagle.ru/showthread.php?t=202670 Regards, Ian.

No problems, good to see your up and going again, seems that windows 10 is a bit problematic at times. Cheers, Ian.

May be video related, only by the fact that it looks like it can't seem to run or initialize the DX11 graphics renderer on your graphics card, it doesn't even get to the stage of logging what GPU driver you are using. How well do other DirectX 11 based game behave ??? Was DCS 2.5 working ok, before the new hotfix was applied today ??? If you have done a recent update to graphics drivers or suspect Window 10 has done a sneaky update, I would try: Uninstall the current Nvidia graphics drivers and reload them (Have any antivirus disabled whilst doing that as may interfere with install). Run the normal "DCS_updater.exe clean" command to remove any MOD files from install and the "DCS_updater repair" command to verify your install and correct any issues with missing or corrupt files. Last resort try the old rename of the saved games directory were dcs saves you preferences. Regards, Ian.

It is a limitation of the shkval TV camera system, that it is not good in low light situations, that is why they have a "mercury LLTV (LOW LIGHT TV) pod" as an option for mounting on that plane to see in low light situations, ie at night with candle bombing lighting and of course in bad weather, etc. Same thing happens with Ka-50 shkval and Vikhr missiles. Regards, Ian.

Hard to help, with no information on issue, Just putting not starting doesn't give anyone a clue to: What specs your computer have, does the video card even meet min specs???. What steps have you taken to get the update installed, did it complete the download correctly (did you do a fresh install of 2.5 OB or update from 1.58 OB). Post any dcs.log and autoupdate.log available maybe will give us a clue. Have you removed all addon MODS, can be done at CMD with dcs_updater.exe clean. Have you tried a repair, can be done at CMD with dcs_updater.exe repair Have you followed some guidelines available on other forums on things to do post upgrade such as deleting "C:\Users\Yourusername\documents\Saved Games\DCS.openbeta\Config\options.lua" and re-setting up your options,etc. When you try to run DCS does it: Do absolutley nothing ??? Show a loading screen and fail at some point ??? Show any sort of error screen ??? Regards, Ian.

Use to be able to do: Get the key from the steam version and copy to clipboard if possible Log into ED website and goto your profile page and do a license check and input your key from steam for Su-27 campaign. It should show what module is allocated to that key and weather it has been activated, If it doesn't show as activated, you will have to link it to your ED account at the top of the page. Once linked to your account, log into DCS World and go to module manager and install new module, or a menu may appear offering you to install the newly found module on your way into dcs. Install module and activate and your done. Can't do it that way any more, they removed the linking to the account, you will have to wait now for ED to implement fully their new copy protection scheme in the future. Regards, Ian.

Campaign has had voices for exactly a year now in DCS 1.5x, text to speech voice is better than no speech at all, IMHO. As for the wrong language, I am sure ED will correct that soon as that is only new, probably due to a little blunder with the conversion to multi-language. Regards, Ian.

Another good source for your problem. https://forums.eagle.ru/showthread.php?t=200906http://

Mine is hovering between 4-5.6MegaBytes/Sec on a 50Megabit Fibre optic link, so that is roughly 80-100% of capacity.

Here is an example of my autoexec.cfg for DCS World 2.5 with setting to use only the real 4 cores for intel I7, instructions are in the autoexec on how to set for other cpu core configs. Place the Autoexec.cfg in the c:\Users\YOURUSERNAME\Saved Games\DCS.openbeta\Config\ Regards, Ian. autoexec.cfg

Don't do reload as yet, as probably will not fix it, so long as you leave your saved games folder intact. The 57% loading isssue is related to the c:\USERS\Yourusername\Saved Games\DCS.openbeta\MissionEditor\ directory, back that directory up and then delete it, run a repair and then put back in the files such as logbook.lua from your backup and others as needed one at a time to see which one causes game not to run. I can't find the previous posts about it, but it has fixed many users isssues. Regards, Ian.

Was an interesting one for me, as it didn't really affect DCS 1.58, because it wasn't as graphically demanding, on retesting with 1.58 it was barely just redlining in GPU-Z with over power threshold every now and then. I posted because there seems to be quite a few people with a similar issues and MSI Afterburner may have reset itself when I installed a newer version, it would be wise to check if your graphics card is throttling down even a little, based on the higher workload of DCS 2.5 graphics. I was so put off by the stutter, I thought well my machine is only just over minimum spec for game, I was going to stick with 1.58 and not run 2.5 at all, but after fixing that issue, it runs better than 1.58 ever did in the Caucasus map with higher settings. Good luck with your issue. Regards, Ian.

DCS 2.5 - You getting over 60 FPS but DCS stuttering, check this Having just updated to DCS 2.5 openbeta from DCS 1.5 I was meet with a very stuttery (micro pauses, call it what you will) game play, although the FPS was running at between 60-80fps. Solution for me and something you might want to check: Run GPU-Z to monitor all aspects of video card under load from running a test mission in DCS 2.5, especially GPU core and memory Clocks. Noticed that the GPU clock was alternating between the max for my card 1072mhz and a mediocre 600mhz (strange as I had locked the GPU to max voltage performance in Nvidia control panel profiler for all DCS versions. Noticed that the "PerfCap Reasons line", was redlining and reporting that the GPU was exceeding max voltage and thus throttling the GPU back to 600mhz to compensate. As I run MSI Afterburner for monitoring FPS, Fans, etc, I decided to have a look at something that might help me with this problem. As soon as I went to the Afterburner main page, it was obvious that some how by accident the POWER LIMIT=0% and TEMP LIMIT=0c had been set, changed them to the proper values of POWER LIMIT=100% and TEMP LIMIT=79c and DCS 2.5 now runs really well with all most options on High. Regards, Ian.

You need to change Date of mission to real life month of season in the given maps area and adjust the temperature to suite season. Here is a rough guide for west Caucasus map in valley areas below 2000m: Winter = Dec to Feb with temps of (Nights = -7c to -10c), (Days= -2c to -5c) Spring = Mid May to Mid June with temps of (Nights=?),(Days=?) Summer = May to Sept with temps of (Nights = Cold),(Days = 16c to 20c) Autumn = Mid Sept to Mid Oct with temps of (Nights=?),(Days=?) Happy to be corrected if anyone has more accurate season data, just gleaned what I could from google about the real life area, haven't tested as yet. Regards, Ian.

Thanks for the tip, might be why my x52 pro just started doing this. Regards, Ian.

Just to let most of you know, as ED converts missions from single language to multi-language, the missions will be moved from the (ie: EN directory) to the prior directory (ie: Campaigns). This has already happened on a multitude of mission and campaigns, so a side effect as reported here, is that campaign progressing is lost, because the log is pointing to the incorrect paths. Regards, Ian.

+1 from me too.

Probably a bit late for you since you have it installed already, but for those that haven't started the upgrade as yet, a little info. To make DCS 2.5 see your DCS World 2 openalpha install for the files it needs instead of re-downloading: If your openalpha was installed the correct way originally, it would have the path in the registry, if you just copied and pasted from another install or moved it to another drive, the path will not be registered in the registry in which case you would have to add it manually. (some one else has shown how to do this already) Second option is to make a test file in the root directory of you DCS 1.5 OB version called dcs_local_source.txt with the path to the openalpha install, I have attached an example, you just have to change it to your appropriate path, but leave the double \\ between directories. Regards, Ian dcs_local_source.txt

Bit of an endless struggle to keep missions working across so many patches that interfere with their execution. DCS 1.58 seems to one of the worst updates so far in the 1.5x class, and has AI planes crashing into ground whilst they dogfight, evade missiles and just flying low. From what I have seen now and before is that, most AI aircraft either have their airspeed programmed too low (500km/h is the default when making waypoints - this can be close to stall speed for most aircraft) for each waypoint they are to follow, or a bug has been introduced that aircraft that are set to fly at a high enough airspeed actually ignore that programmed airspeed and just fly way to slow (Needs ED to correct). Other issue is that SEAD missiles are not as reliable as before, was 100% hit ratio, now less than 50% hit radio resulting in running out of ammo before target killed, so they do a gun run to try and finish the job and die (I can program SEAD AI to RTB after all missiles away and not do gun run, but I chose to do it this way), with SAM systems also capable of turning of their radar and shooting incoming SEAD missiles, most missions with SEAD operations are going to fail due to that fact (This is more realistic to real world, so only solution is to put more planes on task with more SEAD missiles to do job). The strike package shouldn't be able to blow themselves up with a bomb drop as they are using MK-82Air or Mk-84Air bombs with retarding shoots to allow low level bombing and to give aircraft time to escape the blast zone, so most likely planes are exploding for no reason, seen that bug before. As this stage I can only make note of your issues to self and investigate when we are all onto DCSW 2.5 and see if the version improves things, makes things worse or just continues to have same issues. Either way I could be very busy for a long time (Possibility of ever mission ever made for caucusus map will need some type of correcting again), so can't give any time frame for any updates . Thanks for the detailed report. Regards, Ian.

Interesting, a lot of the errors still exist, (these errors could be related to features not implemented yet, obsolete features not used anymore, or some files might have been left out of the install cycle by ED as a lot of those sound files it can't find don't exist on my DCS v1.58 install either), either way it is not uncommon to have errors in logs and have game work fine, has been that way as long as I have been using DCS. I just wanted to see the differences in the logs so I can better understand what is normal for current iteration of DCS v1.58 install, hard to diagnose issues when there is many errors in normal functioning game by default. Errors of most concern would be these type: 00719.434 ERROR Dispatcher: lua_pcall failed,?:0: attempt to index field '?' (a nil value). As you said, we can just hope that it gets better with the next iteration of patch / update. Regards, Ian.

would be good to get a snapshot of the dcs.log now that it is running ok, for comparison to the non-working install. Cheers, Ian.

Not much to go on, but looking at the log: DCS is having major issues with finding and playing sound files, so I would assume your install is missing critical files or has mod files installed in the past that are no longer compatible because of the failing lua code and the amount of errors being logged. I see you have the nvidia 390.65 driver set loaded, whilst I don't think that is a problem per say, but I have recently installed that version on my win8.1 x64 system with GTX-780 and it made my whole windows unusable if I put it into sleep mode, when it came back from sleep, graphics drivers was crashing and not responding and causing all sorts of graphics corruption, I had to totally uninstall the whole 390.65 nvidia driver package and install 388.61 to get a stable system again, YMMV. Things to check: If you have installed any type of MODs directly to the dcs program install directories ?, you need to uninstall them. Next do the standard stuff, put an exclusion in any anti-virus program to not check DCS directories or disable it whilst installing or updating DCS to allow dcs and or patches to be installed without interference. Do a command line CLEANUP of DCS install which will remove all non sanctioned files that aren't supplied with DCS by default, this will remove all modified and changed files that don't match the current image of DCS files and folders. Once Cleaned, run the REPAIR tool which will check if your dcs install has any corrupt or mission files and re-download them if there are. Need info on what changed with computer before it stopped working, update in window 10, new graphics driver loaded, etc. Have a look at the Autoupdate_log.txt and post up also which is located in the root folder of the DCS game install, this might be helpful also. If you have done a complete reinstall, install is most likely being interfered with by antivirus program, or your USER saved options may be corrupt. list of instructions here: https://www.digitalcombatsimulator.com/en/support/faq/709/ Regards, Ian.

Something along these lines. Passive Defense means: Chaff / flares against radar scanning and fired missiles and does no combat maneuvers at all to avoid missiles and doesn't engage combatant. IF able to continue and not damaged, at Bingo fuel, or not out of ammo continue with mission, otherwise RTB. Will not jettison fuel tanks or weapons, even when under attack. Evade Fire means: Chaff / flares against radar scanning and fired missile and does basic combat maneuvers to avoid missiles and engage combatant. IF able to kill combatant and not damaged, at Bingo fuel, or not out of ammo continue with mission, otherwise RTB. Will jettison fuel tanks and some weapons, if attacked to become more maneuverable when under attack (can be over ridden with advanced waypoint command to not jettison under any circumstance). Evasive Vertical Maneuvers means: Chaff / flares against radar scanning and fired missile and does advanced combat maneuvers to avoid missiles and engage combatant. IF able to kill combatant and not damaged, at Bingo fuel, or not out of ammo continue with mission, otherwise RTB. Will jettison fuel tanks and some weapons, if attacked to become more maneuverable when under attack (can be over ridden with advanced waypoint command to not jettison under any circumstance). Best to use Evasive Vertical Maneuvers for more of a challenge from the AI when up against fighter / interceptors, but might use other settings for different flights for SEAD or Bombers as they need to accomplish different goals and aren't good for dogfighting. Regards, Ian.

This thread sounds like the old problem on servers, where the mission your playing has been created with the "PREPARE MISSION" option of the Mission Editor, which saves radio frequencies, default cockpit views and a few other things to that of the creators settings in the mission set. The side effect of this is if the creator had a 1920x1080 single screen, and you the client have a higher resolution 3440x1440 or triple screen setup you will have a incorrect FOV (Usually face smashed up to the HUD) because the missions view setting is overriding all of your default settings for views, snapviews, etc on your computer, no amount of playing around with your computer settings will fix it, the mission on the server has to have the VIEW folder deleted from the CONFIG folder so that when mission is played it uses only the clients connected settings. This is very prevalent with Ka-50, A-10c missions more than any other module, because people like to pre-program the radio frequencies, SADL, ABRIS and other options. A couple of the default Su-25T single player mission have this programmed also because they are using prerecorded track files for intro to missions. Contact server admin and get them to modify mission and remove the VIEW folder from the base CONFIG folder. Also don't confuse zoom / and * keys with moving camera position, your moving the camera position with Rctrl+/ and * which stuffs the HUD up in the A-10c but not so much with other modules, I assume if the module has a culmulated sight it will, but with Fc3 modules it doesn't. Over the years with some patches for dcs, it has reset a lot of my custom set default cockpit positions and you just have to set them back up your self again using a combination of the camera positioning and zoom controls, followed by saving them to the Default view, Default Zoom, Default Centre, Default Snapview key positions. I have a mission that has just about all DCS modules in it just for this purpose, I jump into each aircraft with out TrackIR active and go though all of the view options and re-save any that are out of whack. Regards, Ian.

In my experience, that is correct, the more you replay the same mission in succession and or use time acceleration will cause the issue more (Usually only doing this when testing missions anyway). If it didn't calculate results correctly, people playing all of the campaigns out there would be complaining about not being able to advance to the next missions. Regards, Ian.