MadDog-IC

I have exactly the same issue with both missions in that mission result is not always displayed correctly, first run of mission on fresh start of DCS works, but not duplicate run through of same mission with out reloading DCS from scratch. Might also be due to me using AI to test with and accelerating time quite a bit, doesn't register properly may haps. I have modified the second mission a bit, so I could test more easy with AI flying Players Huey and correcting the completed mission triggering correctly: Modified the trigger zone radii as they are way to small, you are asked to hover with in 50 meters of target ship, but you have radius at 10m, similar with Carrier, radius to small, have to make as large as the carrier is long, several hundred meters (300m as quick guess) so when landing anywhere on carrier is valid, also added speed and height requirements to the huey so that mission complete is done on touch down with zero speed in the vertical and horizontal and 22m deck height Also made triggers references from "Target in zone" to Target in moving Zone" and linked to correct ship - this makes sure the target zone will follow the ships if they do move and be perfectly aligned from their centers. Put in a couple of extra Huey (Player) waypoints to program AI to fly in zone for required time to pick up rescue dudes. Added False flag = 3 condition to Fail trigger to stop failing message displaying and ending mission when you have actually completed it successfully by rescue and landing and then dematerializing. Mission still suffers from not showing 50 score on rescue, but displays score of 100 when landing on the carrier (This is what has been happening to me for years with DCS 1.5 and a great deal of the missions I have repaired). Hope this of some help to ya. Regards, Ian. Test - UH-1H_Expert_Night_SAR_fixed.miz

Checked your first upload before you put this one here, The score is recorded but not displayed correctly, this has been a random bug for quite a while, so I suspect it will be the same for this new mission, if you have a message to show when flag 2 = true and it displays and your score is set to Flag 2 = True (50 points), then it will set 50 even though it doesn't show up. If you have the results screen open using the ' key next to the ENTER key, before the event happens in mission, ie Flag 2=true, it will usually display the result 50 correctly, if the results screen isn't open, it may or may not show the result correctly when using the ' key, but on mission completion and the Briefing / results are shown, you will see that the correct result has been recorded (barring any faults in flag logic in mission of course). Regards, Ian.

Although not the same rig as you, that 390.65 driver completely trashed my machine with immediate graphic glitches and driver failure after putting my machine into and out of sleep mode (Couldn't even draw the windows desktop correctly with out stalling driver and glitching graphics all over the place, let alone try and run DCS or any game for that matter. Completely removed 390.65 and went back to 388.71 and problems completely gone. Beware, but YMMV. Regards, Ian.

Classic corrupt / missing briefing picture, deleted the offending slot and fixed, mapresource file is pointing to a file nme.jpg that isn't in the miz file, causes somethign like a compile error and crashes DCS. This has been and issue with 1.5x for ages, but only happens occasionally. Regards, Ian. Operation Big Bird2_fixed.miz

It is Mission Push 2-3, objective is to destroy the mobile Ru HQ, it is a truck / convoy not a building, however due to a slight change I made to the original mission to fix that convoy not appearing at all, it is now set to appear at mission start 07:30 and hold position for 15 minutes and then move up the road to the north West of the HQ WP. Kind of simulates intel not always being spot on, always expect the unexpected ;-) Also noticed that the Bullseye isn't set correctly to match the brief. Campaign may be corrected some more when dcs 2.5 hits. Regards, Ian.

Been a long time but I think it is related to screen resolution, the game may only support 1024x768 or something close to that, and on modem equipment, such as HD LED monitor at 1920x1080 it doesn't show the stuff in Mission editor, you might have to scale it down in software. Regards, Ian.

Just interested to know a little about this campaign set of missions. Do they all work flawlessly in DCS v1.5x and up or do they need some things fixed. Would they benefit from a multi-language upgrade to have english voice overs and subtitles as well as the included russian eqivalents ??? Cheers, Ian.

Would be nice if all of these options below could be retained in the mission editor whilst swapping a Ka-50 helicopter from a "Human Player" or Client to an "AI piloted" flight for testing out a mission, so that when you change it back to a "Human player" the previous setting are all still there, instead of all being wiped out or set to defaults. INU points Navigation Target Points Random system failures Radio presets Best wishes to all, Ian.

Been updating some missions to multi-language and would like to know if this is a feature or an issue (DCS 1.57 stable). Is it a rule that picture files must be uniquely named between all missions in a campaign set, even though they reside in different missions and directories, I ask because if they are not it causes all sorts of wierd issues to what is displayed when you view your briefing pictures in the ME or in game for any given mission. ie: For a campaign with 12 missions, each mission has 2-5 different pictures for their briefings, the pictures in each of the 12 mission are named the same, both in the Default and RU directories. It will usually display the first picture from the first mission in all subsequent mission and the rest from the proper pictures for that mission. Default (English) directory: Briefing00_eng.png Briefing01_eng.png Briefing02_eng.png Briefing03_eng.png Briefing04_eng.png RU directory: Briefing00_eng.png Briefing01_eng.png Briefing02_eng.png Briefing03_eng.png Briefing04_eng.png If I name them uniquely for each mission changing the Mxx to each mission number and the ending from eng or rus for the russian pics, it all works fine. ie: Default (English) directory: BriefingM01-00_eng.png BriefingM01-01_eng.png BriefingM01-02_eng.png BriefingM01-03_eng.png BriefingM01-04_eng.png RU directory: BriefingM01-00_rus.png BriefingM01-01_rus.png BriefingM01-02_rus.png BriefingM01-03_rus.png BriefingM01-04_rus.png Regards, Ian.

I think you miss understood me, it is not an intricacy but a bug, they should be able to see their targets at night just as well as in the daytime, but they don't, so I suspect that they either the AI never use night vision sensor or its range parameters are incorrect. The JTAC short distance to target and Line of Sight has been a problem for ages, to get good LOS, put them on high hills looking down at targets, or on open flat plains with no buildings, trees, hills, etc between the JTAC and targets, also use excellent setting for the JTAC AI skill. You could also use AI AFAC aircraft such as a Predator, A-10c, etc to lase for your with their superior look down aspect, LOS isn't such a issue. All the best, Ian.

Would seem it is broken, all though you have met all conditions, the AI is blind at night time and can't see the targets unless they are close to the 1-1.5km mark, any further out up to the 5km IR pointer and laser 10km maximum ranges and no go, so it is either a Line of Sight, sensors or night blindness problem, I would say a sensors or mk1 eyeball problem (as it works in daylight, but not night), even AI in aircraft are half blind these days.:smilewink: If you change the mission to a day mission it works as is. If you move your JTAC with in 1-1.5km of targets at night it works as is. Best to make JTAC invisible and Hold fire as they will get killed otherwise and or kill your targets themselves depending on vehicle used. Also recommend to never use "Easy Comms" as it can be problematic, I am guessing you had to for the harrier because it's full radios aren't going yet. Made some changes for it to work a bit better. Kind Regards, Ian. Harrier_Naval_Strike_Fixed.miz

There has been constant changes done to SEAD missiles and SAM AI in patches which unfortunately, doesn't always guarantee that a SEAD missile will always hit its target, it use to be a 100% hit rate, then went to a 0% hit rate, but now is approx a 50% hit rate, this is due to SAMS now being able to shoot incoming missiles, and the AI being sneaky and turning off their search radars at intervals so your SEAD missile has no signal to follow. However, the current english version of Flaming Cliffs 3 (F-15c) module has the patches applied, and the more recent updated versions are available on the Eagle Dynamics website in the USER files section, it has also be brought to my attention that if you have the F-15c standalone module (ie NOT FC3) the patches aren't included with that version currently, so they will not work well, Eagle Dynamics have indicated they will be adding the patched version in a coming update. A dead give away for the old set of faulty mission is, If the SEAD flights drops there weapons when engaged by aircraft or SAM's. In the newer versions they are programmed to never drop their weapons when targeted. Usually if you take out the CAP flight, the only way the F-16's will get killed is if they run out of missiles due to the 50% success rate of SEAD missiles, and they try to finish their mission by gun running the SAM's. Regards, Ian.

