L.E.A. Help Please
mwnciboo wrote:
LEA in ARMA2 was dynamic and could be updated on the fly in the editor with ARMA2 open and running in the background, the loadouts would magically appear in game as you created them.
THIS IS NOT THE CASE FOR LEA ARMA3 AT THIS TIME!
If you try to update or re-initialize, with ARMA3 already running in the background you will re-order the profiles and it will cause you problems because your Profile Names will not match your loadouts e.g a Medic can become a Sniper and other such problems, I believe this is due to the engine re-ordering the name in ALPHA-NUMERIC order independently of the loadout, rather than as created in the Editor and is possibly linked to the issue below. Still trying to establish how it is re-ordering profiles.
Also if you try to save profiles while ARMA3 is open and running, I believe LEA locks changes as the Data is being accessed by the @LEA MOD, so if you change a profile and save it, it will say "saved" but will not actually save.
I'm not sure why you're seeing this behaviour Mike, but it works fine "dynamically" for me, just like it did in Arma 2.
Procedure:
- Arma 3 running
- Running LEA as admin
- Profile Editor tab
- Create Profile
- Edit Profile
- Profile > Initialise LEA (F4)
Technically what is happening:
- As a profile is created/edited it is
immediately stored in
...Program Files (x86)\LEA_A3\profiles\units- LEA automatically reorders the list alphanumerically based on the profile description
- When you click 'Initialise LEA'
--- the list of profiles is written to
...\SteamApps\common\Arma 3\Userconfig\lea\Loadout.sqf--- the loadouts are written to:
...\SteamApps\common\Arma 3\Userconfig\lea\Loadout_XX.sqf- When you 'Apply Loadout' in game, @LEA reads the sqf files generated in the step above
These SQF files are simple scripts. Nothing in the @LEA mod or in game prevents these text files from changing.
This is how I was using "LEA" for months prior to it's official release, by manual editing of these two files - quite straightforward to cut and paste from A2 profiles (with the odd class name change and slightly different code execution) - all can be done on the fly with A3 running.
Two rules:
1) DON'T drop new downloaded profiles into
...Program Files (x86)\LEA_A3\profiles\units when LEA (the graphical front-end) is running
2) DO use Profile > Initialise LEA when you want to see your changes in game
