MadDog-IC

Nice of you to notice, many man hours invested in mission editing an testing as you would know. Felt some one had to do it to bring the core game play back for the aging Su-25T, A-10c, Ka-50 modules in particular. This work is slowly filtering into the game itself, but I posted them on the User files sight for those that want them early or don't have the English version of DCSW (as has been requested by forum users with russian and other versions). Cheers, Ian.

Had same issue with my setup, installed tacview 1.53 and all seemed to go ok, but it only installed correctly on DCSW v1.55 OB and 2.04 Openalpha and the v1.55 stable version was left out in the cold with it making empty ACMI files. Long story short, Go to tacviews website and read on how to set it up manually in the FAQ/ Troubleshooting, and double check that the files are in the right places, etc. http://www.tacview.net/documentation/dcs/en/ Most importantly, make sure that DCSW Export.lua file has the correct line in it to run the tacview exporter, with my dcsw stable version, it hadn't replaced the old tacview 1.28 script entry with the newer one for tacview 1.53 (runs different named lua file now). I also removed all traces of tacview v1.28-1.41 scripts from all of my dcsw scripts folder to be sure. Tacview works a treat now. Regards, Ian.

Far as I know the feature is only available on some aircraft, A-10c, Ka-50, Huey. Their may be others I am not sure. To use: Load mission in ME, choose the prepare mission option from the top menu system. Fly mission and setup your radio frequencies and presets, and other things that the aircraft module supports. Once you have it set the way you want it, quit the flight back to ME and click save once again. To check if the mission has any presets saved to it, open the *.miz file with a zip viewer program and it should have a few extra folders inside for radio data, etc. (Try it with the A-10c for example to see what it makes). Even in the A-10c it creates issues with radio and weapons use, because of bugs and just the way it works. Regards, Ian.

Ruling out "Dispersion under fire" settings, the DCSW engine is faulty, same thing happens with most ground vehicles and troops, they just get tired and can't go on. Been seeing this in my mission testing lately, missions run in old DCSW v1.216 have no problem getting to their waypoints, copy the same mission into DCSW v1.55x and mission stops working because guys can't walk all the way to a trigger zone, or cars following waypoints on road, swerve off road and stop in the bush and stay there permantely, haven't done boats for a while, but I suspect it is the same. Needs to be formally reported. Regards, Ian.

I wouldn't recommend a roll back myself: For the most part newer versions offer much more positives in general than the draw backs. There is also the possibility of other issues with config files if there was a major change in the format between the different versions when you go backwards. Couple of ways of changing versions: Use the autoupdater with command line instructions to load a certain version: https://forums.eagle.ru/showthread.php?t=114030http:// Probably easier to use this program: https://forums.eagle.ru/showthread.php?t=160053&highlight=rolling+back+dcs Regards, Ian.

some nice steady flying there, thanks for sharing.

No problems, I appreciate the time and head banging it takes to develop software, especially when the goal keeps changing. Kind of like trying to keep DCS itself running well enough to play a game, let alone the the state of the multitude of missions themselves that have issues. Wish you all the best with it. Regards, Ian.

Not sure what I am missing here, I have watched the progress of this program thinking that it sounds fantastic, but didn't really need its features until now. I think it would be very useful to help me setup some Helios profiles, where I have to change the whole layouts for 1920x1080 screen to 1280x1024 screen and re-position all the exported data windows. So I downloaded UltraMFCD v2.55 and even v2.58 beta, but both programs instantly stop responding on trying to running them. Running standalone DCSW v1.55x stable, 1.56x Openbeta, 2.04 Openalpha with tacview v1.54 and no other MODS. Any clues as why that would be happening, as no one else seems to be mentioning that it stops responding on running it. Regards, Ian.

Nope, the two issues you have with Prepare mission, I can remember and are still there. Mentioned in manual, with the A-10c particularly is if you change the weapons loadout in mission you have issues with DSMS and inventory being out of wack. If you assign a default and predetermined radio frequencies to UHF, VHF, FM radios the VHF radio doesn't work, even though it is on the correct frequency, unless you cycle off the frequency you need and back to it, then it works, I think it works fine with the preselected dial fine though. Might be other issues I am not aware off, as I haven't used it much. Regards, Ian.

