MadDog-IC

The Attack map object command is not designed to be used for attacking objects that you can place on the map, it is for the buildings, etc that are a hardwired part of the map itself, so it is more of an attack this building at grid co-ordinate xxxxx. To have choppers attack moving vehicles, you would need a CAS role for the huey flight. You can then use advanced waypoint commands such as Search and engage, Search and engage in zone, etc. Regards, Ian.

Would help if you posted your mission so we could have a look at it as already asked, but it sounds like the mission briefing pictures have been corrrupted and need to be deleted an re-added to your mission, as this can cause the symptoms your describing, it is quite a rare bug now, but can still happen. Regards, Ian.

Very strange issue, can't see that being specific to any missions, and the following is only a general diag regime. Check calibration within windows still works fine with joystick. Check there is no conflict with two or more controllers assigned to the same axis (Joystick / Hotas, gamepad or steering Wheels) in the A-10c SIM controls sections. Have you added any other joystick, game pads, Xbox, steering wheels recently ??? Just having a force feedback device installed but not used in anyway within DCS has caused issues in the past, which caused the trim functions not to work in aircraft, but was resolved. In controls section for pitch, with pitch curve, pitch saturation set as default, does the joystick track the full motion in the test window when moving the joystick to its extremes ??? Use Cntl-Enter in game to bring up the joystick axis monitor and see if that is behaving as intended when flying. If the above seems ok, then I would be looking at this: What sort of frame rate do you have whilst flying, is it lagging badly ??? What are your air speeds when it's working fine and when it's not working fine, could you be in a stall, high angle of attack causing too low an air speed so the elevator can not correct, but can when plane pitches down and it gathers enough air speed. What payload does the A-10c have onboard and is it just too heavy for good flight dynamics. Read this also, might be related: https://forums.eagle.ru/showthread.php?p=2974059#post2974059 Regards, Ian.

I have tried bs1, has a bit of a resolution issue now, if I go to a resolution of 1920 x 1080 I can't see the buttons in the mission Editor, only the map so have to run in 1024x768, probably video card driver issue. Have done a quick apprasal of the mission in bs1 and in dcsw 1.55x and all looks fairly ok to me, but I am sure you know your mission better than me. All the units seem accounted for, same amount of Heli, planes, vehicles, ships and static objects. Triggers are harder to check, but I see no real issue as yet, only way to know is to fly mission and I am not a position to do that at the moment. Tested Single player version in dcsw v1.55x with AI doing the flying. Deleted some extranious and almost duplicate triggers causing mission to mis-fire. Replaced corrupt payloads on the bombers with a valid payload. Changed Players Ka-50 to CAS so I can use AI to test fly mission Gave Players Ka-50, attack orders to engage SAM (So AI can fly it). Checked triggering of certain critical events, some issues, but I think they are programming mistakes (please don't this personally). Bombers hit their targets hard after SAMs down. Changed scoring for single player scoring Mission completed successfully. With knowing much about how the mission is supposed to be, it is playing quite well, except for some strange triggering of kill the sams because dam convoy is getting artilleried, the sams are dead and the bombers have dropped their payloads and have mission success, so I am guessing the bombers are suppost to take out the arty units also, but didn't. I think the mission is good shape, but has a few minor issues that are easily fixed, I would say don't be put off by what has been said by some, not all missions get broken by each patch and is more that the game engine is faulty and ED need to fix their stuff and not the mission file itself, not unless the Mission Editor corrupts or deletes part of the mission file which is very rare, but it has and does happen. The mission looks exactly the same in BS1 and DCSW BS2 editors by the way, so nothing has been removed from the original. My test version is attached with Ka-50 AI flying the mission. Cheers, Ian. eV1Te - Behind Enemy Lines SP_DCSW BS2_fixed.miz

Very sad to hear that you have been put off by our comments, but it is totally understandable, there have been a many good mission designers come and go in the ED forums for the very same reasons. I for one have large respect for these people for their time, passion and commitment they give to the hobby of ours. Unfortunately this is the price we pay for having new features added constantly to the flight sims, with progress comes deletion of backwards compatibility and new ways of doing things, especially when the programs version in question are almost entirely different programs in their own right, but just happen to have the same aircraft in them. I love to play those old mission from long ago also, that is what got me into the mission editor in the first place, I was reasonably successful in getting most of my old downloaded bs1 missions working in BS2 and then DCS World. The biggest issues faced with the old BS1-BS2 conversions: Some static objects were removed or renamed in the assets register for placement on the map. Don't recall it actually ever deleting aircraft flights on conversion, but most definitely did some static objects due the above reason. Mission Editor roles were changed for some aircraft types which caused advanced commands such as bombing and ground attack to be invalid commands for said aircraft, requiring changes to the role to the new appropriate one, and or to changing the bombing commands to something else. Biggest problem faced was triggers being deleted due the units they were associated with no long existing in the converted mission. Probably other issues I can't remember with referring to my notes. With all this in mind, there is a big difference in trying to get a: BS1 mission working in the latest DCS World BS2 module - Might need several hours, days or months of work to getting it going successfully (Depends on complexity). BS2 or newer compatible mission working in the latest DCS World BS2 module - Might only need a few minutes or a few hours of work to getting it going or you may have to wait until the bug that is stopping it from working is fixed by ED, or it may just work perfectly the same (ok). I would be happy to have a quick look at some of your missions for conversion it you want to PM me and arrange a way for me to download them. Regards, Ian.

I have done conversions before, and it is not impossible, but can be a lot of work, not for the faint hearted ;-). if you are talking blackshark 1 missions, I would convert them to blackshark 2 format using the stand alone version 1.1.1.1 first, checking for problems such as aircraft roles, etc as there was a lot that had changed between those versions (When you try to resave missions you usually get several error message and have to address them before it will even resave), and then maybe load and resave using the newer DCS world versions v1.216 and / or v1.55. Sticking with v1.216 keeps the same mission file format, with v1.5x they changed the mission file layout so isn't backwards compatible anymore with previous versions. Cheers, Ian.

When you upgraded to windows 10, did you just go over the top of your windows 8.1 install with the original firewall and antivirus already installed ???? In the past, any new operating system would need an upgrade of any third party antivirus and / or firewall software, so if they were already installed when you upgraded win8.1, I would uninstall both the antivirus and firewall software and reload it, and make sure they are windows 10 compatible. Third party firewalls are notorious for disabling all ports if turned off, so I would still uninstall webroot fw, test DCS without the firewall and then reload the firewall and re test DCS again to see if it works in either configurations. Also check that the forward port in the router is still pointing to the same IP address as before, and that the IP address of your computer hasn't changed. Regards,Ian.

Your welcome, good to see you have it working again, and it is a shame I don't know why it only happens to a few people, it has only happened once to me, all other update patches have been fine, but I do keep a backup of all DCS installs just in case something catastrophic happens. Regards, Ian.

Sounds to me like your modules have been deactivated, check in module manager that they are in fact installed and activated correctly, even try deactivating one module and removing it, and then reload it and reactivate to see if it fixes anything. This happened to me recently with a patch, it had deactivated and uninstalled all of my modules, reading your logs this looks like it is your issue, all modules may have been uninstalled, so definitely check in module manager and do a reload. Did you have any MODS installed during the update ???? Do you run bit defender for an anti-virus ???? If running any antivirus it pays to: Put the DCS world game directory path in the exclusion section to not monitor / scan game files as the antivirus may block or even delete critical game files. Apparently bit defender is a bad culprit. Run the dcs repair function to re download missing or corrupt files. Regards, Ian.

The Georgian Hammer CA campaign missions are essentually the same missions (but have never been upgraded by me), but have no radio commands at all for controlling the ground platoons as you have to control them manually using the extra DCS module (Combined Arms). Voicing for the pushx-x missions wasn't completed so I think it is only available in the first couple of missions. Glad it going for you now, just keep an eye out for the text prompts from your other units as voicing isn't on 99% of the missions (Yet). As I said before I have recently done some voices for all of the GH campaign but there needs to be a lot of changes to the trigger systems for them to be output correctly. I am just using the windows 8.1 voices for my voice overs as it takes to much work otherwise, and when you are doing 100's of missions it takes months. Regards, Ian.

Feel your pain, I've only recently moved to a 100mb fiber system, and on first signup a few months ago you only get 30gb / month, luckily it then went to 50gb and only just now to 100gb (And all data is counted for both upload and downloads). For this I pay $75 a month. So we are not all so lucky to have unlimited data usage are we. Regards, Ian.

