11 réponses à ce sujet

[Petycon]

Hey there, all,

I've got a bit of a problem - at the Githyanki base, there's a door guarded by the demon Zaxis that - according to all sources - should open upon his defeat. That door, however, has remained shut for me when he bit the bullet. What's worse, I have both quicksaved and overwritten my last saved games since then, and my closest save is hours away. I have tried fiddling with the console mode, but so far wasn't met with success.

I'm playing the Steam version of the game, if it's any help, with all the expansions installed. Thanks in advance!

[kevL]

So you're left standing in front of the door and they just won't open?

- having a look at it now, i found the place they're supposed to unlock ..


Loading, please wait ...

[kevL]

oops, looks like another GroupOnDeathBeginConversation() fubar ....

Control your mainPC, no target, run from console (DebugMode 1):

rs ga_start_convo("1623_ip_zaxis", "16_zeeaire_door", 0, 0, 1, 0)


standing before the locked doorway.

hehe, looks like they also tried to fire this from Zaxis' death then commented it out and went with the 'less unreliable' method .. there might be a hitch-up with a local_int set incorrectly for this convo to fire (i doubt it tho)

goodLuck, let us know,

[Petycon]

My sincerest apologies for taking so long to reply - my trip did not leave me with as much free time as I originally anticipated. I have now tried your solution, kevL, and am ecstatic to say that it works - the door sprung open as soon as I input the command (correctly, after several attempts). Thank you! I'll go back to enjoying the game.

[kevL]

Petycon wrote...

I'll go back to enjoying the game.

it's for the best :|

[Axe_Edge]

Hey KevL,
I think the community really needs you to have your own thread. Your findings and solutions should be kept in a single/secure location, and stickied. Maybe just one long post in a stickied thread.  You've identified way too many errors and shortcommings to let the knowledge be lost. This great game will be the only game of this type for a long time, and we need to keep it going.

If you put something together, maybe DNO will consider it.

Modifié par Axe_Edge, 03 novembre 2011 - 02:40 .

[kevL]

hey Axe,

thanks for the, ahh ... thanks for ... Thanks.

I'm sure peepls are finding the fixes they need through Google (whether by myself or others). I agree with your assessment of 'a long time' btw. Maybe someday i'll pull these together and post them to the Vault or paste them into nwn2.wikia - but anyone can do that really, i just post because I want to, and want to figure something out, and all that stuff ...


as long as the Powers that wanna-Be (sic) don't get their hackles up consider everything under a GNU license.

[Axe_Edge]

What is really needed is for all of the known/confirmed bugs that have workarounds to be listed in a single/concise thread. The thread should list all of the solutions that have been figured out, no matter who did the figuring. I'm just suggesting that your work could start the thread and the countless other community members who have resolved issues can add their findings.

I'm not really talking about all of the spell and feat problems. I'm thinking more along the lines of the known plot or environmental issues like: specific doors not opening, reading, summoning, and spell casting not consistently being completed (due to being interrupted accidentally), a certain green NPC not speaking correctly (unless right-clicking him and clicking "talk"), a certain maiden not going to sleep, caravan route problems, etc...

It would be cool if a post simply listed:

1) OC, MotB, or SoZ
2) Which act
3) Specific result of the error/shortcoming when playing
4) Specific reason why the error/shortcoming occurs (listing the erroneous code)
5) Specific fix/workaround
6) Result of fix/workaround
7) Author of fix
8) person who confirmed findings

Any discussion should be handled in a second thread to keep the first thread clutter free.

Imagine if Kaldor Silverwand read the thread and decided to quickly add more fixes to his makeovers. Maybe a few would build and maintain an override that incorporated the fixes. The override could be considered "The NWN2 Communities Unofficial Patch 1.23.5"

/pipe dream

[kevL]

Axe_Edge wrote...

/pipe dream

_~

nwn2.wikia.com \\ Bugs


heads up (for those who don't know) ... but many of these are probly outdated and could be removed ( idk )

[Axe_Edge]

Yeah, i've seen the wikia. Just seems very short and has very few permanent fixes. Its great people posted problems they came across, thoughtfully.

[Kaldor Silverwand]

I also think a real bug fix would be good. But I would only want it to correct things very conservatively. Only conversations and scripts that are clearly broken due to typos or logical mistakes. The problem is that sometimes people call something a "bug" when it is really just their preference. I also wouldn't say for example that things like pickpocketing or secret doors are "bugged", when really they are just poorly implemented. I also wouldn't fix things like journal entry text that are nits, because the more you alter the more you risk introducing new bugs or making things incompatible with mods.

I'm not planning any more updates to the Makeovers, but if they were the right mechanism to use to release true bug fixes, I'd be willing to consider it.

Regards

[kevL]

Kaldor Silverwand wrote...

I'm not planning any more updates to the Makeovers, but if they were the right mechanism to use to release true bug fixes, I'd be willing to consider it.

Regards

that thought occurred to me a long time ago. But yes, there should be an OC bugfix pack with only bug fixes. Either that or everyone should make their CC compatible with everyone else's, and fully configurable to boot. Can't see this happening ...

My own Override starts with Kaedrin's (Player1's fixes), and when i work on something I tend to look at WRFan's Plot Fixes (an inactive version!), plus there's stuff strewn all over the place. my Override has both straight fixes as well as many preferences & tweaks - the thought of going through it and pulling relevance out is very unappealing ( and far from comprehensive ). I believe that the project we're speculating about here, would require a dedicated clik of persons, working at the "Community Bugfix Pack" - and even then to become the best fix, 'twould have to rollup with others' efforts at true modifications


perhaps we should just sit on this and make sure it doesn't struggle too much for a year or two .. The thing is, a CBP would have to have some way of warning people, 'this file is redundant/conflicting with such and such a file in external Pack X' etc. This doesn't even get into questions like "Is cut content legitimate?" - many people, including myself, would love to have it available ... but making it optional would double the time, after extra testing is considered, vs going ahead and implementing it.

Personally, KS, I don't consider the OC balanced in any sense of the word, though it may well be amusing or fun, for moi to get involved it would have to be about a lot more than simple fixes :|


- all that said, consider this a positive vote if you want to keep a directory with files that have pure fixes ( i do ), and either slide them in with the Makeovers or release them as separate pack(s), or just sit on them and wait for the bandleader to tap his/ her baton