[Ascent] Does Vmap Collision system actuall work?

[Diversion]

Okay well I did everything as stated on the Wiki for Ascent and it still doesn't work...

The finished vmaps folder was moved back in the Ascent folder as well as the collision.dll file and no difference when Ascent is loading.. I don't dismount upon entering a building.

I also noticed Kameleon's has two different collision.dll files with different sizes.. I have a feeling this is where the confusion/problem is.

Jay

[mihai00792]

for now dont work vmaps becouse you create the folder buldings (have 1.7 gb) put in folder on ascent server but dont work, npc pass over walls and other.

[WiKKiD]

Just tested it on my own compile, and it's working fine. Not sure what's going wrong for you, but if everything is compiled correctly, and all the files are in the correct places, it should work.

[Diversion]

I'll probably just have to start making my own compiles..lol. I'm pretty sure my vmaps were set up properly.

[aceindy]

Yes it works; I rewrote a patch for inns to stay rested inside.
This patch relies on collision detection.

But yes compile your own;
Collision detection is disabled by default in c++ and it has to be compiled with it enabled (meaning. you can't enable it anymore afterwards if it has been compiled without it).

:technolog :busted_co

[Diversion]

I don't understand why you'd ever compile without it enabled... They should just release it always enabled.. if you don't use vmaps, it just won't work.. and if you put the vmaps folder in the ascent directory, it will detect and launch collision detection.. You know what I mean? Kind of pointless.. Just make the default auto-detect and not give a choice. Yes it's probably sometimes buggy, but if you don't want to use collision they should have just have a switch in the conf file for it.

[WiKKiD]

/** Enable/disable 3D geometry calculations
* Warning: This may be resource heavy.
* As of last update, it was nowhere near complete. Only enable for dev use.
* Default: Disabled

That'd be why. (Taken from AscentConfig.h) :)

[Diversion]

/** Enable/disable 3D geometry calculations
* Warning: This may be resource heavy.
* As of last update, it was nowhere near complete. Only enable for dev use.
* Default: Disabled

That'd be why. (Taken from AscentConfig.h) :)

I understand it's CPU intensive.. however, even if it's always enabled, if you don't place the vmap folder in ascent, vmaps won't be used; therefore collision support will be OFF.. So either way, you're green.. It gives users a choice.. Want VMAPS? Put vmaps in the directory.. Don't want vmaps? Don't have the vmaps in the ascent directory.

[aceindy]

ok..vmaps won't work... but it is not OFF;
So it will still be cpu intensive as all calculations are made,
It's only that the result of those calculations is useless, as core can't load the vmap at end of calculations.

[rr2739]

for now dont work vmaps becouse you create the folder buldings (have 1.7 gb) put in folder on ascent server but dont work, npc pass over walls and other.

dont use his compiles....

Make your own and enable collision support.

[mihai00792]

man i make my own copile from 2.4 but .. i know how to enable i know every think but dont work ... npc pass over walls