It would be nice to have some _optional_ smoothing applied to the camera movement (as seen in F3's spectator). It makes it easier for recording cinematics and is generally nicer for the eyes. I'm not sure what the math is for it, but it's like an easing function in JavaScript for example easeInOutCubic smooths the animation on both start and end points.
This is something I've considered implementing, I don't think it's very hard to do but just haven't got around to investigating and testing an implementation yet.
It's also a feature request :stuck_out_tongue: It can stay open though
:+1:
Shouldn't that just be camCommand "inertia on"? Never experimented with that command but it may be worth a try.
Yes, although it first requires the camera code to be rewritten using the cam commands (which I recall having odd experiences with)
Is it possible to use the old camera.sqs code since that supports the Bulldozer controls by default so there would be instant controller support?
camera.sqs
O_O
I mean, if you want to use that why don't you just use that instead? :smile:
Silent, that should not be a problem. You are using a camera, thus using that command should be fine, if it works at all... I know some camera commands are completly broken though.
I would appreciate that feature. One of the things CSSA3 is still better in as of now.
Inertia - Command works just fine.
@BaerMitUmlaut Yeah I've tried it before, and the command works, however I seem to recall that it didn't move as expected even though the code was otherwise the same as now
It's been so long since I looked at this that I can't remember what my issues were with the cam commands, but a recent dev branch changelog means I'll probably look into it again once it's in stable:
Fixed: The camSetDir script command was working incorrectly
An update on this:
The spectator overhaul that is now merged to master is using a camcurator camera object so that it can make use of the engine driven movement controls associated with that (massively reduces code complexity and overhead). Unfortunately a side effect of this is that camCommand "inertia on" is not supported by that camera object.
I won't close the issue as unsolvable as it's possible there's still a method of implementing this (perhaps we can make our own camera object that supports everything we need?).
the easiest thing would be a call on https://community.bistudio.com/wiki/BIS_fnc_cameraOld which is a really basic camera with inertia toggle and zoomability. would be sufficient for most cases.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.