MadDog-IC

Sorry to see you still having some problems with the mission, hard to say why that happened, I would be just guessing. (If you had TACVIEW you could check what happened post mission) Strikers may have jettisoned their bombs prematurely due to being attacked or hit (Were they ever in any danger ???). Low on fuel maybe (Very unlikely). All I can say is that the AI builtin testing system I use with the mission, shows everything working as it should with dcsw v1.55.x (The striker aircraft still continue to bomb the runways with extreme predudice), run it through the whole mission a couple of days ago, before replying to your previous posts just to rule out any new bugs.

Didn't know squat about this aircraft, but she does look great, thanks for the history lesson. Being built by SAAB makes me worry though, as I drive old Scania buses (From about the same era) for a living and the electronic are very unreliable in those, so I wonder it the viggen suffers any reliability issues.:joystick: Thanks for posting. Regards, Ian.

Nice job all involved in that video, It never gets old watching pro's do their job. I've had a go at your carrier landing mod and love the work you have done with it, I just need more practice, can't get over how close and slow you have to come in at, with an all mighty thud at the end on landing. Thanks for sharing. Regards, Ian.

Never had that one, so can't help unfortunately. This is quite a rare issue now, but I did have it happen to me a couple of days ago, luckily it was on a copy of the mission so no work lost. Always happens at the most inopportune moments, unfortunately experience has shown me that once the unit names change to DictUnit_.... the mission is stuffed and the only recourse is to re-do it or get the backups out. Hopefully someone else may be more helpful on how to get it back into working order. They would need to see the mission and your DCS log and crash files to see if there is any hints as to what went wrong. Regards, Ian.

Firstly check that you are using the English version of DCSW as other localisations such as russian, etc haven't had the missions updated and none of this help is appropriate. If bombers are killed by SAMS, you haven't used the radio to call in the SEAD flights to take out the SAM's. Good luck with it.

Objective for mission 8 is not only to kill enemy planes, but guarantee bombers can get to their destination and bomb the runways, Mission is only a success if the runways are bombed. It would be a mistake to send them in whilst there are any enemy planes that could possibly get close to them and get a missile or two into them, if you lose the bombers or they are turned back you fail the mission. No good landing at Sochi or any other neutral airport that have no support vehicles there for refueling or repairs, so you must manage your fuel usage wisely. Regards, Ian.

Download and install directx9 I would be guessing.

There is the problem, would only be the english version sorry, never even gave it a thought about different localizations. I would have to go and learn russian to help you. Just for your info, I have attached my current changelog of the A-10c Georgian Hammer campaign as it is today to give you an idea of how many fixes were need for the missions. (It is about to be updated again for tried and tested true v1.55x compatability with simple english voice overs) Cheers, Ian. + A-10c Campaign - Georgian Hammer (Fixed + English VO) (v1.55x).zip

If you have this version of DCSW then: All of the A-10c Georgian Hammer Push mission files should be dated 23-06-2016 and actually have Flag=100 for all win conditions. Hope your not confusing it with the All CA-Push missions that have never been corrected and us Combined arms to move convoys, etc. Do you run the Georgian Hammer campaign via the normal campaign manager in DCSW ??? If all else fails try a DCSW repair for standalone version or a Cache integrity check for the Steam version to correct any issues. Regards, Ian.

You must be running an older version of DCSW 1.2.16 or earlier as this campaign did have several programming issues, All of which were fixed in DCSW v1.54 and onwards. An older fixed version of the whole Georgian Hammer Push Campaign for DCS 1.2.16 is available 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=Filterer Regards, Ian.

