MadDog-IC

Questions: Are you running any mods in DCS ??? When changing your nvidia drivers, did you disable your antivirus program and use DDU to completely remove all traces of nvidia drivers and software before reloading the other version ??? How are your monitors setup, the Nvidia 850m should be running the first monitor setup in windows, onboard INTEL CPU's GPU should be running the second screen, recommend disabling the second screen temp whilst fault finding ??? Remedy: DCS: I would run the DCS cleanup and repair options to clean up DCS as the log indicates their may be some errant code in there, most likely a mod causing a trigger failure, quickly followed by a failure of a Nvidia software component. DCS: Might also try renaming your saved games folder temp for testing. - Download and install DDU cleaner and have Nvidia drivers accessable for installation. Nvidia driver: I would turn off any antivirus at all stages of these procedures and uninstall all nvidia software first such as "Nvidia Geforce experience", "Nvidia HD Audio", "Nvida Physx" and last by not least the drivers and reboot. Once again turn off the antivirus, check "Control Panel -> Program and features" for nvidia installed software and uninstall drivers and any other nvidia stuff that has reappeared, once uninstalled, run DDU cleaner and use the recommened top button on menu to completely remove all traces of Nvidia software, as if it never existed on you machine and then reboot computer. On reboot it should detect your nvidia card as new hardware and show up in the device manager as a standard vga card. Here we go again, disable antivirus until you reboot, run the Nvidia drivers package you wish to use, (I don't recommend the latest 390.x series as they have a few issues that only compound the problems you may be having, stick with 388.71 or there abouts) and install the options you normally do, also suggest do a clean install option. Once drivers installed and completed, reboot and re-test system with games and dcs. Log errors of note: Regards, Ian.

Not saying there isn't an issue, just commenting on something to be aware of. Unfortunately things change between patches for DCS, going from the old 1.2 to 1.5 did a lot to effect missions, with the season, time of day and year being changed due to the new DATE based season system, this did a lot to affect the lighting of the missions. For example a lot of missions set at dawn in early morning or dusk in late evening with reasonable lighting became pitch black and needed the hour of day to be adjusted to get same lighting conditions or the date changed to make the day the same season as it was once manually programmed to be. (Big difference between 09:30am lighting in winter compared to summer), the fog and cloud haze also plays a large part. Regards, Ian.

Log would seem to point to a video card driver issue or your primary video card is the integrated Intel CPU 5000 series that wouldn't meet minimum specs for DCS, at no stage does the log show the descrete Nvidia 960m video as being initialized, this is most likely were the system has crashed trying to do the first Direct X calls. Remedy: Make sure that the nvidia 960m is driving your main screen for windows and gaming. Disable the CPU's onboard GPU or only use for a second screen. Investigate the Nvidia 960m driver for issues, test with GPU-Z and other benchmarks and re-install or update it if need be. Regards, Ian.

I use the following: Set the last waypoint before landing 15-20km from runway threshold and set altitude at 500m at 500kph for speed (If altitude is way higher than 1000m or too fast, the plane will have to circle to lose altitude and speed). Place landing WP on runway, should snap to the nearest runway once made and moved near one (If not snapped to runway, they tend to just circle around). That is about all you have to do, but they will land fine themselves usually with out making landing pattern WP. Tested with jets, works ok, but with any WWII prop base planes, their pilots seem half blind, flying to within approx 5-7km of runway threshold before they realize there is a runway there, by that time it is to late to prepare for landing as they are still too high and they have to go around again and then they fly in at exactly the same specs as I had programmed and land ok this time. If this doesn't help, just post the mission up so we can have a look at it. Regards, Ian. Landing Example.miz

DCSW - F-15c "Bear Trap" Campaign Update for DCS 2.5 For your pleasure,work in progress early access for said campaign, still testing each mission for faults, (SEAD is a real headache, AGM-154c no good at all and are being replaced with AGM-65D, yes they work better so long as plane can get in close and avoid missile fire). PHASE 1: Complete at 22-03-2018 - Changed - Date, Season and Temperatures of missions:- - Missions 0-10. = Spring 22-31 March 2011. (COMPLETED) - Changed - Briefing info and waypoints to match pictures. - Missions 0-10, (COMPLETED) - Changed - US F-15C (Player) flight payloads back to Aim-120C x 6 and fuel x (1 or 3) to match brief. - Repositioned - All "Ground units" and "FARPS" from out of forests. - Missions 0-10. (COMPLETED) - Changed - Position of all static aircraft and vehicles from taxi ways and parking areas in Airfields:- - Missions 0-10. (COMPLETED) PHASE 2: Complete at 27-03-10-2018 - Tested missions 0 to 10, (COMPLETED) So if you want try it out, here is the link. https://www.dropbox.com/s/nddpm6m4rbo1zl5/DCSW%20-%20F-15c%20Campaign%20-%20Bear%20Trap%20%28Patch%20to%20Game%29%20%28v2.5x%29.zip?dl=0 Regards, Ian

