Jump to content


Photo

Game calls for nosound.wav and *.wav


  • Please log in to reply
2 replies to this topic

#1 Milamber

Milamber
  • Member
  • 11 posts

Posted 21 May 2012 - 03:39 AM

For some reason ToBEx reports nosound.wav and *.wav, the first likely shouldn't exist and the second cannot exist because it is not a legal filename. This coincidences with massive slowdowns, freezing for minutes at a time.

I was unable to isolate a component that caused this, but when the games starts without ToBEx I didn't encounter the same problem. I also have infinity animations installed and I think the false wav-references might come from the 2da sound-ref files that are introduced by that mod.

Edit:

By replacing all '*' with 'nosound' in MDKN.2da and placing a silent nosound.wav in the override folder I was able to resolve my problems with the Death Knight animation, so these files seem indeed to be the source of the incorrect references.

Edited by Milamber, 21 May 2012 - 04:12 AM.


#2 Ascension64

Ascension64
  • Modder
  • 5983 posts

Posted 24 May 2012 - 12:06 AM

Do you have Log Missing Resources=1 in your TobExCore.ini? Should only be for debugging. Since this routine is an internal routine, I wouldn't be surprised you get all these weird missing resources.

--------------
Retired Modder
Note: I do not respond to profile comments/personal messages in regards to troubleshooting my modifications. Please post on the public forums instead.

Baldur's Gate Trilogy-WeiDU and Mods
Throne of Bhaal Extender (TobEx)

Contributions: (NWN2) A Deathstalker (voice acting) - (IWD2) IWD2 NPC Project (soundset editing) - (Misc) SHS PC Soundsets (voice acting)
Legacy: (BG/Tutu/BGT) Beregost Crash Fixer 1.9 (18 Jul 10) - (BG2) Enable conversations with charmed/dominated creatures (18 Jul 10) - (BG2) Experience Corrections (18 Jul 10) - (Misc) Platform Conversion Utility RC2 (13 Feb 10)


#3 Milamber

Milamber
  • Member
  • 11 posts

Posted 31 May 2012 - 06:44 AM

I activated the option only after I encountered the problem, and deactivating it bring no improvement, but I've since come to the conclusion missing resource reports are entirely unrelated to my freezing issues. They come fairly regularly, even when there is no freezing at all, the fact that they were always the last messages in the log-file turned out to be misleading.

I need to restart researching the cause.