Firstly make sure you throttle axis is working to full ranges, if it doesn't go to 100% you will not get afterburner and the special mode will not engage. If your throttle goes from 0% to 100% correctly, then you may need to reload a default config setup for the su-33 key commands as per this thread. https://forums.eagle.ru/showthread.php?t=194014 and for take off protocol, check this: https://forums.eagle.ru/showpost.php?p=3256607&postcount=12 Regards, Ian.

Need to set advanced waypoint Options to "Dispersal under fire = 0" or how many seconds you want them to wait, 600 seconds or 10 minutes is the default. You have to create a template for the pattern you want the BTR group to deploy into (ie: BTR Group Guarding), then in the end waypoint for the group where you would specify "on road", "off road", choose "custom" and then next to it "Template = BTR Group Guarding". Regards, Ian.

In my travels with DCS over the years and most recently, I have found that pc manufacturers are throttling cpu and Gpu processors to keep heat down, whilst this is great for longevity, it can cause poor game play. Mostly arcade base games, with terrific graphics and little to no physic calculations will run extremely well, as they will load a single core or multi core processor enough to make the cpu ramp up to its maximum GHZ rating and stay there, the same for the GPU, it will engage its cores to process the extreme graphics. By comparison, DCS does not, it is a completely different best, so if your system is mainly a gaming rig you will want to change your power management profiles for CPU and Graphics card GPU to run at their maximum GHZ ratings and never throttle down to anything lower. The more any processor throttles (even for micro seconds) the more stutters and issues you will see in DCS, the closer you can get your processor to a fixed setting of 4 - 5 ghz the better it runs, same for the Graphics card make sure it is running at a fixed highest GHZ rating and or its Boosted rating. You can set the minimum and maximum CPU throttling values in the standard windows power profiles and for a nvidia graphics card, you can set profiles for individual games to disallow throttling in its own nvidia control panel under 3d settings -> Program Settings -> Digital Combat Simulator (Blackshark) -> Power Management Mode = Prefer Maximum performance. Regards, Ian.

I appreciate how frustrating it is and whilst I am no expert with log files, I can't see any glaring difference from your logs to mine, except obviously that yours records a crash in the "D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\edterrainGraphics41.dll" file just after loading the "terrainoptions41.lua" file. I know you have said that you have modified the "terrainoptions41.lua" and made a backup and then restored the original to fix to no avail. But thinking outside of the box and silly as it may sound I would delete both the "terrainoptions41.lua" and the "edterrainGraphics41.dll" files and then run dcs repair again and let them be regenerated from the ED server.:wallbash: Apart from that, last resort would be to remove NTTR map altogether and reload, but no one ever wants to have to do that.:censored: Best of luck.

For any one to help, we are going to need a clue, so a copy of your dcs.log files is a must. Following on from what you have tried: Remove all mods again. Do a DCS Cleanup from the command line to remove unsanctioned files, just in case there is some leftovers you have missed. Do a DCS Repair from the command line just to double check things. Retry letting DCS create a new dcs.openalpha saved games folder and do not put in any changes such as controls, etc until you find out if it works as is (Usual culprits are the MissionEditor, Metashaders and FXO folders). Instructions here: https://www.digitalcombatsimulator.com/en/support/faq/709/ Regards, Ian.

Check here, excellent video on whole proceedure. https://forums.eagle.ru/showthread.php?t=197346

Some hints here for carrier and wind setup to allow different weights and takeoff speeds. Guide on how to take off from the short runways also. You will have to get use to taking off from the two short runways if you play single player (Player) a lot, multiplayer (Client) you can pick which slot you use if there is 3 planes in flight as you have found out. You will need some head wind 10 m/s or more if you want 80% fuel and good load out of missiles and still be able to take off on short runway. https://forums.eagle.ru/showpost.php?p=3256607&postcount=12 Regards, Ian.