I was also going to ask for such a feature also, thanks for the info, that will be real handy, haven't investigated half of the new features in the Mission Editor. Cheers, Ian.

Having similar issues with default DCS campaign and single missions, I wish you well with the update, these iconic missions deserve to live on. But boy does it take some time to correct them. Kind regards, Ian.

Not a problem, comes from 30+ years experience in computing. You and other fellows did all the work, you just had to convince me there was a problem. When I flew the A-10c again to test missiles the other day I was embarrassed at how long it took me to kill something. Its a real insult that the AI A-10c can maverick at 19km no problem with the H. Having noted that last bit, I swapped out the AGM-154 cruise missiles on an F-16 for sead work (as it is useless at the moment) with a pair of AGM-65D in the F-15c bear trap campaign, and they worked a treat, no as long range as the AGM-154 but a hell of a lot faster to target. All the best.

Hi AVERNUS your still playing then, I thought I use to play online with you, ages ago now.

Your never alone in here, we are all suffering the same fate.:disgust::director::detective:

The AI logic has changed quite substantually as we can all see for the worse because: AI planes use to fly up to the altitude of the next waypoint gradually and realistically over the distance between them, now they only change altitude when they hit the next waypoint and try to climb to the new altitude all in one big go within a few short meters after the waypoint they just passed, instead of over the kilometers given to the next waypoint. Real shame I miss the days when they worked correctly, looks ridiculous now. Regards, Ian.

I thought it odd that you programmed the radio to only transmit when your within 3km of the frigate (in moving zone) to get the homing beacon, kind of defeats its purpose, the homing beacon should be transmitting at mission start from the actual ship unit, so you can navigate to the ship via radio beacon (Just checked, you can't link radio beacon to a ship and certainly will not be linked to the in moving zone trigger area, effectively the radio signal has no fixed position). I have always used normal altitude because that was the only way you could do it, I have never seen the AGL option you were using before, so I think that it is relatively new, secondly, you can just read the MSL altitude off the info panel of map on any spot to get the height of ground for the setting. Cheers.

I have reported it, internally with track file. I felt that with a listed effective range for the AGM-65D at 8-16km and AGM-65H at 5-12km as listed in the games encyclopedia and with in game results of the AGM-65D at 7.6-8.8km, AGM-65H at 3-5km under any bright light day with no fog, hot or cold temps, little cloud and no wind conditions the D was serviceable at minimum range, but the H was very sub par at below or on minimum effective range as being discussed. Regards, Ian

Your welcome, hope it's useful. Good question, but you would be able to use it like any other trigger zone, AI or Player makes no difference, it will still trigger. There must be a bug in DCS at the moment because having the Radio command and message command in the same trigger, didn't allow the message to be displayed unless the radio command was deleted, that isn't normal, hence why I separated both commands into 2 different triggers. Cheers, Ian.

Problem: Radio transmisson command in trigger doesn't allow message to display for some reason, rewrote, but didn't test radio transmission was working. Few units height for landing embark and disembark incorrect. Unit in moving zone trigger setup incorrectly, top unit is the players unit, second is the zone and the third is the ship unit you want the zone to follow. Disembark command had condition of "Group in zone" and not "Unit in moving zone". Changed Message commands to Message to all, because I use the AI and Combined arms commanders to monitor flight, and Message to Coalition or group will not show to a commander. Made a AI version that will fly mission to show things working, and the normal one for player to play. Cheers, Ian. UH-1 - Pick up AI test.miz UH-1 - Pick up_Fixed.miz

Got it, thanks for the explanation on maverick, Not sure about the reporting thing, I haven't gotten into that side of things yet. Regards, Ian.

They tout 12 - 17nm range for mavericks IRL, under what firing conditions I know not, probably from 30,000 feet or something. I don't know what is normal, but 3nm sounds awefully short to me too.

For what it is worth, I had a fly today in the edited version of the winter instant action mentioned using only the AGM-65H. My results were quite mixed also, some times I could fire at just under 5nm but mostly at 2.5 to 3 nm (Probably depends on attack vector to target), but I could always get a lock eventually, also had the issue of having to relock the target (Shika) with TGP and then slewing maverick onto spi but the point tracking keeps drifting off target and I reposition the TGP and re-slew maverick and end up with no cross hairs at all in the maverick seeker unless I slew it around a bit. All up I would say it has issues, and if not faulty, utterly frustrating. But I remember it always being this way with the point tracking not staying locked onto target even though you are flying straight at the target with minimal jinking, perfect line of sight with TGP and certainly no violent turning or masking of TGP view. As for the cross hairs disappearing in the maverick seeker view, that's a new one on me. Attached is edited mission I flew and the track file of me flying it badly, be kind ;-) Regards, Ian. Medium - West Georgia - Winter.miz Test - A-10c AGM-65H range and lock.trk

Not trying to stir things up, I think you guys have been diagnosing your issues well. But I wouldn't think a missile AGM-65H with CCD designed to work in an Desert environment would work well in a winter environment as well, no matter how enhanced the camera system is, the lower temperatures, less light, fog and denser air in general would highly affect it. Same could be said for the IR AGM-65D in a desert environment with, Heat haze and super hot air and ground would upset it from detecting the actual tanks. Snipet of info on missiles: Not saying you guys don't have issues, well with the game anyway, there all always a lot of variable to take into account with DCS if indeed they model the real life stuff. By the time I get around to testing the mission myself, you lot will have it sorted one way or another. ;-) All the best with it. Regards, Ian.

