UU 1.5 campaign problem -1 reply

Please wait...

Mr Trek

I post to get attention

50 XP

7th April 2009

0 Uploads

73 Posts

0 Threads

#1 8 years ago

Well, I just finished the last ENT mission "Stirring the Hive" in my UU 1.5 version of the game. When I went on to the next mission "The Squeeze" which is in the Kirk era I still had the NX-01 as my ship and could not change it. Will this be fixed if I download somehing called "UU 1.5 Minipatch" that's on the website? If not, any suggestions on how to fix this dusturbing problem??




086goinfast

NObama

50 XP

6th March 2006

0 Uploads

9,633 Posts

0 Threads

#2 8 years ago

Well, since its a patch you should already have it installed anyways, I would.

But, if that doesn't fix it than the search function is your friend. This specific problem has been brought up many times.




Guest

I didn't make it!

0 XP

 
#3 8 years ago

It's a legacy bug it happens stock or modded. Randomly. It might happen for you 10% of the time or it might happen 1% or it might happen 50%.

There are two ways to fix it. 1. Delete your stlsave folder in your My Documents folder and Start over from the beginning and you have a fair chance of it not happening the second time around (althought it still could). Ofcourse you will start over from the first mission..

Or modify some odfs turning the NX into the 1701 (but be sure to switch it back or if you do start over again you will have the 1701 when you should have the NX.

The only way to prevent it 100% would be to modify the stock missions sourcecode and recompile them. Bethesda did release source code for "most" missions but not all of them.




MARKYNCC

NG-Mods Mission Creator

50 XP

26th May 2009

0 Uploads

148 Posts

0 Threads

#4 8 years ago

This is a strange problem, I have seen it posted several times now, I replied to the same question earlier! The hero ship in the original campaign missions is selected via the ' Legacy.xml' file in nearly all of the campaign missions.

If you change the Hero ship in the xml file, it changes in game

This is because in the scripts there is a function that says:

enterprise = GetCraftFromTeamList( 1,0 );

therefore whichever ship is listed in the .xml file as the hero, will automatically be the players ship.

I know this, because I have substituted other ships in place of the stock ones in the xml file, and it changes in game. I am also scripting the campaign for TB3, and changing the ship in the xml, governs what we see in the game.

I repeat what I said earlier, go into the campaign>Legcy folder and open the Legacy.xml file.

Have a look and see which ships are assigned as the hero, and in which missions.

You should have:

'F_Enterprise_ NX_01.odf' for the first five missions 'F_Enterprise.odf' for the next three 'F_Enterprise_A.odf' for the next two 'F_Stargazer.odf' for the next one 'F_Enterprise_D.odf" for one mission 'F_Enterprise_E.odf' for the final three

I dont see how the hero ship in the campaign missions can change, if no changes have been made to the stock scripts, other than changing it in the Legacy.xml file.

Unless I am totally wrong?

There is one other possible reason for this issue, if you have multiple copies of Legacy on your computer, ie One version that is stock, another that has UU installed and maybe a third with Trek Battles 2 installed, and you have played the campaign in all of them alternately, maybe playing the first few missions on stock, saved the game, then changed over to UU, played it on that game, then it could be an issue with the stl save folder?




Mr Trek

I post to get attention

50 XP

7th April 2009

0 Uploads

73 Posts

0 Threads

#5 8 years ago
MARKYNCC;5145923There is one other possible reason for this issue, if you have multiple copies of Legacy on your computer, ie One version that is stock, another that has UU installed and maybe a third with Trek Battles 2 installed, and you have played the campaign in all of them alternately, maybe playing the first few missions on stock, saved the game, then changed over to UU, played it on that game, then it could be an issue with the stl save folder?

The xml looks fine, so it's probably because I have five versions of Legacy :P However when I decided to play the campaign in UU1.5 I started the campaign from scartch... I'll install the patch and if that doesn't work I'll copy the Enterprise odf to the NX-01 odf and put a "basename" in it. That should fix it shouldn't it (of course I'll have to do that again when I should have another ship)?




Guest

I didn't make it!

0 XP

 
#6 8 years ago

Changing the XML "after" it happens won't fix. It's a potential preventive measure.

Personally knowing what I do of the issue and scripted missions, I doubt having the right xml has any ability to prevent the problem, although having the wrong xml does mean you will certainly get the wrong ship I don't think it has any ability to stop it from happening. I believe the problem is the xml gets overlooked and that's why you end up with the wrong ship therefore no matter what you had set in there you would still get the same old ship. But that's an estimate.

If you look at the xml you will see what ship you "should" have. In that case you can make a copy of the odf of the ship you "should" have and rename it to the name of the ship you "do" have. That will then give you the right ship, but again it will cause you to have the wrong ship the next time around unless you restore the original odf at that point.

Because the "right ship" likely already has a base name you should be fine just swapping them, but if it happens to not then ya just add the proper basename reference.




davyou5

GF Pwns Me!

50 XP

9th September 2009

0 Uploads

52 Posts

0 Threads

#7 8 years ago
Mr Trek;5146373The xml looks fine, so it's probably because I have five versions of Legacy :P However when I decided to play the campaign in UU1.5 I started the campaign from scartch... I'll install the patch and if that doesn't work I'll copy the Enterprise odf to the NX-01 odf and put a "basename" in it. That should fix it shouldn't it (of course I'll have to do that again when I should have another ship)?

I've had this problem a few times on the Stock version of the game, and using the Official Legacy Patch 1.2 did the trick: however the Last Mission Sturring the Hive had to be replayed, I truly don't know if it'll work with UU, though you can try.