Rivvern

I'm still struggling getting this to work. Is it really possible to get this to work without cas flights engaging eachother? Whats wrong with my mission? https://dl.dropboxusercontent.com/u/16996823/2014/MA_BASE%20v0.108_CAP.miz

I cant seem to move this darn thing! Ive edited the following file but i notice no difference. "Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\declare_kneeboard_device.lua"

Have the same thing. I really need to move it to another location on the screen. Is it possible to change position like the other viewports?

For those of you who are interested in AAR (air-to-air refueling), Taproot has made an excellent guide. Here it is: We are looking for Swedish members! If you are interested please register on the forum and join us! http://www.masterarms.se

Im just checking if you have any time to look at the script this weekend SNAFU. No hurry though.. Just planning next weeks squadnight if i will be able to have the script in the mission or not.

Copy that SNAFU. What i would like is to have CAP flights patroling inside the zone and as soon radar detects enemies over the border or inside capzone they will engage targets. Otherwise they should ignore enemy flights. That would open up possibility to create exciting covert strikes inside enemy territory.

No they are still turning north and engages the enemy cap... hmm. I attached the .miz in the previous post if someone want to have a look.

Roger that. Will try.

Im trying to set up a base mission to be used for trainings and scenarios. I do have some problems with the CAP flights. They dont stay within their capszones and they engage eachother almost immediatly. I have moved their zones furher back but no noticable difference. Have i done anything wrong? This is what it looks like. local numberofredcapzones = 2 --input of numbers of defined CAP zones for Red side local numberofbluecapzones = 2 --input of numbers of defined CAP zones for Blue side local numberofredCAPgroups = 2 --input of numbers of defined CAPs for red side local numberofblueCAPgroups = 2 --input of numbers of defined CAPs blue red side local redCAPzone = 'redcapzone' --Triggerzones defining the Red CAP area have to be name according to 'redCAPzone1', 'redCAPzone2',...'redCAPzone[numberofredcapzones] local blueCAPzone = 'bluecapzone' --Triggerzones defining the Blue CAP area have to be name according to 'blueCAPzone1', 'blueCAPzone2',...'blueCAPzone[numberofbluecapzones] local redborderlineunitname = 'redborder' -- Name of group which waypoints define the red border local blueborderlineunitname = 'blueborder' -- Name of group which waypoints define the blue border taskingintervall = 300 -- Time intervall in which ongoing intercepts are renewed --names of red interceptorbases local redAF = {} redAF[1] = {name = 'Beslan'} --Exact name of airfield with the triggerzone of the same name between 'xxx' redAF[2] = {name = 'Nalchik'} --Exact name of airfield with the triggerzone of the same name between 'xxx' redAF[3] = {name = 'Sochi-Adler'} --Exact name of airfield with the triggerzone of the same name between 'xxx' --names of blue interceptorbases local blueAF = {} blueAF[1] = {name = 'Batumi'} --Exact name of airfield with the triggerzone of the same name between 'xxx' blueAF[2]= {name = 'Kutaisi'} --Exact name of airfield with the triggerzone of the same name between 'xxx' blueAF[3]= {name = 'Vaziani'} --Exact name of airfield with the triggerzone of the same name between 'xxx' debuggingmessages = TRUE -- set to true if tracking messages shall be printed env.setErrorMessageBoxEnabled(false) --set to false if debugging message box, shall not be shown in game debuggingside = 'blue' -- set side for which tracking messages shall be printed Missionfile: https://dl.dropboxusercontent.com/u/16996823/2014/MA_BASE%20v0.106_CAP.miz

This is very helpful. Id like to create some kneeboards myself. Where can i find info about this Kneeboard folder?

Just tried it out really quick. Awesome i must say! Works right out of the box! I can see many possible features for this. Keep it up. Will follow this thread.

Please tell me how i do that. Unchecking "Comm" in editor doesnt seem to help. AFAIK its not possible in FC3. It work. Clientside only. :/ Im happy as long as i dont hear the ATC spam.

I deleted the ATC files in DCS World\Sounds\Speech\Sound\***\ATC. Works for me.

Thanks HiJack. What about deleting the ATC sound files? Would that work? Thats "client side" though. Best would be if it could be disabled in the mission or on the server.

Is there any way of disabling the ATC in missions (or mods maybe)? We have been flying FC3 quite a bit lately and the ATC is just so annoying. Id actually would like to have it removed completely from DCS: World until a new system is released.

I get same problem on 1.2.7.23803. Workaround is to set the aircraft to "Takeoff from parking" .

Yeah me too. Got em all. The A10c is waaay to cheap. Everyone with a joystick should buy it. ASAP.

I can't say what your problem is but I can confirm that running without Aero cuts the frame rate pretty hard. What if you load another simple profile in helios?

Happy bus failed with 1.2.7. Chinooks halted. Ranger I sent you a mail with the track. Keep up the good work! Lets hope this mission breaking madness ends!

I think the tanker is bugged in this version. Can someone confirm?

I tried an usb-adapter. Deltaco i believe. It wasn't able to render any advanced games.

Very good suggestion. They could also redo all keybinds as well. Like all aircrafts have the same keys for "open canopy/door", "chat window" and all other similar functions.

DragonShadow: If i edit the names of the aircrafts, will that mess up the trigger system?

Really entertaining mission. Ran it twice today! Thumbs up!

Thanks!