Good call, I had this problem also. To be more precise, Just delete any keyboard.diff.lua files, If you have old ones left over in each aircraft folder under the, ie "c:\Users\yourusername\Saved Games\Dcs\Config\Input" directories for adding or removing keys from the defaults, those keys will not work. This would save you from wiping out all your controller setups in the process. Regards, Ian.

DOA wouldn't be a good anachronism, not sure about AAA either. :megalol:

Just remember your mission, SEAD is nearly always sent in first to cripple their defenses, then followed by CAP (Which is you to get air superiority over the battle area, then CAS, etc for final assault. However in this mission, your job is: That is kind of the idea of SEAD, except the get shot down part, but that is a symptom of a bug when missiles don't hit their target, they only have 8 and with less than a 50/50 chance of hitting at the moment (There are about 8 SAM Systems), also the F-16 will also have to do gun run on the final EWR installation as it will not have any missiles left to take it out at range, this is most likely when it will get killed. Will play the exact same either way, Su-27's at back are for their base defense, will only engage if you threaten it by getting to close, fly over there and see what happens. Good Luck, and timing is everything Regards, Ian.

Your most probably not doing anything wrong persay, as a current bug in the DCS engine is affecting all SEAD missiles and causing them to miss more often than should be the case, the ARM-88 is most affected in this mission, where as the aim-154c seems ok (but is a lot slower to get to target). The net result of this BUG is: When SEAD / DEAD flight engage with the AGM-88 they will nearly always miss, leaving the SAM active, they will either try to re shoot it with the AGM-154c or may have targeted another SAM and launched the AGM-154c at that, this missile will hit and kill what ever Sam it is aimed at, but it takes an aweful long time to get to target, in the mean time after launch, the SEAD aircraft now having off loaded all their missiles, still detect active SAMS and go in for the gun run (Suicidal kamikaze runs) as this is all that have left to fight with. Watch your track file for the SEAD flights AGM-88 missiles and you will see they hit the SA-13, but don't kill them, that is because it falls just short, goes wide or to long and only does splash damage, however the AGM-154c hits and kills. SEAD bug is being worked on and corrected in dcs v1.56 Openbeta due for release shortly, so not much you or anyone else can do until then. Regards, Ian.

Would be multiple setting in the Motherboards BIOS to fix that (have to be computer savy to do this), something along the lines of: To get to BIOS on most M/B by pressing DELete key (F2 for other brand names) whilst post screen showing and before booting main operating system. Full initializing the USB port for legacy DOS, EHCI on bootup, etc. Type and brand of USB port chipsets can make a huge difference, INTEL chipsets driven USB ports have best compatiblity, Asmedia ones have issues, USB 2.0 better than USB 3.0 for older devices, so if it isn't working fine on one port try another. I have had certain external USB hdd not detect on my system until I played around with the different settings, particulary enabling the XHCI stuff. Anyway below is a link to forum on issue, that may help you. http://www.overclock.net/t/1477283/asus-bios-no-usb-during-boot Have same problem, no resistance or feed back from toe brake pedals is the main problem, they just require so little pressure and have so little travel, best to change the curves so that they apply very slowly first up and increase in pressure the more you approach max application (Curves=20 -> 30 for example). Regards, Ian.

Yes it helps, games are complex things these days. Seems to be a few issues, that BIGNEWY might be able to explain better than me. But I would check: Anti-virus your using, disable it whilst installing DCSW or add the DCSW games directory to the list of excluded directories not to scan for, as it may be stopping some components from installing properly. If re-installing DCSW from scratch, make sure you always right click on install program and choose "run as administrator:, as you should for any program install under windows 7,8,10. Delete your ..\DCS World\MissionEditor\ folder as it seems to be a source of problem. If your using any old plane config files, make a backup of them and delete the c:\Users\Borje\Saved Games\Dcs\Config\ folder. Looks like the TF-51 module might be missing or corrupt also. Make sure you also have Microsofts VC runtimes installed Run a DCSW repair to check and fix any all missing files or corruptions. Run DCS and try login again. 00004.525 INFO TERRAIN: lSystem::lSystem 00004.592 INFO EDCORE: (dDispatcher)enterToState_:1 00004.735 ERROR VFS: add_location {"My Missions", "C:\Users\borje\Saved Games\DCS\Missions\"}: path already added as "My Missions" [b]00005.868 ALERT Dispatcher: Error starting Mission editor: [string "./MissionEditor/MissionEditor.lua"]:946: ERROR not type in plugin:TF-51D Mustang by Eagle Dynamics 00005.958 INFO EDCORE: (dDispatcher)enterToState_:2 00006.032 INFO EDCORE: (dDispatcher)enterToState_:3 00006.435 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_waitDsbweb.lua"]:76: attempt to index global 'sImage' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_waitDsbweb.lua"]:76: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>[/b] 00006.453 INFO NET: Login success. 00106.897 WARNING LOG: 17 duplicate message(s) skipped. [b]00106.897 ERROR NET: Login failed with code 403. 00123.548 WARNING LOG: 12 duplicate message(s) skipped. 00123.548 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_modulesmanager.lua"]:603: attempt to index global 'window' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_modulesmanager.lua"]:603: in function 'show' [string "./MissionEditor/modules/MainMenu.lua"]:148: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:318: in function <[string "./dxgui/bind/Widget.lua"]:313>[/b]

