Zayets

Small question, although the answer can be very well "in progress". Flying the Harrier, do I have the channels for landing AWLS in Persian Gulf? Ta

Best news! :punk:

Thank you for confirming. I have tried with the workaround and it works now as expected. Basically the only sequence I was able to make it work was this: - STRS page select - AG mode on - Select AGM - select sensors aft TV (DMT must be ON otherwise it does not lock for me) - lock ground - slew over target - uncage AGM - DMT off - sensors FWD IRMV - TDC down until lock confirmed - fire away

Just updated to the latest one few minutes ago and noticed sensors IRMV not working (used to work in the previous version). Can anyone check this and let me know? Don't want to put this in the bug thread because maybe something was changed in how the sensors are employed. Can't select sensors FWD even if Maverick D is uncaged. Attached, my test mission, see if it works for you. I am running the latest and newest open beta, no mods test.miz

Thanks for confirming :thumbup:

That makes sense. Tested it and it works as expected. Saved a lot of debug and reading and I thank you for this. One small question, adding a Harrier on Tarawa will not allow me to get into the cockpit. As soon as I move it to an airfield I can jump on cockpit. I have changed it to Client from Player and when jumping in the slot says flight is not ready. Checked Tarawa stores and seen that it has unlimited ammo and planes. Also times when these spawn (carrier and planes are identical). Is it a glitch or something I done wrong?

I am trying to schedule a function through mist but no matter what I do I can't get this one firing. When I simply call the function it works a charm but it does not look to be scheduled to fire every 30 seconds. Is there any changes in OpenBeta? function broadcast_message() local msg = {} msg.text = 'Regular broadcast function' msg.displayTime = 10 msg.msgFor = {coa={'all'}} mist.message.add(msg) env.info("broadcast function ends") mist.scheduleFunction(broadcast_message,{},timer.getAbsTime() + 30, 30, timer.getTime() + 3600) end broadcast_message() -- only this one is firing once Took out the mist.scheduleFunction from the body and calling it like do mist.scheduleFunction(broadcast_message,{},timer.getAbsTime() + 30, 30, timer.getTime() + 3600) end Still nothing. Any clues?

I believe this is a long time request since FC3 (or maybe even Lock On). Probably in works, hopefully. It helps a lot. Someone made a (quite complicated) hack in the sense that you had to have like 2 sessions opened so that you can see in real time how the objects look on the terrain but not on the map.

Ah, my bad. Didn't read carefully the request. It is following between coalitions. Indeed, Follow is not possible

You can simply set a plane to escort your flight. In the advanced waypoint you can assign the task Follow to the flight you want to follow you. Not sure if this works only for groups having CAP mission or not though. Here's a mission I made for SU-33, jump in it and wait to see the second group (which takes off before you) joining on your group. I am using this mission as a campaign start. SU-33-0-1.miz

As per above, it looks this works only with ground vehicles (and offline only). I remember I did this trick before for aircrafs : in front of the aircraft place a Humvee having one waypoint which just to free the taxi path for that particular aircraft once it moves. Now, you can make this visible before start as it is a ground vehicle. Then set a flag to activate it once a certain condition is true. The Humvee will move aside and the aircraft can taxi. There is one small drawback to this for AI planes : they will start their engines and they will obviously consume some fuel until they move. But other than that, it should work.

Why don't you use Late Activation and tick the box Visible before start?

I just deleted the Huey group from the mission and all is good. Just to recap what I did, I had initially added a Chinook pair to land at point for 5 minutes and then changed my mind (as USMC is not known for their Chinooks) and switched them with Hueys, same waypoints and tasks. Then it crashed exactly at the same point everytime. Which means I can't give team a log after cleanup and that would probably mislead investigations. If you can get something out of the log I sent, that would be a bonus , if not then also good, thank you for checking nevertheless.

Thanks for the answer. I don't use mods as I prefer vanilla DCS especially when building missions for everyone to use.

