Severe system Lock up at the Orc Cave

Discussion in 'The Temple of Elemental Evil' started by SerpentSoul, Jul 18, 2006.

Remove all ads!
  1. SerpentSoul

    SerpentSoul Member

    Joined:
    Jun 16, 2006
    Messages:
    1
    Likes Received:
    0
    Hello there!

    First of all, thanks alot for the hard work that went into the CO8 5.00 patch! You are making an all time classic of mine into an even better playing experirence.

    However, I seem to have encountered a bug that will not let me progress further. I have a party of 6, all but one are lvl 3 characters. Before venturing deeper into the Moathouse, I decided to kick those Orcs outa the Ogre Caves.

    But some time into the fighting, I think everytime I try to cast a spell later in battle, ToEE just ceases to function. The music is running in the background but I can't do shit anymore.

    Sometimes it's possible to leave the game by pushing the win-button, most of the time it's system reset.

    It reminds me of that fire node bug in the old versions. I already waited 5 minutes, but it just doesn't work. My system is quite powerful, so all the summoned critters and stuff shouldn't cause this.

    Up until the Orc cave, playing experience was smooth as silk, performance- and bugwise.

    I also tried disabling one core of my X2 AMD processor, this helped alot with other games having problem with the new processors, but to no avail.

    I really hope someone can help me out here, you guys are doing an awesome job...:cool:

    My system specs:

    -S939 Athlon 64 4600+ X2
    -2x 1024 MB DDR PC400 RAM
    -512mb Ati x1900xtx
    -Creative X-Fi Xtreme soundcard
    -S939 MSI RD480 Neo2 Mainboard
    -Win XP Home, constantly updated
    -HDAS 250 GB hard drive (@7200)
     
  2. Sirian

    Sirian The Red Leaf

    Joined:
    May 15, 2006
    Messages:
    26
    Likes Received:
    0
    I suffered from the same type of lock up in the orc cave when I summoned a small viper into the fray. Game locked,couldn't get back to windows and had to hard reset. tried again and had no probs even when I summoned the viper again.
     
  3. Fahrenheit

    Fahrenheit Pyromancer

    Joined:
    Jul 7, 2006
    Messages:
    19
    Likes Received:
    0
    I had the same exact problem when I was trying to heal a fallen party member, again in the Ogre Cave.

    Instead, I just did a heal check to keep him from dying, and finished the battle.

    I think I had a problem with too many spell effects. With all of the raging orcs there, supported by spellcasters, plus the fact that I had to buff up quite seriously to take them on, there were a lot of things going on.
     
  4. Noran the Axe

    Noran the Axe Member

    Joined:
    Mar 30, 2006
    Messages:
    76
    Likes Received:
    0
    Try turning down your graphic and sound effects while in that area. That should clear up the problem.
     
  5. rufnredde

    rufnredde Established Member Veteran

    Joined:
    Apr 8, 2006
    Messages:
    266
    Likes Received:
    1
    I am aware of the lock up problem and Cerulean the Blue and I have done some extensive troubleshooting on it. It does seem to have something to do with all that is going on in there in the background.

    In the latest fix I reduce the amount of background scripting and tried to get it to stop. But it is quirky and seems to vary from machine to machine. I rarely have problems with it but during testing it seems to affect Cerulean the Blue almost everytime he cast a spell.

    Any feedback on this is appreciated. I would like to get the bottom of it and eliminate the problem entirely.

    So if you don't mind when you report this bug. Please let me know which version of the the Orc quest you are running. 5.0.0 final or the date of the patch you have installed.

    Thanks for helping me make this encounter better
     
  6. Noran the Axe

    Noran the Axe Member

    Joined:
    Mar 30, 2006
    Messages:
    76
    Likes Received:
    0
    @ruf

    You might want to look at any scripts with loops in them in the area. Sounds like either a memory leak or a loop that isn't properly completing. Could also be just too much for the processor to do during the loop. Haven't had the chance to look at it myself, but as someone who programs in PERL, I can tell you it sounds exactly like a problem when a loop isn't properly written. Hope that helps.

    -Noran
     
Our Host!