The hallmark feature of the Carpe Iter controllers is something we call "autoprofiling". This feature requires that NGH is used and running (including the Carpe Iter NGH Accessibility service) on your Android device.
Autoprofiling means automatic controller adaptation and re-configuration to each supported application at the moment the application is opened.
With autoprofiling active, the controller is automatically reprogrammed for each supported application without any intervention from the user.
The autoprofiling is active by default and is indicated in the NGH - Controller - App profiles configuration settings by indicating "Automatic profile".
As cool as the autoprofiling is, there are situations where it is more useful to lock the profile for a specific app to limit room for software glitches. Primary situation of this kind is a rally raid race, where you might want to lock the controller into the profile for the app you plan to be using for the race navigation, such as the Terrapirata.
You can achieve that by clicking the "Profile Selection Mode" settings item and selecting the app, for which the profile should be locked. To be able to change the Profile Selection Mode, the controller must be connected and selected in NGH (otherwise the option is greyed out).
If the app uses keyboard keycodes (such as the Terrapirata), the keycodes are hardwired to the controller and the controller will function correctly in the selected app even if the Carpe Iter NGH Accessibility service is disabled for any reason. This brings additional robustness to the system in situations, where reliability is paramount, such the rally race.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article