Delta99

Your issue is likely the single sensor

Excellent!!!

Grimes, Where would be the best place to suggest a enhancement to land.getSurfaceType? With the introduction of 2.5 and trees / forests playing a much larger role in LOS etc, knowing if the land area is in a forest could be extremely useful when spawning units (ie. might not want to spawn units in the middle of the forest). I haven't done extensive testing but with some of my missions units are now spawned in a forest. I'm not sure they are able to shoot out of the forest and of course they are much harder if not impossible to find. In any event, the mission designer might want to spawn either in or out of a forest. If it is possible to determine this in the DCS engine it would be great to have such an enum returned with this function.

I think in your OnEventDead function you will have to spin through all the units to see if they are all dead.

Updated for issues that cropped up due to DCS 2.5: Changelog: V2: - updated parking spots to work better with 2.5 due to changes in ATC or parking handling or something that brought bugs into 2.5. Don't think it is fully fixed but works much better now.

Doom, you probably saw my response on Discord about this right? If you use something like AI_CAP along with AI_BALANCER the detection should work just fine. AI_BALANCER on its own with AI_PATROL I don't think does much of anything for detection and attacking the enemy.

Rassy, welcome aboard the Moose train ;)

Lots of times some of this stuff comes down to personal preference as others have said. I've used this post to make some adjustments and I also used to run with shadows off but have turned them to flat with no real performance hit that I can determine. I do like how it changes things and looks better. And I'm not one to care too much about having the best look. I'm looking for the best performance over graphics quality.

This also happens in SP

Well it seems that after 2 years and change with 2.5 this is fixed. Has anyone actually tested it yet??!!

You can do this with scripting of course if you wanted to get into that.

Thanks Grimes

Can this be done on a per mission basis by going into the .miz and finding the right spot and editing? I don’t want to change things globally just on an existing mission.

The first thing you should make sure you do is check your DCS.log file to make sure that Moose is actually loading. I bet you are missing something simple in the setup. In the log file you will see where Moose is initialized and also an indication of the version. Post that here.

If you don't normally, try starting the Oculus software before starting DCS. As another post suggested returning to the older Oculus software, I'm running the latest without problems. I do find that some games require the Oculus software running first though whereas in the past that was never required. I would just fire up any game and Oculus client would start up then the game would start up.

Great stuff just in time for it to break when 2.5 releases ;)

Yeah no worries Stonehouse. Whatever works. I just wanted to make sure that you understood how we were using Discord. Both the forums and Discord have there place.

Except Pimax can’t even do 4K so don’t count on 8K!

We use it exactly like slack. I don’t think anyone has used the voice commas all that much. Almost all the groups I am connected to use Discord just like slack with a few of the much larger ones using voice comms. Most gaming groups still stick with TS as primary though.

Will check this out soon.

I had some minor issues with autopilot as well but I think it was due to my joystick being too sensitive. Having no deadzone at all and overall being too sensitive in the middle position. Once I created a very slight deadzone and adjusted my curve a little autopilot would not drop out nearly as much and I can rely on it a lot more. Not to mention flying in general is a lot better.

You'll get a ton of more answers and likely quicker on Discord than you will here. There are usually people on either in North America or Europe so you'll like to get responses pretty quickly. At least I see a TON more discussion and quick answers there than here. We tried to organize the Discord the same as slack. Its really not much different at all except for some minor workings. I don't understand your point about text messages. I will say that in some instances forums are easier to follow etc.

Strange although it might be something odd with the scope of the trigger code with Moose or anything for that matter. What you might want to do is convert the trigger into plain Moose mission script. You can easily create menu options with Moose to do what you are doing in the ME as well to launch the way you want to. That will probably be the ticket.

Seems to me like some examples and docs are not consistent. I think the proper way is to pass the first 3 parameters as lists rather than strings even if a single element. However, when I tried your mission I did not get any errors but I didn't fly towards the zones either. But try this:

I was going to suggest that change too but then thought "nah, the . might work as well"!!!!