I was doing fine with everything until I installed the Official 1.02 patch (I never bothered with the 1.01). Now I get the Limbo effect when I try to talk to Shale in the camp, where the game seems to think I am back in Honnleath and have not saved the girl yet.
I noticed by searching the topic that people started to experience this problem 30 days ago, back when 1.01 came out. So, it would seem that Bioware fixed something in the first patch that carried over to the second that, in turn, broke Shale.
The Official Patch broke Shale
Débuté par
Suilebhain
, déc. 16 2009 03:24
#1
Posté 16 décembre 2009 - 03:24
#2
Posté 16 décembre 2009 - 03:34
This problem has been linked to the toolset (and to having the DLC become unauthorized due to being disconnected during an authorization attempt) it's not in any way linked to the patch.
#3
Posté 16 décembre 2009 - 04:21
JironGhrad wrote...
This problem has been linked to the toolset (and to having the DLC become unauthorized due to being disconnected during an authorization attempt) it's not in any way linked to the patch.
Sorry, bro, but I have had the toolset installed for a few weeks now, but only installed the PATCH last night, and as of last night, I am no longer able to talk to Shale in camp without getting sent into the Void.
Besides, I have only used the toolset once, and that was long before this happened.
#4
Posté 16 décembre 2009 - 04:25
Sorry, but the problems that occur don't necessarily have anything to do with "when" they manifest. The toolset devs have even said so. Try the "fix for strange issues" from the link in my signature, download the new 1.01 toolset (which is corrected to prevent recurring issues). It may be that you've been bugged for weeks and the patch just brought it to light as the patch was what they used to correct the toolset bugs.
#5
Posté 16 décembre 2009 - 04:32
"It may be that you've been bugged for weeks and the patch just brought it to light as the patch was what they used to correct the toolset bugs."
Do you realize how silly that sounds? The patch brought it to light BECAUSE THE PATCH CAUSED IT. In "fixing" toolset bugs, they broke Shale. How do I know this? Because I go to my camp several times during my play sessions, and I talk to EVERYONE at least once when I do. Until last night, Shale was its usual effervescent self. Now, the Void.
To summarize:
Before installing patch - Shale speaks in camp!
After installing patch - the Void!
Cause->Effect
If the patch triggered a bug, does that not make the patch something like a trigger for a trojan?
Do you realize how silly that sounds? The patch brought it to light BECAUSE THE PATCH CAUSED IT. In "fixing" toolset bugs, they broke Shale. How do I know this? Because I go to my camp several times during my play sessions, and I talk to EVERYONE at least once when I do. Until last night, Shale was its usual effervescent self. Now, the Void.
To summarize:
Before installing patch - Shale speaks in camp!
After installing patch - the Void!
Cause->Effect
If the patch triggered a bug, does that not make the patch something like a trigger for a trojan?
#6
Posté 16 décembre 2009 - 04:48
Not at all. What causes this is the exports from the toolset. Which is broken. The fact that it broke something and you noticed it after installing the patch have nothing to do with each other. You played the game... for all you "really" know, the part of the game you completed caused the glitch with shale rather than the patch. Try fixing it as I suggested
#7
Posté 16 décembre 2009 - 05:20
The only export I made from the toolset was I changed a saved game for a whole different character in order to change his face.
So, following your plan to fix this thing, I am supposed to delete my saves, delete my mods, and run some third party utility? Why not have me format my hard drive while I am at it?
So, following your plan to fix this thing, I am supposed to delete my saves, delete my mods, and run some third party utility? Why not have me format my hard drive while I am at it?
#8
Posté 16 décembre 2009 - 05:24
Suilebhain wrote...
The only export I made from the toolset was I changed a saved game for a whole different character in order to change his face.
So, following your plan to fix this thing, I am supposed to delete my saves, delete my mods, and run some third party utility? Why not have me format my hard drive while I am at it?
Uhmm, no, I guess what he means is that you must delete the contents of the override\\toolsetexports directories....?
That's the way to solve such problems as far as I've heard (but unlike in NWN/-2 I'm not THAT into the TS of DA:O, so don't shoot me if I'm wrong.... :innocent:)
#9
Posté 16 décembre 2009 - 08:08
I went to his tutorial and it said to delete everything in the Override folder, not just the \\toolsetexports folder. It's in that link in his sig.
#10
Posté 16 décembre 2009 - 09:36
You do need to clear out the entire override... you can reinstall mods (but some of them have broken the game as well due to improperly exported resources)
#11
Posté 16 décembre 2009 - 09:50
Well, I don't have the Toolset installed. I don't even have an override folder, strange as it sounds even to me. After all, I've played NWN 1 & 2 long enough to know what it is, and I swear it's not there. I haven't downloaded any mods, nor anything, apart from DLC. The fact is the same bug hit me, and even if Suilebhain claims to have found related posts on the topic, I've found none, and I'm clueless about what to do. To me, it also happened right after patching, and I'm surprised so little people seem to be encountering the same problem. If anyone could help it would be highly appreciated, because it really sucks having a dumb Shale, and broken DLC on top of it.
Modifié par Lamia Barad-Dur, 16 décembre 2009 - 09:54 .





Retour en haut






