MadDog-IC

All problems in the missions of this campaign (English version) have been addressed and fixed in DCSW 1.5x since mid 2016 and should work as advertised, barring any new issues recently. You can also download the updated missions from the DCS user file sections with a changelog of fixes applied to each mission if you have a different localized version (ie: Russian, etc) with out the corrections. Following the instructions given in the briefs, and any radio commands on route is all that is need to succeed in any mission. Regards, Ian.

As other user has said, apart from other issues the drivers may have, If you program a joystick button in SST it can't be programmed in DCSW and Modifier joystick buttons in SST will not be recognised in DCSW. In SST: Program joystick buttons to what every you wish. Program modifier buttons or modes. Don't program any thing to joystick buttons or axis you want to use in DCSW. (Leave them as UNPROGRAMMED) In DCSW: Program joystick buttons to what every you wish that weren't assigned in SST. Program modifier buttons, You just can't use the same ones as SST has programmed. That is as simple as I can describe it, I appreciate these things can be hard to grasp at times. Regards, Ian.

Need to stop SST from loading any of it's profiles. Right click on SST profile editor on task bar and "Clear Startup". Right click on SST profile editor on task bar and "Clear Profile". MFD on X-52 Pro Throttle must read "NO PROFILE". Now go into DCSW and map buttons as normal.(May take a few presses of each button to register though) Regards, Ian.

Yes I found out these things the hard way, when fixing some missions and using the AI to test, all looks ok when they fly the mission, but when you fly it yourself, you see the glaring problems of the existing missions aircraft airspeeds, etc (at or below Stall speed). It doesn't help that the mission editors default speed is 500km for all aircraft (from memory). There is just an enormous amount of variables to consider with playing around in the mission editor and with missions. Regards, Ian.

Really nice to have a fan, looks like you have as many mods as I do for DCSW. Most of those fixed campaigns and single player files are slowly finding there way into the actual release games of DCSW 1.5x. I initially was doing them all in JGME format, but changed due to EDs requirements. I have been working on the Su-33 Heavy Sky Campaign, but it is a hard slog, as there are 25 missions (First 10 are done), IMHO the missions are poorly written, and don't play as described in the brief, so makes more work. I had started on the the Ka-50 Medvedev campaign also, but some times its hard to get the AI do the missions for you, especially when it is in poor light and windy. The Ka-50 and A-10c was my primary focus for correction of missions and campaigns (As these are my favorite modules). Good to hear more and more people are finding those files for download and enjoying the missions as they once were in the glory days. Regards, Ian.

That is the best way to do it. I was in the process of starting to fix all of the Ka-50 single player missions a year ago, but my time has been diverted to a mixture of other DCSW projects since that time. I may will get around to them in time, but I am one man, and having already fixed literally hundreds to a thousand missions over the years is extremely time consuming and draining. I sure can appreciate the time that the ED team must put into all of this software. Glad it has helped someone. Regards, Ian

In the mean time, here is a quick fixed version of the mission for v1.5x. All Farps corrupt and not rendering in game, fixed their missing names and frequencies to make them appear. Tested Ka-50 take off correctly from farp and that you can contact ATC for startup and Takeoff clearance = OK. Regards, Ian. Relocation.miz

I have edited hundreds of missions over the years, and the problem really only come about with DCSW v1.5. Some airfields do have other strange behaviours to do with parking spots that haven't been fixed either. I can't remember DCSW v1.216 ever having any issues with static or vehicle objects being placed on airfield taxi ways and aprons, but now AI is super sensitive and can and will get held up on them and not taxi about properly, and the disappearing act is a strange one, all occurring at different stages of patch development. Because I am fixing missions to work properly, I simply just move the offending objects into a less problematic area of the airfield and the AI move on. There was a few rare instances where the AI planes pathing was faulty though and ED fixed them. Looking back threw some fault logs of missions: The A-10c Georgian Hammer campaign had a lot of the disappearing landed and taxing aircraft bug in missions (Batumi). The FC3 Mig-29 Over the Hump campaign had taxiing and take off issues (MINERALNYE VODY) and (Nalchik). Regards, Ian.

Seen this problem at certain airfields in most versions of dcs v1.5x, If they taxi too close to some parked trucks, if you move the parked trucks they usually taxi fine. Regards, Ian.

Feel free to list missions mentioned and we might be able to help. Regards, Ian.

This mission is now darker due to a time of day bug with DCSW v1.5x and wingman probably can't spot enemy or use shkval, as it is no good in low light conditions. I have debugged all the missions (with change logs) for dcsw v1.5x in that campaign and have them available on the ED user site for download if you want to give them a try. Time of day should be corrected on that mission also. https://www.digitalcombatsimulator.com/en/files/1744245/ Regards, Ian.

Not sure what ATME does, haven't looked into it (assuming it does dynamic spawning, etc), but in normal Mission editor flight groups which have CAS -a or SEAD, -a or like instructions in the advanced way point commands it will do exactly as your description of not following waypoints when enemy's on map. Solution is to remove those lines or disable them and add in search and engage commands at certain other waypoints for them to attack in only the areas you want them to. Regards, Ian.

