Delta99

It is possible this only happens on nVidia cards where I have seen it also. But on AMD i don’t think I have this issue.

Try flat shadows. At least for shadows that fluxed things for me.

This is normal for any planes spawned via scripts. In other words if it is not placed in the ME it won’t count on the debrief.

Nice work guys and a different use of Moose!!! Very cool.

This shouldn't be too difficult. You can probably easily find the centre of the zone or a random point in the zone and use that to build a waypoint. Then just wait for the aircraft to hit that waypoint OR enter that zone and do the same for the other zone. Rinse and repeat continuously.

You can’t compare Arma scripting to DCS. You can do almost anything in Arma. It’s at least 10,000 times better than DCS maybe more. Arma is in a totally different league than DCS in this area. No comparison whatsoever.

Typically you don't need to as that is what it is doing by going to its "Home" location that you designated. Unfortunately they won't shut down engines so will just sit there forever until they run out of fuel (maybe). I suppose you can stop the dispatcher but not sure that is really necessary. As I said the only way to do that RouteRTB is by spawning a new aircraft in place of the current one. So this is an ugly work-around but the only way to do it as far as I am aware.

I believe that is standard behavior for using RouteRTB. There is nothing to make a group go land at an airbase otherwise. There have been a lot of attempts to do this but none work. Airframes only like landing at their original airbase or their destination airbase that is setup in the ME.

It’s awesome. I hope to have my mission out using it at some point. But haven’t had a lot of time to work on it and finish it.

That looks correct. Did it work?

I've loaded over 1000 times minimum and I have never had a problem. Just saying!! :)

dcs.log is your friend. Get used to looking at it whenever something is not working and it will likely point you to issues like this. The last couple of errors I see posted here were straight up syntax errors that will be easy to catch in dcs.log I would think.

These are steps I wouldn't recommend. See my previous post. Much more simple than this and a lot quicker. Easier for testing etc.

You have to save the mission file typically after adding them to the trigger menu. When you update your .lua mission file, just open the trigger, reselect the file and save. Usually its pointing right at the file already.

Hoping to have some time to try this out at some point

Don't think so. The ejected pilot is not like a regular infantry unit in the game that you can pickup. This is why scripts replace that pilot with a ground unit typically.

Hopefully this will be fixed by 2020 at least. Looking forward to that year.

If you are DCS 1.5.8.x you are probably stuck with the version of Moose that is working for you. There were likely big changes that had to be made for Moose to work with DCS 2.5.x that are likely not backwards compatible to 1.5.8. I am surprised anything would work in 1.5.8. Is there a good reason you cannot update to DCS 2.5.x??

I believe this was a bug recently fixed and likely available in the development branch of Moose. This is a branch that is NOT officially released yet but you can try it at your own risk. Just make sure you can revert back to what you have now. I believe this will be released officially soon as a stable release.

FOW setting seems to work fine for me when in tactical commander position.

Thanks for posting that @Hardcard

There is with the Moose variant or at least with mortars. And I think it just uses standard DCS functionality.

OnSpawnGroup() is your friend for grabbing the group that is spawned and then you can do whatever you need with it

Thats the development branch of the documentation for MOOSE development code branch. Stuff that is not necessarily released yet. It can be used of course but you need to remember its under change until released.

If you are ok with using a scripted version that you can use in your missions and call in arty requests via F10 map menu marking then checkout what FunkyFranky developed for the MOOSE framework. I have some videos of a mission I am play testing using these features: Development documentation on the Arty Class: https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Arty.html