Zayets

Right. Out of curiosity I hooked 4xADM-141 on the cat just to see how SAM's reacts after I dropped them. And it was a pretty sight I must say. However, I noticed that these are super high drag stuff. Max speed attained was 370-400kts level flight at 20k with a high nose down tendency. Took me full burner from the runway to lift the kite into the air. Not to mention full flaps. Can anyone confirm this?

I have a 42 inch 4k monitor and planes are very hard to spot anyway.

This is not really hard to simulate as basically any AI plane carrying bombs can be thought as a drone. I see what you mean and I agree hat visually is not what you expect. Nevertheless, you can use a trigger in ME so that when a Predator reaches an area then a bomb explodes at the given coordinates. I think that's a good compromise.

I am not really sure is the patch of today which causes it.

Same here. went with GYRO to drop some AUTO Mk82 at 300FT spacing after waiting 10 mins without QUAL-OK. 8xMK82 were spread across Nevada from Tonopa to Groom Lake. Unbelievable how a proper INS align affects A/G weapon deployment. I presume this is how it should work IRL. No ranging TACAN and so on. Well, back to F-14 then.

Whatever was done, I can't use a single dollar for any module, being old or new. A big fat 0% discount is written for all modules I try to buy. I picked a rather old one, A10C. Not much joy. Again, I don't have much points (36) but this would probably halve the amount to pay for one aircraft. Never understood this system and probably I would never be able to.

One more thing, don’t bother too much eith it. Pick the default dds, smudge a bit around decals , give it a general look to resemble your skin and be on your way up in the air Sent from my iPhone using Tapatalk

Lod file is used when you see the aircraft from distance. I assume the reason would be so that game engine won’t have to load the whole gig of dds file at such distance. Because you won’t see much anyway, that is. Sent from my iPhone using Tapatalk

Used photoshop online to convert all dds from the Maverick&Goose helmets skin (basically the 201 livery default) into png and from there on I created my own templates. They are primitive and in no way good to be used generally but for the moment they do their job. There's one LOD file which needs a bit of fiddling but I am not too woried about. It only affects the livery when you see the plane from far away. In any case, I ended with almost 800Mb in size. Probably the official paint kit will be even bigger, who knows.

I think he means modern usage of a drone this days, like instruct them to bomb stuff and things like that.

Noticed that lately myself. But this is not really something I hate. If you don't announce your intention to refuel, the baskets are retracted. I am not sure how realistic is that, but I like it more than before.

I have noticed this few months ago but I thought it will be fixed or someone else will report it. Well, it may be a bug, reported or not but I will post it here anyway because my search didn't come up with anything useful so far. So basically what happens is that if you assign a frequency (to let's say a HMWWE) and add a sound to play as "Transmit Message" in the Adwanced WP Actions (usually a Morse code but that can be basically anything, I remember people doing Huey missions with continuous emitting radio stations ) then it works like a charm. Or does it? As soon as another sound plays then if you are tuned to that particular frequency then transmission stops. And no, the sound produced does not happen on the same frequency. Say that I am tuned into such frequency station from an emitting vehicle and I am listening to its transmission then as soon as I call (again few examples) the ATC for inbound or I request flight check in then previous transmission stops. Again, I am not sure if this is reported or not, feel free to delete the post if that's the case.

I have spent some $1000 on ED online products (that's it, does not include boxed editions of LOMAC, FC, A10C or BS which I bought probably three times over during the confusion years). I won't even think of gear or rigs needed to play the game somehow decent. I am on this journey with them from at least 2005 (and I am not including Flanker days here). If this is not loyalty, I am not sure what it is. I don't have bonus point, well maybe few but I never benefited from them and did not care about them too much. Even the announcement for changing the bonus system didn't actually make me twitch or make me very excited. Until I read the word "loyalty". And that, my ED friends, supposed to mean something. Not sure it has the same meaning today. Look, I thank you for all your work, it gave me countless hours of joy. But it is not like this was an one sided affair, I did my share as well. Your news were disappointing, for me at least. Hope others will have better luck. I will still remain the same loyal customer, you can rest assured. I am just writing this for others to see it and make sure they hold buying products until the new system gets in place. Have a great weekend.

Is that the first MiG-29 kill by an F-14?

This is looking very, very nice.:thumbup:

It does not really have a tail. You basically shoot through it's body. Kill the engines.

I don't think that's an option in ME. The IP wants an AI unit to actually start firing on a location marked by him/her and not on a preset location given prior the mission in ME. Of course this is possible using scripting. The simplest way is to create a F10 menu entry which calls function fireAtPoint on the exact position the player find itself. You need to do these steps: - create a menu entry calling a function, say fireAtMyLocation. - create function fireAtMyLocation which when F10 menu is called, will calculate your position and call fireAtPoint in which you will pass the calcuated position. It is not dead easy but also not very complicated to do exactly that. What's not easy is to actually calculate where your smoke will actually hit the ground so that you can use it for position. But there are workarounds for that as well.

Setting up TACAN on the initial waypoint always works for me. What does not always work is activating TACAN using simulation script engine.

Thanks Grimes. Very strange as I have yet another set of zones which are not indexed numerically yet the result of #table is correct. I will switch to zonesByNum, see what gives. Most probably it will work.

Hi Grimes, Not sure why this stuff is not working anymore. See the snippet below local zonesClone = mist.utils.deepCopy(mist.DBs.zonesByName) env.info('mistDBZone size = ' .. #mist.DBs.zonesByName) env.info('cloneZone size = ' .. #zonesClone) Both of them return 0. I am loading mist at time 1 second and this script at 10 seconds after. When I dump DB's I see all zones in the dump file. Funny stuff is that in another script I made they work just fine.

What happens if you change the interval to 1 second instead to 0.25? Also, try to run your function into a do - end block function HVTLASE() local jtac = Unit.getByName('HVT_JTAC') local target = Unit.getByName('HVT'):getPoint() local ray = Spot.createLaser(jtac, {x = 0, y = 2000, z = 0}, target, 1113) end do LASE = mist.scheduleFunction( HVTLASE, {}, timer.getTime(), 1 ) end Another alternative would be to push a lasing task for a (invincible and invisible) shadowing unit and see if that's better. Also, I can't find Spot.createLaser function, I see only Spot.createInfraRed. Is that a new function because I can't see it in the SSE documentation.

Yeah, tasking on the respawned units sometimes sub par. They do what's expected quite often for me. One thing I do myself is to use dynAdd instead of respawn. It is the same approach, have a late activated group and then use dynAdd. This function is more to my liking as I can modify the route on the fly. It does take more coding but it (almost) never fails.

I just took your script from the DO SCRIPT trigger action and created a new file which I loaded 5 seconds after mission starts with DO SCRIPT FILE. So basically it is exactly as you wrote it. If you want to see the file you will have to unzip ReSpawn Yes.miz and then simply look into the folder for it.

There you go, mate. I took your script and loaded it after mist was loading. It should work now. ReSpawn Test.miz

Question, can you output the value of v.ID ? By the looks of it it returns the group ID and not the name of the group. I haven't checked the mission yet