[eikka]

I previously had the problem with the Capellan Governor's shuttle crashing into the Ganymede docking ring, but I updated to the patched version of Derelict via Turey's and that issue was fixed. I went back to the old version and confirmed that this crash exists there, too.

I am having the same problem with my Derelict setup. Teh governor shuttle keeps hitting the Luxor surface until it is destroyed..

I downloaded the DerelictSCP*.vp files from the OP links and my DerelictSCP.vp has date 3/7/2006 (file size 7 709 071). I haven't dared to use FSOInstaller on top of my manually configured install, since I don't want to load everything.

I am using fs2_open_3_6_10r-20090118_r5042.exe with 3.6.10 MediaVPs.

Any advice? Thank you in advance!

[GTSVA]

I am having the same problem with my Derelict setup. Teh governor shuttle keeps hitting the Luxor surface until it is destroyed..

Hey...welcome to the HLP!

This is a common one nowadays. I used FRED to edit the mission just a little bit and to move the Ring. I forgot what the mission name was...Help anyone?

[Goober5000]

Use Turey's installer to update your Derelict installation.  It will download a patch that includes (among other things) a fix for that mission.

EDIT: Or, if you don't want to use the installer, I've attached the patch.

[attachment deleted by admin]

[GTSVA]

Oh...that's convenient...

[eliex]

I had to cheat-kill the Luxor's ring before I realized there was a patch around. 

[eikka]

Use Turey's installer to update your Derelict installation.  It will download a patch that includes (among other things) a fix for that mission.

EDIT: Or, if you don't want to use the installer, I've attached the patch.

That was fast, thank you! All I need to do is to copy it to my 'derelict' mod directory, right? No need to set-up anything in the Launcher?

[Jeff Vader]

Correct.

[Aurora Paradox]

Apologies for necro'ing the thread. However...

I'm replaying Derelict SCP a year or two after my first go. This is a new computer, with new install of FS2/FSO and everything else. Had no problems the first time, everything worked perfectly.

Now, however, I'm on Vista 64. Athlon X2 5000+, Nvidia 8800GT, neither overclocked. Two gigs of RAM. Using the 5020 nightly build and the 3.6.10 MV_Complete vp. Don't know if any of that is related to my problem, but it seems unlikely as the error is also occuring with the same build and .vps on an XP machine with an Athlon X2 4200 and a GeForce 7900GS.

The mission 'Code of Honour' - the first GTI mission - crashes during load, when loading either cargo03.pof or fighter13.pof. Attached is fs2_open.log.


Advice? Questions? Something?

I just ran into this problem yesterday.  Updating to latest nightly build for Windows(February 4, 2009) fixed the problem.

Aurora Paradox

[eikka]

The patch fixed the governor shuttle bug, thanks. However, I am not sure if I have found another bug.

In the mission "The third man" I need to identify an unknown vessel. However, I cannot find anything that could be targetted and identified.  There is one Vasudan ship floating still but I cannot select it. Alongside there is a satellite of sorts with rotating panels, also floating still and unselectable. Nothing happens when I fly around them. Is this a bug or is there some hidden ship somewhere that I just haven't found?

[Jeff Vader]

It's been a while since I last played Derelict, but I took a quick glance at the mission file. There should be a ship in the area that is hidden from sensors (i.e, you can't target it, but it shows up as a flashing blip on the radar). Once you get close enough to it, you should "identify" it.

[eikka]

It's been a while since I last played Derelict, but I took a quick glance at the mission file. There should be a ship in the area that is hidden from sensors (i.e, you can't target it, but it shows up as a flashing blip on the radar). Once you get close enough to it, you should "identify" it.

Alright, couldn't see anything in my 3D radar so I switched back to default radar. Still nothing. By digging the archives I found more posts with similar problem, where the solution was to change radar radius. Switching from 2K to 10K gave me the blinking spot and I could finish the mission. Thanks lobo and folks!

[Jeff Vader]

I found more posts with similar problem, where the solution was to change radar radius. Switching from 2K to 10K gave me the blinking spot and I could finish the mission.

I like to keep the radar range on ∞ so I won't miss anything.

[GTSVA]

I found more posts with similar problem, where the solution was to change radar radius. Switching from 2K to 10K gave me the blinking spot and I could finish the mission.

I like to keep the radar range on ∞ so I won't miss anything.

Same here.

[Titan]

wait, you can change it?

[Rhymes]

Yeah.

The default control is mapped to the apostrophe ( ' )
It cycles between 2 kilometer range, 10 km, and infinity.
The range is defaulted at infinity.

[GTSVA]

Yeah.

[Mongoose]

It used to be defaulted at 2k, at least in FS1.  At least in my opinion, it's the singularly most useless feature in the games.

[Rhymes]

 

It used to be defaulted at 2k, at least in FS1.  At least in my opinion, it's the singularly most useless feature in the games.

  Huh?  I never remember it set to 2k, mine always was at infinite, even in FS1.  And yeah, it is useless.

[Mongoose]

I know mine always was back in the dawn of time.  In fact, it took a while before I figured out how to increase the range...which made certain missions substantially more difficult.

[Rhymes]

Ouch.  Lucky me, I never had that problem.  Bet you were pretty happy when you found how to change the range, though.