The problem it caused is that some users have the expected P4IGNORE=.p4ignore.txt configuration setting while others don't. The issues is further exacerbated by the fact that last year Perforce handling of P4IGNORE changed last year. Previously, P4IGNORE was in effect only when explicitly set. However, now, when P4IGNORE is not present, it defaults to .p4ignore and .p4ignore.txt. What it all means is that users who had 'P4IGNORE=.p4ignore.txt' were not using the few incorrectly named .p4ignore, while users who didn't have P4IGNORE at all, were affected by them. It turns out that a few of the .p4ignore files had incorrect definition in the past, which led to Perforce issues that didn't seem reproducible on machines with the expected P4IGNORE configuration. After renaming the files, all users, regardless of the environment, should be affected in the same way. The incorrect .p4ignore rules have been augmented in CL 35021865. #rb wojciech.krywult #rnx [CL 35457520 by wojciech krywult in ue5-main branch]
live_link_vcam
A rebuild of the Live Link VCAM app for Flutter, enabling cross-platform deployment.
Tentacle Integration
This project depends on the Tentacle SDK located in Engine/Restricted/NotForLicensees/Source/ThirdParty/TentacleSDK.
We use some Tentacle SDK functions through Dart's Foreign Function Interface (FFI). Dart bindings for these functions are automatically generated using ffigen and checked into source control.
If you need to regenerate them, first set up ffigen (see https://pub.dev/packages/ffigen), then run the following command in the root VCAM project directory:
`dart run ffigen --config ffigen_tentacle.yaml`
Pigeon
This project uses Pigeon to automatically generate platform channel bindings for native APIs.
See pigeons/README for more information.
Signing Certificates
To setup signing certificates, follow the instructions outlined in this article
Add your android-key.tks to android\app folder and key.properities to android\. The gradle files are already setup
to read these files when app bundling