-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using TA with Tibia using DX5 or OGL renderer crashes the tibia client #24
Comments
It doesn't work for OGL too. I'm on it. |
The culprit is, as suspected, drawRect and drawBlackRect hooking. |
0e78afa |
Damn, my PC is teasing with me, obviously. I swear it worked for a while... |
Nevertheless, its impressive that you know your way around such low level programming! Keep it up (: |
91f2405 |
Why don't you guys make another install file for this new version of TA? |
Yes, I'll make a new release without a mana bar until we can get this fixed. |
I fixed it 5 days ago in master. ;P 2016-04-18 15:42 GMT+02:00 Wisling notifications@github.com:
|
Its indeed fixed, my build of 91f2405 is working good. I thought of uploading to the forum but it would have probably been misinterpreted x) |
It looks like there's still a bug with this. Using OpenGL, loading TA removes the health bar(though activating the manabar works nicely) |
Does Ctrl+N change anything then? |
Hi Rebell, im getting this same error in win 7 32 bit with dx9 engine, i run both TA and tibia as admin then i log in, and when i press "Ok" in TA the game crashes with that same error mentioned above. I have all dll's instaled, python 2.4.4 etc etc i dont know why i keep getting this error. |
@RickyyF could you paste a crash report here? I find it hard to believe the error is the same. |
Since the latest release (2.64.2 for version 10.92) injecting TA in a client using the directx 5 engine crashes the tibia client upon login, or instantly if theres a character already connected. This happens every time, and on different systems.
Following is the exception text displayed on the next client start
The text was updated successfully, but these errors were encountered: