[Buckshee Rounds]

Hiya hard light. I've been prowling these forums a while now and decided to sign up. 

I recently updated my copy of fs2open via tureys installer, all the vps, user campaigns etc. I was playing through the fs2 main campaign and did the mission Fog of war. For some weird reason it promoted me from lieutenant to full admiral.  Was wondering if anyone else came across this sort of bug. I only have one good idea why it happened and that is I'm using the 3.2.12 exe. Could this have done it? Just curious to find out. Maybe now I can order the GTVA to collapse Gamma Draconis and save themselves some hassle or somesuch.

[Jeff Vader]

Never heard of something like this. The promotion system works (somewhat) as follows: You get points during missions from at least blowing up ships (and probably for achieving objectives, I dunno). Once you reach a milestone in terms of those points during a mission, you'll be promoted to the rank of the exceeded milestone in the debriefing. But it should never jump from lieutenant to admiral just like that. And the game engine shouldn't affect this at all. The only thing I could come up with is that perhaps you had a tweaked mission (for some reason) that gave you OVER 9000!!! points (I mean, a lot of points), which exceeded the amount required for admiral.

Regardless of what some people say, I still don't fully trust Turey's Installer, including its actions when used over an existing FSO installation. You could provide us a copy of fs2_open.log (instructions here) just for kicks. If there is something wrong with your installation, it might reveal that. The E also knew of that one program that could generate a text file including every single file within your \freespace2\ directory, but I forget what that was.

[Buckshee Rounds]

I checked the wiki: promotion to admiral is 9 million apparently!? I followed the instructions in the link, running debug in windowed mode, but when I went to look for the mission in the simulator it wasn't there, only the one 2 missions before it. Very odd. Anyway I'll assume it's like you said - probably an issue with Tureys installer.

Thanks for the quick reply.

[Jeff Vader]

Uh, the point was that now that you've run the debug build, there should be a file called "fs2_open.log" in your \freespace2\data\ directory. Please post that file here somehow.

[MatthTheGeek]

It may be related to a corrupted pilot file. I've been told that the code dealing with that is zomg-like destructive.

[Buckshee Rounds]

Uh, the point was that now that you've run the debug build, there should be a file called "fs2_open.log" in your \freespace2\data\ directory. Please post that file here somehow.

I thought the point of running the debug was to recreate the circumstances of the issue? Debug file attached.

[attachment deleted by admin]

[Jeff Vader]

I thought the point of running the debug was to recreate the circumstances of the issue?

If you've been experiencing crashes that occur at specific circumstances, it can be a point to recreate those circumstances when playing with a debug build. That way you can be sure that the crash occurs again, and that whatever takes place during the crash is recorded. But the point is that when you play with a debug build, it will write all sorts of things into the fs2_open.log. Things like used command-line parameters, .vp files that were found in \freespace2\ and possible active mod folders, and all sorts of other crap that goes slightly beyond me.
In short: recreating the circumstances is good, but if you don't post the fs2_open.log, no one will ever know what happened.

Can't see anything wrong with the retail files and the MediaVPs. The mission can be run through the mission simulator; if you press Ctrl-Shift-S, all missions in the current campaign will be revealed. But I don't think promotions are taken into concideration, if you play the mission there.

It may be related to a corrupted pilot file. I've been told that the code dealing with that is zomg-like destructive.

May be. Have you been playing more than one campaign with the same pilot, Buckshee?

[Buckshee Rounds]

No, this is the only campaign for the pilot I use. I have downloaded and played a fwe campaigns with another pilot though. Can't see how that would have any effect. Thanks for the advice.

[Buckshee Rounds]

I'm starting to run into problems. I'm unable to select the maxim cannon even after it's been introduced. In the mission where you have to take out the Sathana's beam turrets it arms my bomber with harpoons! Yet playing the mission in the simulator seems to generate the correct armament. I think my install is f*cked but everything else seems to work perfect.

[The E]

Sounds like more pilot file issues to me. Sorry, but your current pilot is corrupted and will have to be shot (that is, you'll have to delete that one and create, NOT CLONE, a new pilot). There are altered campaign files that will let you continue from several points in the campaign linked to in the Support FAQ stickied here, use those so that you don't have to restart the entire campaign.

[Buckshee Rounds]

I'll give it a shot thanks.

[el_magnifico]

In the mission where you have to take out the Sathana's beam turrets it arms my bomber with harpoons!

Well, I can't blame the crew chief...

I mean, you're an admiral now! What are you doing on a bomber to begin with!?

 

[jr2]

The E also knew of that one program that could generate a text file including every single file within your \freespace2\ directory, but I forget what that was.

I think there is a link in my sig...

EDIT: Nope, sig restrictions got changed and it is cut out of my sig now.  Nice  

basically, put this in cmd: (or create a text file, hit File > Save As and set type to "All Files" and put a .cmd extension on it)

Code: [Select]

dir <drive:>\<pathtoFS2dir>\ /s /tw>%USERPROFILE%\Desktop\fs2dirlist.txt
EDIT2: Fixed my sig so it works again. Yay for the Wayback Machine.