funkyfranky

+1

:cheer3nc: :bounce:

Well, initially I wanted to make a list/table about which DCS events are working and which are broken in either single (SP) and/or multiplayer (MP). But I just realized that I would (once again) do the ED's work (or that of their moderators, testers and the like). Events are very useful - some even vital - for creating good content for DCS. However, many bugs have been reported over the years; most of which have been flagged [REPORTED] but then silently moved to read only sections of this forum. Sometimes even with a moderator telling us that we should not raise another bug report about the same issue. Again, we, as a community have done our share by reporting the issues. And we even have been patiently waiting for fixes that never happened for years. Now, the least thing ED could do is to tell us, which bugs are known and which are going to be fixed in the no too distant futrure. Thanks ED, for helping the us to let DCS thrive by creating good missions without too much unnecessary workarounds so that you can pay your employees a good salary :)

Remove that line. Also, if you start the range after 19 sec, the script will not detect you entering an aircraft (hence not create the F10 menu) if you do that before. You need to wait at least 20 sec or change the trigger condition to a shorter time. Furthermore, in single player, always hit ESC twice before you enter a slot. Sorry, many DCS bugs when trying to detect a player entered a unit need to be circumvented :( I wish they would fix it as this is a very important event as you can see...

It actually destroys mission on ALL maps!

Any feedback on this? This is a very critical issue as it prohibits dynamical spawning at airbases.

For Jean Airport the function :getDesc() returns nil. Similar for :getPosition(). This is for DCS version 2.5.6.43931.

Sounds a bit like an old bug back? I mean this one https://forums.eagle.ru/showthread.php?t=193363 Anyway, it would be nice if there were a smooth (linear) transition between the altitudes of two waypoints.

Mission is working like a charm now in DCS 2.5.6 :thumbup: Looks like carrier ops are coming together nicely. Thanks!

Issue is fixed in DCS 2.5.6 with additional "airborne" parameter in the mission task [1]. Thanks :thumbup:

That is great! I still cannot quite believe that this is working now, but it does. Thank you and kudos to ED :thumbup:

It is the airbase ID that is ****ed up in DCS 2.5.6. Providing the airbase:getID() value to the airdromeID field of the spawn template causes the aircraft to explode.

Moose is using the enumerators not the IDs. Still each event that occurs is processed and needs to be defined in Moose.

For me, they want to drive through the buildings but get stuck. Maybe this is what you meant, too? Because, e.g., the Abrams in your first pic does not look like it's getting back on its feet ;)

I would not say "through" but rather "into" unfortunately. Some more examples I captured recently attached. I makes missions, which rely on a rather "simple" task where the group is supposed to go from A to B and arrive at B very difficult. Needless to say (I hope) that this is a very common thing in practice.

Cheers, mate :thumbup:

Anyone got insides as to what the above warning message in the DCS log file means exactly? Task "XXX" could not be executed and is still existing? Task was executed and is still existing? Anything else? Thanks!

Lol, yeah :) BTW, I ran the mission a couple of times now. There were also cases where I did not see the engagement stop within any reasonable time frame. Just FYI! I think this is a very tricky one. The info about skill level of excellent is already quite helpful. I did not know this before.

Thanks a lot for investigating into this and talking to the team, BN :thumbup: I just tried it out. Setting the groups to excellent indeed makes the battle a lot longer. But eventually, the engagement did stop. Please find attached an example mission which generates an endless battle between (excellent) infantry groups. Note that it is sometimes necessary to run it up to 5h or more (in accellerated time). Hope it helps :) WHS - 180 - Capture Zone Infantry Excellent.miz

+1

The strange thing is that the lion share of the work has already been done by ED. People who don't own the module will not be able to use it properly. Why it is now such a big thing to allow everyone to place a bloody icon on the map and have a carrier in the mission, which can only be used by people who bought it, is beyond me. Or, in other words, disabling all the goodies puts the SC more on the side of a module rather than on the side of an "asset pack". I have not heard any good argument, why the SC is on the asset pack side. It seems more like a "we can't explain it, but it is what is is". Anyway, I'm looking very much forward to the SC. Still, I dislike how things are developing...

I have seen this as well. Was on the Caucasus map actually so it is not only Nellis. It happened when I assigned a specific parking spot (i.e. not "auto") at the landing waypoint. Interestingly, it happend only for specific aircraft types.

:thumbup: Good decision!

Might not really help you Snoopy - sorry, but that feature is working fine here with my Reverb.

Ah, sorry to hear that. However, the method I suggested works. I use it like this all the time as I simply cannot be bothered to create dozens of triggers for each mission ;) Check out some of my ATIS example missions. Files are at an arbitrary folder inside the miz.