Sounds like they are the updated ones, so still not sure why you have no feedback when playing the missions. Campaign system wouldn't have a fly again option as the result you get in the mission determines weather you advance to the next stage (51-100%), stay on the same one (50%) or actually go back one (49% or less). Their is also a randomization system within the A-10c Georgian Hammer Stages and missions so it is possible that if you just quit out or fail a mission with a result of 50% you may still get quite a different mission to replay instead of the one you just failed even thought you are at the same stage (this confuses new comers a lot, as there is only 14 stages but 32 missions, if you always get a result of 51% - 100% in each stage, you will only ever fly 14 mission in total). The only way to fly a specific campaign mission (To test or refly) is: DCS Main Menu -> Mission -> A-10c Select .. on the missions menu files directory to right to go back a directory. Select Campaigns directory and then the mission you want to play (Push*.miz). This will give you the mission planner and START button Press START button and try mission. When mission is complete the Fly again button should be available. Regards, Ian.

Re: steam, yes in a perfect world it should be current and updated, but I have had numerous other steam games stop working in the past and when you use the cache validator function to check for corrupt files, it has found some faulty ones and re-downloaded them, and then the games functioned correctly. The auto update can also be disabled by a user, so pays to check that auto updates is still on. To check: Find DCS World in the list of steam games and right mouse click on the menu entry and then choose "Properties" from the menu presented. To check the Auto update is on, choose "Updates" tab, and the first entry at top should read "Always keep up to date automatically" To check all DCS files for corruption choose the "Local files" tab and finally the "Validate integrity of game cache" button. It will take a while to process, so just let it go thought the motions, if it finds and issue it will tell you that it is re-downloading the offending files, but you have to be watching for that, as it doesn't give any indicators at the end of the process on how many files had to be replaced, it just tells you it has checked all the files. Check files in the Steam Files cache (..\Steam\steamapps\common\DCSworld\Mods\aircraft\A-10C\Missions\EN\Campaigns\PUSH*.miz are dated in 2016) Finally re-run DCS world and see if there is any change in the missions. Regards, Ian.

I flew push 4-1 as a test. Take off and follow all way points, when between Fence In and IP waypoints you are contacted automatically with a group of messages on screen for allied AI flights and the platoons that are ready to advance (there are no sounds or voices, so keep and eye out for them, if you don't get them by the time you are in the IP waypoint I don't know what you are doing wrong, and mission will not be able to be completed). You can now use the radio to send the SEAD, CAS flights into the fight You can now use the radio to send the two armoured platoons to their objectives. The fight is now on, and you can start to kill stuff. Killing enemies will do you know good if you haven't recieved the radio calls to advance the armoured platoons by the time you have entered the area of operations (ie the IP waypoint) I tried all radio comms with both easy communications and realistic communications settings: I called JTAC and he did take a long time (a minute or two) to respond on the initial time on station stuff, but he did respond. (Push to talk key: Shift+Num-) I called the tanker and he responded fine. (Push to talk key: Alt+Num+) I called the AWACS for bullseye and he responded fine. (Push to talk key: Alt+Num+) I called my wingman to engage and he responded fine. (Push to talk key: Alt+Num-) I called both armoured platoons and sent them on their way, both responded fine. (my version has a slight bug fix for one platoon stopping half way for no reason) I understand all of your frustrations, I had the same feeling with DCS, but have come to learn things will get broken when adding new features. The original A-10c Georgian Hammer campaign mission had no feedback what so ever, I have added messaging and intended to do voice overs but hadn't had the time to do it, in my current version the voice overs are done, but it requires a total rewrite of the trigger zones and triggers to have them work properly. If you are not getting the messages when you hit the IP waypoint, you must have a faulty install of some sort and I suggest you either do a repair or at least check the individual files in ..\DCS World\Mods\aircraft\A-10C\Missions\EN\Campaigns\Push*.* are all dated in 25/05/2016. Saving a track file and uploading might help me understand what you are doing differently. Regards, Ian.

