Lazza
Registered
HeadTilt Plugin v1.1 30th April 2015
This is a small plugin for altering the cockpit camera angle/position per-class, and optionally per car in that class. Each class (or vehicle) setting is saved and restored when you enter that car.
Download:
https://www.dropbox.com/s/ubajbm049tdqmxh/Install_HeadTilt_Plugin_V1_1.zip?dl=0
Installation: Extract and run the zipped .exe file and follow the instructions. The installer will ask for Administrator access in case your rF2 folder requires those permissions.
Alternatively you can extract the .dll files manually (they're in the archive) but please put them in the right place
Usage:
Start rF2, then quit out and check your Userdata\<player> folder for a HeadTilt_Plugin.ini file (not there? Check the plugin installation) Some basic settings will have been written including the "MenuKey" which is Y by default. This is the key you need to press to bring up the HeadTilt 'menu' when in the car.
Menu navigation and the angle adjustment is done via the rF2 'pitmenu' controls. So whatever buttons/keys you use to move up/down in the pitmenu, and increase/decrease values (like fuel, or tyre compounds) will be used to 'move' up/down/right/left.
Note: For simplicity I've used the Message Center to show what the plugin is doing. Most of the time this works fine but if it keeps displaying the same message a few times rF2 will no longer update it. If you wait a few seconds all the previous messages will 'time out' and you'll be able to see what you're doing again.
Main Menu:
When you press the HeadTilt menu key, you'll have these options you can cycle through with the up/down controls:
- Adjust class
- Adjust vehicle
- Clear vehicle setting (only available when you've already got a vehicle-specific setting)
Pressing 'right' on any option will enter that option. Pressing HeadTilt will exit the menu.
Adjustment:
Having entered the class or vehicle adjustment, you use the up/down and optionally the left/right controls to move the view around by changing the camera angle.
Optionally:
Holding Shift while adjusting will change the camera X (left-right) and Z (forward-back) position.
Holding Alt while adjusting will change the camera Y (up-down) position, and the Roll angle. (roll isn't very useful, and doesn't quite work how you might think)
Press HeadTilt to save the setting.
As per the note earlier, if you move back through previous settings quite quickly rF2 will stop writing the messages. If you're moving and it's not saying anything, just wait a few seconds for all the messages to turn grey, then it will start showing the current angle again when you move.
Class vs vehicle:
Your current vehicle class is shown in the expanded timings screen. Usually a single class includes a number of different cars, quite often physically identical. This means a single class-wide adjustment will be enough.
Sometimes a particular car may have a different camera setting, or actually be a different physical design. In this case you can adjust the vehicle-specific setting which will only affect that vehicle. 'Vehicle' is based on the defined vehicle text for the car; upgrades won't affect it unless they also affect the vehicle class, while multiple cars in the same team will be considered different vehicles even though they're almost certainly physically identical.
Clearing a vehicle setting:
The third main menu option, which will be available when you're in a car with a vehicle-specific HeadTilt setting, is used to stop the current vehicle having its own setting that overrides the class setting. The default option in the clear vehicle menu is Cancel, so press up/down to select confirmation and then press 'right' again to clear the setting. The view will revert to the class setting.
Extra configuration:
The HeadTilt_Plugin.ini file in your player folder is where all the class and vehicle settings are stored. At the top are a few extra settings you may want to adjust; for example you can alter how much the angle changes per input press. Note that all angles are expressed in degrees * 1000, so the smallest increment is 0.001°.
Issues:
- The displayed angles will be correct with the default Glance (left/right) and Look Up/Down angles, which are 0.75 and 0.4 respectively. If you change those values in your player.JSON the actual angles will change accordingly. For example: if you double the default glance angle, you'll be looking 90° left or right when the plugin says 45°.
- The position numbers don't have proper units. I haven't looked at what 1.0 actually means, but it's definitely less than a metre (likely a player.JSON or controller.JSON setting is affecting this).
- Not all cameras will let you adjust the angle or position. The 'driving' views, which you can cycle through using Insert, are usually ok. The various car mounted cameras, chasecam, etc, usually don't respond to angle changes but the position can often be changed.
- The plugin disables itself when you're not in the car in realtime. Cockpit replays at the monitor will not look the same as when you're driving, but this is a better option than making some camera angles unusable because the plugin keeps moving the camera. For the same reason the plugin will also disable itself when you toggle FreeLook.
- By default the plugin won't switch off when you 'Disable Hardware Plugins'. You can change this in the .ini.
Toggling FreeLook and HardWare Plugins in combination can lead to the plugin getting confused and applying its settings when it shouldn't. You have been warned
- If different mods use the same class text the plugin won't be able to tell them apart. Adjusting the vehicle-specific setting should get around this most of the time, because it's unlikely that both the class and vehicle descriptions will be identical.
- If a car class or vehicle description ends in 'orientation' it could lead to problems with different vehicles reading the wrong settings. This is unlikely.
Todo:
I may look into trying to read the player.JSON to compensate for non-standard glance/look angles, but this is low priority. People changing those values should be able to compensate for it themselves.
Please let me know if you have problems or (simple!) suggestions. Take a couple of minutes to get used to the menu navigation though - it does make sense once you get the hang of it.
This is a small plugin for altering the cockpit camera angle/position per-class, and optionally per car in that class. Each class (or vehicle) setting is saved and restored when you enter that car.
Download:
https://www.dropbox.com/s/ubajbm049tdqmxh/Install_HeadTilt_Plugin_V1_1.zip?dl=0
Installation: Extract and run the zipped .exe file and follow the instructions. The installer will ask for Administrator access in case your rF2 folder requires those permissions.
Alternatively you can extract the .dll files manually (they're in the archive) but please put them in the right place
Usage:
Start rF2, then quit out and check your Userdata\<player> folder for a HeadTilt_Plugin.ini file (not there? Check the plugin installation) Some basic settings will have been written including the "MenuKey" which is Y by default. This is the key you need to press to bring up the HeadTilt 'menu' when in the car.
Menu navigation and the angle adjustment is done via the rF2 'pitmenu' controls. So whatever buttons/keys you use to move up/down in the pitmenu, and increase/decrease values (like fuel, or tyre compounds) will be used to 'move' up/down/right/left.
Note: For simplicity I've used the Message Center to show what the plugin is doing. Most of the time this works fine but if it keeps displaying the same message a few times rF2 will no longer update it. If you wait a few seconds all the previous messages will 'time out' and you'll be able to see what you're doing again.
Main Menu:
When you press the HeadTilt menu key, you'll have these options you can cycle through with the up/down controls:
- Adjust class
- Adjust vehicle
- Clear vehicle setting (only available when you've already got a vehicle-specific setting)
Pressing 'right' on any option will enter that option. Pressing HeadTilt will exit the menu.
Adjustment:
Having entered the class or vehicle adjustment, you use the up/down and optionally the left/right controls to move the view around by changing the camera angle.
Optionally:
Holding Shift while adjusting will change the camera X (left-right) and Z (forward-back) position.
Holding Alt while adjusting will change the camera Y (up-down) position, and the Roll angle. (roll isn't very useful, and doesn't quite work how you might think)
Press HeadTilt to save the setting.
As per the note earlier, if you move back through previous settings quite quickly rF2 will stop writing the messages. If you're moving and it's not saying anything, just wait a few seconds for all the messages to turn grey, then it will start showing the current angle again when you move.
Class vs vehicle:
Your current vehicle class is shown in the expanded timings screen. Usually a single class includes a number of different cars, quite often physically identical. This means a single class-wide adjustment will be enough.
Sometimes a particular car may have a different camera setting, or actually be a different physical design. In this case you can adjust the vehicle-specific setting which will only affect that vehicle. 'Vehicle' is based on the defined vehicle text for the car; upgrades won't affect it unless they also affect the vehicle class, while multiple cars in the same team will be considered different vehicles even though they're almost certainly physically identical.
Clearing a vehicle setting:
The third main menu option, which will be available when you're in a car with a vehicle-specific HeadTilt setting, is used to stop the current vehicle having its own setting that overrides the class setting. The default option in the clear vehicle menu is Cancel, so press up/down to select confirmation and then press 'right' again to clear the setting. The view will revert to the class setting.
Extra configuration:
The HeadTilt_Plugin.ini file in your player folder is where all the class and vehicle settings are stored. At the top are a few extra settings you may want to adjust; for example you can alter how much the angle changes per input press. Note that all angles are expressed in degrees * 1000, so the smallest increment is 0.001°.
Issues:
- The displayed angles will be correct with the default Glance (left/right) and Look Up/Down angles, which are 0.75 and 0.4 respectively. If you change those values in your player.JSON the actual angles will change accordingly. For example: if you double the default glance angle, you'll be looking 90° left or right when the plugin says 45°.
- The position numbers don't have proper units. I haven't looked at what 1.0 actually means, but it's definitely less than a metre (likely a player.JSON or controller.JSON setting is affecting this).
- Not all cameras will let you adjust the angle or position. The 'driving' views, which you can cycle through using Insert, are usually ok. The various car mounted cameras, chasecam, etc, usually don't respond to angle changes but the position can often be changed.
- The plugin disables itself when you're not in the car in realtime. Cockpit replays at the monitor will not look the same as when you're driving, but this is a better option than making some camera angles unusable because the plugin keeps moving the camera. For the same reason the plugin will also disable itself when you toggle FreeLook.
- By default the plugin won't switch off when you 'Disable Hardware Plugins'. You can change this in the .ini.
Toggling FreeLook and HardWare Plugins in combination can lead to the plugin getting confused and applying its settings when it shouldn't. You have been warned
- If different mods use the same class text the plugin won't be able to tell them apart. Adjusting the vehicle-specific setting should get around this most of the time, because it's unlikely that both the class and vehicle descriptions will be identical.
- If a car class or vehicle description ends in 'orientation' it could lead to problems with different vehicles reading the wrong settings. This is unlikely.
Todo:
I may look into trying to read the player.JSON to compensate for non-standard glance/look angles, but this is low priority. People changing those values should be able to compensate for it themselves.
Please let me know if you have problems or (simple!) suggestions. Take a couple of minutes to get used to the menu navigation though - it does make sense once you get the hang of it.
Last edited:
