Jump to content

agb1

Modders
  • Content Count

    409
  • Joined

  • Last visited

Everything posted by agb1

  1. The Pale Master kit tp2 does not include EET in the GAME_IS check, even on master branch. I did not check the other kit mods.
  2. Here is another (unrelated) bug report from the same thread: https://forums.beamdog.com/discussion/comment/844310/#Comment_844310
  3. I've updated the Fixpack patch for NWN Spell Deflection to include kreso's latest revision.
  4. The only thing I did with these spells is made them act properly when "NWN style deflection" is installed. Why these act different from 100+ other spells I included in that code is beyond me. Anyhow, I've removed all code tweaking spells from mods of unknown origin, all megamods and similar; I don't know why I bothered with this in the first place. Replace the file in SR/components with this one. I've incorporated this hotfix into the BWP Fixpack.
  5. It has been reported that SR is modifying some spells from The Grey Clan mod in a problematic manner: http://www.shsforums.net/topic/56670-big-world-setup-an-attempt-to-update-the-program/page-187?do=findComment&comment=592557
  6. Here is an SCS bug report (Durlag's Tower) from the Beamdog forums: https://forums.beamdog.com/discussion/comment/843105/#Comment_843105
  7. here is patch for bpseries. Extract it on top of v0.3121 before installing. This updated patch for BP Series AI has been incorporated into the BiG World Fixpack. The Fixpack patch corrects another issue also - using the wrong TRA files for BG2EE/EET installs. The BWS expert notes say "This mod is temporarily marked Expert because of installation errors due to missing WIZARD_REMOVE_MAGIC in Spell.IDS and missing STATE_DISEASED_FIX in Stats.IDS." K4thos' latest patch did not address those IDS references, so until someone reports a successful install I will leave the expert warning in pl
  8. The Firkra01.cre remaining in copper coronet after visiting Windspear Hills bug is indeed a vanilla issue. For BWS users, a block is now added to the copper coronet area script by Nightfarer's area patcher (which is distributed inside the Fixpack but must be installed separately) to remove the cre in this case.
  9. Haven't looked in detail, but- nothing unsolvable, just needs work. GAME_IS checks need EET added where appropriate. References to BG1 items (eg in sections with GAME_IS bgt) need to use EET converted item file names. Maybe chapter checks (didn't check if it uses any).
  10. Try copying KEY19.ITM and renaming it KEY20, putting it in the override folder, then rerunning the installation (note: you don't need to reinstall the earlier main component). Immediately after the installation, restore the real KEY20 to your override folder (save the current copy there).
  11. Did you search your registry for "baldur" and "bioware" ? Or maybe something in My Documents?
  12. You are correct that V4 beta 9 included a fix intended to solve the same error (albeit seen with a different item). Clearly there is something unique and unanticipated about the KEY20.ITM file in your override folder. As a workaround, you can manually move that file out of your override folder while installing IR, then move it back into your override folder immediately afterwards. If you also attach the item file to your post here, someone may be able to determine the problem.
  13. The installer must be finding something on the system still that makes it think the game is already installed. Do you see an entry for the game in the control panel (add/remove programs)? If yes, try removing that too... Jarno's suggestion would also work, but remember that if you ever copy/move the game folder, you must manually edit baldur.ini and correct the game folder path lines (lines starting with CD and HD) before you install mods or play.
  14. Hmm. The MostRecentApplication is probably just Windows' temporary list of recent programs used. Not relevant to the installer. The other two (the SOA/BG2 keys), if they have no path entries, are probably just remnants of an old install, but I see no harm in removing them -- and it is possible that one of those is preventing your DVD's installer program from to giving you the option to start a new install.
  15. Since you deleted the physical files already, delete those registry keys too.
  16. Delete the game folder too. Try searching for 'BGMain' in RegEdit. Possible registry location - somewhere under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths
  17. If it does then we're back to the RegEdit path.
  18. Ah, in that case just delete the entire BG folder manually and then start a fresh install. The new install will overwrite all relevant registry settings.
  19. http://www.gammadyne.com/registry.htm I thought you already uninstalled the game using its own uninstaller (don't bother with uninstalling mods, as they leave no traces elsewhere on your computer so you can just delete any remnants in the game folder, but definitely use the official game uninstaller first).
  20. A regedit search for the folder path should turn up the registry keys you need to delete. You can launch RegEdit by typing regedit into the Run... box that opens when you press WindowsKey + R.
  21. 1pp was incorporated, partially, in the core game files shipped by Beamdog.
×
×
  • Create New...