Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: McMad on May 13, 2008, 03:39:23 pm
-
I'm not sure if this is the right place for this but never mind:
I've been trying out some player made campaigns recently, but in two of them I've run across this problem :mad:. It's like I've got my HUD but no ship. I can target and all that but I can't move, jump out or do anything. External view doesn't show anything and the enemy just ignore me.
Any help would be appreciated. Just say if you need more information.
-
:welcomeblue:
(dunno if you've been beamed yet, but what the heck)
Well, was there anything wierd with the loadout/ ship selection?
-
There was nothing weird on the load out because they are both red alert missions. I should of noticed that before. :nervous:
-
At this point it seems like some specs could be useful. So,
- FS2 or FSO?
- If FSO, how did you install it?
- Furthermore, if FSO, what build?
- What mods?
- Have you been switching between mods with the same pilot file?
-
Ok:
FSO :yes:
I instaled it with T's Installer (and I downloaded blue planet myself).
Says 3_6_9
Sync and Blue planet
No. The blue planet one isn't even a clone.
Hope that helps.
-
Hmm. No ideas so far. Though I have this feeling I've seen an issue like this somewhere... I'll try to scour through the forums.
Edit: Actually. What missions does this occur in?
-
First, he said he gets it in Red-Alert missions. (ring a bell) Second, he said in several campaigns, which leads me to think pilot corruption.
McMad, try to create a new pilot. If it doesn't work, get a 3.6.10 build, preferably this (http://www.freespacefaq.com/Misc-Downloads/Builds/Is-Player-Build.7z) one, of the 3/14 Xt build.
-
First, he said he gets it in Red-Alert missions. (ring a bell) Second, he said in several campaigns, which leads me to think pilot corruption.
McMad, try to create a new pilot. If it doesn't work, get a 3.6.10 build, preferably this (http://www.freespacefaq.com/Misc-Downloads/Builds/Is-Player-Build.7z) one, of the 3/14 Xt build.
Well the pilot for blue planet is actually brand new so I'll try the other build.
Edit: Actually. What missions does this occur in?
I don't know how to get the mission name when I can't get a briefing or debriefing.
-
From the normal hud view, does everything look correct? Can you see other ships? Is the background messed up?
If you can't see other ships and the background looks messed up, then I would think that you are experiencing the same bug that I experienced at one point. I think that using a newer build fixed it though.
-
I tried the other build but that made it even worse. It messed up the instruments as well.
From the normal hud view, does everything look correct? Can you see other ships? Is the background messed up?
If you can't see other ships and the background looks messed up, then I would think that you are experiencing the same bug that I experienced at one point. I think that using a newer build fixed it though.
I can see everything normally unless I press the afterburner, then the screen goes white. Is there a newer one to the one I'm using?
-
What GPU and graphics drivers are you using? Have you tried running debug builds?
-
When I run a Debug build with Sync:
There are a lot at the start and when I start the mission (all about fighters and missles):
Warning: Unable to find a sufficient number of bitmaps for this mission's background. The background will not be displayed.
File:J:\src\cvs\fs2_open_3_6_9.final\code\Starfield\StarField.cpp
Line: 3396
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
parse_bitmaps() parse_mission() parse_main() mission_load() game_start_mission() game_enter_state() gameseq_set_state() game_process_event() gameseq_process_events() game_main() WinMain() WinMainCRTStartup() kernel32.dll 76974911()
ntdll.dll 7781e4b6()
ntdll.dll 7781e489()
------------------------------------------------------------------
The mission then starts and crashes instantly.
Anyway I'm now fairly sure that the problem is caused by the game thinking I have no ship :mad:
-
Not sure if this is related to the bug but... where have you installed FSO?
-
Turey's installer.
-
Not how, my good man. Where?
-
:eek: I'm loosing It!!! :eek:
Just in the normal freespace 2 directory. (On a vista)
And while I remember, I have been able to play through other campaigns such as Derelict without any problems.
-
Thank you. That's what I was after. Something like C:\Games\Freespace2 is good. But having it on the desktop or My Documents is a no-no.
But this seems really weird. Did I understand correctly that, after using Turey's Installer, the only thing you've done to your FSO was to install Blue Planet?
-
I am certain that I didn't install anything before sync got the bug :mad:.
I am almost certain that I have instaled nothing but blue planet since that when wrong :mad:.
I have since instaled whatshisname's nebula pack and an earlier version of the SCP in order to try and fix it (it hasn't helped :mad:). I am going to install inferno.
-
To where did you install Blue Planet? Did you make a new folder inside your FS2 folder, or just dump everything into C:\Games\FreeSpace2\?
-
In a new folder, like the instructions said:
C:\Games\FreeSpace2\blueplanet
It goes wrong on the mission after the one where the catch up with the duke. The one where the two unknown fighters from the sanctuary pop up.
-
I can't think of anything. Try a different build.
-
Like?
-
http://www.hard-light.net/forums/index.php/board,97.0.html
-
Instead of throwing a pile o' stuff at you, I for one would like to present a single option: 20071028T (http://fs2source.warpcore.org/exes/latest/taylor/20071028-win32.rar). I've had good results with it. And in your case, it can't hurt to try.
-
Try either of the ones in my sig. The first one is the best one I've found.
-
I can shed light on this problem.
It's an error from the arrival cue in the mission. I've noticed it in Sync and Transcend, but not Blue Planet. It appears to be confined to 3.6.9. Simple solution: Use a 3.6.10 build.
I believe it is related to the whole host of issues 3.6.9 has with red alert missions. To my knowledge it has not been Mantis'ed, but it also does not appear in 3.6.10 builds.
3.6.7 does not experience the bug. 3.6.9 does. 3.6.10 does not.
A new pilot file will not resolve the issue in general.
-
Thanks for the info.
Is there any way to skip levels. I can't face playing through the first levels of Blueplanet again :sigh:
-
Just try a 3.6.10 build first. If no luck, then create a new pilot and start over. The usual way to "skip" a mission is to fail it five times in a row. Or you could fiddle up a modified campaign file where the campaign starts from a later mission. And, that's about it. Unless you want to use the Mission Simulator and the key combination Ctrl + Shift + S, but that would really ruin the feeling.
-
Thanks for the info.
Is there any way to skip levels. I can't face playing through the first levels of Blueplanet again :sigh:
You don't need to, unless you deleted your pilot.
Simply download a 3.6.10 build, dump it into your FS folder, select it in the launcher, and run with it. Pilots can be used interchangeably with more recent builds, it's just reverting back that can be problematic.
That said, I've been using the same pilot in all the 3.6.10 builds with nary an issue.
-
This poor guy, you've all been asking him random totally unrelated questions when it's a common red alert bug... all he needs is the latest build
-
This poor guy, you've all been asking him random totally unrelated questions when it's a common red alert bug... all he needs is the latest build
And what exactly did you do to help? At least we tried. And now the issue is solved. Touché.
Also, for the record, I've had abso-****ing-lutely no red-alert issues with 3.6.9. Well, apart from Homesick, but that, as we know it, is another story.
-
I thought that it was a Red-Alert bug from the start.
-
This poor guy, you've all been asking him random totally unrelated questions when it's a common red alert bug... all he needs is the latest build
Yeh, shame it doesn't work though. None of the 3_9_10 builds I have tried have worked. When I run in debug with them they make no complaints until the problem should happen, then they crash.
-
You can also fix the problem by simply editing the mission in question to get rid of the red-alert.
(I had this very problem in Sync - I got into the mission and had the hud but absolutely nothing else - just black, endless black.
If that's the problem you had.)
-
You can also fix the problem by simply editing the mission in question to get rid of the red-alert.
(I had this very problem in Sync - I got into the mission and had the hud but absolutely nothing else - just black, endless black.
If that's the problem you had.)
I'm having the same problem with Procyon Insurgency, HUD visible everything else blacked out! :(
I've tried newer builds (3.6.10), but it didn't help. I'll have try again with another pilot but I'm not sure it will work. And some of those missions are long and tortuous! :sigh:
-
AFAIK, it shouldn't happen in 3.6.10. You may need to try a new pilot file if it is happening - its possible that encountering the bug has totally muffed your pilot in the first place.
Also, as someone else mentioned, you can delete the red alert flag.
If you can get it to happen reproducibly in a recent 3.6.10 build (e.g. one from May) with a new pilot file, then this should be Mantis'ed. Like I said, I haven't run into it in 3.6.10 so I'm going to venture a guess your pilot is hosed and its not a simple matter of a build upgrade with an exisiting pilot but rather a build upgrade and a new pilot.
-
Well, I did make a new build 10 pilot earlier and had the problem, but I couldn't tell you if it was before may. Anyway, how do you remove a red alert flag? I don't know how you get at the FRED file from the .vp
-
Anyway, how do you remove a red alert flag? I don't know how you get at the FRED file from the .vp
Get VPView (http://www.descent-network.com/cgi-bin/descman.cgi?module=vpview) and extract the necessary mission file(s) from the vp. Next, open the extracted mission file(s) with Notepad. If there is a line that says:
+Red Alert: 1
, set it to
+Red Alert: 0
or just remove the whole line. Save, and place the modified mission file to \freespace\data\missions or \freespace\modname\data\missions (create the folders if/when necessary).
-
I can't find anything saying red alert in the file. Is there anything else it could be?
I would have thought it would be round here somewere:
+Game Type Flags: 1
+Flags: 327808
+Disallow Support: 1
+Hull Repair Ceiling: 0.000000
+Subsystem Repair Ceiling: 100.000000
+Viewer pos: 11997.007813, 8896.418945, -3212.658936
+Viewer orient:
0.013894, 0.000001, 0.999903,
-0.372030, 0.928206, 0.005169,
-0.928117, -0.372066, 0.012897
N.B. I did find the level name, whover it was who wanted to know: "Frankenstein's Monsters"
-
If it is a red-alert mission, the red-alert flag should be there. Use the search function of Notepad (Ctrl-F) and look for the word "alert".
-
If it is a red-alert mission, the red-alert flag should be there. Use the search function of Notepad (Ctrl-F) and look for the word "alert".
I know, that's what I did. It only finds Alpha 1's "red-alert-carry" tag.
EDIT: I just changed it for sync, and that now works. But I still can't find it in BP.
-
The red-alert-carry SExp means that it carries the stats from one half of a Red-Alert mission to the other.
-
Anyway it's no longer an issue. I removed the no red alert patch for BP, used the new build and the mission worked! :) :D :cool: Interestingly, the duke was missing as well as me before.
Thanks for all the help. :yes: