Tom_48_97

Full changelog and TECHREP

22-02-2021 Size: ~ 2 MB TOOLS Publisher Added: Support for Art of War DLC Steam configuration Changed: Incremented version number to reflect the current stage (1.025.2)

27-01-2021 Size: ~ 26 MB TOOLS Publisher Changed: To avoid confusion, the Custom Compositions are not longer displayed(*) Binarize Added: New predefined Preprocessor Macros (see CfgConvert changes) Fixed: An issue that would prevent Binarize to promptly exit once all the operations were performed Tweaked: Crash dumps are now more detailed CfgConvert Added: Support for new Preprocessor Macros ( __DATE_ARR__, __DATE_STR__, __DATE_STR_ISO8601__, __TIME__, __TIME_UTC__, __COUNTER__, __COUNTER_RESET__, __RAND_INT, __RAND_UINT, __GAME_VER__, __GAME_VER_MAJ__, __GAME_VER_MIN__, __GAME_BUILD__, __ARMA__, __A3_DEBUG__) Added: Support for #pragma directive and basic support for #if #else #endif Steam configuration Changed: Incremented version number to reflect the current stage (1.025.1) NOTES Binarize and CfgConvert share the same Preprocessor Macro definitions, meaning there are all available from both applications. (*)The Compositions can be managed from the Eden Editor

Sadly, we're aware of this issue and didn't manage to address it so far. I'll take another look and see if there is anything we can do.

Thanks for the information and the screens. To rule out a model/mod specific issue, can you, please, download the sample of plane, load Test_Plane_01.p3d into Object Builder and check if Buldozer displays the textures? It requires the Arma 3 data, and once loaded, it should look like this (fresh test).

Due to the update of the PhysX library, we had to update the tools too. In the install directory of Buldozer, can you check that the DLL folder contains the followings? F:\Futura P\dll>ls -R .: x64 x86 ./x64: GFSDK_SSAO_D3D11.win64.dll PhysXCooking_64.dll PhysXGpu_64.dll Tobii.EyeX.Client.dll PhysXCommon_64.dll PhysXFoundation_64.dll PhysX_64.dll ./x86: GFSDK_SSAO_D3D11.win32.dll PhysXCooking_32.dll PhysXGpu_32.dll Tobii.EyeX.Client.dll PhysXCommon_32.dll PhysXFoundation_32.dll PhysX_32.dll

Have you tried to define the config file in the Buldozer startup parameters? From Terrain Builder navigate to Tools, Settings, select Buldozer and add -cfg=path\to\buldozer.cfg to the launch parameters, mine is: -buldozer -window -exThreads=0 -mod= -noAsserts -nologs -profiles=P:\Buldozer -cfg=P:\Buldozer\Buldozer.cfg -name=Buldozer If this doesn't work, do you run any of the tools (and or Steam) as administrator?

The Profiling branch has been updated on Steam (the usual Dropbox and Google Drive will follow shortly). Please, note that clients that aren't running on the Profiling branch may still experience the issue. 1.98.146.356 new PROFILING branch with PERFORMANCE binaries, v02, server and client, Windows 32/64-bit, included Linux 32-bit server Fixed: Attempted fix of multiplayer desync connected with physics Fixed: A Zeus related server crash Tweaked: Small adjustments to improve the overall server stability You can find more information about the Steam branches on the community wiki, and share your feedback in this thread or on Discord.

Full changelog and TECHREP

08-04-2020 Size: ~35 MB TOOLS Arma 3 Tools Launcher Added: Support for the updated PhysX library (4.1.1) Changed: Updated health check Fixed: An incorrect tool-tip for the sound tools Publisher Added: Support for the Global Mobilization DLC and the Contact Expansion Added: Support for the Livonia, Weferlingen, and Weferlingen (Winter) terrains Binarize Added: Support for the updated PhysX library (32b and 64b) Addon Builder Fixed: A crash occurring when used in CLI mode with an exclude parameter DSUtils Fixed: The elapsed time displayed in the logs would return negative values Work Drive Added: Support for the updated PhysX library Steam configuration Changed: Incremented version number to reflect the current stage (1.023.1)

