MadDog-IC

Known bug, has been reported. need to adjust by advancing time by 30-90 min approx for v1.5x to get same lighting conditions as v1.216. Cheers, Ian.

Had the same issue whilst playing with a buddy in the modified version so two of us could do that mission together, Both of us were able to do mission with out issue, well except for me having the same blind landing as described above ;-)(, I lost all visibility and paniced by the time I calmed down and went into Instrument flight rules and checked my artifiscal horizon, I was in a 45 degree bank turn with nose down into the dirt, as I corrected this dire attitude I was so low that I had come out of the fog and could just make out the the ground that I was about to hit, but I had survived, just, I then landed successfully and accomplished the mission successfully. (Nail biting stuff !!!) Re: The darkness can be due to a bug that 1.5x has with the time of day, it varies to the original by 30-90 min, I have seen it in other missions. ie: If it was 05:30 in the morning at sunrise (able to see quite well) in v1.216, it would be (pitch black) and have to be set to 06:15 or so in v1.5x to have the exact same lighting conditions as v1.216. So to others, yes it can be completed unmodified, I only changed the amount of choppers that were flyable. Regards, Ian.

Yes this is by design, each stage after the first mission has two possible mission scenarios as you describe, they are provided on a 50/50 chance at random, No problem their. Not sure why this doesn't work, logic is fine for scoring, 50 for starting mission and 50 for doing objective. When pressing the ' key next to the enter key, does it show a score of 0, 50 or 100 after you think you have done the mission ???? Do you get the mission complete, you are free to depart message ??? Just tested in campaign stage 1 > stage 2 > stage 3 progression and worked as advertised. All I can suggest is you try using the DCS repair tool or send a tracks of the missions as played (These are notorious for not working also unfortunately). Cheers, Ian.

Mi-8_UH-1_co6_AbandonShip_day Corrected these missions to work with DCSW v1.5x, seems to still work sort of, but as I have never played it before, not quite sure what I am supposed to do. I have picked up off the rear of the boat and placed them back at the airfield apron, no problems, haven't tested the front of the boat yet. But when trying to hover over a guy in the water, can't seem to stay in position for long enough to pick him out of water, I'm guessing you have to stay spot on for 4-6 seconds, what is the area zone size you have to stay in ???. The standard hover height is 0-4 feet, changed the height to 0-15 feet in copy of mission to make it a little easier for me, and the crew chief barks out directions and distance, but I still haven't managed to get one, just wondering if I am doing something wrong (just suck at hovering maybe)or mission is actually broken (It doesn't seem to be though as it is doing all the other stuff correctly). Anyway, thanks for a great mission, will continue to practice. Attached patched missions if anyone else wants to give it a try and let me know if it is working as expected. Regards, Ian.

yes in mission and working fine

Huey fixed single missions: Elbrus Rescue and Stray Eagle The old mission theory could hold some water, as a lot of the existing missions in DCSW it self are still in the old pre v1.216 format and haven't been converted to v1.53 / 2.02 format. I have a copy of all standard missions in DCS 1.53 in my custom missions directory, All of them have been resaved under dcs v1.53 to freshen them up, and a lot of them have been edited to fix a lot of other issues, such as missing sound files and other version of corruption. I nearly always run my copy of mission instead of the default ones from the games menus, and don't usually have to many problems unless DCS itself is borked. I have done some testing: The Huey mission:- Elbrus Rescue and Stray Eagle all use the same method that you want to know how to use (40.50mhz FM beacon assigned to the specified soldier). The mission (Stray Eagle) didn't work from the default game directory so I had a look at it, and it is missing the ELT-tone.ogg file that is needed for the FM Homing sound, that is why there is no sound or course direction (I would have fixed this in my own version some time ago, when I converted all v1.216 missions to v1.5x and checked if the file size increased or decreased, as the conversion does sometime throw out sound files, etc.). Cheers, Ian.

This mission is a bit confusing, it tells you there is no ils at the airfield, but talks about using it (not real sure yet about this as ils is available to US aircraft, so I am not sure why they say it isn't available to Russia). There are flares there, they can be dropped from 1000 - 3000m normally and work fine in the old v1.216 but due to an issue with v1.53 they don't light the area at all if dropped from 3000m, However they will work if dropped from 1500 - 2000 meters, so the run in and bombing height has to be adjusted to less then 2000meters. It is also darker than in the old version by the time of day being bugged also, by around 30minutes - 1hr behind, so that needs to be adjusted forward from 7am to 8am. Will have a look at this one later. Whilst I have done a lot of fixing of official missions for the game, but left the training missions alone, I have no influence over when and if they will get incorperated into it by ED, but I do try. I do take notice of posts for broken missions and try to at least inform the user what the problem is and or fix it at the same time. Cheers, Ian

FM homing in MP non functional for external clients Struck the FM homing problem today in MP where I was hosting and created a soldier with a custom 40.50mhz FM transmitter, and it worked fine for me with sound and cdi direction, but no sound or cdi movement for my flying buddy as a joined client. So the issue still resides or has been reintroduced. Regards, Ian.

Yes they are sort of equipment as you can kill them with the system failure commands in the mission editors equipment failure system or threw the trigger commands as well. Cheers, Ian.

I was looking to update and checking this campaign for full working capability as a part of my campaign restoration project for DCSW 1.5x, it looked quite complex on a quick look, so I wasn't to keen to fiddle with it and have left it for my final FC3 campaign to correct. As I haven't seen or heard about too many issues with it, I would assume it is working well. Do you have any thoughts on the matter, and would you have any problem with me fiddling and re-writing triggers and such to make it work if it is indeed broken and re-submitting to ED for distribution (I claim no credit at all for mission creation and just like to have the game working as it should). I found quite a few odd choices for loadouts of the other FC3 campaigns and changed them to something more suitable, mainly AI SEAD and Strike bombers flights, no so much for the player flights. Regards, Ian.

I let the Ai play (Self Test method) the mission and I watched the F-15 Strike package kill each bunker with just 2 x GBU-27s each and all scoring worked as intended (Penetrator warhead works a treat). Side note, I have this issue in a A-10c campaign mission, that was working fine with 2 or 3 x gbu-10s per bunker, patched game, then the bunkers were too hard to destroy, I think I had 12 x gbu-10s hit one bunker and only half health off it, not sure if it was fixed yet or not. (I would assume gbu-10 aren't that good against bunkers and command bunkers as they don't have the penetrator warhead, a GBU-31 V 3B or GBU-27 would be the go, but neither fit on the A-10c, the F-16 they do) All FC-3 campaigns bar the Su-25 Cold war warrior and Su-33 Heavy Sky ones have been repaired (Working on Heavy Sky for the next month), they have just been released in the DCSW v1.54 OB and above default game. Regards, Ian.

Could be a new problem but my corrected version was working a few months ago. It is actually mission 8 of Bear Trap, I have attached that and the next two missions for that campaign if you want to give them ago. These and many more fixes should be eventually be in the official game, when ED get around to it. Changelog of fixes ------------------------ Mission - BEAR TRAP - 08 (Escort Command and Control strike).miz ------------------------ - Triggers - Added Win and Loss messages. - Fixed - (Remove push call) radio remove, flag=60 not flag=2 - Added voice overs - Waypoints - All CAS aircraft set to cas -a -x and Engage in zones set. - All CAP aircraft set to cap -a -x and Engage in zones set. - All SEAD aircraft set to sead -a -x and Engage in zones set. - - Fixed Airport Coalitions - Units - Fixed all US aircraft Callsign Numbers - Changed US-STRIKE 1 + 2 flights load out to gbu-37*4 each to enable to destroy Ammo bunkers and HQ. - - DCS v1.5x compatability - - Changed - US Sead Flight - Reaction to Threat = Evasive Maneuvers, Restrict Jettison = ON - Changed - US Strike 1+2 Flights - Reaction to Threat = Evasive Maneuvers, Restrict Jettison = ON - Fixed - US F-15c (Player) Weapons Load out - Replaced the missing 6 x Aim-120c's on Pylons - Changed - Weather - Set Fog ON to enable defined settings - Working Fine ------------------------ DONE ------------------------ Mission - BEAR TRAP - 09 (Defensive Battlefield CAP).miz ------------------------ - Triggers - Added Win and Loss messages. - Added voice overs for US SEAD1+2, US CAS1+2, COMMAND - Changed - Flag 3 and 4 for unholding ALL US Flights, RU flights, RU TANK platoons - Changed - RU CAS 1 + 2 and RU CAP to go on US player out of Exit zone - Waypoints - All CAS aircraft set to cas -a -x and Engage in zones set. - All CAP aircraft set to cap -a -x and Engage in zones set. - All SEAD aircraft set to sead -a -x and Engage in zones set. - Changed - Us Sead 1+2 Flights hold position back further for SEAD Shots with out getting killed - Fixed - Airport Coalitions - Changed - Wind direction 180 degrees to make flights take off on runway 14 as in brief - Units - Fixed - all US aircraft Callsign Numbers - Fixed - all ARTY - corrupt Fire at Point commands - Changed - RU TANK PLATOON ASSAULTS - from late start to Start at mission start but Hold insitu - Changed - US SEAD 1+2 Flights weapons loadouts (AGM-64, ARM and AGM-88c, AGM-154c) - Changed - US CAS 1+2 Flights weapons loadouts (AGM-64, CBU-105) for better armour destruction - Scoring - Changed - 50 + 15 + 15 + 50 (Time 5, US Cas1 success, US Cas2 success, US F-15c (Player) Success) - DCS v1.5x compatability - - Changed - Sead Flight - Reaction to Threat = Evasive Maneuvers, Restrict Jettison = ON - Fixed - US F-15c (Player) Weapons Load out - Replaced the missing 6 x Aim-120c's on Pylons - Changed - Weather - Set Fog ON to enable defined settings - Working BUGGED - Current Issue with AI dropping CBU-105's, will not drop sometimes, cluster impacts are locking up game at mission end / exit and causing the Score not to update during the mission. ------------------------ DONE (Bug Needs Fix) (Lot of work in this one) ------------------------ Mission - BEAR TRAP - 10 (Offensive Battlefield CAP).miz ------------------------ - Triggers - Added Win and Loss messages. - Added Voice Overs - Changed - Flag 3 and 4 for unholding ALL US Flights, RU flights - Changed - Flag 5 and 6 for unholding all US TANK platoons - Changed - RU CAS 1 + 2 and RU CAP 1 + 2 to go on US player out of Exit zone - Waypoints - All Cas Aircraft set to cas -a -x and Engage in Zones set. - All CAP aircraft set to cap -a -x and Engage in zones set. - All SEAD aircraft set to sead -a -x and Engage in zones set. - - Fixed Airport Coalitions - Units - Fixed all US aircraft Callsign Numbers - Fixed - all ARTY - corrupt Fire at Point commands - Changed - US TANK PLATOON ASSAULTS - from late start to Start at mission start but Hold insitu - Changed - US SEAD 1+2 Flights weapons loadouts (AGM-64, ARM and AGM-88c, AGM-154c) - Changed - US CAS 1+2 Flights weapons loadouts (AGM-64, CBU-105) for better armour destruction - Scoring - Changed - 50 + 15 + 15 + 10 + 10 + 50 (Time 5, US Cas1 success, US Cas2 success, US Tank1 success, US Tank2 Success, US Tank3 Success, US F-15c (Player) Success) - DCS v1.5x compatability - - Changed - Sead Flight - Reaction to Threat = Evasive Maneuvers, Restrict Jettison = ON - Fixed - US F-15c (Player) Weapons Load out - Replaced the missing 6 x Aim-120c's on Pylons - - Working BUGGED - Current Issue with AI dropping CBU-105's, will not drop sometimes, cluster impacts are locking up game at mission end / exit and causing the Score not to update during the mission. ------------------------ DONE (Bug Needs Fix) (Lot of work in this one) Let me know how you go. Cheers, Ian.

Here is a repaired mission were it should all work correctly, just tested Jtac and so long as you contact him on 140.000 am he responds and gives targets, also lighting adjusted and SEAD flights do take out some tunguskas before being shot down. ------------------------ Mission - MIDNIGHT TRAIN TO GORGIA.miz ------------------------ - Triggers - Added Win and Loss messages. - Adjusted Light Candle drops to proper height 1500m and at 5 minute intervals - - Waypoints - All CAS aircrafts set to cas -a -x and Engage in zones set. - All SEAD aircrafts set to sead -a -x and Engage in zones set. - Added "Switch waypoint" commands to make all attack aircraft loiter around Battle area until Loss or Win condition then disable via Flag 9999 - - Units - Adjusted timing on Sead to arrive when area lit up - ------------------------ Done - (Could use a little more work) Other A-10c missions are also broken, have fixed most of them and are available on request. Regards, Ian. Midnight Train to Georgia.miz

Just starting to have a look at these missions, (SU-33 Heavy Sky Campaign) under DCSW v1.5x. No time frame on a fix as yet, takes on average a month of working on them to bring them up to scratch, barring any deal braking issues with the core game (Broken trigger system, etc) and then it is up to ED to release them. I will keep an eye out for these issues, and would like to know about any other issues you may have with that campaign. The missions are quite basic in nature and seemed to have a flawed scoring system which could send you back a mission if you failed or quit the mission prematurely if playing via the campaign system. I have just fixed this so you would only have to replay the current mission if you fail it and you get rewarded for doing the tasks asked of you, namely killing certain aircraft, boats and finally safely landing on the carrier or at a land base. Regards, Ian.

Yep seen this in a lot of my mission editing, any mission with wind in it makes the AI useless with CBU-97 and probably CBU-87, so much so I usually replace with the wind corrected CBU-105 and CBU-103. Regards, Ian.

Only just started playing with the embark and disembark commands, But I think you may have missed removing the said commands from the aircraft / helo you were using to do the transports. Remove the troops with their embark and disembark advanced waypoint commands which specify the pickup / drop off zone. Remove the Helo / Aircraft groups embark advanced waypoint command, the one were you define the distribution to each helo / aircraft. That should do it. Regards, Ian.

Already fixed internally, just not released yet. Regards, Ian.

I am going to shoot from the hip on this one, sounds similar to an issue I saw with F-16s in a few missions I was repairing, may give you a place to look. The F-16 tried to take off from the wrong way on the runway without getting airborne and crashed, other similar missions didn't have the problem. Through trial and error, I suspected the weather settings were to blame: I backed up the weather pattern in the faulty mission, reset it to the default or another saved weather condition. Then I either reloaded the backed up original weather system and directions or re-set it up manually so that it was exactly the same as it was originally and the F-16's took off from the correct end of runway successfully. Regards, Ian. Dam I just read your message a little closer and run the original failed mission I was referring to above, and they do indeed take off correctly now.

Really looks like you have done all the right things so far. I have used the following website before to get port forwarding information, and their port check is excellent. http://portforward.com/english/routers/port_forwarding/Arris/ I have never had a problem with the server not working with at least 3 different modem routers since blackshark 1 to DCS 1.5x using only the 10308 port on UCP/TCP. I have never found it necessary to use port triggering either. I would be suspecting your anti-virus / firewall, In the past I have seen third party firewalls block ports even when supposedly turned off / disabled. So either uninstall the Kaspersky firewall or enable it and put in the correct allow port statements for DCS. Previously on this topic http://forums.eagle.ru/showpost.php?p=2272049&postcount=13 Cheers, Ian.

Usually when you score a perfect 100 for every mission (On first play) you play in all 14 stages, it has 2 or 3 missions per stage and there are 14 stages, so it will vary quite a lot based on scoring for each mission and a certain amount of randomness. Just quitting isn't a good option because it is unlikely you have gotten over 50 points so you will stay in the same stage and will not get the same mission, you have either a 33% or 50% chance of getting the same mission you just played based on the stage either having 3 mission or 2. So a score of over 51 to 100 will advance to the next stage and select at random which of the missions you will play out of the new 2 or 3 available. Cheers, Ian.

Quite a lot of the FC3 campaigns have been fixed now in the internal versions, definitely this one, they are awaiting release into the wild with a patch release (In ED's hands at the moment). I would be very interested to know the exact issues, so I can double check if they have been dealt with previously. You say you are getting mission complete, so what score are you actually getting is it 100 or less than 50 ??? Can't check anything right at the moment, have had a hdd system failure in my gaming rig and I need to totally rebuild my computer system as all of dcsw is affected. Will try to check the fix logs for that campaign and get back to ya. UPDATE: Fixes are now included in default game as of 1.54 OB. Cheers, Ian.

Looked in the mission editor, and weather effects are quite similiar to the other 3 alternate missions in that stage, the only thing reasonably different between the 4 missions are: Season is mainly Fall but can be Spring Cloud thickness and density - Very overcast Wind directions and strength, but there are very high winds of 8 - 15ms. So I would conclude that it is both a colmination of poor light and high winds causing the issue, as some of the KA-50 missions I have been fixing have the same issue with very similar conditions in the missions. Cheers Ian.

I do all of my aircraft modules controls with SST for the sake of it is easier to manage and configure and isn't affected (unless they change the keyboard commands) when you need to clear your DCS config and input folder due to dcsw problems, However it is more work to setup the SST profile to start with. I have just found it more tedious to re-setup all buttons to the joystick in DCSW than using SST. Using drivers and SST v7.0.40.1 under windows 8.1 Regards, Ian.

Vaguely remember reading that any units created within the mist system can't use flags, zones, or ai commands from the normal units placed in the mission editor itself. However I may be incorrect on some or all of those points, as I am no expert with the mist stuff. Regards, Ian.

Bit hard to help if you don't mention the specific mission name or number (should show up in briefing), knowing this would allow me to investigate or fly the mission to see if I have the same issue. I have had this issue before myself, I don't think it is a wind problem in the video because: The vikhers is flying dead straight, not following the laser in a corkscrew pattern, if it was wind it would still follow the laser for a certain time until it was blown further away from the laser beam so that it could not track it anymore and missile would just go rogue. The issue is more likely due to low light conditions and atmosphere or laser failure, as the vihkers isn't capable of seeing the laser, because the beam isn't being projected onto the target or that the vihkers seeker isn't capable of seeing the reflected beam due to poor contrast due to too low a light or refraction of the laser beam through fog, haze, rain, etc and simply can't see or follow the laser beam to target. Regards, Ian.