second: it is basically open, in that you can write whatever c modules you want for it, and they provide documentation how to do that.
third: if you want help doing this, I can come in before class tomorrow and help. what you want to do sounds easy -- there are plenty of ways to do everything you are saying. I have no idea what your feedback loop thing is about -- right now, the currentframe is being spit out at every frame -- the issue I saw with your patch was the the way the movie wasn't stopping unless qmetro was off. I didn't have time to look into this, but it's most likely the problem.
Posted by will at February 23, 2004 11:12 AM
well, i seem to just have boatloads of trouble pulling anything out of the objects provided. perhaps this is my own ineptness.
extensible, fine. but it doesnt seem easy to expose a lot of the information i know is lurking about in these objects. but then it might just be the visual nature that is throwing me off.
and id love to sit down with you tomorrow and look at it...say...2.30?
maybe then ill stop looking like such a dumbass.
wait, no thatll never happen.
yeah, the help objects are sometimes not that great -- the lurking factor is large, in that you know the answer is there somewhere, but you spend a lot of frustrating time trying to find it...
2:30 is fine. it'll be nice to take a break from the godawful collision detection for a bit.
max is a weird program -- takes a lot of manhours to start feeling comfortable.
first: max is by definition oo
second: it is basically open, in that you can write whatever c modules you want for it, and they provide documentation how to do that.
third: if you want help doing this, I can come in before class tomorrow and help. what you want to do sounds easy -- there are plenty of ways to do everything you are saying. I have no idea what your feedback loop thing is about -- right now, the currentframe is being spit out at every frame -- the issue I saw with your patch was the the way the movie wasn't stopping unless qmetro was off. I didn't have time to look into this, but it's most likely the problem.
Posted by will at February 23, 2004 11:12 AMwell, i seem to just have boatloads of trouble pulling anything out of the objects provided. perhaps this is my own ineptness.
extensible, fine. but it doesnt seem easy to expose a lot of the information i know is lurking about in these objects. but then it might just be the visual nature that is throwing me off.
and id love to sit down with you tomorrow and look at it...say...2.30?
maybe then ill stop looking like such a dumbass.
Posted by tripp at February 23, 2004 11:18 AMwait, no thatll never happen.
yeah, the help objects are sometimes not that great -- the lurking factor is large, in that you know the answer is there somewhere, but you spend a lot of frustrating time trying to find it...
2:30 is fine. it'll be nice to take a break from the godawful collision detection for a bit.
max is a weird program -- takes a lot of manhours to start feeling comfortable.
Posted by will at February 23, 2004 11:20 AM