MadDog-IC

Glad it is useful. I just upgraded my machine again, and did the whole deactivation and reactivation dance once again. Thank god I got on the ED site and checked that each module was indeed deactivated, as I had forgotten to do the combined arms one. But the whole deactivation and activation proceedure went with out a single hickup. Merry Christmas to All, Ian.

A shameless advert to the files ;-) https://www.digitalcombatsimulator.com/en/files/?arrFilter_pf Enter in UPloaded BY: Maddog-IC Merry Christmas, Ian. Su25 Campaign GOW Changelog.txt

Hope to see the albatross in my christmas stocking on christmas morning, would sure beat a lump of coal ;-):yay: Thanks for the kind gesture. Merry christmas to ALL.

Not sure if it is a fault or just design feature ??? But when a Ka-50 unit is assigned in the mission for a human player (Player) singleplayer or (client) multiplayer, it has the box to input multiple Target Points and their coordinates. This works fine, but as I routinely change a Human flyable aircraft into an AI driven unit to test the missions with, this box disappears on the change, that seems like it would be normal, but when I set the same flight back to the Human drivable type, all of the Target Points have been erased. Point is, can those Target Points be auto saved instead of being erased. Regards, Ian.

Ai Ka-50 become stuck in a permanent hover when engaging enemy AAA vehicles: If helo runs in and doesn't dodge fire and kills the AAA in first pass, the helo will continue to the next waypoint / target ok. If helo waves off to avoid fire and has to go around for another pass or two to kill the enemy AAA target, it will either get stuck in a hover permantly and not continue or will continue after approx 19 minutes and do stupid flying. So the more skilled the enemy at firing, the more likely for the issue to happen. Test - Helo attacking (RTT).miz

Ai controlled Ka-50's (set to blue or red side) will attack their own farps if Rules of Engagement changed from default (Only Designated): Weapons Free - Continually shoots own farp Return Fire - Continually shoots own farp Weapons Hold - Shoots own farp once, then keeps attacking without firing. Priority Designated - Continually shoots own farp Only Designate - Functions Properly Example mission attached. Test - Ka-50 shooting Farp.miz

F-86 Sabre for me. Thanks for the kind gesture.

Not necessarily set by the server host, it is a feature of the Mission Editor, so it is the mission designer that causes the problem if he uses the Prepare mission option. Some mission designers use it to pre-configure a mission with preset radio frequencies and other aircraft parameters, the file mentioned above is one of many that gets saved in the mission file. Been an issue for a long time and is an issue for many a triple screen client.

Don't recall ever watching any of your videos, but they must have something going for them, with that many subscribers, well done. Oh, almost forgot, I want to go to Las Vegas

Like many others I am neither a new user or overly proficient with the A-10c, but do all right. I have a real love/hate relationship with the DCS series, but still invest a lot of time in mission fixing and some learning of systems, etc and actual flying. All ready owning the A-10c and quite a few other modules though, I would dearly love the NTTR map as I think the new maps about to be released will be the only thing on my wishlist, as I have enough aircraft to keep me busy for the next few years, favorities are the A-10c and Ka-50 for their complexity. Being of Scotish decent I am always looking for a bargain, but I know I don't fit your criteria, so I hope you find someone more deserving of what would be one of the best combinations of dcs modules to have. Regards, Ian.

Thanks. But minor, I think not for all us perfectionist around the forums, we like to be wowed, even by the little things.:surprise: Cheers, Ian.

Not sure if a bug, but I have seen at least a couple of mission I have converted from dcsw 1.216 to OB 1.51 upd 2 where the lighting of the time of day at mission start is different. ie. Mission Starts at 08:18 on the 27th of October 2011: In dcsw 1.216 the sun is above the horizon at mission start In dcsw 1.51 the sun is below the horizon and mission in darkness Regards, Ian. Su-33 - Sea Dragon - 06.miz

Based on other users observations. Quick test of 2 x 4 ship flights taxing in Nalchik: If one flight set to (ramp hot start) and the other to (ramp cold start) = some planes get stuck on taxi to runway. If both flights set to (ramp hot start) = some planes get stuck on taxi to runway. If both flights set to (ramp cold start) = All planes taxi to runway correctly. So there seems to be an issue with taxiing if there is a flight in the airport that has been set to a (ramp hot start). Regards, Ian Test - Nalchick hot start taxi_DCSW v1.5.miz

Like to chime in here with a bit that might be relevant. Have a mission that was affected by the AI collisions with a lot of aircraft taxiing and taking off from multiple airports and they were all fixed by OB 1.51 update 2, bar one. This one flight of P-51d weren't taxiing, holding and taking off properly, and this had been like it ever since I had ported the mission to 1.51 from 1.216. Problem turned out to be: 4 static Ah-64d helicopters on ether side of the last taxi way to the runway, deleted them from mission and P-51d taxi, hold and take-off as they should. Tested by putting a Farp near runway and it stuffed their taxi and take off also. So it seems that placing any static object near a taxi pathway or runways can influence the taxi and take off routine of flight groups. Mission and pictures Attached to show Ai playing up. Regards, Ian. Test - Beslan airfield taxiing_DCSW v1.5.miz

Using SST profiles: ------------------------ Press and hold Clutch button on Throttle Scroll to profile using up and down on Sticks' silver POV When Profile you want showing - Move POV to right on Sticks' silver POV to activate it. Alternatively, run Profile editor and load profile and test in built in test section to see if keys are being parsed from profile. Change to DCS World ---------------------------- Go into controls section for aircraft type Left click in any joystick button spot to select it in x52 pro Throttle joystick column Select "Clear Profile" up in top right of menu to remove all pre-assigned button functions. Left click in any joystick button spot to select it in x52 pro joystick column Select clear profile up in top right of menu to remove all pre-assigned button functions. Check and setup Axis's for x52pro throttle and joystick. Load DCS and test it all works as designed. Regards, Ian.