I am very rusty with the A-10c, but I can't reproduce your issue in push 5.3: I contacted "Mantis JTAC" from the runway without taking off on 30mhz fm and the 9 line data was correctly called to the target (GG 214772) and then marked on the TAD with the correct data. I then "hooked" the red triangle with TMS Forward-short, followed by TMS Forward-Long to make SPI, I then made a "Mark point A" with TMS Right-short. Changed steerpoint switch to Mark points and selected "A" in CDU and Co-ordinates were correct (37T GG214772). Next: I contacted "Pinpoint JTAC" from the runway without taking off on 40mhz fm and the 9 line data was correctly called to the target (KM 527827), but wasn't marked on the TAD at all when told to standby data. Next: I contacted "Pinpoint JTAC" when in the air on 40mhz fm and the 9 line data was correctly called to the target (KN 527827) and then marked on the TAD with the correct data. I then "hooked" the red triangle with TMS Forward-short, followed by TMS Forward-Long to make SPI, I then made a "Mark point B" with TMS Right-short. Changed steerpoint switch to Mark points and selected "B" in CDU and Co-ordinates were correct (38T KN 527827). Also: At no stage with 9 lines from both JTAC's did I get a 37T or 38T designation (Is that normal ???). So it seems to work ok here, are you getting the data message and triangle in the TAD after 9 line verification or are you inputing coordinates manually into the CDU from the 9 line talk, if the later I would suggest your using the 37T instead of 38T as stated by others. Generally speaking there will be JTAC issues with line of sight that will have to be checked and corrected down the track due to trees being in the way now, and yes this mission has a few line of sight issues, but they can track 80% of the targets they are assigned. Regards, Ian.

Looking at your coordinates on the video as: 37T KN xxxxx xxxxx Doesn't match in game areas any listing of KN xxxxx xxxxx should be in zone 38T: JTAC Hammer 1 should be listing targets as 38T KN xxxxx xxxxx JTAC Jaguar 1 should be listing targets as 37T GH xxxxx xxxxx JTAC Axeman1 should be listing targets as 37T GH xxxxx xxxxx Pedator Uzi 5 should be listing targets as 37T GH xxxxx xxxxx Regards, Ian.

Don't want to sound condescending and this might not be relevant because your not even getting to the lock stage, but are you following the recommended procedures for maverick launch, I had to adjust my firing procedure when they added the keyhole parameters sometime back in V1.5. ie: http://www.unitedoperations.net/wiki/Mavericks https://www.google.com.au/search?q=MAVERICK+KEYHOLE&num=50&client=firefox-b&dcr=0&tbm=isch&source=iu&ictx=1&fir=6310UkGq1xwImM%253A%252CjA6oqwinxB7pHM%252C_&usg=__vFVxiD4X6eX6uaMQie9vGFe7Fno%3D&sa=X&ved=0ahUKEwiC4ZzTjujZAhVCUrwKHYdSDsUQ9QEIKzAA#imgrc=6310UkGq1xwImM: Regards, Ian.

Just to be sure, In the date section, your month has to be in December, January or Feburary for winter at its coldest, you can go -12.4c to 10c in editor, a month either side and things get warmer and can do only -6c or there abouts. Works fine in DCS 2.5 beta here, have been using it for a month or more in edited missions I am doing in winter time with temps ranging from -12c up to 10c. If still not working, send me your mission so I can have a look. Cheers, Ian.

Thanks for the kind words, I am glad others are thankful and find them useful, as I am for all the hard work others do in the background with sound mods, Skins, missions, campaigns and the other things. I just look forward to a day where I wouldn't have to fix missions so I can enjoy them. All hail the A-10c and Ka-50, long live the kings. Best regards, Ian.

Couple of issues with these missions: Some targets were moved, but not the smoke marker to new position. Smoke trigger on some set to a wrong smoke marker (Tanks) Waypoints with wrong tag names. Moved JTAC as no LOS. No issues with triggers, so long as you kill each thing in succession. Find attached: updates https://www.dropbox.com/s/h04qec6thar9uw6/A10c%20-%20Quick%20Start%20missions.zip?dl=0 Haven't any experience with radio issues in new DCS 2.5 as I haven't flown a mission for months. You will have to look it up in the manual or some one else might chime in. Regards, Ian.