You have to play around a bit with Cockpit view controls (this is from memory): First disable trackir before getting in game or pause it whilst in plane and center the view. Press Lwin + Numpad 5 to tell dcs you want to adjust snapview 5 Use Numpad / and * to adjust your zoom level in, out. Use Numpad arrow keys to position up, down, left, right. Use R-Shift + R-Ctrl + Numpad / and R-Shift + R-Ctrl + Numpad * to adjust forward, back eye position. Use R-shift + R-Ctrl + Numpad arrow keys to move eye point up, down, left, right. When you have it the way you want it, use R-Alt + Numpad 0 to save it. [*]Press Lwin + Numpad 0 to adjust snapview 0 Use R-alt + Numpad 0 to save. [*]Now shutdown DCS and enable trackir again and play as normal, and your default cockpit zoom level should be good and zooming in and out will be in proportion of the center zoom. [*]Also can't use any axis that is self centering for zooming in or out and expect it to stay zoomed. Regards, Ian.

Had problems with v1.53/4 myself on install. If you have an older version loaded prior to these versions, uninstall all versions of Tacview, so they can uninstall the older .lua script files, as different script names are used in the new versions. Then re-install tacview v1.53/4 and try using again. If that fails, check that you don't have other programs that modify the export.lua file and are over writing tacviews changes. Check the tacview help at Q13 and Q14 particularly, this shows what files should be where for tacview to work. http://www.tacview.net/documentation/dcs/en/ Regards, Ian.

Updated here: https://www.digitalcombatsimulator.com/en/files/?arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=MadDog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter

Updated mission set for "Bear Trap campaign" is on the ED user files site, addressing the tanker speed. Don't know why the speed would be locked in the mission editor, I know of no way of doing it. Regards, Ian.

Having been contacted about this problem, I see you are correct, the real life tanker booms are set to be used at 315-355 KIAS for F-15's, the Bear Trap Campaigns tanker orbit speed of 490kmh (Set by defaults) is way to slow and will be amended ASAP. After testing Setting speed in ME to 850kmh TAS for tanker = 620kmh IAS at 6000m = approx 320 KIAS. Regards, Ian.

Glad to help, no fun flying broken missions. Eventually most if not all of these fixed campaigns and missions will be available in the stock modules of DCSW, some are already there now, some on the way. I have noticed ED are now starting to put additional language options for missions now, so you can have english, russian, chinese, french, etc. subtitles, voice overs and briefing pictures in the same mission set. (Have had a look at how this works, and I think for the moment it is too time consuming for me to play with, but I will probably update some campaigns or missions that originally had russian voice overs and were replaced with my english versions, I could now have both available. But that is for another day. Regards, Ian.

Just be carefull if you change anything more in the future such as ram or a hard drive, the bios change will be added to it, so if you go over the points system it will cost you activations. Can't remember but probably 3 points for Bios, 3 for ram and 3 for Hdd.

Just from memory, may have changed as I haven't tested recently, but if you adjust the weapons loadout of the huey, so that it doesn't have any rockets or miniguns for the co-Pilot / Pilot to use, ie: just the door gunners weapons, they will work and open fire. Also up in the advanced options for the huey (Accuracy or something like that) from 90 to 100% if you want them to be able to hit anything. Regards, Ian

Most likely the replacement .lua files where replaced with originals when an update was performed for DCS, those .lua files used to get the ekran, etc working are separate from the monitor.lua. Reinstall the mod or copy the files from the _Backup directory created under DCS World root directory back into the proper directory structure, starting here: ..\DCS World\Mods\aircraft\Ka-50\Cockpit\Scripts\ CautionLights_panel.lua Ekran_init.lua PVI_init.lua UV_26_init.lua Regards, Ian

Had a look at mission, disabled all your commands for chevy 1 and put in Reaction to Threat = ignore threats and even Evade fire and it doesn't do the dive to ground, which is happening at the ship moskava detection range marker, so It is the threat. Put all your commands back in and still works fine, so long as their is a Reaction to Threat = something other than the default. Saved to new filename using DCS v1.5.6.1938. Regards, Ian.

@mustang Looks awesome, fantastic work, don't know why I hadn't been running this texture pack till now. Thanks for your hard work on this, much appreciated. Regards, Ian.

I believe the issue is that the beacons are broadcast fine at the start of the mission to any aircraft that already have the pilot in them, but under multiplayer this isn't the case, all players aren't in their aircraft the very second the mission starts, so they will not be broadcast too. Only solution I have know of is to write a trigger event using switched condition so that each beacon is re-broadcast, every few minutes through out the mission or when a new client is detected in a certain zone. Some hint here on how to do it https://forums.eagle.ru/showthread.php?t=105554&highlight=huey+beacons https://forums.eagle.ru/showthread.php?t=140567&highlight=huey+beacons Regards, Ian.

+1 Right with you there, very depressing when you favorite stuff just doesn't work right.