Hard Light Productions Forums

Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: 666maslo666 on February 09, 2013, 05:27:40 pm

Title: Bug with has-arrived-delay and starting wing names
Post by: 666maslo666 on February 09, 2013, 05:27:40 pm

I cannot get Beta wing to arrive later in my mission. If I set its arrival cue with has-arrived-delay with enemy cruiser as an argument, it never arrives. If I rename it to something other than Beta, the arrival cue suddenly works. The worst part is that the problem does not always appear - I have managed to get it working by deleting and exactly recreating the wing, but it stopped working again after a while..   :doubt: Since the bug is hard to recreate, the mission is attached.

[attachment deleted by a basterd]

Title: Re: Bug with has-arrived-delay and starting wing names
Post by: 666maslo666 on February 20, 2013, 12:25:18 pm

So, anyone tried to test the attached mission to confirm the bug?

Title: Re: Bug with has-arrived-delay and starting wing names
Post by: Yarn on February 20, 2013, 03:54:43 pm

Check the ship selection screen (in the game, not FRED). Is Beta wing assigned any ships? I'm guessing not.

Title: Re: Bug with has-arrived-delay and starting wing names
Post by: 666maslo666 on February 21, 2013, 08:10:50 am

Quote from: Yarn on February 20, 2013, 03:54:43 pm

Check the ship selection screen (in the game, not FRED). Is Beta wing assigned any ships? I'm guessing not.

Yes it is, and now when I downloaded the mission it suddenly works again even though I am sure it was the buggy mission that I uploaded... :/ Why is this happening?

Title: Re: Bug with has-arrived-delay and starting wing names
Post by: karajorma on February 21, 2013, 09:21:09 pm

Your PC doesn't like you?

Weird bugs are a common occurrence during mission design unfortunately. Sometimes they indicate an issue with the engine which won't resurface again for years.