Skip to content
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

Integrate movement maps into the core #1

Open
ghost opened this issue Sep 2, 2011 · 7 comments
Open

Integrate movement maps into the core #1

ghost opened this issue Sep 2, 2011 · 7 comments
Labels

Comments

@ghost
Copy link

ghost commented Sep 2, 2011

Movement maps by faramir118 have reached a stage where they should be integrated into the core, to provide for a broader spectrum of people using, and testing the system.

The goal of this is to integrate a clean, usable version of movement maps into the mangos-zero core, removing all the road bumps we may (or may not) hit while doing so.

@ghost ghost self-assigned this Sep 2, 2011
@ghost
Copy link
Author

ghost commented Sep 10, 2011

Commit c3ab7d6819f0ca04d550549263d316607047ae28 added the Recast library into the build process.

@ghost
Copy link
Author

ghost commented Sep 10, 2011

Commit 0721d0dc1584cb674d8b7fbe96ea9aea2a721b54 made Recast aware of the different navigation meshes used for MaNGOS maps.

@ghost
Copy link
Author

ghost commented Sep 10, 2011

Commit c0c1571a3e4c741835a1ed4b8752a065e7fab337 added the changes to the map extraction tools, and also introduces the movement map generator in contrib/mmap/.

This is a change which is not backwards compatible. Extraction of all maps has to be redone with the updated tools, and old map files will no longer work.

@ghost
Copy link
Author

ghost commented Sep 14, 2011

Commit 2481ca9c3324a6486fb50516c1cb6895310c7f8f contains the core changes required to support movement maps.

This change also is not backwards compatible. There are a few open ends here which we'll correct, and - as pointed out by faramir118 - the extraction process needs to account for multiple map versions in 1.12 MPQ archives.

One further requirement before this can be considered done is to properly document the process of using maps, and also describe the usage of recast, detour, and the recast demo application.

@vermie
Copy link

vermie commented Sep 14, 2011

Also need to solicit contributions to the default off-mesh connections list

@ghost
Copy link
Author

ghost commented Sep 14, 2011

Probably a centralized location for that? Besides the need to document the how

@KuraiNeko
Copy link

We should take some test's with offmeshes places.
And make offmesh db after some researches in world.

Also we should solve mistiq tile unloads on zero branch.

And we have big problem with hover moments.
Hover added in WoW later vanilla times.
Andway's of work hover moments on classic is unlearned now. We have no info.

When we used mmaps on some positions where 'stand fly' ( hover called in master now - exist ) we have recalculetion by z coord. And creature fade on flour. It ugly exploit and should be fixed.

Priority:
1 - some more backports from mmaps-master branch - try make et evening.
2 - We SHOULD found problem with tile unload. I try found in Debug but have not debug info in console. Need more test's from all staff.
3 - We need sniffs. We need make 'fly stand' system to zero. We need hover analog now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants