MadDog-IC

No it wasn't meant to fire, but they sort of will now, quick and dirty effort on my part. Could be related to the days temperature, lighting and or wind in mission. The A-10c and Ka-50 are my personal priorities, but I don't always get to do what I want to ;-). Not by any means, I would encourage you to report anything you deam important, and to be accurate and concise (something I am not), I might not be quite as responsive if at all, but I do take note of issues people report regardless, I scan forums when I am fixing a modules mission sets to hunt out the issues reported. Other would also benefit from such reports. Regards, Ian.

And the problem is ???? What didn't fire the maverick or the smerch ??? (only the first smerch is programmed to fire at the AFB you took off from, all the others are just static with the drivers having donuts) If you have issue with default loadouts, you can change loadouts at base before you take off, no expert on the mavericks, can never remember their capabilities from the designator. Not sure on why the IR maverick wouldn't lock on, where you within the keyhole launch parameters. Also force correlate isn't normally used for vehicles only building I thought when using the AGM-65H. Not a specific mission problem, more a user error or DCS game engine missile / systems bug. New smerch Hunt mission updated with 3*AGM-65D and 3* AGM-65H loadout in previous post. Can't get too bogged down in doing these A-10c mission at the moment, doing a few easier A-10c single mission just to see how much work might be involved with them and for a diversion from the Su-25T stuff I have to get finished. Catch ya. Regards, Ian.

Kind of both, it is possible to get 100% by killing the wrong targets and not getting mission completed and then loosing for not taking out the right targets or protecting the right friendlies. Is a throw back from the compromise between the existing scoring of the ED missions (points for every kill) before I edited them and changed how I wanted them scored based on taking out the ordered: enemy targets, protecting front line units and escorting the advancing armor. You need only do as ordered in the briefs, through out the campaign: If front line armour pop "GREEN flares", you must protect these units from any damage from the advancing enemy and stop the enemy from reaching their assigned objectives. If friendlies mark enemy locations with RED smoke you must take out those front line enemy armour to allow your assaulting armour to advance unhindered and undamaged to their assigned objective locations Others are based on recon and kill what you find there. or Could be what was said in previous message. :lol: Regards, Ian.

Showing other system hidden files in picture so option must be on to show all system files. Usually saves in the expected places, ie: c:\Users\TOM\Saved Games\DCS.openbeta. Don't have windows 10, but may be different if your run DCS without or without admin privleges. Out of interest check this directory to see if it has put it there. c:\Users\TOM\AppData\Local\VirtualStore\ Not generally, except for the separate DCS or DCS.openbeta folders depending on stable or beta branches. Clean and repair will have no bearing on the saved games folder, never touches it. Bit of a mistery, others have had that issue before, but never took much notice about a solution, I think they had to run DCS as admin, didn't initially install with run as adminstator. Thats all of got on that, added "weapons training.miz" to other missions message for ya.

You can just over write the originals, but you will have to re-do that everytime you update DCS, or you can just put them in your saved games folder and play from there. Re-download the smerch hunt.miz, fixed the JTAC LOS issue. Cheers, Ian.

No probs, just as a side note, have your tried my corrected versions on the ED websites USER file section, they had extensive work in dcs 1.5 and may work better that what is in 2.5 at the moment (They will have issues also now, until they are updated once again). https://www.digitalcombatsimulator.com/en/files/?PER_PAGE=100&set_filter=Y&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=MadDog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter I just did a quick test of surrounded and the main things that stand out are: All waypoints for vehicles that travel on road, need to be re-snapped to the road, otherwise they are positioned all over the map and not on the actual road (May cause unknown consequences). All aircraft need to be re-snapped into their parking bays and landing waypoints re-snapped to the runways (If this isn't done, AI aircraft will not move or take off). A couple of tanks in trees need moving. Quick test with AI flying A-10c seem to work fine. Issues with smerch hunt: Waypoint and parking needed re-snaping Few AAA and smerch in trees JTAC blind, has no LOS (Line of Sight) even when placed next to target, moved JTAC and Smerch to get LOS. Try these quickly edited versions for v2.5 and let me know how you go, I think there is an "Line of sight" issue with the JTAC, in editor it shows no LOS with target for all (Laser, IR,etc), even if placed right next to target, so I expect that not to work. Regards, Ian. Surrounded!.miz Weapons Training.miz Defend Camp Yankee.miz Hideout.miz Smerch Hunt.miz

+1 from me also. Working and testing in Mission editor with AI and I have to click all those things off frequently so I can monitor the mission correctly with out to much clutter on the screen, seems totally unnecessary, would be great to just remember what they were set to. Cheers, Ian.

