F/A-18Cs don't Late Activate, v123.9871

[Wrecking Crew]

Have three groups of four F/A-18Cs that will not activate with a Late Activate setting and a trigger.

 

Instead I had to use a Delayed Start for each group.

 

I tried Late Activate with Time More, and also with Time Since Flag from a flag I set at Mission Start.

 

WC

Edited March 4, 2013 by Wrecking Crew

[BRooDJeRo]

Like in:

 

[Mission Start]Flag 1 On

[Time Since Flag 1 (120 sec)] Group Activate FA18C

 

?

[Wrecking Crew]

^^^ Yes - did not work.

 

Neither did Time Since (600). (10 minutes)

 

WC

[Grimes]

Unable to reproduce the issue. I need a little more context.

[BRooDJeRo]

Is it the same mission with the dating going red etc.?

 

Create a quickmissionfile with 1 FA18C and how you want to trigger it and attach it here when itś the 'evil-mission-that-cannot-be-shared-or-else-death-penalty/ban-for-life' one.

[Wrecking Crew]

No, different mission.

 

:-)

[Wrecking Crew]

Ya gotta wonder if my Start Time and F/A-18C no Late Activate may be issues that are carried over from earlier versions. Especially if these issues are not being duplicated with a fresh mission build on the new release.

 

WC

[Grimes]

I know you don't like to share missions, but at least attempt to create the same issue in a separate mission file that is nothing but the issue. I do basically the same thing when reporting official bugs, as it is simply more efficient and better to illustrate the isolated issue than using a full or WIP mission and saying, "check out the F-18 group activate triggers, its halfway down the list"

 

If you can't recreate it in another mission either PM me a link to the full file or delete everything but the F-18s and upload it here. Otherwise "this is broken" + short discription of what is going on without screenshots, logs, miz, or track file, makes it quite difficult to be helpful in solving the issue...

Edited March 4, 2013 by Grimes

[Wrecking Crew]

I created a new mission in v123.9871 with a F-16A at 12:0:0/0, and an F/A-18C on Late Activation with a Time More (60).

 

The F/A-18C activated as expected. So all is working on a fresh mission at the new release.

 

Grimes, I will send you a link to Bay Of Hogs that has the F/A-18C issue.

 

WC

[BRooDJeRo]

So itś safe to conclude thereś not a bug/issue with the missioneditor, but something that went wrong in missiontriggering, most likely did it yourself, perhaps without knowing and need someone else to fix someone elses mission?

 

I think you need to be in the missioncreatorscorner of this board.

[Wrecking Crew]

Most likely did it myself? Completely disagree. I don't spend all this time running down these bugs for fun - I do have better things to stay busy with.

 

Most likely a DCS compatibility issue between older missions and the latest release.

 

WC

[BRooDJeRo]

Ok, cool.

 

Prove it (miz/trk/log)

Edited March 4, 2013 by BRooDJeRo

[Grimes]

Forgot to mention in PM reply.

 

Whenever you are in doubt if a trigger is working or not, ALWAYS add a "Message to All" to the action. If the message appears but the other actions don't work, then you will know there is likely a bug. If the message doesn't appear then there is a logic error.

[Wrecking Crew]

Wow - never thought to look at that.

 

I'd discounted On Event conditions for the most part. And was completely not focused on that attribute!

 

Make sense - appreciate you running this down!

 

WC

[Wrecking Crew]

Folks - it was the Event type that was set to On Destroy, where the F/A-18Cs were being spawned - that is why it didn't work.

 

Brood - say what you want, but I've dealt with many issues in mission design since LOMAC days. Always something new to learn/realize.

 

Everyone needs to appreciate all of the time and work that goes into these missions - mine are not public missions for anyone to take and use/change.

 

WC

Edited March 5, 2013 by Wrecking Crew

[Speed]

Folks - it was the Event type that was set to On Destroy, where the F/A-18Cs were being spawned - that is why it didn't work.

 

Brood - say what you want, but I've dealt with many issues in mission design since LOMAC days. Always something new to learn/realize.

 

Everyone needs to appreciate all of the time and work that goes into these missions - mine are not public missions for anyone to take and use/change.

 

WC

 

How will anyone appreciate the amount of time and work that went into a mission if it is not public? :huh:

 

Sorry, I just don't comprehend your train of thought. It's your mission to do with as you please though :)

[Mojeaux]

How will anyone appreciate the amount of time and work that went into a mission if it is not public? :huh:

 

Sorry, I just don't comprehend your train of thought. It's your mission to do with as you please though :)

 

Yea i know the missions become an extensions of your self / our selves... But you gotta share....Hay some missions are better than others..:doh:

[BRooDJeRo]

I know exactly how long it takes to create full map size missions and what you can run into, but pls dont hate me for being honest.

 

