LFCChameleon_Silk

there is no way you died from something at that range and the only thing that could have engaged you would be something radar guided (if really at that range) you probably got killed by something in underneath you that you just didn't see. I know my threat envelopes... just ask youself this, when a hellfire is fired from an apache, do they do it on the move? do they do it while a T-90 fires back at them... no of course not because the weapon system is designed to kill from outside their envelope and the Vikhr is no different in that regard. apples and oranges i suppose though since they are vastly different AT weapons... but you guys kinda disappoint me by not taking a basic rule into account that you should only enter threat range as last ditch effort -- i'm afraid many will read that as that they should be flying 4km running in blasting Vikhrs but i think that is an absolutely fool hardy strategy. I mean this is basic ground attack theory and to suggest otherwise undermines intelligent conversation. Why do people assume something without testing for themselves, on editor excellent T-90 AI threat envelop is 5km exactly now watch what happens when i enter 5km in this video. http://www.twitch.tv/land_force/c/4553581 so I will hear no more of a T-90 shooting at over 5km, its just a downed pilots memoir.

no worries, I didn't base my changes off yours cause i came across the official one first, i didn't find this thread until i actually started to use the 3rd party scripts in my mission. Tested my changes and they do take off great and work fine, although BARO would be better waypoint then RADIO for sure. and while i am very novice at scripting to add this fix was extremley easy to see and find it took me only a few minutes to realize how to fix it and required no testing before implementing the change. When i make further edits (which i'm sure i will) i will definetly share my changes with this thread... ultimatley i would like to have SNAFU implement all changes and fixes we come up with to the script for future users. as for anything i script myself I always leave it open to modification as well provided credit is given to original author (much like this script) unfortunately until I get a few more issues solved I can't release my latest version of my missionfile... its been weeks since i updated Operation Perched Eagle (v2.16) and I'm testing a lot before pushing out and publishing (v2.50) I learned my lesson releasing something too soon (with good intentions of wanting to share my work) but i fear now that so many ppl ran broken versions of OPE that they maybe reluctant to try out the latest (even tho it should be the most polished and working of all the versions) anyways I will keep plugging away at these scripts sometime tmrw

umm ShuRugal, vikhrs outdistance ANYTHING a T-90 has, and i routinely kill things without ever being shot at online or offline so not really sure what you mean by easy prey... any fighter who spots you and worth a damn is gonna kill you since you literally have nothing to fight back with. staying out of weapon engagement envelopes when flying is always the way, be it in a su-25 or a ka50, they can't shoot you unless you give them a shot. I'll be the first to say that hotdogs flying ka50 5 feet off the ground in videos without APs on and using cannon on manpads who shoot 15 missiles and miss by 2 inches looks really rad, but besides killing a couple men and smacking the bottom of the helo off the ground about all they accomplished was some bad "pro" flying that got them killled in a fireball from a bad situation turned worse by absolutely no understanding of threat envelopes...no survivability with their tactics despite how "good" they think they can handle the helo. FYI 8.5km stationary shots are money in the bank -- not even radar sams have a chance since i can use the vertical space to hide behind a hill if it does happen to fire at me, hows a T-90's svir ATGM gonna hit me past 5km.... Then again maybe i fly the helo different then everyone else but i have easily the best K/D ratio while flying it since its virtually untouchable from anything except aircraft. sure if your 4.5km from a T-90 you might want to launch the vikhr on the run, but then again you probably shouldn't be worrying about shooting it so much as you are about getting out of dodge.

Sapphire 270X 2GB 14.6 drivers barely ever below 30 fps with highs of 70ish (but this vastly depends on mission and amount of units)

decemeber 25th, i had to I just had to add a mysterious date in there, although i debated on september 11th i figured that joke wouldn't fly so well with so many patriots :P

I'm using Mbots script in my mission, quite awesome just be careful of pouncing on an OSA or something, it will go active inside threat! having said that though absolutely terrific that you can now surprise convoys etc.

i think the real question is HOW much wind, its measured in meters per second and i think ppl are using some really insane wind settings when they do add wind and turbulence. forward momentum is always good for rockets or vikhrs it will help to give better range and delivery but i think firing from a hover is much better and easier to do (maybe not with rockets) as for auto turn to target, try it with no wind you will be amazed at how well it turns to target, now add some wind, look it struggles using AP to get it right almost as though it is putting it right but the wind is throwing it off... amazing eh? I would say auto turn to target is very reliant on your ability to trim and the outside conditions.

on another note: did anybody get the CAP to engage player planes yet?

----------------------------------------------function to spawn CAP function spawnCAP(color) local CAPside = color [b] local _definealt = 0[/b] --XX new variable to hold altitude if Spawnmode == "parking" then RNW_type = "TakeOffParking" RNW_action = "From Parking Area" [b]_definealt = 0[/b] [b]-- ADD THIS SO ITS SET TO 0 IF TAKING OFF[/b] elseif spawnmode == "takeoff" then RNW_type = "TakeOff" RNW_action = "From Runway" [b]_definealt = 0[/b] [b]-- ADD THIS SO ITS SET TO 0 IF TAKING OFF[/b] elseif spawnmode == "air" then RNW_type = "Turning Point" RNW_action = "Turning Point" [b] _definealt = 3000[/b] [b]-- SET TO DESIRED AIRBORNE SPAWNHEIGHT[/b] end CAPPatrolunitstable = { [1] = { ["alt"] = [b]_definealt, -- CHANGE HERE TO NEW VARIABLE[/b] ["heading"] = 0, ["livery_id"] = CAPplaneskin, ["type"] = CAPplanetype, ["psi"] = 0, ["onboard_num"] = "10", ["parking"] = 1, ["y"] = actualCAPairfieldposz, ["x"] = actualCAPairfieldposx, ["name"] = CAPgroupname.." #1", ["payload"] = CAPpayload, ["speed"] = 200, ["unitId"] = math.random(9999,99999), ["alt_type"] = "RADIO", ["skill"] = "Random", }, -- end of [1] [2] = { ["alt"] = [b]_definealt, -- CHANGE HERE TO NEW VARIABLE[/b] ["heading"] = 0, ["livery_id"] = CAPplaneskin, ["type"] = CAPplanetype, ["psi"] = 0, ["onboard_num"] = "10", ["parking"] = 2, ["y"] = actualCAPairfieldposz, ["x"] = actualCAPairfieldposx+50, ["name"] = CAPgroupname.." #2", ["payload"] = CAPpayload, ["speed"] = 200, ["unitId"] = math.random(9999,99999), ["alt_type"] = "RADIO", ["skill"] = "Random", }, } elseif strengthrandomizer == 2 then CAPPatrolunitstable = { [1] = { ["alt"] = [b]_definealt, -- CHANGE HERE TO NEW VARIABLE[/b] ["heading"] = 0, ["livery_id"] = CAPplaneskin, ["type"] = CAPplanetype, ["psi"] = 0, ["onboard_num"] = "10", ["parking"] = 1, ["y"] = actualCAPairfieldposz, ["x"] = actualCAPairfieldposx, ["name"] = CAPgroupname.." #1", ["payload"] = CAPpayload, ["speed"] = 200, ["unitId"] = math.random(9999,99999), ["alt_type"] = "RADIO", ["skill"] = "Random", }, -- end of [1] [2] = { ["alt"] = [b]_definealt, -- CHANGE HERE TO NEW VARIABLE[/b] ["heading"] = 0, ["livery_id"] = CAPplaneskin, ["type"] = CAPplanetype, ["psi"] = 0, ["onboard_num"] = "10", ["parking"] = 2, ["y"] = actualCAPairfieldposz, ["x"] = actualCAPairfieldposx+50, ["name"] = CAPgroupname.." #2", ["payload"] = CAPpayload, ["speed"] = 200, ["unitId"] = math.random(9999,99999), ["alt_type"] = "RADIO", ["skill"] = "Random", }, [3] = { ["alt"] = [b]_definealt, -- CHANGE HERE TO NEW VARIABLE[/b] ["heading"] = 0, ["livery_id"] = CAPplaneskin, ["type"] = CAPplanetype, ["psi"] = 0, ["onboard_num"] = "10", ["parking"] = 3, ["y"] = actualCAPairfieldposz+50, ["x"] = actualCAPairfieldposx, ["name"] = CAPgroupname.." #3", ["payload"] = CAPpayload, ["speed"] = 200, ["unitId"] = math.random(9999,99999), ["alt_type"] = "RADIO", ["skill"] = "Random", }, -- end of [1] [4] = { ["alt"] = [b]_definealt, -- CHANGE HERE TO NEW VARIABLE[/b] ["heading"] = 0, ["livery_id"] = CAPplaneskin, ["type"] = CAPplanetype, ["psi"] = 0, ["onboard_num"] = "10", ["parking"] = 4, ["y"] = actualCAPairfieldposz+50, ["x"] = actualCAPairfieldposx+50, ["name"] = CAPgroupname.." #4", ["payload"] = CAPpayload, ["speed"] = 200, ["unitId"] = math.random(9999,99999), ["alt_type"] = "RADIO", ["skill"] = "Random", }, } end --Debug("debuggingmessage stuck at spawnCAP point 3: counter:"..string.format(counter).."/ side: "..CAPside, CAPside) local CAPdata = { ["modulation"] = 0, ["tasks"] = { }, -- end of ["tasks"] ["task"] = "CAP", ["uncontrolled"] = false, ["route"] = { ["points"] = CAPPatrolpointstable, }, -- end of ["route"] ["groupId"] = math.random(10000,99999), ["hidden"] = false, ["units"] = CAPPatrolunitstable, ["y"] = actualCAPairfieldposz, ["x"] = actualCAPairfieldposx, ["name"] = CAPgroupname, ["communication"] = true, ["start_time"] = 0, ["frequency"] = 124, } coalition.addGroup(CAPcountry, Group.Category.AIRPLANE, CAPdata) actualCAPtable[CAPside][#actualCAPtable[CAPside]+1] = { groupname = CAPgroupname, group = Group.getByName(CAPgroupname), unit1 = Unit.getByName(CAPgroupname.." #1"), unit1name = CAPgroupname.." #1", unit2 = Unit.getByName(CAPgroupname.." #2"), unit2name = CAPgroupname.." #2", CAPzone = actualCAPzone, status = "enroute to station" } actualCAPtableTable = mist.utils.tableShow(actualCAPtable[CAPside]) Debug(CAPside.." actualCAPtable: " ..actualCAPtableTable, CAPside) return actualCAPtable[CAPside] end Keep in mind i have an interest in modifying and working on this script further since i need it for my missionfile (which is currently up and running great with some new improvements) I may build a much more sophisticated plane selector so that it can be used to spawn *ANY* kind of plane or to set it into a WW2 mode etc. time will tell... but i think you will find my edit quite helpful. also: I'm a novice too but this is one of the best ways to learn (off of someone elses script) so keep plugging away at it guys.

good news guys, i have fixed the not spawning on the ground and using airbases problem... gonna look into it some more and see what else i can fix up.

yea what a complete farce to have gift monies expire... thats like gift cards that expire (which are illegal in Canada)

you can descend and scan from outer edge with eyeball and ascend once you have the spot, in the A-10 you can't really do this since its a pain to climb up again but the su-25T can do it no sweat.

so many people so eager, I AM ONE OF THESE PEOPLE :) can't wait to fly the MiG-21

I think mainly web designers would care about inspect element etc or if you were unsure that something fishy was going on behind the scenes of a website... besides until recently you would have had to check the source and couldn't just inspect a web element, this is a new feature that came about like last couple years with firefox and chrome (about the only real innovation in web browsing!) and who says half these people memorized anything they could be playing game mode with labels for all you know, i know lots of people who think they can fly because they can drop a laser guided bomb but would die to a second shilka since they can't jink and have no concept of threat envelopes. I'm not so easily fooled into believing everyone in the community knows what they are doing.

I immediately thought about fake screenshots when i seen this thread but they must have a way of checking that its genuine, although its probably time consuming.

thanks i will check it out Stonehouse

theres something you must realize 238thFalcon just because i add 50 slots into the mission is to not limit the player (to much) in terms of selection so that they can fly what they wish to fly in my mission, I would never set my server for 50 ppl, i usually limit to 8 or 12 slots, so you can clearly see you would never have 50 planes airborne at once. I also limit tankovys only to red side since 12 were created makes little sense to give blue such a limited quantity aircraft and helps force players to try and balance out blue and red a bit... what i hate is how i have ground attack mission and everyone jumps in the 2 F-15s and goes and trolls red teams ground attack -- no one ever jumps into a red CAP role unless its as a response to F-15C trolling... for this reason alone when MiG-21 is released i will be creating a different variant of Operation Perched Eagle with just MiG-21's for blue and red - and that will take over the player CAP for balancing reasons. probably call it Operation Perched Balalaika :P on another note, it seems that only 1 percent of people flying actually have half a clue as to what they are doing -- i can count on my hands how many people i know that actually know how to jink or understand ground attack at all... and this is just the basic stuffs.. nevermind how to read a VVI, HSI or anything else that isn't ripple firing 8 AMRAAMs at RMAX. its a running joke with the people in my circle when some unknown guy joins the server, on teamspeak we begin taking bets how long it will be before the player has died message appears or they just taxi into the grass and leave.... now don't mistake this for me being cold to new comers, I often help new pilots and show them the ropes but unfortunately I can't actually take the controls for them or make them understand the theory of flight faster then they can absorb it themselves. back on topic though, I design every task to be possible to complete with a single aircraft in 1 sortie if done perfectly and a maximum of 2 if done sloppy, obviously with a wingman it becomes much easier to complete a task -- in this regard i agree with you fully, there are times I try other peoples stuff (that had a crappier designer then me) and i see missing bullseye information, no way to see the bulls, radio is full of bullseye calls, no waypointing for su-25s (like they don't fly the plane and therefore don't realize how or why to waypoint), unrealistic expectations of an aircraft capability... a great example of this was a training mission surrounded by radar sams and I'm in a grach and its like proceed to the range for practice... couldn't even get anywhere near my weapons envelope without a hail of SAMS... thats just the worst designed training mission i have ever seen and its quite common for ppl to give me a grach slot and then expect me to fire rockets at 20 km.. aka ain't gonna happen. the bottom line is its up to the community to not run such poorly created / designed missions and I'm not trying to hate on anybodys work but if it sucks it sucks don't shoot the messenger.

i have issues with having dynamically created reinforcements being able to capture my zones that are setup with MIST, but no one has any answers for me :( but as Stonehouse said - I'm beginner but that won't stop me from sharing anything I've learned or created for the sake of helping others and the community.

anytime man, make sure you give me a link to your mission so i can test it out myself and see how it develops, or better yet the server your hosting it at -- you can also dissect anything from my mission: Operation Perched Eagle, I'd be lying if I said it had advanced scripting in it but you will find examples of a lot of working MIST functions without the elegance of other scripts written by other people (sometimes the elegance really makes scripts hard to follow whats occuring) its not well documented (if at all) but you may recognize mist functions easy enough.

np i think you will find that part of the script works wonders for fixing radio command issues, remember that you can build a lot of the flag throwing right into the script itself and also have it run a function and output text to players etc, this is how i built my task system.

if you guys cant load a track in the mission editor, make sure you go to the bottom right and change to show file extensions from .miz to .trk the editing to a zip and removing files etc predates DCS world and i believe was a lock on 2 thing (although can't verify if thats really the case)

nah your not really understanding what i mean, there is a portion of the CTTS script and many other scripts where radio commands are given out to the players based on an table of unit names at the top of the script, the radio commands are then linked to a function that is run elsewhere in the script (if your doing a lot of trigger based stuff in the ME then you can simply make a function that sets a flag - here here is a working example. (although i admit i did not test this prior to posting) MIST has nothing to do with the radio adding this way. -- Radio add example -- ------------------------------- -- INIT VALUES FOR FIRST RUN -- ------------------------------- radiotable_red = {} radiotable_blue = {} local rradiotext1 = "Example red radio text" local bradiotext1 = "Example blue radio text" -- add for which group names you want to get the radio red_radio = { "Su-25 Russian #000", blue_radio = { "Su-25 American #000", ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function addradio_red(arg, time) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ for i=1,#red_radio do AddRadioMenu_red(red_radio[i]) end return time + 5 end --- ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function addradio_blue(arg, time) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ for i=1,#blue_radio do AddRadioMenu_blue(blue_radio[i]) end return time + 5 end --- ------------------------------------------------------------------------------------------------------------ ------------------------------------------ RADIO COMMAND ADD ---------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function AddRadioMenu_red(unitName) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ if radiotable_red[unitName] == nil then local unit = Unit.getByName(unitName) if unit == nil then return end local group = unit:getGroup() if group == nil then return end radiogid = group:getID() missionCommands.addCommandForGroup(radiogid, rradiotext1, nil, example_function_to_run_for_red, unitName) radiotable_red[unitName] = true end end --- ------------------------------------------------------------------------------------------------------------ ------------------------------------------ RADIO COMMAND ADD ---------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function AddRadioMenu_blue(unitName) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ if radiotable_blue[unitName] == nil then local unit = Unit.getByName(unitName) if unit == nil then return end local group = unit:getGroup() if group == nil then return end radiogid = group:getID() missionCommands.addCommandForGroup(radiogid, bradiotext1, nil, example_function_to_run_for_blue, unitName) end end --- ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function example_function_to_run_for_blue() ------------------------------------------------------------------------------------------------------------------------------------------------------------------ trigger.action.setUserFlag(1, 1) -- set a flag when radio command used return end --- ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function example_function_to_run_for_red() ------------------------------------------------------------------------------------------------------------------------------------------------------------------ trigger.action.setUserFlag(2, 1) -- set a flag when radio command used return end --- ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function recheck_red() ------------------------------------------------------------------------------------------------------------------------------------------------------------------ for i=1,#red_radio do local unitName = red_radio[i] local unit = Unit.getByName(unitName) if unit == nil then local playerName = unit:getPlayerName() end end timer.scheduleFunction(recheck_red, nil, timer.getTime() + 2) return end --- ------------------------------------------------------------------------------------------------------------------------------------------------------------------ function recheck_blue() ------------------------------------------------------------------------------------------------------------------------------------------------------------------ for i=1,#blue_radio do local unitName = blue_radio[i] local unit = Unit.getByName(unitName) if unit == nil then local playerName = unit:getPlayerName() end end timer.scheduleFunction(recheck_blue, nil, timer.getTime() + 2) return end --- timer.scheduleFunction(addradio_blue, nil, timer.getTime() + 5) timer.scheduleFunction(addradio_red, nil, timer.getTime() + 5) timer.scheduleFunction(recheck_red, nil, timer.getTime() + 2) timer.scheduleFunction(recheck_blue, nil, timer.getTime() + 2) its actually a good idea to run seperate scripts as seperate files that way if one fails the rest of your mission keeps working (or should) you can "do script" a MIST function as long as the mission has mist loading at the start and then the trigger thats doing the do script is delayed by a few seconds of mission time. adding radio items this way actually solves a problem it doesn't create one and it will never fail to work, the script is not complex and is very simple and if this failed then ED would have some big problems with the scripting engine on their hands. also about you init question dooom, you can init a script not just at the bottom of the ME trigger window, it only needs to be loaded for access to its functions to be available so if you made a trigger that on the 33rd second loaded mist, you would be able to use its functions after 33 seconds and this could be done with a trigger with do script file or do script with the entire contents of MIST in it (once they fix the cutoff bug of do script)

using the ingame triggers to give radio has this behaviour however if you use the radio adding part such as from the CTTS script then you will circumvent this issue. as far as i can tell this bug was also present in 1.2.7 possibly previous versions as well (i never reported i just assumed such an obvious bug was noted already)

unless your running a recording studio the really whats the point of an expansion card all the heavy lifting gets offloaded to the cpu regardless so anything about fps being improved could only ever be the slightest improvement. having said that i still dislike anything onboard or integrated (a ritual/grudge that i must hold on to after all those crappy SiS chipsets i had to deal with troubleshooting problems on computers owned by friends)

it will be out on the 4th with a fresh june newsletter and 1.2.9. ok so i'm kidding but at the same time ------- PLEASE, PRETTY PLEASE!!! cherry on top!