Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: JoeLo on June 12, 2005, 05:06:28 pm
-
Could some one convert this mission http://www.sectorgame.com/goober/ross128.html it is goober's Ross 128 mission.
-
Convert to what? FS2?
To be honest even if it wasn't his mission I'd say that Goober is the most qualified to do that anyway :D
-
Goober had trouble converting it on his own. He would have to re-build the entire thing from scratch...
-
Hehe. :)
Converting it is on my list of stuff to do, but I want to do two things first:
1) Roll out the Port v3.0
2) Fix the FRED converter (it takes forever)
EDIT: Hippo, I don't recall having trouble converting it, other than the fact that it takes nearly an hour.
-
Originally posted by Goober5000
2. Fix the FRED converter (it takes forever)
EDIT: Hippo, I don't recall having trouble converting it, other than the fact that it takes nearly an hour.
hell yeah, although it takes longer for me. I was converting that Ross 128 mission, then i had to leave for about an hour and a half, and when i came back, it wasn't even done, and FRED_Open had frozen. :(
-
Hmmm as long as its on your list thats cool. I can't get it to work with my copy of freespace the game crashes every time. Is there something special you have to do other than unzip the VP into the main directory?
-
strange... I thought there was some weird effect with send-message and nearly every other event not being recognised... Or maybe that was the FS1 version... :nervous:
-
That's all you have to do.
I'm wondering if it crashes due to a conflict between the regular FS1 and the FS1 OEM versions.
-
possibly, but then why did the FoW set I tested work?
-
or it could be a misuse of the vp. i didn't just plop the vp in, i just put the files in their proper folders. :)
of course, Goob's idea is good, too. :D
-
Okay, try this, just to see if it works. Plop the VP in the main directory, and then put this file in the tables directory. Then try the mission again.
-
My table! *takes it back*
;) :p
-
*watches another magically reappear*
-
Hm... I'll take two :nervous:
-
haha. must be cookie based. :p
-
What is this FRED_Open converter thingy?
-
I took a look through the Ross128 pack some time ago, and noticed that it included another model... a planet model I think. Would the model need to be converted any for it to be compatible with FS2?
-
Yes, but we're not using it with FS2 at the moment.
-
I still get this error
Error: Argument count is illegal.
In sexpression: ( send-message )
(Error appears to be: send-message)
File:D:\PROJECTS\FREESPACE\Mission\MissionParse.cpp
Line: 3245
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
-
looks like an invalid message.
-
There's nothing wrong with the mission - it plays perfectly fine on my computer and on other people's computers. But some people have reported crashes like this.
Maybe different versions of FS1 have different sexp limits? :confused: What happens if you use this EXE (http://fs2source.warpcore.org/temp/FSP3.zip)?
-
AUGH! I figured out what the problem is. :rolleyes: Karajorma's going to love this.
Simple fix for the bug: Drop the attached campaign file in the missions folder and play it via the campaign room instead of the tech room. (I'll upload a revised VP to the website shortly.)
Simple explanation of the bug: The game was running out of sexp nodes.
More complicated explanation: As with most ugly bugs, the symptom looked rather different than the root cause. And the worst thing is that it happened to some people but not others. The reason is that sexp nodes are shared between campaigns and missions. If you have a complicated campaign in memory, it may not leave enough sexp nodes for the mission. Playing the mission via a campaign ensures that the mission starts with a known number of free sexp nodes.
If I didn't have the source code on hand, I would have never figured this out. :p
-
That's a rather interesting bug. :)
I might have problems with it but the one who's really going to get screwed by this one is ShadowWolf's Mercs campaign.
-
Hmmm now I get this error
Error: Couldn't open mission 'Ross128.fsm'
File:D:\PROJECTS\FREESPACE\Mission\MissionParse.cpp
Line: 3440
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
Could it be that I am running the Euro version Conflict Freespace?
-
Hrm. Open the campaign file and rename "Ross128.fsm" to "FOW-Ross128.fsm". :)