But, i'm glad you have it fixed now. Concider yourself lucky with people like Grimes and Speed around. I already had the towell in the ring.

[Wrecking Crew]

How will anyone appreciate the amount of time and work that went into a mission if it is not public? :huh:

 

Sorry, I just don't comprehend your train of thought. It's your mission to do with as you please though :)

 

Speed,

Easy - They are hosted on two public servers.

 

WC

[Wrecking Crew]

I was really pulling my hair out yesterday - and never glanced at the Event Type on these F/A-18C triggers.

 

I think I know how it happened. When I want to create a trigger up near the top of the list I will Clone an existing trigger instead of creating a new trigger which will appear at the bottom of the list. This way I don't have to move the new trigger up - my trigger lists can be lengthy.

 

So I bet I created these F/A-18C triggers from one that had the Event Type set to On Destroy. I prolly spent two hours trying to figure it out before I posted my thread.

 

Thanks for the help. I needed a second set of eyeballs.

 

---> edit ---> I do much appreciate that my problem was found quickly.

 

WC

Edited March 5, 2013 by Wrecking Crew

[Speed]

Speed,

Easy - They are hosted on two public servers.

 

WC

Ah, well then, at least there is that. I assume then, although not stated, you are not officially sharing the missions because you want to have a competitive edge over other public servers? Or is it that you are afraid that people will modify them, and you don't like that?

 

If its the former, I understand your thinking, but I still think it's better to make high quality missions available for all. That way, you enrich the DCS community with more content. By enriching the DCS community with more content, you give people more reason to want to click on the DCS icon instead of whatever alternatives they might have had in mind instead. In the end, you get a higher number of players across all servers.

 

If it's the latter, I can't say I really understand this thinking. But hey, it's up to you... your mission will be enjoyed much less than if it was easily available, but at least some people are still able to play it. And if someone really wants it that badly, they can always join the server, leave, unzip the track, delete the extra folders, and rezip it as a .miz.

[Wrecking Crew]

Speed,

A few years ago we had a Fly-In through SimHQ.com and the 104th was kind to host the servers. We flew a bunch of 104th_Moa's missions - I'd been flying his stallturn server for a while and asked him if he and the 104th would help with the Fly-In.

 

In preparation, Moa delivered his mission briefings and contributed to the Fly-In announcement. He made it clear that his missions were his IP and so we included a copyright notice in the Fly-In announcement (I doubt that had legal standing).

 

A while after that I saw one of Moa's missions on another server and asked him if he 'allowed' that, based on what he'd told me earlier, and he said No.

 

A while after that, after I designed an extensive mission (mine are typically pretty extensive) called Thunder Of Kojori I saw that mission on another server - the title had been hacked and some of the stuff in the briefing had been changed. What else did they change? Who knows. But the mission was designed to tell a story and I did not appreciate that it had been taken w/o permission. -- I joined that server, it was open, and politely asked the admin to take it down and I never saw it hosted there again (which I much appreciated).

 

I found out that anyone joining a mission can capture it and save it for later and host it. That surprised me - I think it is a hole in the way the DCS system works and wish we could password protect missions.

 

I would just hate to find my missions on other servers where they had been changed w/o permission. That violates my sense of integrity - I would not do it to someone else's IP!

 

 

There is a question as to 'rights' - I don't think we really have legal rights to the missions we create, per the DCS license agreement. But now that DCS has partnered with 3rd party developers, who are going to charge for their software, that does lend to a 'rights' issue. Even though I am not 'selling' my missions, I want to have a right to restrict who hosts them.

 

 

Hundreds of hours go into my mission designs, and a lot of time and money goes into the servers we use to host them. My server is always open and anyone can join it to enjoy and participate in a story, and spend time with good folks. It would be disappointing to see a messed up version of a mission I designed being hosted on another server, open or locked. Even if I could password protect missions, I'd still want to host them only on servers of my choice. ***My opinion.***

 

 

It's great that folks such as Dragon like to make missions and publicly post them for others to use. And kudos for your efforts to provide the DCS community with Slmod.

 

---

 

It was prolly in the late 1990's that my squadron, the Smooth Operators Squadron, was at the Loveland Colorado airshow. We were wearing our squadron shirts which had our patch and motto - "We fly so that others may die!" So we were standing around and started talking to this guy about flight sims and he says he's a part of a squadron out of the southern U.S. and flies regularly. He says his squadron's motto is..................... "We fly so that others may die!" Well, that started a big rift on CompuServe boards to the point where the moderator was at the point to ban mottos. But we could prove that we'd been using the motto - I can clearly remember when we made it up, and we had artwork for the shirts. But we were attacked, in that on-line mottos were not IP and that we had no right to insist that it was exclusively ours. Scheesh!

 

It's all the same in my view... It's about respect for other's IP and what they wish with it.

 

 

Wrecking Crew