Thank you and others for taking the time to mention these issues, personally I know how disfunctional most if not all mission based in the caucasus map will be now, with the trees, map positions changed and any other introduces bugs, but they can't all be corrected overnight (I do however take note of any issues and would fix them in a heart beat if it was possible and up to me, but there is so much to do as a whole and you can only do one mission at a time, so priorities have to be set). ie: I have been correcting the Su-25T Georgian Oil war campaign with a proximately 100 missions and as a guestimate I can tell you: It is taking me about 1-2 hours per mission just to re-position all ground units, modify advancing units waypoints. Another 1-2 hours to fix other issues and test if things are working as a whole. That is a Total of "200 to 400 hours" / 8hrs a day = 25 to 50 days of work if you did it as a normal job for one campaign. We are all suffering the same anguish, but we need to be patient. Kind regards, Ian.

I bit the bullet and cleared my old 388.71 install with DDU and installed 391.01, seems to have installed correctly compared to previous 390.x driver versions. Pros: Runs DCS and other games ok. Will run for a while to see how things pan out and wait for a fix in later driver patches. Cons: Wouldn't install over the top of previous drivers with out first clearing all traces of Nvidia software with DDU. Doesn't support sleep mode on my machine as previous versions did, comes back from sleep fine, but runs like s#$* in windows with severe graphics corruption which is only fixed with a reboot. (Never have any corruption unless I put computer into and out of sleep). GPU-z reports no CUDA core support, but I would say that is an issue with GPU-z detection of the new CUDA 9.1 interface, as card runs CUDA benchmarks fine. Regards, Ian.

Thought you would like it Gazace. Well said, I couldn't agree more with your comments, you have a great attitude. Enjoy.

You are welcome, Not much, but on looking up the problem this might be you only savior, worth a try, a work around maybe, but not a proper solution in my book: Read first post to see what one user did. https://community.amd.com/thread/196190 How to patch the registry: https://community.amd.com/thread/180166 All I can offer, as it seems to be a common problem. Regards, Ian.

