peterigz
Forum Replies Created
-
Posts
-
I’ve just updated the library and implemented CheckCollision and PreventOverlap functions. I added a couple of examples to the example folder as well, see CheckCollision.monkey for an example of use, it’s pretty straight forward 🙂
FOV would be an angle, so the arc to check within. The direction is the way the observer is facing, so it will check either side of the direction. So if FOV is 45, then it will check 22.5 deg to the left and right of the direction. This is infinite though so you might want to put a separate distance check if needed.
I should update the module so it uses strict really, not sure why I didn’t!
Hey, I’ll take a look tonight, I see that I’ve omitted examples of using the collision code, I do have a few so I’ll upload them tonight. This is a conversion of the Blitzmax version which had a CheckCollision function that would use casting as you mentioned, but I probably didn’t convert it because callbacks were involved. You have to implement callbacks differently in Monkey so as a result I didn’t implement few features of this collision system yet (like quadtrees for example), but I can’t see why I couldn’t make a checkcollision function that just returns a tlCollisionResult.
Will let you know how I get on 🙂
Glad you got it working, sorry I haven’t responded until now but I’ve been moving house and currently have no internet! It would be interesting to see if this behaviour is replicated on the blitzmax version… I’m not convinced it should work like that so will investigate, at least you have it working for now.
That’s odd, the only I can think that would do that would be if the config file got damaged some how, or just couldn’t be read from.
I’ve just updated the Monkey module so it will work with the latest version of Diddy and Monkey.
Thanks for the bug report! 🙂
Hmm, it uses diddy just for the XML parser, so maybe that’s changed somehow, I’m not sure. I’ll test with the latest version of everything when I get home tomorrow.
I’ve uploaded the little shootem up example that’s here on this site so you can have a look at the code and see if you’re doing anything different, link here: http://www.rigzsoft.co.uk/files/MonkeyExample.zip
It’s quite small so hopefully it’s easy to follow.
How are you adding the effects to the particle manager? Are you making sure that you copy them first? Maybe you could post a little snippet for the shield hit.
Hi, I do recall this when I was testing the Monkey version but can’t remember what it was, maybe something to do with emitters that are relative, or something to do with how you’re setting the particle manager origin. I have used it with a virtual resolution and had it working fine, I just need to look at the code again.
I’m at work at the moment but will check when I get back home. Have you got a simple bit of code to replicate the issue in the meantime?
Well done for getting out of the day job 🙂
You’re right about the space creature, I remember looking into that and thought I’d fixed it. Was quite a while ago now, maybe it’s crept back in somehow. It could well be a rounding issue. If I remember correctly that effect has single emitters that never die, they just have sub effects that spawn the tail of the worm. So it’s something in way that they rotate I think, thinking back it maybe have been something that happens when the angle passes from 360 back to 0, something jolts so they slowly spiral outwards. I can’t remember for sure I’ll have to take a look again 🙂
Many thanks for your contribution Damucz, that sounds great! 🙂
With regards to unzipping the eff files for use, this sounds similar to the monkey implementation. You can export the effects files as .zip files in TimelineFX to make things easier. I guess if the image files are in the same folder as the xml you only need to extract the file name from the path without any need to edit the xml manually, that’s what the monkey version does anyway.
I wish I had time to learn c++, I could remake the vaders example, but sadly I’m knee deep in PHP for my day job… Oh well, one day 🙂
An email contest would be cool, not sure how many would participate. Unfortunately time is my biggest downfall at the moment to organise these things! There is a video tutorial about creating an explosion from scratch here: http://www.rigzsoft.co.uk/video-tutorials/
Peter Ward has very kindly made available his C++ code for TimelineFX, which you can find in this post here:
http://www.rigzsoft.co.uk/c-code-for-timelinefx/
Perhaps I should GitHub it?
