PathCamera vs. Camera
by Kuju Manila · in Torque Game Engine · 05/27/2007 (7:17 pm) · 0 replies
Hello guys!
I've been dealing with PathCameras lately and I'm surprised that PathCameras are actually not Cameras at all! We've been using fairly inefficient workarounds on PathCameras by copying the PathCamera transform onto the "viewing" Camera transform. Plus, there are lots of issues with PathCameras with regards to making it the control object, etc.
So, to make PathCameras behave just like Cameras, I modified the engine code of PathCamera to inherit Camera class instead of ShapeBase (changes occured accordingly). I'm happy with it -- as far as I know.
Now, I'm really wondering and at the same time worried, if what I did is RIGHT. I mean, what was the reason the Torque Engine base code of PathCamera not to be a Camera in the first place? Can anyone from GG explain this? Based on my changes of the engine code, will it cause more harm than good? Any design gotchas I should know?
I've been dealing with PathCameras lately and I'm surprised that PathCameras are actually not Cameras at all! We've been using fairly inefficient workarounds on PathCameras by copying the PathCamera transform onto the "viewing" Camera transform. Plus, there are lots of issues with PathCameras with regards to making it the control object, etc.
So, to make PathCameras behave just like Cameras, I modified the engine code of PathCamera to inherit Camera class instead of ShapeBase (changes occured accordingly). I'm happy with it -- as far as I know.
Now, I'm really wondering and at the same time worried, if what I did is RIGHT. I mean, what was the reason the Torque Engine base code of PathCamera not to be a Camera in the first place? Can anyone from GG explain this? Based on my changes of the engine code, will it cause more harm than good? Any design gotchas I should know?
