decibel_spl

I will put my $0.02 into this thread - Yes the editor is the main tool for pilots wishing to learn to fly and is where you learn to take off, land, fly and all around control of a helicopter. But, no matter how many hours on the editor a pilot might have you need experience of flying on the server 'in-situ'. I will personally put my hand up and will happily teach newer pilots how to fly on the server, given that they are willing to learn and are capable of following instruction. If anyone is reading this and want to learn to fly on the server, poke me on the ts when I'm on the server and I'll happily help you out

I agree, removing the laser designator from the UAVs would be the perfect solution to half that problem cause you gotta actually go out there with the darter or fly it out there yourself, plus the darter is rather redundant at anything over a 500m altitude (the whole point is to use it close to the ground). Leave the GBUs on the fixed wing UAVs and use it for secondary ATG bombing and reconnaissance. They can use the IDAP drones? I thought they weren't able to use them due to being a different faction :/ That's good to know.

Idk, but I think the whole point of this thread was to say (and this is just my $0.02) that UAV should not be able to call in air support. In my opinion, air support needs to be called in by forces on the ground cause a UAV sitting up at 2 clicks won't be able to determine threats and proximity of friendlies as well as a soldier on the ground. Like said before, it also would prevent the case in which the AO is the other side of the map and the UAV and jet bolt it over there and take out the AAA when a single soldier hasn't even entered the AO.... That's a bit ridiculous. For those people saying that it is half the UAV's role to call in CAS, I believe the UAV needs a rework in how it is operated - it needs to focus on supporting the ground forces by means of the UGV's, autonomous guns, intelligence and support assets. There should be some more options as to how you can do this, a reallllllly good idea would be to somehow enable the UAV op to use the new drones from the IDAP faction - medical, resupply, etc. Now that would be awesome

Trav, I understand your point and I respect your opinion. Sometimes it's not always possible to simply educate these pilots on how it should be and more often than not, the times we are complaining is when you have some idiot that wants to do it 'for the lolz' or are so ignorant and big-headed they just won't listen to suggestion and will continue to do as such. This proposed idea is my solution to the problem of the random idiot jumping in the plane and causing havoc - I have nothing against a player who is willing to learn and will happily teach them myself, although in this day and age unfortunately the idiots outweigh these people. I see that this specific idea is not liked by staff, so I will drop the suggestion - perhaps you may be able think of something better than I. I just want what's best for the majority of people. Please lock this thread, thanks

I myself have had enough of CAS: there are too many people going up in it doing whatever they want (losing it too quickly as well) and forgetting that we're playing on an infantry based server in which the CAS is a secondary role to assist the ground forces. It has been suggested and agreed upon by a lot of pilots, so therefore I am formally suggesting to staff that the CAS jets (Neophron and A-10) be whitelisted to pilots who are deemed to be capable to flying it appropriate to it's role in the server. - NB, this has nothing to do with whitelist slots and the idea of paying to use CAS This whitelisting would be done via application and decided upon by a vote of yay/nay by a group of trusted pilots who fly CAS regularly and know what they are doing. Just to name a few there's Tungsten, snaf, lazy, and tracer just to name 4. This can be done on the server and doesn't require extra time from staff determining who is and isn't capable and would require minimal work to upkeep. I myself agree with the ongoing topic of CAS requiring an overhaul and this is one small step that can improve our current situation without modifying anything too big

Nova, being good at flying cas and flying it properly to the server are two different things. I'm sure that said pilots have maturity enough to not have bias in saying whether someone shouldn't and should be allowed to fly it - I know i think every time i see a CAS pilot who adheres to the ROE, doesn't do what they want and can take out a target they should be the ones to fly it regardless whether i hate their guts or not. As to the whitelisting issue, yes ok that is problematic and can put a stop to my idea

If you knew the circumstances you would realize that it is not promoting a server for any form of gain - it is in fact a gain for the players of Strayagaming Kyroe doing this creating another avenue in which to play cooperative in a more organized fashion more in line with the intended function of ARMA other than what I&A usually pans out to be

http://steamcommunity.com/sharedfiles/filedetails/?id=1118070050 For the mods required, follow this link:

