Hard Light Productions Forums
Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: DiabloRojo on June 30, 2007, 10:44:34 pm
-
First I'd just like to say how happy it makes me to find out just a couple days ago that FreeSpace is alive and well after so long.. only recently did I dust off and play through both and I'm hooked again ;) I never got Silent Threat originally, bringing me to my problem...
I tried some searches in this forum but couldn't find anything close.. though there's always a good chance I overlooked a post like "Hey DiabloRojo, here's the exact solution to your problem, ya hoser!"
I used Turey's installer (beautiful, btw) today to get everything, and all is working fine...until I got to the mission where the Krios is under attack. When the mission starts (after the 'emergency briefing' I am completely stuck, the screen, with the exception of the HUD will go black or visible almost randomly (pressing keys like targeting seems to make this happen) All wingmen (including myself!) show as dead in the HUD, and the missions scripting continues as it should. I can still target (but can't move or fire, etc) and I was able to enter cheats to kill enemy ships and complete the objectives, but can't warp because it never loads my ship.
I did some mission building back in '99 or so, though I never messed with missions that kept the previous mission's ships/loadouts/damage etc, but I'm guessing something with this function is the cause. Considering I seem to be the only one experiencing this, I doubt it's the mission file, but what else could I check to see if it isn't saving/loading my previous loadout?
I installed to a clean location and copied my retail-installed FS2 pilot over to the new location to use. That pilot was at the end of the FS2 campaign, so it loaded the final mission and it still had my loadout/etc when I initially loaded up FSOpen to check out the new visuals. Could the pilot be the issue? I do have a 'Rojo.SilentThreat.cs2' file in the data\player\single directory... Also, just in case, I downloaded and replaced the mission pack, but that didn't help. I've since replayed the previous asteroid shooting (ug) mission twice, but still have the same problem.
Thanks for any thoughts, suggestions or verbaltyped abuse!
-
oh yeah... the "cool" known (to me) RA bug
(I can only theorize on what is causing it but I guess it has something to do with the loadout saved at the last red alert and now being called on (like if the mission loads a loadout from another mod with conflicting tables or there is no saved loadout to call on at all) -- mantised this mess a year back or so, but there was no time to monitor the issue; I don't recall the bug number either)
---------------------------------------------
one simple solution (for someone expericened in basics of FS modding):
get yourself VPView and search the fs_port_mission.vp for the file callled "md-09.fs2", extract it to [fsport]/data/missions (you might need to create that folder), open it up with the editor and delete the line "+Red Alert: 1" -- this will kick out the red alert and will remove the bug
If you don't dare I can supply you with the fix if you want -- just takes one minute away from me
-
Beautiful, worked like a charm, thanks!
What a funky bug...
Only thing I can guess at is that it's trying to load an Erynies with Kaysers which doesn't exist in FSPort, since that's the last redalert my pilot went through. Fun stuff!
-
So when I open the FRED editor, where do I find the red alert line?
-
Shift + N, uncheck 'Red Alert'
-
:welcomepurple:
matthew!