First solid crash on 2.5.0 for me. I had crashes during the years but I was expecting them in a way. This time is on a fairly easy mission I made, no big stuffs. My system is pretty much high end : i7 8th gen, 32 GB RAM , 1080Ti, all SSD and M.2 (in fact DCS is installed on its own 512GB M.2 disk ). It crashed while looking through F2 at one Huey. For what is worth, attached is the crash dump (running open beta). BTW, the crash is consistent, mission crashes everytime there. dcs.log-20180423-002454.zip

You can use mist.groupToRandomPoint function from MIST to actually create a route to a a given point. If you add a radius when calling the function then the destination would be a random point in that particular zone (basically a circle with having the center the point you have given initially).

Did not want to stir you up and I apologize if you feel I have anything against your proposed solution. I was just suggesting the fact that while you may know the headings of the player's plane you can't know the relative position to the carrier by checking if the aircraft enters a moving zone attached to the carrier itself. It would work on stationary carrier/airfield but not when it's moving. If there was a trigger checking bearing limits (just like heading) relative to other unit then all this stuff would have worked like a breeze. That it from me.

The zone is attached to the moving object, the object being the center of the zone. You may have the flags checked for condition but if you decide to abort the landing after the flags are set then the logic is not going to work. If you ask me, the best thing to do it is to add a continuous function (see MIST) checking the position of (every) aircraft coming to landing on the carrier. You will still use a moving zone (although this is not mandatory) with this but it will be cleaner. It maybe possible to make it work with triggers only but you must make them continuous and that means extra processing power. If you have a good rig then it may be ok. If not then, well, scripting is still king.

Trouble with that is that the zone is a circular one so basically when you enter the circular area having the carrier as center (no matter from which direction, that can be head on) the the call the ball will be triggered. There's some fine tuning to this in the sense that you must know the relative position of your aircraft to the carrier and that must be from the aft.

I like this idea, I will try to see if moving zone works for this type of scenario.:pilotfly:

Viggen I can understand but isn't the Harrier able to land anywhere there is a small patch levelled out, like a FARP? Don't get me wrong, this is something I want for a long time in the game but there is something that you should take into consideration if you want 100% realism : civilian traffic. You can turn this one off to make sure you are not hindered in any way when you land your Viggen (or any aircraft) on a stretch of road. I believe any civ traffic passes through your aircraft like nothing happens (maybe that's changed since). The best approach for the moment, IMHO, is to continue and develop the grass airfields as you can place these anywhere there's some flat terrain. Tried some FARP at the side of the road (you only have to be near it for rearm, no necessarily ON it) and could not refuel my Mustang unfortunately. Also, on inbound call they tell me to seek alternate landing point :)

Wanted to ask this question for a long time but was too busy playing DCS (yeah, Open Beta). So, is there any (significant) advantage, behaviour in AI if there is an AWACS present in the mission? Does the AI is smart enough to (for example) keep his radar/comms off and rely on AWACS completely? Same with the recon on the ground when AI is tasked to do some ground damage, is the precision affected in any way? I know ED is busy to deliver some kick @$$ AI in 2.5 release, just wanted to know if some of these are taken into consideration because it will totally change the game. Literally.

You will need to make use of events in the beginning of your mission. In this case S_EVENT_HIT. Basically, you will need to create a short script and running it in the beginning of the mission. You will have to provide a list of all MEDEVAC in that script. I haven't wrote a script in months but your script should look like that: Apologies for the sloppy script, I am at work and I can't spend lot of time on this. I will try to come later with something better but if you know programming then you will pick this up very fast and make your own script.

I own everything (to my recollection) from what ED sells under DCS and that includes NTTR as well. But what I have said was this: I had no previous versions or modules installed. NTTR is sold as a module.

I am not 100% sure vanilla 2.5 OB is 100 GB in download. I THINK that when I started install it said that it will download somewhere around 25 GB, Mind you, this a clean install of 2.5 OB what I did, I had no previous versions or modules installed.