Perhaps a nice little thing which would make going to the FOB better would be once the FOB is activated, have the typical AI squads and equipment spawn there to make it feel alive. It's kinda weird when you go to the FOB when an AO is right near and there's just no one and nothing there - makes it a bit dead

As this is an issue of late, here is a list of the ROE in writing. - Classification - CAS: Close Air Support. For the purposes of I&A, CAS consists of any fixed wing or rotor propelled aircraft with primary weapons - this does not include miniguns on Ghost Hawks and other transport helos Fire Support: Fire support consists of all fixed position or mobile artillery. - The ROE - 1. CAS and Fire support CAN NOT engage ground targets without tasking by ground forces; ground forces are INFANTRY on the ground IN THE AO, the exception is the UAV operator who can designate and call in. What is tasking? This is as follows: A friendly requesting a CAS mission on a specific vehicle which can be soley identified among others A friendly clearly stating they are lasing a target from a certain cardinal direction (N, NE, E, SE, etc) and stating what the target is A friendly requesting fire support or CAS, specifing what their requested target is and giving a precise indication as to their location - grid reference, map mark or landmark CAS and Fire Support will not engage if there is any doubt friendlies could be harmed. If you wish to call in support when there are friendlies within 100m of the target, you must call "DANGER CLOSE" to indicate there is Bluefor infantry within the area. 2. The ONLY targets which CAS and Fire Support can engage at free will are as follows: AA threats - Tigri and Cheetahs only Enemy Aircraft - Attack helos and enemy jets alike Vehicles who are outside of the AO who pose minimal to no risk to friendlies i.e. outside a 2km radius of the edge of the AO Enemy Watercraft if they ARE NOT an integral part of the AO's at main or side Enemies outside a 100m radius of HQ in the case of a defense 3. For clarification, other targets CAS CAN NOT engage without tasking are: The Radio Tower Vehicles shooting at you in the CAS that ARE NOT either a Tigris or a Cheetah - if you are getting shot at by neither of these, you are too close HQ Actual Side Objective Vehicles or infantry Zues Missions

Well unfortunately, that's just the price to pay flying CAS. Contrary to popular belief, it's not as interesting as people want it to be. The amazing thing is, if people understand this post and understand that the pilot up in the most powerful tool in the game is waiting for them, they will use it and it will be interesting. Just a case of education

As this is an issue of late, here is a proposed and discussed list of the ROE in writing. - Classification - CAS: Close Air Support. For the purposes of I&A, CAS consists of any fixed wing or rotor propelled aircraft with primary weapons - this does not include miniguns on Ghost Hawks Fire Support: Fire support consists of all fixed position or mobile artillery. - The ROE - 1. CAS and Fire support CAN NOT engage ground targets without CLEAR and SPECIFIC tasking by ground forces. Ground forces are INFANTRY on the ground IN THE AO, this cannot be pilots, UAV op or other artillery roles. What is clear and specific tasking? This is as follows: A friendly requesting a CAS mission on a specific vehicle which can be soley identified among others A friendly clearly stating they are lasing a target from a certain cardinal direction (N, NE, E, SE, etc) and stating what the target is A friendly requesting fire support or CAS, specifing what their requested target is and giving a precise indication as to their location - grid reference, map mark or landmark CAS and Fire Support will not engage if there is any doubt friendlies could be harmed. If you wish to call in support when there are friendlies within 100m of the target, you must call "DANGER CLOSE" to indicate there is Bluefor infantry within the area. 2. The ONLY targets which CAS and Fire Support can engage at free will are as follows: AA threats - Tigrises and Cheetahs alike Enemy Aircraft - Attack helos and CAS jets alike Vehicles who are outside of the AO who pose minimal to no risk to ground forces - as a general guide, 2kms should be the minimum Enemy Watercraft if they ARE NOT an intergral part of the AO's at main or side 3. For clarification, other targets CAS CAN NOT engage without tasking are: The Radio Tower Vehicles shooting at you in the CAS that ARE NOT either a Tigris or a Cheetah - if you are getting shot at by niether of these, you are too close HQ Actual Side Objective Vehicles or infantry This combined with the new - Waiting for CAS slot - on the TS channel will hopefully clear any issues and improve the enjoyment of all players