Sounds like you haven't put in your username and password to login to the master server may haps, (Login button at top right black bar, at end of that in mid screen is login icon, is your ED Usename showing next to it ???), hard to tell from your description. Also check that firewall isn't blocking it. Regards, Ian

I was modifying wavehoppers first few excellent missions he was doing for his (Huey Medivac Campaign) so that in MP, two of us could actually pickup multiple soldiers and get them back to base. Unfortunately due so some of his choices in the way he did things, It makes a lot of work for me to change them all around to get what works for me, (Not saying anything bad about the missions, they are highly regards and I myself didn't mind them), but I really only like to fly single or MP with one wingman and use AI programmed to simulate me flying whole mission to have a check and easy way of check mission works fine, given all the issues that happen over time with bugs in the DCSW engine. Check his finished campaign here, obviously only for single player though. https://www.digitalcombatsimulator.com/en/files/2316694/ "Op Erase and Replace" is very good for MP with huey, uses CTLD script, this the only way to get your fix of troop transport at the moment, as all builtin MP troop transport mechanisms in DCSW are broken and have been for some time. The huey's default Elbrus rescue and Stray Eagle single missions from memory are easy to convert for MP. Regards, Ian.

With any single player or campaign missions I edit these days to support easy conversion to multiplayer as I usually play CoOP with one human wing-man in MP. Make a copy of the Mission and change these for MP: Change all triggers that look for the "Players Plane or Pilot" to be in a zone of some sort, such as "UNIT IN ZONE=Player Pilot" and add an "OR" and "PART OF GROUP IN ZONE=Players Group". Change the "Players Flight Group" to have a 1-3 more "Player Aircraft" and set all aircraft to "Skill=Client". Problem with chopper missions also, is that they check for landing parameters (Forward Speed, Vertical Speed and Vertical Height) to see if chopper has landed, and that only can be done on a per unit basis, not a whole group, so with multiple choppers the trigger updates needed can be daunting. Another issue with most single player chopper mission, is the wing-man more than likely has nothing programmed to do, such as pick up passengers and drop off, etc. Regards, Ian.

Yes this use to be the case in versions 1.2.16 and earlier so I always programmed the AI SEAD and AI STRIKE aircraft to do: SET IP Waypoint at max range to target for the SEAD weapon so they would fire at max range and not over fly the SAM. Reaction to Threat = PASSIVE DEFENCE (They will get the job done with all missiles away, but die quite quickly after that, was only way to get around the dump and run short coming) But since DCSW v1.5x and later there is a new option to stop these behaviours, it just has to be added to the missions flights. SET IP Waypoint at max range to target for the SEAD weapon so they would fire at max range and not over fly the SAM. Reaction to Threat = EVADE FIRE (Can now try to evade all incoming fire) Restrict Jettison=ON (They will get the job done with all missiles away, They will never dump their missiles even when engaged in a dogfight or trying to evade a locked on incoming missile. - DCS v1.5x compatibility settings I use now in all mission repairs. (SEAD) Flights - Reaction to Threat = Evade Fire, Restrict Jettison = ON (STRIKE) Flights - Reaction to Threat = Evade Fire, Restrict Jettison = ON (CAP) Flights - Reaction to Threat = Extreme Vertical Manueuvers, Restrict Jettison = OFF (Can't dump Fuel tanks otherwise) (CAS) Flights - Reaction to Threat = Evade Fire, Restrict Jettison = ON

Bugs do pop up in the game engine itself which make things change drastically, SEAD weapons are a repeat offenders (50% hit rate with missiles not locking on properly or losing signal and missile drops short or goes to long doing no damage. It is happening at the very moment in DCSW v1.55x Stable, v1.56 Openbeta is addressing these I believe. SAMS get upgraded some times (Might have had incorrect electronic and missile data before and now have more real life simulation), The tunguska never use to shoot down missiles, but does now, etc. Overall the AI seems to me to be getting worse in general, but sometimes it is just many variables of game and real flight dynamics that cause an issue in missions. Fixing quite a few missions over the years, my observations are: I see that a lot of missions with AI planes waypoints speed set to low, so that the plane is near stalling all the time (With DCSW v1.2.16 it didn't seem to be a problem, but when same mission are run on DCSW 1.5x, AI flying low or NOE in valleys would crash into mountains all the time. AI Sead flights are usually setup with waypoints that has the plane fly directly on top of their target before firing, or so close then can't lock and fire and have to go around before getting their first shot off (No need for that when the missiles have a 25km, 50km or even 100km range, stay at range of your missiles and hopefully our of the enemies. All AI flights, need about a minimum range of 15km run in from Ingress Point to spot target, lock and fire. Default programming in mission editor for aircraft roles, is to just seek out enemy no matter how far away it is, ignoring all waypoints when it detects that enemy. (CAS -a, SEAD -a, etc) and once all detect enemy are destroyed, fly back to its very first waypoint and then proceeds to follow them in order. Bomb ballistics and hardened Bunkers, etc are another issue that comes around quite often, Bunkers that become impossible to destroy with bombs that are quite capable of doing so. (Cause could be the damage amount of bomb is modeled incorrectly, the Bunkers armor might be modeled stronger that it should be or it could be just that the bombs aren't flying properly and not hitting the target. (Having this issue right now in A-10c single mission (Serpents Head, 4 x GBU-10 bunker busting bombs were more than capable of destroying it before, but not even 10 will, the accuracy seems to be off as bombs keep hitting beside the bunker instead of directly on top of it). Plenty of others I just can't think of now. Regards, Ian.

I am sure you already know this, but I would just like state this for the benefit of others. Yes this use to be the case in versions 1.2.16 and earlier so I always programmed the AI SEAD and AI STRIKE aircraft to do: SET IP Waypoint at max range to target for the SEAD weapon so they would fire at max range and not over fly the SAM. Reaction to Threat = PASSIVE DEFENCE (They will get the job done with all missiles away, but die quite quickly after that, was only way to get around the dump and run short coming) But since DCSW v1.5x and later there is a new option to stop these behaviours, it just has to be added to the missions flights. SET IP Waypoint at max range to target for the SEAD weapon so they would fire at max range and not over fly the SAM. Reaction to Threat = EVADE FIRE (Can now try to evade all incoming fire) Restrict Jettison=ON (They will get the job done with all missiles away, They will never dump their missiles even when engaged in a dogfight or trying to evade a locked on incoming missile. - DCS v1.5x compatibility settings I use now in all mission repairs. (SEAD) Flights - Reaction to Threat = Evade Fire, Restrict Jettison = ON (STRIKE) Flights - Reaction to Threat = Evade Fire, Restrict Jettison = ON (CAP) Flights - Reaction to Threat = Extreme Vertical Manueuvers, Restrict Jettison = OFF (Can't dump Fuel tanks otherwise) (CAS) Flights - Reaction to Threat = Evade Fire, Restrict Jettison = ON DCSW Flaming Cliffs 3 Campaigns (English version of DCSW v1.54x and higher where totally reworked, corrected and now use those settings and verified that missions work faultlessly as of mid 2016) A-10a The Valley Campaign v1.5x (100% Completed) F-15c Bear Trap Campaign v1.5x (100% Completed) Mig-29s Over the Hump Campaign v1.5x (100% Completed) Su-27 Fortress Mozdok Campaign v1.5x (100% Completed) Su-33 Sea Dragon Campaign v1.5x (100% Completed) Regards, Ian.

Can understand your frustration.:mad: Just to be double checking your playing the exact same mission versions as me (Certainly doesn't sound like it). All "Su-27 Camp*.*" missions in "....\DCS World\Mods\aircraft\Flaming Cliffs\Missions\EN\Campaigns" should all be dated: 25-06-2016 (DD-MM-YYYY format) or later and time stamped 07:44a. If dates are earlier than that, your running a version of DCSW that isn't for the english market and all the missions are still the original older ones with all the original issues. Regards, Ian.

You only have to land on the FARP or within 100m radius of it to off load the troups and refuel. To refuel: Be on the FARP Shutdown engine and wait till blades stop (This is a new requirement) Have correct radio tuned to AM 116.0mzh for SKALA Use Radio (Ralt + \) request for refuel by using proper radio selector (R-Cntrl + R-Shift + Y) or (R-Cntrl + R-Shift + Y) can't remember which one. IF radio request doesn't work anymore use (L-Shift + ') for the new Refueling and Rearming window. Once topped up, get the engine and blades going again and off you go. Regards, Ian.

Just for fun and giggles, I re-ran the test yesterday, I watched on the F-10 map and when the the AI Su-27 flying as me was over the mountain range and level with all the other holding flights, I radioed them to let ever flight go almost simultaniously, I think the bombers got fired upon and it was massive furball for all, but every one still got their jobs done and mission completed successfully. I was trying to tacview it, but I had upgraded to the new 1.5.3 and it wasn't working, for some reason when it installed it installed fine on the dcs openbeta and openalpha versions but not the release version. Got tacview working today, by copying over some folders from the openbeta install, but haven't had time to try the mission again. I am busy finishing repairs for all of the A-10c Single player missions that come default with the A-10c module. You would be an expert at shooting down planes with that Su-27 by now ;-) All the best, Ian.

Storage locations of downloaded missions, should go here by default: ie: DCSW v1.55x: c:\Users\YourName\Saved Games\Dcs\Missions\ DCSW v1.55x Open Beta: c:\Users\YourName\Saved Games\DCS.openbeta\Missions\ DCSW v2.04x Open Alpha: c:\Users\YourName\Saved Games\DCS.openalpha\Missions\ Also when you have downloaded your mission file. Check the filename ends in .miz, if it does, just move into one of the above folders for your version of dcsw. If the filename ends in .zip .rar .zzip or something else, then the mission file is most likely in a compression file, so you will have to decompress them to get the *.miz file inside extracted. You can do .zip with the window 7,8 and 10 default unpacker or us third party software such as ZZIP. Once the .miz file is unpacked just move into one of the above folders for your version of dcsw. Lastly, to load up mission within DCSW, run MISSION or MISSION EDITOR from the main menu, click the top right MY MISSIONS button, find mission you want to run and click it. If non of this helps, you could have some sort of corruption with DCSW itself, try a repair or post your dcs.log files so others can help. Regards, Ian.