When having 2 x Su-33 AI jets take-off from the "Admiral Kuzetsnov" carrier: The first plane is positioned correctly up against the blast flap. The Second plane is positioned incorrectly behind the second blast flap and takes-off through it. Doesn't seem to make any difference which mission has the Su-33's on the deck, but with three in the flight the third member gets positioned onto the second blast flap properly. Also affects the ability of the flight to land properly on the carrier, with the second plane waving off all the time for no apparent reason. Update: 18/03/2016 ----------------------- The above is caused by the initial angle of the ship they are taking off from If angle of boat is at either 0,90,180 degrees heading all planes are positioned correctly and will land correctly if the boat is at one of those angles when they return to land. If angle of boat is at either 45, 135, 225, 270, 315 degrees heading the flight lead will be in correct position, but his wingman will be not positioned correctly and will not land correctly if the boat is at one of those angles when they return to land. Regards, Ian.

Quote from guy with similiar issue, different game, different hardware. thread http://forums.bit-tech.net/showthread.php?t=266200 Finally fixed this two days ago!! I had been still having problems even after all of the above and to be honest was getting ready to RMA the RAM and Graphics card purely on the basis, it had to be one or the other when I had a mini epiphany after reading two web pages, after another bout of google'ing until my eyes bled. Although it failed 99% of the time on the nvd3dum.dll it did also fail rarely on some other modules, but always when WoT was driving so to speak. But the Exception code: 0xc0000005 was always the same. So I started looking into what the codes meant. From a google result I got a post on tomshardware, which has a link to another site purely talking about "Exception code: 0xc0000005" and after reading through the very long guide (which didn't bear much fruit tbh) I read some of the comments left at the the bottom of the page, which is where I hit pay dirt. Someone had listed lots of the HEX numbers and what they generally mean. 0xc0000005 = Memory controller issues. At first I thought "but I have checked the RAM 3 times already" when it dawned on me what if, what is being sent into the RAM is garbage? So a look on Gigabytes site for a BIOS update found that they had one more new bios and it had better compatibility with overclocking and high speed ram. And so fair I have not had a problem.

I am with blooze on this one, I thought that originally it my be a an ogg or wav thing, but on testing couldn't prove anything either way. I had been testing mission conversion from 1.216 to OB 1.5 and since the hotfix 3 most issues seem to be resolved. My issues with missing sound files / sound files not playing, was caused by some wierd thing in the script init boxes within the Mission Editor, there was no file or code in each box, but the code box was highlighted with a big grey box. This caused the OB Mission editor to generate a general lua error on saving of the mission and subsequently to drop a random amount of sound files from the mission file - (this was checked with a zip file viewer to see the differences in the original mission file and the new OB 1.5 version). Suspect it is mainly missions that have either a mist.lua or other xxxx.lua scripts in the init section or through out the mission triggers. I have been editing some missions after conversion to OB 1.5 format and testing and haven't found any corruption issues as you guys have been having, ie with multiply edits and resaving of a mission for example.

I concur, very nice addition, well done ED.

Oh snap, first time I had tried AAR with the F-15c also, managed to connect a couple of times so far, but no lengthy refuelling yet. Was worse than I remembered when I use to AAR with the A-10c, so I thought it was bugged.

If you double click on the greyed out commands in the advanced waypoint section the options should come up, if not, can't help sorry. However here are the quickly, edited, fixed and tested version of Mission 8 and 10 of the Su-33 Sea Dragon Campaign. Regards, Ian.

For me in DCSW v1.51: The mig-15 snapviews were non-functional, in that none were set by default, all set to a default cockpit view. Reprogrammed snapviews for looking to rear of plane, left and right cockpit panels, etc. (No issues, all new views working as expected and have stayed persistent) Cheers, Ian.

Had similiar issues with my x52pro: I was using an extension USB cable and the the female recepticle wasn't fitting very snug onto the joysticks usb cable, so I crimpted the outer metal sheath to hold plug snuggly, fixed my flashing LCD, unresponsive HOTAS, etc. The round svhs plugs in the throttle body and Joystick also become unreliable and lose connection intermittently. Pressed these in hard and continuing to operate OK. Might have other issues, but sounds a bit like an intermittent connection issue, check your cables. Regards, Ian.

Evaluating OB 1.5, so want to go to it exclusively, but mod compatiblity, stability, ability to use old missions correctly all come into the decision. Not quite there yet, but getting ever so closer. Just watching how things are panning out in general, reporting problems as I find them in OB 1.5. Still playing missions in Stable 1.216

Appreciated your video, I hadn't tried the F-15 in refueling, but you inspired me to have a go for a giggle. Three attempts, Mostly hit boom and blew up along with tanker, but I did manage to hold formation in pre contact position pretty well, but only contacted once for a second or two, only to find out I had forced unlimited fuel on in the mission, so disconnected almost instantly, damn it !!!! That was enough training for one night, will give it some more goes in the future. Can't be that hard, I can refuel in the A-10c fine ;-) Just trying to figure where boom is in relation to cockpit when behind me near the refueling recepticle (used your offsets to centre of aircraft, but may have drifted to far left), Tried watching 4 replay tracks to see externally what I was doing, when only one actually showed what happened properly. Regards, Ian.