[Legate Damar]

Starting Wing '
' has more than 'MAX_WING_SLOTS' ships

ntdll.dll! KiFastSystemCallRet
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! Warning + 430 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! ss_init_wing_info + 337 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! ship_select_init_team_data + 184 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! ship_select_common_init + 115 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! common_select_init + 254 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! brief_init + 529 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! game_enter_state + 661 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! game_process_event + 318 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! game_main + 782 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! WinMain + 330 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_14_RC5_DEBUG_NO-SSE.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

[headdie]

debug log would be more useful to be sure but I, would go with you have more than 4 ships in a wing that the player would normally be able to change the loadout of, Alpha, Beta, etc.

[Legate Damar]

All of the 3 custom named starting wings have only 4 ships (2 of them have multiple waves, though)



[attachment deleted by a ninja]

[headdie]

taking them back down to a single wave would be my first step and seeing if that resolves the problem.

[Legate Damar]

That didn't seem to do anything

EDIT: I had an idea of what might have been wrong, I had a wing of 6 enemy ships and the table entry for those ships had the "player ship" flag, I figured that might be causing the problem so I removed it from the table, but I'm still getting the error. I'm stumped.

[headdie]

Player Ship shouldn't affect it, the flag deals with if the player can use the ship or not.

I have been experimenting to reproduce this and the only way I have been able to manage it is by assigning more than 4 ships to Alpha, Beta or Gamma (as their default names)

[Crybertrance]

EDIT: I had an idea of what might have been wrong, I had a wing of 6 enemy ships and the table entry for those ships had the "player ship" flag, I figured that might be causing the problem so I removed it from the table, but I'm still getting the error. I'm stumped.

In my experience albeit small of FRED, I've had multiple six-craft enemy wings in a mission, and didn't receive any errors whatsoever. Are, you sure there are no (even enemies, just to be sure) wings with more than 4 ships? Maybe a stray SEXP or something?!?

[headdie]

A wing can have 6 ships in it unless its is Alpha, Beta, Gamma (Delta might come under this I cant remember) which are limited to a maximum of 4 due to things like interface art, though waves can still be specified for any wing the player is not part of.

[Legate Damar]

The only wing in the mission with more than 4 ships is the enemy wing.

BTW I am using custom starting wing names, if that's relevant.

[headdie]

very strange.  No changing the names shouldn't cause an issue, all you are doing is changing the names of the wings reserved for the player squadron.

post the mission file and I will open it and see what is going off.

[Legate Damar]

I will PM it to you if you promise not to reveal any of the spoilers in it to anyone

[headdie]

Yer, no problem, all secrets are safe.

[Legate Damar]

Okay I sent it

[Crybertrance]

BTW, I would request you to reveal the problem and solution in the most spoiler-free way publicly, to help fellow newbie modders. Like myself... 

[Legate Damar]

I will once headdie gets back to me

[FreeSpaceFreak]

Hm, yeah, I've seen this one as well... It appears to have suddenly started popping up in RC5, on missions that older builds didn't have a problem with. Haven't tried RC6 yet.

[Legate Damar]

I am using RC5 so that could be the problem

[Goober5000]

Use RC6.

If the problem still exists, then open a Mantis bug, mark it as private, attach the mission, and assign it to me.  I'll take a look at it.

[headdie]

Looking through the file I cant see an issue with it so I would follow Goober's suggestion

[Legate Damar]

Oddly enough I switched to RC6 yet I'm still getting the warning.

Still if it doesn't seem to actually affect anything in the mission and the only way to actually be aware of it when playing is to use the debug build, I guess I can just ignore it... right?