moricky

Author and debug console settings were accidentally not saved correctly, will be fixed in the dev build soon. Meanwhile, using author and enableDebugConsole properties in description.ext will still work. I'm afraid I'm unable to reproduce the scenario name problem. Are there any specific steps I should take? Could you please specify which scripts sometimes don't work, and how do they malfunction?

Appears to be a problem in AISS mod, I recommend to contact its authors and notify them about the issue.

code = "f_var_debugMode = %1"; Arma 3 params system doesn't support any code property, where did you find this? When the code is not called, f_var_debugMode variable is not declared and the error appears.

I fixed the code example, thanks for noticing. class Title and class TitleWide were indeed declared incorrectly, and class Controls was supposed to be class Controls: Controls

Thanks for the detailed report, It helped me to quickly locate the issue. Fixing it now.

The notification is intentionally prepared with two message styles - note and warning - in order to clearly indicate to user what kind of message is being displayed. I recommend to use the pre-defined style to avoid confusing the user. Yes, you could use pink text on lime background, but the fact that something is possible doesn't necessarily mean it's useful.

This is an obsolete command used in experimental Arma 2 Xbox 360 version. It doesn't work in Arma 3, unlocking Steam Achievements is handled directly in the engine.

I fixed the bug with missing scripting help in the init field. As for the size, it's not as straightforward, because the same attribute window layout is used also for modules, and they often have custom attributes which you want readily available without much scrolling.

I recommend to check in-game tutorials, are major actions (and especially those which are different from the 2D editor) should be described there.

We're still evaluating what to do with the 2D editor. We'd prefer to offer only one tool which is officially supported, but I understand that many advanced users like you would want to retain access to the 2D editor. One of the options is to have it still available from the main menu, but only using some keyboard shortcut (similar to hove the old 3D editor prototype was accessed). A mod could even map it back to a button. What do you think about such approach?

You're welcome ;) Honestly, trying to replicate tree structure in a listbox gave me headaches too (this is long before commands for tree operations were introduced).

Could you please provide specific steps, so our QA can take a look at the issue? Namely: * Which units are affected? * How are you checking the skill value?

I started documentation on the Community Wiki, will expand it as we implement the new sorting. Eventually, it will contain the list of all categories and subcategories, and description of their usage.

Seems I've read the "maxZeroing" property from the wrong directory. Gonna be fixed in the next dev build update.

To make things a bit clearer, I renamed the Preferences option to "Binarize New Scenario Files". I've also added the checkbox directly to the Save Window, so now you can see if the scenario is going to be binarized and change it if needed when saving it. Should be available in the next dev version.

Workaround for what? Simply open the scenario in Eden, disable binarization in General attributes and save it again.

At this point we're not making any changes to SQM format, so there's 99% chance your current scenarios will work fine even in the full release.

Scenarios are now binarized by to save space and improve loading times. Most people will never edit SQM manually, that's why we decided to make it default behavior. Advanced users can toggle this per scenario (in General attributes) or in editor preferences.

Actually, it seems the date is based on when the Steam downloaded the file. Instead, could you please open the addon file in a text editor, and on the first line, you'll see something like this: sreV prefix a3\data_f_exp_b product Arma 3 version 86189 config.bin Could you please tell me which version is your file (e.g., 86189 in the example)?

Could you please go to Arma 3 addons folder, find data_f_exp_b.pbo file and post here its date of last modification? Config in that addon already contains class 3DEN in CfgPatches, so no external addons should be required.

While Eden Editor (3DEN is its system name) is currently available only in the dev branch of the game, dummy 3DEN addon is present even in the default branch to prevent any issues. It's been like that already since the previous patch. Where are you unable to open them? In the 2D editor? From Scenarios menu?

We're planning general object revision as we get closer to the release. As a result, most of existing objects with classes will be made available (scope = 2) and in more logical categories than now. The reason why it's planned for later is because it will also affect 2D editor. However, vegetation or rocks won't be among these, because they intentionally don't have config to save performance.

Vehicle contents won't be available in the Garage, but it's likely they will be configurable through the same attribute which will be used for ammo box configuration. Attaching is on our roadmap, but with very low priority, possibly even after full release.

Or, you know, you can use deleteVehicleCrew to delete vehicle crew ;)

We'd like to introduce searching by class names or even by tags (e.g., Marshall would be tagged as "Armor", "APC", "NATO", etc.), but that will have to wait for the next year. Right now, we're focused on Arsenal and Garage implementation. 3DEN is a technical name (pretty much 3D Editor New), it was selected long before we were sure about public name. There was similar situation with Zeus, which is named Curator in data.