and geodata from l2j mobius?Посмотреть вложение 77767
another example of problem that comes from movement is this
i m using l2jmobius.
and geodata from l2j mobius?
Looks as your character buged after airbind
its 2019Which version of mobius is this?
etinas fate , protocol 152Helios? Infinite Odyssey? I don't even know what was in 2019 Mobius.
But it seems to me its a version that uses the typical l2j movement... and the amount of work needed to improve it is a lot.
I cannot agree with this statement that it uses the typical L2J geo engine.Helios? Infinite Odyssey? I don't even know what was in 2019 Mobius.
But it seems to me its a version that uses the typical l2j movement... and the amount of work needed to improve it is a lot.
I cannot agree with this statement that it uses the typical L2J geo engine.
I know for a fact that in 2020, L2jOrg, based on Mobius, was using a geo engine that uses L2D format, adapted from ACIS. I know so, because I spent sh1tload of time digging while trying to debug it to no avail. I even went as far as to purchase a license for ACIS just so I could get access to their latest version of the said GeoEngine and asked for permission to implement it to ORG, which was granted. I implemented it, but the improvements, while there, were simply not enough. You had to have exquisite/flawless geodata, else it would be glitchy AF.
The said Geo Engine was/is not the typical L2J Geo Engine, nor it used the typical geodata file format. I made a comparison between that engine and the one from L2Scripts' HF build, and they were nothing alike.
In fact, the more I dug into it, the clearer it became to me that it was inferior to the old L2J. So much so, that many who had used it, including ACIS, have moved away from it.
To the creator of the thread - my only advise is to make sure you use some premium geodata, and not one created by automation tools like the `l2mapconv`.
Поиск пути и геодвижок это разные механизмы, с разными задачами.
Геодвижок - это система которая предоставляет информацию о ячейке мира размером 8 на 8 точек(количество слоев, высоту для каждого слоя и NSWE для каждого слоя) по заданным координатам. Все. Ничего другого геодвижок делать не должен и не обязан.
Поиск пути - это намного более сложный механизм, который строит путь из отрезков для движения из точки А в точку Б.
Следовательно, если вы стоите в точке мира и ваши координаты совпадают с расчетными координатами заложенными в геоданных, то геодвижок работает корректно, а все проблемы стоит искать в механизме поиска путей.
Я говорю про то, что геодвижок это очень простой механизм и в нем в принципе практически нет частей, которые могут работать «чуть-чуть» не правильно. Т.е геодвижок либо работает нормально, либо не работает в принципе. 99% проблем - поиск пути.насколько я понимаю, это всетаки взаимосвязанные вещи, которые могут компенсировать косяки друг друга. И в примере топикстартера проблемы возникают вроде от косяков и того и того.
А так же координата в клиенте почти никогда не совпадает с координатой игрока на сервере, и есть весьма большой допуск, как минимум по Z. иногда в целый этаж здания )
Я говорю про то, что геодвижок это очень простой механизм и в нем в принципе практически нет частей, которые могут работать «чуть-чуть» не правильно. Т.е геодвижок либо работает нормально, либо не работает в принципе. 99% проблем - поиск пути.
It also doesn't contain any improvements regarding casting / attack visibility checks,
Я нахожу странным, что это не очевидно для вас.I have no clue why Aristo would make such a separation and go as far as saying the GeoEngine was a simple mechanism, especially given the fact that you can rewrite it however you like and name it whatever you like.
Honestly, I do not know what geodata those sources use, but regardless, I am aware of the amount of work needed to fix all the movement related issues. I have dealt with it on several packs and it takes weeks, even months to clean all the issues and make it work without problems. I don't even know how to price such kind of work. Without investing that much time, I might be able to fix some more critical issues, such as going through castle walls or falling through ground, but fixing movement glitches, desynchronizing (rubber-banding) and so on is problematic. Depending on your movement system, it might ignore geodata completely when underwater or flying, like vanilla l2j does.etinas fate , protocol 152
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?