Jump to content


Photo

Assertion Failure again!


  • Please log in to reply
7 replies to this topic

#1 tomkaz

tomkaz
  • Member
  • 992 posts

Donator

Posted 19 July 2014 - 08:28 AM

I have search the forums and noted the the following Assertion Failure has occurred many, many times before.  It is not an easy fix as it has occurred in several different places.  Even I have previously asked for help on how to fix it.  The error is:

 

An Assertion failed in ChVidImage.cpp at the line number 1921
Programmer says: .BAM is corrupted (GetFrame() failed)

 

This time it happens while playing Drizzt Saga V 3.0.  After Durlag's Tower, I talk to Regis, go into Ulgoth's Beard Inn and join with Drizzt, talk to Regis again and go into the Nine Hells and meet Wulfgar.  Wulfgar joins immediately.

 

I can save the game and reload any time I want up to the point where I join with Drizzt.  After leaving Ulgoth's Beard Inn with Drizzt, the action is to fast to save until Wulfgar joins the group.  With Wulfgar in the group, I can save the game and play as long as I like.  But if I reload the save game at any time after Wulfgar joins, the game reloads, but crashes immediately after the game is loaded.

 

I have downloaded NI.  But I am not able to use it as I need more detailed instructions.

 

I think I can try to complete this mod without reloading, but that could be a challenge.

 

Any suggestions would be greatly appreciated.

 

Tom 



#2 tomkaz

tomkaz
  • Member
  • 992 posts

Donator

Posted 19 July 2014 - 03:11 PM

Well, I search on the wrong terms.  Did another search and found "Help With Drizzt Saga??" by Nikito98 (just down the page).  In that post, veecoo's has provided a solution which works.
 
The scimitar that is in Drizzt's Shield slot is Scimitar +5, Defender.  The resource name is F_DRIWP2.itm and it is associated with ISWIH15.bam.  I assume that is the corrupted BAM.  It in reality does 1D8 +3 damage and is +3 to hit.  I found that using Near Infinity.
 
I replaced it with Scimitar +5, Twinkle.  The resource name is DRIZZTDE.itm and it is associated with DRIZZTDE.bam.  It is a true +5 scimitar as it does 1D8 +5 damage and is +5 to hit. 
 
I am a novice with Near Infinity so I was unable to determine how to fix Scimitar +5, Defender or ISWIH15.bam.
 
Tom

Edited by tomkaz, 19 July 2014 - 03:13 PM.


#3 tomkaz

tomkaz
  • Member
  • 992 posts

Donator

Posted 20 July 2014 - 05:40 AM

Drizzt came equipped with two scimitars.  In the Shield slot was Scimitar +5, Defender which needed to be replaced to eliminate the crash on reloading the game.  I replaced Scimitar +5, Defender with Scimitar +5, Twinkle and the game worked.

 

I did try the switch the scimitars.  In the Weapon 1 slot was a D8 +3 scimitar (I forgot the name).  I felt it was better to have Twinkle in that slot.  I switched the scimitars.  This caused the game to crash on reload.  So perhaps the problem is with Drizzt not the weapons.  I hope this information helps the mod author fix the problem.

 

Tom



#4 veecou

veecou
  • Member
  • 54 posts

Posted 21 July 2014 - 04:04 AM

Hi I am glad i could help :)  ..I didn't understand what you mean  "problem is with Drizzt not the weapons" I thought the defender(which was not removable) was the problem,and now you mention it I remember I switch with twinkle too,as it is the scimitar Drizzt uses in the books ;) I think I tried other scimitars and have no crash on reload,though I didn't tried the defender again.Can you be more specific please?Thanks :)



#5 tomkaz

tomkaz
  • Member
  • 992 posts

Donator

Posted 23 July 2014 - 05:54 AM

Hi veecou:

 

The crash I had came after saving the game, then reloading the saved game.  The game reloaded, but crashed immediately.

 

I replaced the scimitar in the Shield slot and the came continued without further crashes.  While still in Drizzt Saga, I noticed that the scimitar in the Weapon 1 slot did 1D8 +3 damage and the scimitar in the Shield slot did 1D8 +5 damage.  Since the attack with a weapon in the Weapon slot has a better chance of hitting the target than the weapon in the Shield slot does, I switched scimitars.  This caused game to crash in the same manner as with the original scimitar in the Shield slot did.  So two different scimitars caused the same crash.  Therefore I assumed it was not the weapon causing the crash and that it was a better probability that there was a problem with Drizzt.  I have the same game on another computer and will see if I can identify which Drizzt is used in Drizzt Saga v3.



#6 veecou

veecou
  • Member
  • 54 posts

Posted 24 July 2014 - 05:39 AM

Oh ok ,I understand, I'm in bg2 now and I dont  know if there are any saves at that moment so I can check ,i was under the impression that only the unremovable scimitar was the culprit,do you remember the name of the second scimitar causing crash? It was the default scimitar that was pair from the beginning with the defender?If yes maybe it is those two weapons when used in shield hand,cause I am sure I tried other weapons in same hand without problems.



#7 -Guest-

-Guest-
  • Guest

Posted 24 July 2014 - 06:04 AM

Hi veecou:

 

I am beyond the Drizzt Saga now.  The original scimitar was Scimitar +5, Defender with the resource F_DRIWP2.itm.  I checked all the Drizzt creatures in my game and found nine of them.  One has the resource F_DRIZZT.cre so I am assuming this is the problem creature.This Drizzt has Scimitar +3, Frostbrand in his right hand and the resource is F_DRIWP3.  I also found a Scimitar +3, Frostbrand with the resource F_DRIWP5.

 

I hope this helps you.

 

Tom



#8 veecou

veecou
  • Member
  • 54 posts

Posted 24 July 2014 - 07:00 AM

Hi Tom!

I found an old save.. I tried frostband in off-hand and had crash while saving the game.

So I guess it is not Drizzt the problem after all, in my save he was having another weapon in shield hand with no problem...

It is the 2 original scimitars frostband and defender while in in off-hand.

I hope this will help the modders in any future update.

Thanks a lot for the info 

 

Maria  :)


Edited by veecou, 24 July 2014 - 07:03 AM.