Development Cycle Archive
Thread: gRe: Publish 9 Feedback: Hotfix Feedback July 6, 2004
SwgClient_r.exe: 83896.88652
unknown(0x02118E87) : FATAL 3691ac82: Could not lock dynamic ib 2087=err 1=discard 0=offset 1728=length 1/1=lock 1/1=discard
FantasticPlastic wrote:
They also blame "exceptionally smart" players on buffs and armor quality, ignoring the fact that the developers wrote the program that makes it possible to craft things.
You know, I remember seeing posts like that and cringing because it's not hard to craft items at their theoretical limit, even for players who can't test things out with uber-resources (which presumably the devs would be able to). All it requires is the ability to match the stats on the resource to the stats listed on the schematic, and maximize appropriately. "Exceptionally smart"? Maybe if you're talking about three year olds, but any grade schooler of average intelligence should be able to handle the math involved in high-level SWG crafting.
Anyway, the fact that the devs don't seem to be able to handle said math in order to figure out what stats player-crafted items will have, as evidenced by their complete surprise at the stats we end up getting,gives me serious doubts about the people behind the wheel.
That or they just don't bother to test anything. Either way, I cringe.
Thunderheart wrote:
Merendel wrote:
CTD bug has reared its head with this patch. I and many others (acording to the tech suport board) have sudenly been afflicted by a bug involveing Nvidia cards with 256 megs of ram on systems with 768 megs or more of ram. Personaly I'm runing a GF FX 5700 256m with a gig of ram. all the way up till monday night my system ran just fine and I wasnt even aware that this bug existed for some people. Tuesday morning I log in get the patch start loading into the game and crash to desktop repeatedly. As per tips given by other players limiting my system to 512 megs of ram alows me to get into the game but that shouldnt be nessicary. While the game is playable with this work around I do notice a performance hit compaired to befor the patch when this limit was unnessicary.
snipit of the crash log showing the error that caused the dump.
automated crash dump from SwgClient_r.exe 83896.88652
SwgClient_r.exe: 83896.88652
unknown(0x02118E87) : FATAL 3691ac82: Could not lock dynamic ib 2087=err 1=discard 0=offset 1728=length 1/1=lock 1/1=discard
Thanks for the information. We have reproducible cases and our technical director is at microsoft now, working with them to finda solution to this problem.
Poor technical director. ![]()
Glad I'm still playing on my laptop rather than repairing and upgrading my desktop. ![]()
Merendel wrote:
CTD bug has reared its head with this patch. I and many others (acording to the tech suport board) have sudenly been afflicted by a bug involveing Nvidia cards with 256 megs of ram on systems with 768 megs or more of ram. Personaly I'm runing a GF FX 5700 256m with a gig of ram. all the way up till monday night my system ran just fine and I wasnt even aware that this bug existed for some people. Tuesday morning I log in get the patch start loading into the game and crash to desktop repeatedly. As per tips given by other players limiting my system to 512 megs of ram alows me to get into the game but that shouldnt be nessicary. While the game is playable with this work around I do notice a performance hit compaired to befor the patch when this limit was unnessicary.
snipit of the crash log showing the error that caused the dump.
automated crash dump from SwgClient_r.exe 83896.88652
SwgClient_r.exe: 83896.88652
unknown(0x02118E87) : FATAL 3691ac82: Could not lock dynamic ib 2087=err 1=discard 0=offset 1728=length 1/1=lock 1/1=discard