Jump to content

ESAc_matador

Members
  • Posts

    1605
  • Joined

  • Last visited

Everything posted by ESAc_matador

  1. Grimes, this can this be a Mist issue?? I am having problems with this. I need that the radius of the funcion getUnitLOS is dependant on the altitude of an aircraft. local Position_vec3 = Unit.getByName('recon1'):getPoint() local _elevation = land.getHeight({x = Position_vec3.x, y = Position_vec3.z}) local _height = Position_vec3.y - _elevation _reconradius = math.sin(0.45) * _height -- this works fine so far, gives you a radius, depending on the height and an angle, simulating a Recon Camera. Estimated camera angle is about 50º so, i did Sin(25º)) the problem is that in the function mist. getUnitsLOS does not work with the variable _reconradius. I check the table and it is always empty. It seems a format problem.. Probably due to the function.... any clue?? local redunits = mist.makeUnitTable({'[red][vehicle]'}) local blueunits = mist.makeUnitTable({'recon1'}) LOSData = mist.getUnitsLOS(blueunits,2,redunits,2,_reconradius)
  2. inacurate 1º degree? for 250 km??? mmmmmm
  3. here we go. You need to install mist in the mission previously. Create a group and put in a corner... when the trigger whatsoever is ON, such group will be teleported close to your Helicopter. mist.teleportToPoint({groupName="spawnedgroupname",point=Group.getByName("helogroupname"):getUnit(1):getPosition().p,action="respawn",disperse = true,maxDisp = 50, radius = 200, innerRadius = 50, route = nil,}) disperse is an optional variable that if present each unit of the group will spawn at a random location. maxDisp is an optional variable that defines how far each unit will be from each other. radius is an optional variable that defines the max distance from the point that a group can spawn from innerRadius is an optional variable that defines the minimum distance from the point that the group can spawn from. There you go!!! (this script is easy and awesome for dynamic enviroment) You also have mist.teleportInZone('groupname',{'zonename1'.'zonename2'}, true, 200) This second function will deploy randomly the group "groupname" in a place inside "zonename1" "zonename2" triggerzones. For me it is awesome, because you can fly without knowing where the enemies are in every single mission. You just know the area, but not exact places... If you put for instance 5 triggers about 1km, radius in the area... it is impossible to expect where they are coming!!. You can also can give them a route to go to some place, by using mist.groupToRandomZone(). And you put a zone where enemies will attack, independently of where they start, they will to to a random point in such triggerzone. I made a script that makes, when a group is at 80% life, they move to a random place at 1000 m. When they are at 50% they move back... they retire from the front, and another group goes ahead, as a reserve. WOrks awesome. and it is very very dynamic enviroment. WIth DAWs you can make a dynamic campaings for a day... I am about to release it. ,) stay alert! Enjoy! PSS: I recomend to you to read, the Mist instructions and the MOOSE, they are a good complement if you want to make really good and dynamic missions.
  4. Yes, Using mist... Ill tell you in couple of hours the full script. Is quite simple...
  5. hello everyone... I have done a draft of the script, works perfect but it still not dependant on the height. I am having problems with this. local Position_vec3 = Unit.getByName('recon1'):getPoint() local _elevation = land.getHeight({x = Position_vec3.x, y = Position_vec3.z}) local _height = Position_vec3.y - _elevation _reconradius = math.sin(0.45) * _height -- this works fine so far, gives you a radius, depending on the height ( I estimate the camera angle is about 50º so, i did Sin(25º)) the problem is that in the function mist. getUnitsLOS does not work with the variable _reconradius. I check the table and it is always empty. It seems a format problem.. local redunits = mist.makeUnitTable({'[red][vehicle]'}) local blueunits = mist.makeUnitTable({'recon1'}) LOSData = mist.getUnitsLOS(blueunits,2,redunits,2,_reconradius)
  6. Not very... With the ME but one day it could be helpfull. (Navigating IFR in long hauls for instance)
  7. Actualley, i have not seen it in the game. But, since it has a radar alt, it is normal to go up and down. Another thing us that those up and downs are too pronunciated.
  8. Hello. Where can I access to the messages diaplayed during a mission. Its for a recon script flights. So, everytime a plane fly over a target it displays the lat long and the ammount and type of the group. Ao at the end of the game, i want to have access to all messages to make a report.
  9. Exactly. Combined ops are really funny, take into account that you have EWR, and really good visual and cameras.
  10. See eagle isnt for sea? Ships? I wonder... You are pretty sure? Why?
  11. poly.... Are you thinking in some kind of cockpit improve so it kills less fps? Ot it is not Gazelle's fault? I can fly it properly but there is more studdering than most other modules. Is it due that sincr you have less cockpit you are rendering more terrain? Just wonder.
  12. If you like helos then YES. It is really well done, you can do recon missions which is really funny, if you fly with other people. It is simple like UH and Mi8 so the learnimg curve is really fast. The FM has been updated and now is really funny to fly. For Recon missions I did a script were you can send aircraft to objetives you find and identify its situation. Hell, i am loving it and let me tell you that was just an impulsive purchase. I did not expect too much, but i am really happy. You can still do tranport missions (documents, officers, or even a two team special forces for jtac or recon (again check my script)
  13. With the 1.5.4 now is harder to have this problem. I am not against any help but, i am fine with the helo as it is now!! You just need to get use to it and an eye in the Instrument!. Is it due overheating or why it happens?
  14. Actually I love both!!! I find them extremely compatible... the M goes ahead looking for tanks and big targets, with the HOT, and the L goes behind covering against Infantry, small AAA with the gun. And, couple of Ka50 behind waiting for targets!!!. Also, couple of A10 for CAS, Couple of Mirages for CAP and some UH, deploying comandos to identify more targets ( with my superhyperdeeper script CAS Recon!! hahaah)
  15. I love the L version!!!!!
  16. Yes it does..
  17. Sources? I have not idea about this weapon but I guess it has a radar to detect ita altitude. So, i dont think how it can work differently...
  18. Hello !! WIth the 1.5.4 the when I put the DAWs mod, the mision editor does not work!! ooohhh!!!
  19. Hahha quite simple! Cheers!
  20. Can anyone tell me if the IFF is not working? I switch the IFF on, at the rigth panel.... and I press the nose wheel/iff but i cant see the diamond.... o the double bar in TWO mode....
  21. So I create the file and I put it in that path?? that is all?
×
×
  • Create New...