Dead Ex - Hollywood main quest bug

Hey guys! Loving the mod so far, big fan of it. I registered because I couldn't find this particular problem anywhere.

During the main quest "Dead Ex" in Hollywood, when I meet the guy in the alley behind the Fast Buck, I talk to him and when he says "i dont have it, i stashed it somewhere. Look for Ginger Swan" or something like that, the cutscene comes he get scared and says "im getting the **** out of here" and he just stands there till eternity for me. Nothing happens. Cant move, cant do anything because its a cutscene.

Help please I love this game and I want to finish it for the 20th time

I had this once try reloading a previous save

Hey, thanks for your advice but it doesn't work I tried multiple loads, none of them work

Have you installed multiple patches or mods ?

Hi FastFood,

welcome to the forum.
I have encounterd your problem once or twice myself, but never reproduceable.
If it is consistent, it's mostly due to map changes after the character has visited this map already. So never use an old save file on a new mod. Or as Claudia already stated, multiple patches/mods will cause any amount of unusual things.

-

I installed the 1.45 patch just before I got to Hollywood I think (no music in the clubs annoyed me to hell :O ) I didn't think that would be any problem?

Is there any way to fix it or get the quest moving? Thanks for the replies and the warm welcome


Edit: I don't have anything else installed just CE 1.4 + 1.45 patch

I.. Really don't know. When Childe logs back in, he'll tell you if save files can be usef from 1.4 to 1.45... If it were another case, I'd kick you for multiple installs and using saved files from one patch to the other... But doesn't seem to be the case >_>

If I knew anything about coding, I'd tell you the console code, but.. ¯\(°_o)/¯

Well at any rate, thank you ever so much for your replies and assistance. It means a lot. I'll try a couple of things out keep your fingers crossed :O

Fastfood,
the 1.45 patch changes the hollywood map. So this probably is the cause for your problem.
Did you get the questlog update in the courier dialog?
Try the console command: Find("!playercontroller").Kill(). Does this work?

-

I get the update in the quest log. I tried the command but nothing happens. The console says something like find<use string> or whatever.

Yea, seems the console can't digest every python command. So we have to get a bit more creative.
Use your texteditor (Notepad or whatever you use), and open the file -bloodlines\vampire\dlg\hollywood\courier.dlg
search for line 81, it should look something like this
{ 81 }{ I don't have it!... }{ I don't have it... }{ # }{ }{ Find("!playercontroller").Kill() }{ }{ }{ }{ }{ }{ }{ }
and add the red command there. Make sure there is a tab in front and behind the command, and that you use the right pair of brackets (2nd after the #). That should free you out of the cutscene, even if it doesn't remove the courier.

-

Sorry for revive this post, I´m playing now the Camarilla final edition and I have the same bug. Trapped in the cutscene with the courier. I only see this post with solution, I read your last message and I put that line, and yes, I´m free to move when he is talking. But beware! In my case, if I stay and he says all, the cutscene triggers and trap again. So I run into the bar XD.... and then run into the car-driver and I get my freedom >-<. Thanks for the help, and If anyone have the problem again, this solution works well if you are quick. Only that. Thanks for all!

I had this problem a couple of times. Sometimes it depends on how you approach the guy. I tried talking to him from a different angle, and the cutscene didn't lock up anymore. I didn't have to insert any lines through the console.

Yep. Usually this is one of the random bugs. If I recall right that was a special case. But after about 2 years, I can't tell anymore why I suggested trying to break out with such drastic methods.

I make a habit of quicksaving before I go near him. Same as with the guy in DMP. That cutscene sometimes also gets stuck for no apparent reason. Though luckily I hadn't one of these issues in quite some time.

-

-