Yes, it would, but using DayZ Mod Licensed Data Packages which are yet to be released. The content developed by the community is and will remain under DML-SA. We will prepare the DayZ Mod Licensed Data Packages based on the data developed by us. You're correct, they should be released during the first or second week of July.

True that license-related things can be hard to understand (well, and to explain). In short, The data packages don't change but the way they can be used does. Then, the main thing for the Arma modding community is that DayZ Mod data can now be used in Arma 3 creations.

This is correct, I have updated the announcement (in all places), this only affects the Licensed Data Packages and nothing else. As mentioned in the announcement, all already released content doesn't change — their licenses remain in effect as they are. As written above (and updated in the text), this applies only to the Licensed Data Packages, released by us (Bohemia Interactive). Generally speaking, the game data are in no way impacted by this change, they are under their respective EULA. In other words; no, this doesn't allow anyone to use DayZ data in Arma 3, nor Arma 3 Data in DayZ. The DLDP (DayZ Licensed Data Packages) aren't planned for now and actually not even possible because the data get updated on a regular basis.

A few years ago, we released the Licensed Data Packages to the Bohemia modding community; a set of data and samples (e.g. weapons and vehicles from Arma 2) from our past games, so they can learn from examples and base new creations upon this content — to expand the Armaverse and others. These packages include configuration files, material files, 3D models, textures, and animations, as well as complete game data in the form of PBOs. We want to offer the same possibility to the young DayZ Modding community, by making most of the Public Data Package available under two new licenses which allow usage in DayZ. The following changes will happen: All Licensed Data Packages previously released under APL will also be made available under DPL. Users may opt for one or the other. All Licensed Data Packages previously released under APL-SA will also be made available under ADPL-SA. Users may opt for one or the other. A new set of Licensed Data Package containing DayZ Mod data (currently under DML-SA) will be made available under ADPL-SA. Users may opt for one or the other. The above only impacts the Licensed Data Packages released by Bohemia Interactive, it is to be noted that the licenses of all already released content won't change — their licenses remain in effect. Here, the summary of the new licenses: DayZ Public License (DPL) Attribution — You must attribute the material in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the material). Noncommercial — You may not use this material for any commercial purposes. DayZ Only — You may not convert or adapt this material to be used in games other than DayZ. Arma and DayZ Public License Share Alike (ADPL-SA) Attribution — You must attribute the material in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the material). Noncommercial — You may not use this material for any commercial purposes. Share Alike — If you adapt, or build upon this material, you may distribute the resulting material only under the same license. Arma and DayZ Only — You may not convert or adapt this material to be used in games other than Arma and DayZ. Here, an example of licensing for a mod using Public Data licensed under APL-SA/ADPL-SA: The mod may be released under APL-SA Is Arma only Can't be adapted to be released on DayZ The mod may be released under ADPL-SA Is DayZ and Arma 3 Can be adapted for DayZ and/or Arma We'd like to take a moment to remind everyone that it's in the interest of us all that the Steam Workshop, and any other user-generated content portal, remains an open and fair place. Please respect the work of others. If you'd like to include content that is not your own, seek permission from the original author, and add credits where they are due. It should go without saying that using assets from other games or other digital sources is especially risky unless there are explicit permissions to do so (i.e., in the EULA). If an original author has decided to take down content, do not re-upload it without permission. Server owners who want to use several mods on their server are invited to create Workshop Collections which are essentially groups of existing Workshop mods, letting the player subscribe to all mods at once, with respect for the author rights, and ensuring the included mods are up to date. Modding is a fantastic aspect of our games, and it makes the game more fun for everyone. There are many wonderful examples of inter-mod cooperation, community documentation, custom tools, and endless hours of extra gameplay (take the excellent Arma 3 Community Upgrade Project (CUP) as a perfect example of what can be achieved with these packages). We want to let our games be an open and creative platform for as many content creators as possible. Let's respect each other and keep moving forward together!

Full changelog and TECHREP