zbizu
Legendary OT User
Imo there should be a standardized status protocol to send things before login. It could send things like viewport size and public key, but that requires cooperation between server and client devs.
@skulls idea is the best one: unify the common functions in a separate library. There is no need to treat otclient and tfs as two different projects when in the end they are two sides of the same coin.Imo there should be a standardized status protocol to send things before login. It could send things like viewport size and public key, but that requires cooperation between server and client devs.
All the protocol status messages could unified with the login server
it is possible yes, it would have to improve the texture that generates this "shadow", in fact, the ideal would be to refactor this whole system, oddly enough, it still uses the same edubart client.This is great. Any chance to make the dark tiles shadow more smooth without hurting the performance much?
it's already like that, from the photo it looks like it's not.@Mehah perhaps I'm not being able to see this through this particular screenshot, but is the luminosity decreasing by floor distance as well? It would be really cool to have something like this
as I said @Night Wolf , otclient already has it, I just need tfs to send a protocol informing me about awarerange.It would be interesting to support extended viewport if this makes it to TFS
![]()
Refactor viewport, move from hardcode by ramon-bernardo · Pull Request #3456 · otland/forgottenserver
Pull Request Prelude I have followed proper The Forgotten Server code styling. I have read and understood the contribution guidelines before making this PR. I am aware that this PR may be close...github.com
may I invite you some beers or whatit is possible yes, it would have to improve the texture that generates this "shadow", in fact, the ideal would be to refactor this whole system, oddly enough, it still uses the same edubart client.
it's already like that, from the photo it looks like it's not.
as I said @Night Wolf , otclient already has it, I just need tfs to send a protocol informing me about awarerange.
just show up here in Rio de Janeiro.may I invite you some beers or what![]()
This is amazing any chance there will be another compiled version?![]()
Congratulations, it really sounds like a very well done job. But I missed a comparison between this fork and the original otclient. Does your client deals correctly with animations from Tibia 10.51+? Like the "chaos acolyte" outfit, which doesn't look well at the edubart's version.
I give it a quick try and it worked well here as well. It indeed seems the best open source client so far.
OTClientV8 has two clients, OpenGL and DirectX. If OpenGL is not working for you then use DirectX, OpenGL is just better.It seems like a nice release and i have few questions.
Is there any kind of bot or built in feature that would allow enabling magic wall timer?
Why is directx 9 greyed out and im not able to turn it on?
What is the difference between otclientv8 and this release when it comes to api like opengl and directx because this one seems to work much better and graphics options let me choose opengl 1.0 or 2.0 instead of opengl 4.6 that is picked by otclientv8 that is not working too well for me.
You dont understand what i mean. Everything is working for me except directx 9 is greyed out on otclient from Mehah why is that? And opengl works differently on amd and nvidia and maybe thats the reason that otclient mehah works better on opengl than otclienv8.OTClientV8 has two clients, OpenGL and DirectX. If OpenGL is not working for you then use DirectX, OpenGL is just better.
What is your GPU? otcv8 is capable of running at 40FPS on a 2008 PC without GPU.You dont understand what i mean. Everything is working for me except directx 9 is greyed out on otclient from Mehah why is that? And opengl works differently on amd and nvidia and maybe thats the reason that otclient mehah works better on opengl than otclienv8.
To have support for directx you have to compile with directx support (angle). You didn't compile with dx9 support or someone who provided the .exe.You dont understand what i mean. Everything is working for me except directx 9 is greyed out on otclient from Mehah why is that? And opengl works differently on amd and nvidia and maybe thats the reason that otclient mehah works better on opengl than otclienv8.
To make this client work i downloaded whole pack from Mehah github and added files from release and he probably did not compile it with directx support or i did something wrong that might be the answer. Lets move to next question then. What is the difference between opengl version that is present in this client compared to otclientv8? Because here in graphics options i can set opengl 1.0 or 2.0 and in otclientv8 it forces me to use 4.6 which on amd rx 580 that i have performs worse than 1.0 or 2.0 from this client.To have support for directx you have to compile with directx support (angle). You didn't compile with dx9 support or someone who provided the .exe.
when i compiled few months ago i had to use 19, cant remember the error somthing 142 when using VS17Do I need to use VS17 or is it doable with VS19?