BOX cam 0.7.0

Good news if you use x4fab's Shaders Lights Patch (0.1.23preview75 or newer, afaik):
Due to the introduction of new python functions, BOXcam is now fully armed and operational. No longer the tedium of installing a weird track camera or dealing with loss of tracking over time. Simply push 'activate' and everything is handled.

- BOXcam defaults to 35 fov (you can use PhotoMode app to adjust this and other camera settings same as normal free cam)
- track cameras are at least trying to load MIN_FOV now, still need to figure out the math for MAX_FOV
- in all cases, camera tracking is now locked in. You can mess up the pitch/roll in boxcam mode (because once it's running it doesn't try to fix these and the way it changes heading is just AC's default method) in chasecam mode it applies its own pitch algorithm so it's fine.

- Added new parameter for chase cam, controlled by F- and F+ buttons on the app.
F- will make the camera follow the direction the car's pointing less closely
F+ will make the camera follow the direction the car's pointing more closely
Can be edited directly in chase.ini as 'facing_mix':
0.0 is the old behaviour, always have camera point the direction the car's traveling.
Default value is 0.9 which mostly follows the direction the car's pointing, but has a little leeway to reduce bumpiness on sudden changes of direction.

- Added new parameter for chase cam, edited directly in chase.ini as 'lookat_offset'.
This moves the point on the car that the camera pivots around; leaving it at 0 is probably for the most part the best option, but it adds a lot of flexibility for use in replays.
For example you can set it up as an onboard view while maintaining the smoothing the app adds, or set it to pivot around the front axle instead of the centre of the car so the back swings out more in corners.

Using pitch in the chase cam will cause the camera to drift slightly sometimes, I recommend using 0 pitch. But as a measure to make it less annoying, the "Activate" button, when used while boxcam is already active, will reset the variables to eliminate this drift. Camera will flicker a bit since it needs to start from 0 again and move back to the car.

As before, if you value chase.ini settings, back it up before installing. Adds buttons to pitch up/down the chase camera & stores as before.

Installing:
Back up chase.ini if you had 0.5 already and want to keep those settings. Then extract the contents of the 7zip.

Changes:
In the config
- clickstep controls how far the camera is moved on each button push (default 0.1m)
- target_trail can now go below a value of 1 without causing issues
- smooth_power added, basically controls the amount of time smoothing of car direction (for old behaviour, set to 0)
- percent_vertical added, adjusts how much the car moves up and down on the screen on hills (for old behaviour, set to 1)
- cars can have their own configs - copy the [Chase] section and call it [Chase_carname]. Examples included in the default of the file.
In the app
- chase cam mode now has adjustment buttons
- 6 direction arrows that move the live position
- 'save base' - which stores current position for all cars
- 'save car' - which stores the current position for the current car.
- box cam buttons are now hidden on app launch until you click 'activate' (probably mode buttons should be hidden too since they don't do anything)

Enabled the same as the other cameras - pick the custom track camera named BOX CAM, hit 'Activate', then select 'Chase Cam'.

Essentially it behaves like chase cams in certain other games.

While it has some wiggle room for smoothing reasons, this cam will mostly point the direction the car is traveling. At low speeds it stops moving because it can't tell where the car's going accurately, though the actual limit is about 1cm/second so it's seriously low speeds. Other than that it should be fairly smooth.

You can adjust its relative distance to the car using chase.ini, and like the other cameras, use cameras_x.ini to adjust fov and so forth (unfortunately the app itself can't set these, they need to be preset into the track).

Changed imports to work with AC 1.3 & 64 bit.

- reads the spline angle from track cameras.ini, slightly more faithful reproduction of camera behaviours
- maybe other bugfixes? I squash them as I see them

- track cameras with splines will now load and play them, rotation not yet correct
- spline cam button will play the spline defined in the app folder's spline.ini, for a way to develop spline motions (every time you hit the button it'll reload from file)

If the app didn't work because of failed import, now it should.

- is_fixed track camera setting now respected

- initial attempt to read track cam files & imitate them
- currently does not respect static cameras, splines, & tracks with no AI route
- no way to change FOV for the foreseeable future because the python API cannot change it

As always, read the READ ME.txt to learn how to install & run the app properly.

- all camera movement has been wrapped into the ACCamera class, which provides utility functions like getPosition() (note: not using API calls to get this data, so it's only as good as the data the constructor provides)
- approximate method (still not recommended - please read the README and use the track cam) is improved