tarantonio
Old School Player
- Joined
- Jun 21, 2009
- Messages
- 865
- Solutions
- 1
- Reaction score
- 274
is your OS 64 or 32? Those who cant open my client only have 32 so far.. I made sure they have service packs too so no issue there.
is your OS 64 or 32? Those who cant open my client only have 32 so far.. I made sure they have service packs too so no issue there.
I just compiled another x64 OTCLient, on the machine where it doesn't start.
Can you test and post some info about your windows version and build?
Oh sorry, I forgot to add that dllWorks. Although it needed ogg.dll
Why is Iryont closing all issues without reason? The only reason I can think is that he dont want the community with a smooth client to compete with medivia, can't think on anything else.
Why is Iryont closing all issues without reason? The only reason I can think is that he dont want the community with a smooth client to compete with medivia, can't think on anything else.
Why is Iryont closing all issues without reason? The only reason I can think is that he dont want the community with a smooth client to compete with medivia, can't think on anything else.
why otland doesnt simply, fork otclient github to avoid the issues with Iryont?
i saw once that otland was plaining to make a fork of otclient but that never happened u.u
"what u mean? with I fear many doesn't know judging by some comments I've seen so far in the forum (not just this thread) "It is already otland/otclient (https://github.com/otland/otclient)
I fear many doesn't know judging by some comments I've seen so far in the forum (not just this thread)
I had to disable completely because I'm compiling for x64, but it worked!I had similar problem, was not able to run it on my 7 years old laptop. I fixed it.
The reason was that visual studio had AVX2 processor extension enabled by default while my cpu was not supporting it. I've changed it to SSE2 and it worked. I also updated my otclient from link above, you can try by yourself (but only works on my server coz have modified protocol)
View attachment 35181
You can also try disabling SEH exception. Tested on i5-430m, works
I've said it before but I'm gonna affirm it again, Kondrah is a god. He rewrote the walking system on OTC.
OTC before:
Kondra OTC:
It's a little bit bugged yet but you can notice the difference on walking, even with 250 ping I feel like I have 0.
should this fix walking animations issues with old clients too?that still looks very poor. theres already been a public fix released some days ago that has same walking as the regular client, only thing i believe thats still missing is outfits with idle animations still walk weird. thats all then i think walking is 100% fixed
smooth walking with new speedlaw by Sundance · Pull Request #27 · otland/otclient
A near complete fix to the wonky walking with the new speedlaw & walking animation speed. Note: it may be smoother to use v-sync (for me it is) even if you have 500+ fps without v-sync.github.com
that still looks very poor. theres already been a public fix released some days ago that has same walking as the regular client, only thing i believe thats still missing is outfits with idle animations still walk weird. thats all then i think walking is 100% fixed
smooth walking with new speedlaw by Sundance · Pull Request #27 · otland/otclient
A near complete fix to the wonky walking with the new speedlaw & walking animation speed. Note: it may be smoother to use v-sync (for me it is) even if you have 500+ fps without v-sync.github.com