Player Area Trigger Component
#1REMOVED
Last edited by fkhaller on Sat Nov 04, 2017 11:47 am, edited 4 times in total.
Re: Player Area Trigger Component
#2Super. Wish something like this came with 5.4. The SensorVolume Component isnt the same.
Re: Player Area Trigger Component
#4why do you use malloc(free) instead of new(delete)?
area should have onoverlap event.so you dont have to calculate every update.
area should have onoverlap event.so you dont have to calculate every update.
Re: Player Area Trigger Component
#5I did the update so that It could be used if players came into a multiplayer game and since i am working with someone else and we are not working on the same repo events where more tricky too coordinate. Also there are usually not very many players in the game so I did not see the update as a problem. About the mallocing I like mallocing and im more used to it.why do you use malloc(free) instead of new(delete)?
area should have onoverlap event.so you dont have to calculate every update.
Re: Player Area Trigger Component
#6Fkhaller actually created this area trigger component for our project, and he published it here although he signed NDA with us
Cryengine tutorial videos on my Youtube channel! Check it out !
https://www.youtube.com/user/MusicForLifePL20
https://www.youtube.com/user/MusicForLifePL20
Re: Player Area Trigger Component
#7Still wondering why the upcoming AreaTrigger Component wouldn't be good enough though? Anyways. You guys need to sort this internally. No need to do that publicly.
Re: Player Area Trigger Component
#8I was told that I could share this idk ill take it down anyway. I am confused I made this post before the NDA, but i dont want to have any bad blood.
Re: Player Area Trigger Component
#9That's sad though. Was the AreaTrigger Component specifically mentioned in the NDA?
Re: Player Area Trigger Component
#10No lazivh, I didnt think about it, someone can take this down no reason for this thread now i guess.