9 réponses à ce sujet

[Midnight1996]

 Hello,I could really use some help,you see,I can't get past west harbor,when I go to the ruins in the swamp to get the silver shard,I get to the room that it's in,and when I take it from the strong box,the no cut scene,and when I take it back to daegun,he asks me why I came back without it,I know that re installing the game won't help because it did this the last time I installed it,does anybody know how I might be able to fix this?
Thank you for your time.

[kevL]

try this:

Silver shard bug/glitch.

[Midnight1996]

Thank you.

[Midnight1996]

Hey,I might sound like an idiot for asking this,but could you please explain to me how to use them,I not very good with computers,I'm sorry to bother you with this.

[kevL]

while playing the game, stand in West Harbor, next to Daeghun i suppose. Then open the NwN2 console by pressing the apostrophe key -- just below the Escape key -- and a translucent 'console' should slide down from the top of the screen. Think of it as a command console! ie. this is how to cheat,

and fix things.

But before the console works, it needs to be switched on: do so by entering

debugmode 1

Enter. Your command console is now functional. Next, the two commands from the other thread:

rs ga_global_int("11_west_harbor_plot", "20")
rs ga_journal("11_ruin_past", 20, 1, 1, 0)

Enter after each one. Ensure there are no typos, and watch the bottom of the console for messages stating "execution successful".

Finally, finish things off by turning the console off:

debugmode 0

Enter. This is very important!!!

Then get rid of the console itself by pressing the apostrophe key again.


try talking to Daeghun

[kevL]

ps. Do all that after you've recovered the shard and are ready to talk to D.

[Midnight1996]

Okay,thank you again.

[kevL]

np. Let us know if it worked..




later : (seems like it worked..)

Modifié par kevL, 23 février 2014 - 03:41 .

[Dann-J]

I encountered this bug at one point many years ago, and read that it had been fixed in one of the subsequent patches. Patching the game to the latest update at the time fixed it for me. I haven't seen it again since patching right up to version 1.23 (the latest patch available).

[Morbane]

I encountered this bug at one point many years ago, and read that it had been fixed in one of the subsequent patches. Patching the game to the latest update at the time fixed it for me. I haven't seen it again since patching right up to version 1.23 (the latest patch available).

 

same experience here - i think it was between 1.15 and 1.17