Trident Down Problem
Moderators: winston, another_commander
Trident Down Problem
I've followed Captain Suslov from Raceedat station to the orbiting transit station as instructed however when I dock I get a blank "Mission Screen" and the only option is "Launch Ship", after I launch the mission status on the F5 screen still reads the same, so I'm kind of stuck
Any help please?
Any help please?
- Disembodied
- Jedi Spam Assassin
- Posts: 6885
- Joined: Thu Jul 12, 2007 10:54 pm
- Location: Carter's Snort
Hi GrahamIC: I think this thread might answer your question.
Hi, I've had a look and found it's an error - there was a hyphen somewhere that should have been an underscore. I've fixed this in the uploaded copy, but here's what the text should have said:
Code: Select all
With the Transit Station surrounded by the People's Police, you go in and demand to see Yuri Batkov.
'You want to see the Director?' says one of the deck officers. 'I'm sure he's around here somewhere. If you just wait here a moment...'
The officer disappears down a busy corridor and after a long wait you get the impression that he isn't coming back.
Your communicator comes to life in a burst of static: 'Commander, this is Captain Suslov. We're seeing some activity in one of the loading bays - it looks like our man might be trying to make a run for it. I've contacted HQ and we are authorised to use any necessary force to stop him.'
'OK, Captain, I'm on my way.'
You hurry back to your ship and prepare for launch.
Download Resistance Commander plus many other exciting OXPs HERE
Okay, I've downloaded the latest version of the OXP and I now get the mission briefing screen, but after launching there is no sign of Batkov's shuttle. I have had a look in the latest.log and the following appears:
[script.addShips.failed]: ***** SCRIPT ERROR :in <anonymous actions>, addShipsWithinRadius: could not add 1 ships with role "batkov-shuttle"
[script.addShips.failed]: ***** SCRIPT ERROR :in <anonymous actions>, addShipsWithinRadius: could not add 1 ships with role "batkov-shuttle"
[script.load.world.listAll]: Loaded 8 world scripts:
communist_population 2.11
oolite-cloaking-device 1.74.2
oolite-constrictor-hunt 1.74.2
oolite-nova 1.74.2
oolite-thargoid-plans 1.74.2
oolite-trumbles 1.74.2
targetAutolock 1.10
trident-down 1.0
[script.addShips.failed]: ***** SCRIPT ERROR :in <anonymous actions>, addShipsWithinRadius: could not add 1 ships with role "batkov-shuttle"
[script.addShips.failed]: ***** SCRIPT ERROR :in <anonymous actions>, addShipsWithinRadius: could not add 1 ships with role "batkov-shuttle"
[script.load.world.listAll]: Loaded 8 world scripts:
communist_population 2.11
oolite-cloaking-device 1.74.2
oolite-constrictor-hunt 1.74.2
oolite-nova 1.74.2
oolite-thargoid-plans 1.74.2
oolite-trumbles 1.74.2
targetAutolock 1.10
trident-down 1.0
Hi GrahamIC,
I have encountered exactly the same problem you mentioned (No shuttle launching from the transit station). I have updated Trident Down to the latest version which has solved the blank mission screen problem, and I have reinstalled the latest version of Executive Spaceways, but upon launching from the transit station I still don't see Batkov's shuttle.
Did you make any other changes when you were trying to get this to work?
Cheers
Tom
I have encountered exactly the same problem you mentioned (No shuttle launching from the transit station). I have updated Trident Down to the latest version which has solved the blank mission screen problem, and I have reinstalled the latest version of Executive Spaceways, but upon launching from the transit station I still don't see Batkov's shuttle.
Did you make any other changes when you were trying to get this to work?
Cheers
Tom
The problem was being caused because I hadn't extracted the OXP for Executive Spaceways properly. Basically what I had was the following folder hierarchy
c:\Oolite\AddOns\Executive Spaceways v2.3\Executive Spaceways v2.3.oxp
this should have been:
c:\Oolite\AddOns\Executive Spaceways v2.3.oxp
Once I'd cut and pasted the OXP folder directly into the AddOns folder and replayed the mission, Batkov's shuttle showed up. If i recall correctly he shows up as a 'B' on the advanced space compass
Hope this helps
c:\Oolite\AddOns\Executive Spaceways v2.3\Executive Spaceways v2.3.oxp
this should have been:
c:\Oolite\AddOns\Executive Spaceways v2.3.oxp
Once I'd cut and pasted the OXP folder directly into the AddOns folder and replayed the mission, Batkov's shuttle showed up. If i recall correctly he shows up as a 'B' on the advanced space compass
Hope this helps
It looks as though Oolite caches the scripts in the following file (just discovered this today):
C:\Oolite\oolite.app\GNUstep\Library\Caches\oolite-cache.plist
you could try renaming or deleting the file and then reload oolite and try again, the file seems to be recreated when you run oolite so it should re-cache the current version of the script.
You may want to have a look at the thread called "Trident down the search for Ezra" as well as there are a couple of other issues you will face after this part of the mission.
C:\Oolite\oolite.app\GNUstep\Library\Caches\oolite-cache.plist
you could try renaming or deleting the file and then reload oolite and try again, the file seems to be recreated when you run oolite so it should re-cache the current version of the script.
You may want to have a look at the thread called "Trident down the search for Ezra" as well as there are a couple of other issues you will face after this part of the mission.
-
- Quite Grand Sub-Admiral
- Posts: 6682
- Joined: Wed Feb 28, 2007 7:54 am
Or you can start Oolite with Shift held down until the rotating Cobra appears and not worry about deleting files in the game folder tree. Oolite re-creates the cache when started with Shift down.GrahamIC wrote:It looks as though Oolite caches the scripts in the following file (just discovered this today):
C:\Oolite\oolite.app\GNUstep\Library\Caches\oolite-cache.plist
you could try renaming or deleting the file and then reload oolite and try again, the file seems to be recreated when you run oolite so it should re-cache the current version of the script.