[Cyker]

Just played it, excellent campaign! 

Those bits with the blackouts are definitely creepy.
Haven't played a space-sim with such atmosphere (haha) since TIE Fighter!

Great stuff

[dyndak]

When i try to launch the first mission i have a message: "Attempt to load the mission failed". What am I doing wrong???

[karajorma]

Does that error message say anything else apart from that rather obvious sentence? If so post it too.

[dyndak]

It's all right now. I just downloaded newer build of SCP. Sorry for problem.

[Qwer]

Error: Can't open file <starfield.pof>
File:E:\Languages\Visual Studio Projects\Visual C++\fs2_open\code\Model\ModelRead.cpp
Line: 1679
[This filename points to the location of a file on the computer that built this executable]

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


 

[Ransom]

Hmm, I thought FS ignored the skybox model entry if it couldn't find the file. That's why I left the file out of the VP, so people could choose to have the new starfield or not.

For now though I'll put the model here (goes in your /models folder), I'll update the VP with it later.

[Qwer]

Thanks, it's working perfectly now.

[Cobra]

wow, 6 or 7 months after the release and people are still raving over it.

[neoterran]

I only just found out about it 2 days ago, (and the SCP about a week ago) and it's consumed all my free time since then. So Awesome !

[The Spac]

Review

Spoiler:

I found the story to be quite unique to a freespace campaign but I found the missions quite repedative, except for the start and end. I dislike being stuck in 1 ship for 40 missions, but I am glad I wasn't stuck in a FS1 ship at least. The presentation was quite high which also matters, and the transcendant voice effects were top notch. Considering this was a solo effort? I have to say it was well done, and can only imagine what would happen if Ransom was in some sort of team project.

Score: 7/10

[Frankie]

Using various 3.6.x Taylor builds for OSX, and various downloads of Transcend (with or without patch files), I consistently get the following error while trying to load Transcend mission #4:

Error: Unrecognized operator.
In sexpression: ( when
   ( has-arrived-delay 0 "Capricorn" )
   ( send-message-list
      "Omicron 2"
      "High"
      "Omicron2_3"
      0
      "Omicron 1"
File: /code/mission/missionparse.cpp
Line 5313

BTW, the following lines are:

    "High"
    "Omicron_4"
    5000

which is where I think the problem occurs. Omicron_4 is a ship reference, but should be a message reference (e.g. Omicron_4_1). However, lacking Fred for OSX I am unable to repair the problem. Manually editing the VP results in other mysterious errors, presumably I'm screwing up a length counter or offset pointer.

[karajorma]

I took a look at the mission. It never mentions Omicron 4 in my version at all.

Maybe I'm looking at an older version or something. Can you post the whole error exactly as it appears on screen?

[Fenrir]

I have the same error using the 4/12 build. I'd use the Debug build if it would work, but it doesn't recognize the flag file. It came with a map file, so maybe this'll be helpful enough:


Error: Unrecognized operator.

In sexpression: ( when
   ( has-arrived-delay 0 "Capricorn" )
   ( send-message-list
      "Omicron 2"
      "High"
      "Omicron2_3"
      0
      "Omicron 1"
      "High"
      "Omicron_4"
      5000
      "Omicron 2"
      "High"
      "Omicron2_4"
      5000
      "Omicron 1"
      "High"
      "Omicron1_5"
      5000
      "Omicron 3"
      "High"
      "Omicron3_2"
      5000
   )
   ( clear-goals "Omicron 1" )
   ( add-goal
      "Omicron 1"
      ( ai-chase-any-except
         89
         "Varcent"
         "Raven"
      )
   )
   ( add-goal
      "Omicron 2"
      ( ai-chase-any-except
         89
         "Varcent"
         "Raven"
      )
   )
   ( add-goal
      "Omicron 3"
      ( ai-chase-any-except
         89
         "Varcent"
         "Raven"
      )
   )
)
(Error appears to be: ai-chase-any-except)
File:C:\projects\fs2_open\code\Mission\MissionParse.cpp
Line: 5328
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    20060412-fs2_open_r.exe 0041495c()
    20060412-fs2_open_r.exe 0041564e()
    20060412-fs2_open_r.exe 0051bf46()
    20060412-fs2_open_r.exe 0040227f()
    20060412-fs2_open_r.exe 00408c86()
    20060412-fs2_open_r.exe 0050110e()
    20060412-fs2_open_r.exe 00407c22()
    20060412-fs2_open_r.exe 00501401()
    20060412-fs2_open_r.exe 0040a3b1()
    20060412-fs2_open_r.exe 0040a4e6()
    20060412-fs2_open_r.exe 006a6872()
    kernel32.dll 7c816d4f()
------------------------------------------------------------------

[karajorma]

Hmmmmm. This could be a problem. Goober edited the SEXPs and removed chase-any-except.

The best solution is for RA to edit and reupload the entire campaign, releasing any missions that use ai-chase-any-except as a patch. Otherwise we're going to see this one turn up a lot.

Here's the thread covering the actual problem.

[Ferret]

Um. Can I ask WHY an entire SEXP was removed?

[karajorma]

Goober explained on that thread.

[Ferret]

But but.. It could break so much, okay it didn't work right, but you could stick that on the in-FRED description.
Why not just leave it there for compatability reasons? Totally pulling it out is just silly.

[karajorma]

It's a fairly new SEXP. It's not going to break any missions and the assumption was that nothing had been released which did use it. Turns out that was wrong which is why I said it could become a problem.

[Ferret]

You should know full well that the second you add something to FSO someone uses to straight away.

[karajorma]

Use it yes. Release it no.

The belief was that the only missions which used it would still be under development and could be fixed quickly without affecting anyone other than a few FREDders.