Far enough about the driver version, but the issue is related to video drivers and how your video card is performing. FAULT: The error "DXGI_ERROR_DEVICE_REMOVED" = Your card has been removed whilst in use or the device drivers have failed and mimics the removal of the graphics card. (This is not specific to DCS, can happen with any DX11 / 12 games such as ARMA 3, Crysis3 and many others. CAUSE: Common cause may be an overclocked graphics card (doesn't matter if it is a factory overclock or not), try using MSI afterburner or other utility to drop the core speed a fraction to the reference speeds for your chipset and you may need a small voltage boost also. Under powered PSU may limit the video card also. I would test with GPU-Z utility to see what your graphics card is up to under load with DCS or other hi-end games. See if you get any error messages from windows about stalled video card driver. Might also try reloading DX11 or DX12 if available. Just a couple of google ref: https://answers.ea.com/t5/Crysis-Games/DXGI-ERROR-DEVICE-REMOVED/td-p/1118490 Might try this registry edit, do at your own risk, I have no idea what this is doing ??? Regards, Ian.

You should be able to use the "prepare mission function" of the mission editor to save all radio presets and frequencies in the mission itself, read the DCS "User Manual.pdf" for instructions. Regards, Ian.

Here is the correct version of logbook. I had to make some assumptions. Your DCS is installed in: DCS World 2 Openbeta (Not just DCS World) Your DCS saved games folder is DCS.Openbeta (Not just DCS). Corrected lines are marked in BOLD: A-10c Georgian Hammer campaign, needed "EN" folder removed from path. A-10c Georgian Hammer campaign fixed, needed .openbeta add to folder path. A-10c Enemy Within campaign, needed all mission filenames changed with the removal of "v1.5" as these files have changed since DCS 1.5. Su-25T Georgian Oil War campaign fixed, needed .openbeta add to folder path. All was backup original file before replacing, just in case something goes wrong. View of corrections and full file attached. logbook.zip

Not my area of expertise, but if you care to send me your logbook.lua via PM or on here, I could take a look. Some one else might be more helpful that has already done this type of fix for their own campaign progress. Cheers, Ian.

Some campaign path names have changed, and the log book now points to the wrong directories (This is why campaigns are inactive), you will have to edit the logbook.lua file with notepad ++ and correct them, there is a forum post on how to do it somewhere. https://forums.eagle.ru/showthread.php?t=201053&highlight=campaign+path Regards, Ian.

I think only you could answer that, I am sure the joystick will fly the Fa-18 (Not released yet) fine, having lack of buttons may hinder you with complex systems management though. Good news is that is the new Caucusas map that you get for free with DCS 2.5, now with millions of trees amongst other things.:thumbup: To see mission like that, you can create new mission with a start Date in the following months: Summer (Bright Sun) is in June with temp of 10c to 30c Autumn (Brown leaves) is in Sept Winter (Snow) is in Dec with temp of -15c to 0c. Regards, Ian.

Me being the cautious dude that I am, and for other reasons: I kept DCS 1.58 stable and disabled the autoupdater for that version, I updated my DCS 1.58 OB to DCS 2.5 OB and then deleted DCS 2.2. If your updating from DCS 1.58 OB to DCS 2.5 OB and have DCS 2.2 installed, leave all versions in place temporarily so install can copy stuff from other installs, saving on downloading nevada and normandy maps (total install would be about 107gb roughly), etc and then delete DCS 2.2 after. If your doing a fresh install of DCS 2.5 OB, do as you please, wipe the existing DCS 1.58 OB and DCS 2.2 versions before or after the install depending on if you want a total fresh download from servers or have some files copied from other versions saving on download size. Till missions get updated in Caucusas map on DCS 2.5 OB, you may have to play with trees set to 0 in settings, so that all ground targets are visable and not in trees. Regards, Ian.

It isn't all beers and skittles, DCS 2.5 has some issues, so I would recommend you hang onto DCS 1.58 also if you want to play old missions in caucasus map until 2.5 catches up and gets more stable. If your playing NTTR or Normandy missions I don't know why you haven't downloaded and installed 2.5 yet, fair enough if you don't like BETAs and the issues they can bring. In new caucasus map seems to runs better than 1.58 ever did, even on all high settings (YMMV). Regards, Ian.

I would try uninstalling that 390.xx nvidia driver (there have been several issues with it, including stuffing my own windows install by constant video driver crashes, your mileage may vary though - I suspect it is the ANSEL feature of the new driver, but just a hunch), try rolling back to 388.71 or there abouts if your game. How did you install DCS 2.5, Fresh or upgrade from 1.58 ??? If you did upgrade, did you delete your options.lua, Metashader and fxo directories as requested. Do you have tacview installed, log seems to suggest you might, but is not logging its presents as per usual. Regards, Ian.

Cheers mate, I must admit I can't stop drooling over the new effects and lighting now that the Su-25t campaign missions start in summer of 1990, then autumn and finally winter of 1990-1991. Getting some nice sunrises and sunsets that never seen before. Looking forward to getting these and other modules versions out in near future. Regards, Ian.

Firstly your welcome, regarding the agm65-H, I can never remember which versions do what, I would have been learning the A-10c at the time most likely. All of my fixed missions sets and campaigns are available on the ED site under user downloads: https://www.digitalcombatsimulator.com/en/files/?set_filter=Y&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=MadDog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter The missions are mostly going to suffer the forest issues if they involve CAS strikes, FARPS or ground units. I wish I could fix all missions instantly with a magic wand, but alas I am but one man and no magician or wizard. Those mission sets would have taken thousands of hours to correct, probably need half of that time again to make them usable for DCS 2.5. Myself, Eagle Dynamics and countless other people are busy doing what they can to get all types of missions and campaigns converted to a DCS 2.5 version. I am currently correcting the Su-25T Georgian Oil War campaign (100 missions) at a pace of 2 to 4 hours per mission, that gives you an idea of work involved. Regards, Ian.

I had issues with 390.xx driver, first attempt to install failed badly and was not operable on any level, in widows or for any gaming, this has not happened for years with previous driver updates. Thorough clean out of all Nvidia drivers and software and started again with install, this time it appeared to install correctly, but another issue surfaced after running my system and then putting it to sleep mode, when brought out of sleep mode the windows desktop had glitched graphics all over the place and running very slowly, very quickly the video driver actually stalled and failed, requiring a total reboot. So once again thorough clean out of all Nvidia driver and back to 388.71, all good again. Boy that was a waste of time, I will wait for a couple more driver versions before I try an upgrade again. Regards, Ian.

under the advanced waypoint commands, "Dispersal under fire" (300 seconds by default I think, you can disable it to 0, makes them do what you want. Regards, Ian.

Directory index of HDD may be corrupted due to the blue screen of death, as a minimum run scandisk on hard drive and have it check for errors. (Will take a while depending on size and speed of HDD) Don't run DCS again, if you had run the mission just before the crash, as you may be able to rescue the mission from the TEMP directory. Grab files from the default windows TEMP storage area: To open the temp folder, click Start or go to the Windows 8 Search charm, type %temp%, and select the folder that appears. ie: d:\[Temp Storage]\DCS.openbeta\LastMissionTrack.trk , rename to with .miz extension and copy to your missions directory. or d:\[Temp Storage]\DCS.openbeta\tempMission.miz, rename and copy to your missions directory. Regards, Ian.