Have you tried the default FC3, Su-33 campaign missions, they are mostly carrier based and freshly updated for the new takeoff parameters: Sea Dragon and Heavy Sky. Both are available on the ED website under user files. Regards, Ian.

Really good to see this change in DRM, in general I loath being held to ransom by software companies, I should be able to play a game with out having to be tethered to the internet for any amount of time, as there may come a time I will disconnect from the internet permanently due to budget constraints. This means all my steam and DCSW based games would be unplayable after a few days of disconnection. However, I am a realist and software developers have to protect there work, so I have to make a compromise, 7,14,30 days grace would be ok, I voted for 30 days but obviously would prefer never ;-{. Regards, Ian.

Maybe in the future, any faults you care to list will be compiled for modification, and consideration will given to pushing an update through. Thanks for the feedback, keep them coming if you spot any other issues. I received word that the F-15c Standalone module will be getting updated in some form to the same as the Flaming Cliff 3 F-15c module in a future DCSW 1.58x update, this would be the Bear Trap campaign and hopefully most of the single player missions. Yep, this is an originally unforseen consequence of mission updating, I have been aware of this issue in other missions recently, but due to the amount of time I spend on multiple missions and the shear number of things you have to look out for correction, I made a decision that I wouldn't be changing briefing pictures due to extra time involved. I do try to stay true to the original authors design, But there are some times I have to add or subtract waypoint, change routes and wind direction to get AI to do the missions. I have corrected the waypoints, etc back to match the mission brief so I don't have to edit the picture. , changed payload and fuel cells to match brief also. Yet another consequence of payload change in an update patch to DCS v1.5x which corrected an incorrect pylon mounting and moved the pylons for the Aim-120c and after effect was F-15c not having any aim-120c in missions, when I re-instigated the correct pylon and payloads, it was easier to put AIM-120B instead, and didn't correct briefs, not a big issue. There will always be issues, some created by me, some already in the mission to start with, either way some modules get checked over more thoroughly than others, Each mission I do may be re-flown 10-20 times or even more, whilst I look out for inaccuraces in briefing, Triggers, messaging and voice overs, Scoring logic, Radio calls, Artillery not firing, FARPS not workings or having no support vehicles for refueling, lighting an repairing, Flights having wrong skins, callsigns, payloads, speeds, the list just goes on. Regards, Ian.

Thanks for the file structures and names, that will come in handy if I talk to WAGS at ED about this issue. (I can only deal with the campaign missions as I haven't any releasable single player, Quick or Multiplayer mission updates for the F-15). Seems that there are quite some differences: The install path is different: ..\DCS World\Mods\aircraft\F-15C\Missions\EN\Campaigns instead of ..\DCS World\Mods\aircraft\Flaming Cliffs\Missions\EN\Campaigns\, that makes sense. The single, Quick and Multiplayer mission sets have some different names, etc. The Flaming Cliffs 3 layout is attached in PDFs: At this stage I would recommend you play my version of F-15c campaign for a more trouble free experience, as for other single missions, just use the games ones. I will see if ED are agreeable to updating the F-15c standalone campaign to the same as the Flaming cliffs 3 F-15c set in one of their up and coming patches. Knowing the directory structure, means I can send the fix to them directly and they only have to install into their release stream. Regards, Ian. DCS World_Mods_aircraft_Flaming Cliffs_Missions_Multiplayer_.pdf DCS World_Mods_aircraft_Flaming Cliffs_Missions_QuickStart_.pdf DCS World_Mods_aircraft_Flaming Cliffs_Missions_Single_.pdf DCS World_Mods_aircraft_Flaming Cliffs_Missions_EN_Campaigns_.pdf

I wouldn't have thought they wouldn't be any different, but ED may have just forgotten to update them, as I don't just have the F-15c stand alone module I can't test. You shouldn't be missing mission per say, except the campaign missions will have a lot of issues that haven't been corrected, a list of the missions and their faults was included with the campaign mission set you downloaded from the ED user files section. I would be interested in knowing what directory path the original missions are stored in, their filenames and the files time and dates, when I submit updates to them, the missions have to zipped up with exactly the same directory tree and filenames as the originals, so if the standalone F-15c module uses different paths and or filenames it would be a problem, unless ED themselves correct for it. FC3 default directories: ----------------------------- Campaigns in: ..\DCS World\Mods\aircraft\Flaming Cliffs\Missions\EN\Campaigns\FC3-F15C-06.miz Single Missions in: ..\DCS World\Mods\aircraft\Flaming Cliffs\Missions\Single\FC3-F-15C-Clean Sweep.miz Let us know how you get on. Regards, Ian.

Whilst I don't doubt what you are seeing, I am seeing things totally differently on my Dcs 1.57.11762 install, which lead me to believe you don't have the latest. I had checked that mission also, in the version that I have with the game, those 2 trucks are now beside the players aircraft but out a lot further of the tarmak as to be not a problem. I even checked "Clean Sweep" in the older Dcs version v1.216 and it looked like the picture you posted with the two trucks too close in the parking bay opposite the players spawn point. ED did update all of the the missions in "d:\Games\DCS World\Mods\aircraft\Flaming Cliffs\Missions\Single" recently, to add multi language support so mission files are now dated 27-05-2017. I would check that to see if you have same. As a side note, the missions editor does have a nasty habit of forgetting where the aircrafts parking slot is assigned and randomly placing them else where which can cause issues like you describe, but doesn't appear to be the issue here. Just to be clear, my original updates to the F-15 Bear trap campaign were completed around 03-10-2016 (over a year ago), they were then only updated recently 04-03-2017 to only correct the refueling tanker speeds and mission 1 where a missile problem was introduced with a dcs patch to do with the SEAD. So over a year ago they were completed, and sortly after that they were incorporated into the DCS game engine by Eagle dynamics for release with the Flaming cliffs 3 module. So that means that the game has exactly the same mission set as my files available from the user files download section. This is why I think something is a miss with your install: I have had this issue before with other users, there issue was they were running a foreign russian version of DCS, which were never updated, only english version. Do you have the full Flaming Cliffs 3 module, or just the F-15c standalone module, there has to be a reason we are seeing different things in mission. Most of the issue your are describing with the campaign and single player missions are all related to older versions of the missions, I know because I have already fixed them before, I just haven't posted the single player missions anywhere. No the log is no help to me, but you can check your progress anytime in mission with the ' key it will show your RESULTS (50 for starting the mission and only goes to 100 when you have completed the requirements for the mission as per the brief), if you get no mission complete message and your RESULT is still 50 you haven't done the mission correctly, or mission may be bugged in some way. My repair log tells me with original mission logic was broken so mission complete was impossible and had issues with radio commands to other flights such as SEAD, Strike: ------------------------ Mission - BEAR TRAP - 06 (Escort OCA strikes on Mozdok).miz ------------------------ - Triggers - Added Win and Loss messages. - Removed Flag=50 from Loss trigger - Should only be on for Win - Total rewrite of US Sead and US Strike hold and radio commands for timing (Changed flags on orbits to suit) - Added Voice overs - Waypoints - - 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. - Added "Switch waypoint" commands to make all attack aircraft loiter around Battle area - - Fixed Airport Coalitions - Units - Fixed all US aircraft Callsign Numbers - Changed US STRIKE 1 + 2 flight path to stay low on run in to runway bombing - Changed US SEAD 1 + 2 + 3 Flights from 2 to 4 ship so able to take out SA-11 batteries - DCS v1.5x compatability - - Changed - US Sead Flight 1+2+3 - 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 - Works Fine ------------------------ DONE Regards, Ian.