Firstly, this is a general summary. Don't use Easy Comms, known to be buggy and unreliable in the past. Do use realistic comms and tune the different radios to the correct frequencies for each unit you want to call, transmit using the correct radio and push to talk buttons. Radio menus have been borked in recent update patches, but quite random in nature. Have the same issue after finishing missions and it locking up, been doing this for ages. Others have been playing this campaign under v1.52,v1.54 quite recently with only a couple of issue in the movement of some tanks pathing in push 4-1, I suspect v1.55 has broken more things. Results will only advance on doing the objective, ie getting the platoons to the objective areas. Regards, Ian.

I take it you are talking about the Su-33 Heavy sky campaign Mission 3 - First Battle. If so this question should be in a new thread. This particular campaign and the Su-25 Cold war Warrior have not been upgraded in any of the release versions of DCS 1.5x. Yes that is a bug, It happens with the russian ai planes on the Kuznetzov carrier also, don't know the cause but probably due to what angle or direction the boat is heading in when the plane lands on it, it will sometimes cause the boat to continue moving as it should but the plane itself stays in the same time space grid position it first landed at on the carrier. I have done the first 10 missions approx in the Su-33 Heavy Sky campaign, but have had writers block on how best to change the missions, combined with some ill health on my part and the state of dcs 1.5x when it comes to running a mission more than twice in a row, it always stops responding and has to be forcibly shut down and restarted all the time. This is such a problem I actually re-edit with the older more stable dcs v1.216 until it works and then convert onto dcs v1.54 and retest for new introduced bugs there. This is one big campaign and is relatively poorly written (IMHO) and the briefings misleading, something I am trying to improve, but have lost my way a bit. But regarding mission 3: Can't remember if the original mission was able to be completed successfully (I think it was ok). The whole mission is about you killing all the F-14s and successfully landing back at base for a mission completed 100%. You will get 50% for starting mission, 30% for killing the F-14 fighter group and 100% when you land at your airbase. All the missions in that whole campaign require you to land back at base to be fully successful. Find attached the first fixed 6 missions: Regards, Ian.

Most people are running on 1.54 now, and I assume you would be also if you have kept up with all the updates (check version in bottom right corner on main page of DCS), as it is the latest stable release, 1.55 is in Open beta at the moment and may be released soon. Forget Frosties version, they have no bearing on things any more, my updates were done under DCS v1.52xx and all mission were tested to complete successfully in that version, the missions were then submitted to ED for updating in the official dcs release and were finally incorporated in the first version of v1.54xx several months ago. There may be new introduced issues with some missions re post patches from v1.52xx - v1.54xx, but when I see a post like yours I run my built in test function and let the AI play as the player and monitor the mission as Battle commander with Combine arms and am able use the radio to trigger AI such as the Su-25 bombers. The mission itself works perfectly fine as it is here, played as a single mission out of the campaign environment. You can monitor your result with the ' key which is left of the Enter Key in the mission, you get 50% for starting the mission, 80% if you kill all the F-16's and 100% if you kill the F-16's and the Su-25's destroy all the arty. So long story short is that when you do the mission, take out the F-16s before they get anywhere near the Su-25 bombers, once you have air superiority, call in the Su-25 bombers with the radio call for CAS-1 and CAS-2 and let them take out the arty as per the mission brief, all 4xsu-25 must survive or they will not be able to complete kill the arty other wise. The Su-25s will not jettison their payloads even if they are attacked, they will try to evade fire but will usually die because they can not out maneuver due the excessive weight. They may disengage and RTB though if damaged enough, this is why you are their to protect them, if they can't complete their mission you don't get the mission complete at 100%. So long as your Result is over 51% on the mission scoring system the campaign system should move you onto the next mission, if it is not doing that then you should report it as an issue to ED. Regards, Ian.

Su-27 - Fortress Mozdok campaign was rewritten and fixed and fully tested at the beginning of the DCS world v1.54 cycle. It will not necessarily play the same as it use to and may indeed have new issues due to the later patches to 1.54xxx and above. The bug fixed were never announced in the official changelogs.

This is actually Su-27 Fortress Mozdok - mission 2.5, and you seem to be doing it correctly, in the spoiler I explain. Regards, Ian.

