14 replies to this topic

[Klosetmonkey]

i have the exact same problem actually would like to know whats wrong as well

[Chevalier]

What weapon are you using?

[Turambar]

Does it also happen with ranged attacks?
What PC are you using?

[Klosetmonkey]

as i said earlier i had the exact same problem, but managed to fix it by running the game through the bgmain.exe instead of ToBexLoader

maybe that will work for you

[Miloch]

So this is an issue with TobEx loader?

[Turambar]

Hey, thanks a lot, that worked! I didn't realize you were supposed to stop using ToBExloader after character generation and switch to BGMain.exe

You are actually not supposed to; TobEX should work for the whole game and better than BGmain

That's what it seems like... however I had another install of BWP ("Standard" -- way too many mods that I didn't like, so I scrapped it and reinstalled with this setup), which I ran with the TobEx loader, and I did not have this problem. So I'm not sure what the cause is.

I thing there's a new TobEX component dealing with damage type and so on. I think this topic should be moved to the TobEX forum, as I think it's quite sure it's a TobEX issue (as it only comes out when the game is launched via TobEX).

[Ascension64]

Yeah, this sucks. Activate "Damage Fix" in TobEx.ini and that should actually 'fix' the problem.

The big problem with testing TobEx is that there are so many ini option combinations that I'm considering removing the ability to configure altogether... funny how activating more options actually makes things work better, since I test primarily with most options on (at least 'standard' install).

The other issue is that BWP does not conform to any standard install of TobEx, because it uses --force-install, of components that do not properly match QUICK_MENU. If it is possible to simulate QUICK_MENU via cmd, then that would help quite a bit.

I've put in a request for something like --quick-menu in WeiDU to allow easier updating of BWP. If that isn't going to work, I'm afraid users may simply have to install TobEx manually...

Edited by Ascension64, 01 February 2011 - 03:18 AM.

[DavidWallace]

Yeah, this sucks. Activate "Damage Fix" in TobEx.ini and that should actually 'fix' the problem.

The big problem with testing TobEx is that there are so many ini option combinations that I'm considering removing the ability to configure altogether... funny how activating more options actually makes things work better, since I test primarily with most options on (at least 'standard' install).

At the least, I think it would be pretty harmless to remove the option to configure the bugfixes, externalisations, and extra flags. I think things like Stoneskin shouldn't be activated by default, but there I think there's an argument for not providing a direct option for end-users to do it, and leaving it for mods to do the configuring. (Then ToBEx moves from being a mod directly for end-users to a resource to be required by mods.)

[JohnMoonlord]

Just had the same problem, using Windows 7 in my case.

I'll try changing the .ini as Ascension64 said and I'm crossing fingers...



Yes! It works now.

Edited by JohnMoonlord, 10 February 2011 - 05:46 PM.