[Spoon]

After saving the mission and reopening it, every waypoint gets duplicated and FRED starts complaining there are objects with the same name.
When deleting all paths and creating new ones, it assigns random numbers (1, 3 then U1) and on saving it says path 5:4 is not linked to any object (despite no path with that name being present in the first place). aka, its a huge mess.
I'm now using 5566 and it works fine with that build. 

[portej05]

An issue was fixed recently that caused FS2 not to read waypoints correctly due to some buggy warp code (WTF!) in some circumstances.

This has probably had a knock on effect.

Kara?

[Goober5000]

Why are you asking for karajorma when you know I was the one who changed the waypoint code?

[chief1983]

Cause you're busy rewriting the installer/launcher? 

[karajorma]

Why are you asking for karajorma when you know I was the one who changed the waypoint code?

I was wondering the same thing.

[Zacam]

So, did un-linking the Waypoint processing from ai_process cause this, or some other fluke?

Also, was this on a Regular, Debug or one of the SSE flavors?

[portej05]

Why are you asking for karajorma when you know I was the one who changed the waypoint code?

Because you said that you were going to be busy over the next week! Sorry!

Fixed:
Kara? Goob?

(this is another reason for my posting in: wxFRED and all that jazz
regarding the massive coupling between FRED2 and FSO).

[Spoon]

Also, was this on a Regular, Debug or one of the SSE flavors?

I tried both SSE2 and Regular

[Goober5000]

Cause you're busy rewriting the installer/launcher? 

1) I took a break from the installer and launcher to fix the waypoint bug;
2) People should fix the bugs they create.

So, did un-linking the Waypoint processing from ai_process cause this, or some other fluke?

Both I'm guessing.

Because you said that you were going to be busy over the next week! Sorry!

Doesn't mean I can't make time to look at it.