Hard Light Productions Forums

General FreeSpace => FreeSpace Discussion => Topic started by: Tyrian on June 27, 2006, 08:53:26 am

Title: Tech Help in Revenge FC Needed
Post by: Tyrian on June 27, 2006, 08:53:26 am
On mission 65 of the Revenge: Final Conflict campaign, I get this error:

Error: Invalid ship type.

In sexpression: ( ship-type-destroyed 60 "escape pod" )
(Error appears to be: escape pod)
File:D:\C++\Freespace\Release\fs2_open\code\Mission\MissionParse.cpp
Line: 5349
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------


I am using Kara's May 9th build when I get this error.  I also tried Kara's May 17th build, Taylor's Y-targeting bug fix build, and the 3.6.9 RC3 build.  All the errors I get reference the same escape pod, just in different forms.

Any ideas?
Title: Re: Tech Help in Revenge FC Needed
Post by: Shade on June 27, 2006, 09:51:10 am
Not familiar with the campaign, but if it's not using mods, "escape pod" should be "escapepod", with no space. Try changing that in FRED and see if it helps. If it does, it's simply a mission design problem.
Title: Re: Tech Help in Revenge FC Needed
Post by: Tyrian on June 27, 2006, 12:47:19 pm
Thanks, will try it.
Title: Re: Tech Help in Revenge FC Needed
Post by: Goober5000 on June 27, 2006, 07:27:13 pm
That's actually a bug in the SCP, not the mission.

EDIT: I just fixed it.
Title: Re: Tech Help in Revenge FC Needed
Post by: Tyrian on June 27, 2006, 08:20:07 pm
Lol, you fixed it?  I just fixed to by changing "escape pod" to "escapepod."  So which is it then?  SCP bug or Revenge FC bug?
Title: Re: Tech Help in Revenge FC Needed
Post by: Goober5000 on June 28, 2006, 01:00:30 am
I know, Shade already posted that.  As I said, it's a SCP bug.  The spelling got changed from retail when it shouldn't have.
Title: Re: Tech Help in Revenge FC Needed
Post by: Tyrian on June 28, 2006, 08:56:45 am
Ah, I see.  Well, it's fixed either way now.  Thanks for the help!