I highly sympathize with your dilemma, I have had a some curly issues in my IT work also. After looking at all the others solutions, it is hard to come up with something meaningful. But I would try, so don't shoot the messenger if you have tried this: Fresh load of win 7 or a 10 non anniversary version with minimal driver upgrades. Stick to single screen and resolution of 1920x1080 and Non-VR. No USB controller peripherals plugged in at all, including your Warthog stick, (keyboard and mouse are acceptable) Just fly with the keyboard and mouse and monitor with GPU-Z and or MSI afterburner to see what is happening with speeds, voltages, etc and if the stutter issue persists. If stutter persists in above config: Then it can't be the USB port causing the issue with the controllers. Bu also try turning the "Power off" components on the USB hubs or port in the device driver sections of Windows so it doesn't try to power down the USB ports to save power, this caused me some grief with my X52pro joystick and other USB devices. So if no abnormal readings from GPU-z, such as GPU not hitting its recommend non throttled speeds, power settings, etc, and pci-x bus is running at PCI-x v3.0. (pictures of my system running the instant action mission east georga showing benchmarks with afterburner and GPU-Z) then it would be unlikely to be a graphics card issue. Also doubt any issue with HDD of any sort: But check they are running on the fastest sata ports that support 6gb or faster speeds and not 3gb as my M/b has mixture of these. I have run DCS 1.5x on standard 7200rpm drives and now a hybrid hdd/ssd all in one and have never had the stutters. As you mentioned you used a ram drive at one stage, pretty much negates any hdd issue. Finally: If all the benchmarks of the graphics system are looking correct with dcs when monitored by GPU-z and it is still stuttering, then it may be settings on the motherboard Bios or the bios version itself that has issues with your brand of graphics card or it may even be the bios on the graphics card, but as you stated you have had two diff cards with same result, so I would suspect M/B, ram or cpu maybe. My GPU GTX-780 wouldn't even run with DCS 1.216 when I first got it till I reflashed the bios with modified voltages for each stage of throttling, earlier dcs didn't even get it loaded enough to get above its base voltage of 0.880 and the gpu chip kept stalling and crashing the driver, i reflashed them with a min of 1.13 and fixed the issue. Either way I hope it can be of some help to you, and that you can get it resolved. Video of my flying test for stutter, no problems. https://www.dropbox.com/s/2l4mdt6njg34kwx/DCS_2016_11_09_21_00_32_031.avi?dl=0http:// Regards, Ian.

I have been working on Operation Medvedev in the past and there are definitely issues with it. Mainly farps not having proper support units for atc and lighting and correct working frequencies. Artillery pieces not firing at targets. Illumination flares not showing light for the mission. Mission time of day out by an hour or two, causing what was a day mission to be a night mission. Occational scoring and trigger issues. Georgian Oil War Totally unknown state, but I would suspect many issues.

Don't have the X-55 so don't know if it has the same cable linking both components, but with my X-52pro, this problem was being caused by a loose connection from cable linking the joystick to the throttle body, specifically where the cable plugs into the back of the throttle body itself, if not absolutely firmly pushed in it would cause your issue, it you wiggled the cable a bit (it will jump into another mode say from mode 1 to 3). Regards, Ian.

It may sound bazar, but I thought about doing it that way last night whilst I couldn't go to sleep, using one of the directories that the prepare mission option creates, such as scripts, etc. I guess great minds think alike, all the best for getting it sorted.:detective: Regards, Ian.

I don't fully understand what you are getting at or trying to do. I was talking about just making a trigger within the mission editor that never activates anything in the mission but references the DAWS file as a .lua and acts as a placeholder for the file. This way the ME sanitizer will not delete the DAWS file from the .miz file. Sample .miz file of my idea supplied. Question about that DAWS file, do you: Somehow inject that file into the .miz file with an external source on each play of the mission in a server ???? Does in only have to be included with the original mission file and never changes ??? What does the table do, and what references its contents ??? Regards, Ian DAWS-SavedMission_1 with table.miz

Only way I could see of doing it, is similar to putting a place holder in the trigger system for sound files that are used in custom .lua scripts so they aren't discarded on mission editing. This may work if you can have your table with a .lua extension, not sure how you or why you are using a table ??? Trigger -> Condition -> Action ======================= Table ---> Random (0) -> Do Script file (DAWS_mountedInfantryTable_SM.lua) Regards, Ian