Had a lot of issues with different module for a while with certain key combinations not working, figured out why not recently. If you have added, modified or removed key combinations from the default keyboard command sets for an aircraft DCSW will make a keyboard.diff.lua file to record the changes. For what ever reason that I can not see why it does it, more than likely ED changed the format recently and any older keyboard.diff.lua files no longer work correctly. So the short answer is to delete any "Keyboard.diff.lua" file in the following folder for the A-10c and let DCS just use its default key set and all should work again (You will have to remap any key customizations you had previously and this may or not break it again, I haven't tested that far: c:\Users\Yourusername\Saved Games\Dcs\Config\Input\A-10C\keyboard\keyboard.diff.lua Regards, Ian.

Definitely not me, but there are a few different maddogs about. I almost never play multiplayer anymore, only with a fly buddy on my own server setup. I did make a test mission to try out your requirements with my suggested options and it was working ok. Cheers, Ian.

Pilot just wants to live, no point going down due to lack of fuel. (Yes the option to not RTB doesn't do anything) I've found setting it to 1 second works pretty good, turning it off doesn't work at all. Called trial and error, try the different setting to try and get a result your happy with, average setting has him miss by a small margin and makes his eye sight worse, so he can't pickup targets quite as well in the first place. Regards, Ian.

Same for all / most AI aircraft is to have your attack commands on a waypoint approx 10-15km from your targets waypoint, so as to give the AI time to spot it and lineup on an attack run, any closer and they might not detect them and engage. Regards, Ian.

Can't verify that TrackIR has this as part of its install, but it most likely that it is required for TrackIR to function correctly, it can be downloaded and installed separately from the microsoft site. Visual C++ Redistributable Packages for Visual Studio 2013 https://www.microsoft.com/en-us/download/details.aspx?id=40784&fa43d42b-25b5-4a42-fe9b-1634f450f5ee=True Yes, you will need to do that, but do it as instructed below. Download the "Vcredist_msvc2013_x86.exe" from the microsoft site and install it, with run as administrator (Right click on file to bring up the menu). Unplug your TrackIR camera from the USB port. Uninstall TrackIR and its USB drivers Reboot computer Re-install TrackIR software and make sure your run as administrator (Once again right click on file to bring up the menu). Plug in the TrackIR camera to the USB port only when asked to do so during the software install. Reboot computer Test that TrackIR is working with its own software and or in device manager to see that it is installed correctly. Regards, Ian.

Played recently with one of the P-51 missions using this technique and survived quite well. I would fly above the zu-23's max firing range altitude of 2.5km (might be higher due to ground elevation) so as to not get targeted in the first place, I would then fly slightly left or right of the target until it was aligned along the side of my cockpit between the the wing root and windscreen support, roll onto my back and dive almost vertical onto the Zu-23, when the target is in the top half of your windscreen / Hud, reverse roll 180 degrees line up the shot and finally start strafing and pulling out of dive, this should be like a surprise attack and not give the Zu-23 time to see you and aim / fire. You will have to be vary careful of final dive speed not exceeding the mustangs rating of 500mph or you will lose your wings on the pull out. Good luck with it. Regards, Ian.

Unfortunately to many things have changed with DCSW since this mission was made, and it has broken the script file it uses. The script file in mission is TTCF_V32 _MI8.lua which is actually the CTTS.lua script, only way to fix it in humble option is: Re-write the CTTS script to use the new calls to DCSW or to totally replace it with the new CTLD.lua script that does pretty much the same thing and more (But this would be a lot of work either way, as the script has to be totally reconfigured and alternative methods used that are used in CTTS but aren't available at all in CTLD, not for the average joe to be able to do). *****UPDATE***** Surprising what a couple of hours digging around in mission in general can do, I have fixed all the errors in the mission startup, so give the fixed mission a go and see if you get any other errors during mission flight time and post back with problems or if it works perfectly. Solution was easier than imagined (You never can tell how hard it maybe): Had to remove the TTCF_V32 _MI8.lua script from triggers INIT field as that has been broken for a while and put it into as a trigger event 1 second into mission start. Put a 10sec delay time for start of each script function call to stop the functions being called before the main controlling TTCF_V32 _MI8.lua script file was loaded. Checked that the script calls were creating the units dynamically, yes they are. Issue I believe happens with CTTS is troop embark and disembark radio commands menu don't show in MP with an external client connecting into mission. Fixed mission file here (Was to large to upload to message): https://www.dropbox.com/s/2lkxbvkvw917594/TOOTALL%20Mi8%20UH%20v3.2%20%28Fixed%20for%201.5x%29.zip?dl=0 Regards, Ian.

Congrats on finishing the campaign, will give it a whirl some time. Thanks for your persistence, as I know how frustrating it is with the state of issues through out the DCS development cycle. I myself find the v1.55x mission editor and DCS core program so unstable I can't work with it any more, just too many random issues.:cry_2: I was really enjoying your initial missions for this campaign with a fly buddy in a re-written multiplayer version, so much so that I rewrote them to have proper troop drop off and pickups using the DCS embark and disembark options, but alas that is stuffed now:cry:. All the best. Regards, Ian.

Yes this is the default behaviour of DCS unfortunately. Correct, well done. You don't click SAVE, you just click OK at the bottom of the options screen, if you don't click that OK button no changes will be saved. Don't confuse those three buttons above for CLEARING a Column, LOAD A PROFILE and SAVE A PROFILE for the saving of your profile for use in dcs, just use the OK button at the bottom of the option window. The last two are only used to make backups of your profiles , say if you want to send a copy of your joystick setups to a friend or load a profile from your friend into your joystick configuration. Profiles configured in DCS for an A-10c aircraft *.diff.lua files are stored here: c:\Users\Ian\Saved Games\DCS.openalpha\Config\Input\A-10C\joystick\ No Can't help with this as I have never had FFB stick, but I do know that FFB in DCS has been faulty quite a lot over the years. It gets fixed, then its broke again, then it is fixed again and the broke again, so on. Regards, Ian.

Either archive all the files into a dcs.zip file if they are larger than 500k each or rename the individual files and change there names from .log to .txt. ie dcs.log, dcs-old.log are main ones needed, crash dumps may be useful only for ED as I can't figure those out. The uploader will not accept .log files, check the list below the file upload boxes to see the formats and sizes accepted. Regards, Ian.

Zip up your dcs log files and post here so we can have a look for you to see what is going wrong. Logs stored here: c:\Users\Yourusername\Saved Games\Dcs\Logs\ Would be handy to have the mod you were using also or at least its name. Also what type of error did you have ??? Regards, Ian.

It isn't the position of your aircraft but the vector and distance you need to fly to line you up with the runways entry pattern. ie: ATC says fly 270 for 10, QFE 28.8 = fly compass heading 270 degrees for 10 km and set you altimeter pressure setting to 28.8 for correct altimeter readings, follow those instructions and you should be flying directly at the airfield / Farp. Regards, Ian.

I've had this issue before, best I can describe it is: Be sure to install TrackIR with Admin Privileges and idearly to another directory other that its default as c:\Programs X86\,etc are protected windows directories. If trackir is installed in any directory and is not run with admin privileges or has no read/write privileges to its own directories, windows will make it save the profiles to a virtual store directory that it can read and write to, ie: "c:\Users\Ian\AppData\Roaming\NaturalPoint\TrackIR 5\Profiles" Secondly naming of the profiles themselves, the filename is not the name that the profile uses, the name that shows up in the trackir profile list is actually recorded and stored in the *.xml file itself, so if at any stage the profiles filename is changed, in trackir it self will still show its original name in the profile list. My trackIR software is installed here "d:\Games\TrackIR5" with a profile folder, but all profiles are saved to a virtual store by windows to:"c:\Users\Ian\AppData\Roaming\NaturalPoint\TrackIR 5\Profiles" What is a virtual store ??? http://www.sevenforums.com/general-discussion/222389-what-virtual-store-folder.html Regards, Ian

Check out these posts, some good fault finding information on server setups. https://forums.eagle.ru/showthread.php?t=166405&highlight=server Most important that you are not using and IPV6 internet connection as it is not supported by DCS as yet, Should be IPV4. Regards, Ian.

I saw that AI flying NOE was especially useless the day dcs v1.5x came out, when I converted most of the Flaming cliffs 3 campaign missions that played out fine in v1.216 with jets going through narrow valleys, now all crashed into the valley walls or kept going out of the valleys for more height. Most of the missions had to have all of the flight altitudes adjusted for the missions to complete successsfully. Regards, Ian.