Search the Community

Hi map/terrain/environment/world… makers, this is, after working at BI/BISim for almost 10 years, my first topic created here at BI forums. In my defense, I’m mostly active in Arma 3 Maps Terrains Skype’s group, but the topic I want to share with you deserves to be discuss here(skype has short memory and is not as comfortable as forums, for such kind of discussion). The Topic? It’s of course the bLandscapeTools(bLT), an addon for Blender I’ve been already working on for the last 8 years. The main reason I started this addon was: already knew Blender wanted to improve my python scripting skills, as I like to automate or at least speed up processes many handy world creation features were not available back then, are not available now and will never be implemented in BI/BISim world creation tools Necessary to note that I never intended to write a tool which would take over the world BI/BISim tools, but rather try to fill gaps(small/large) in terrain development. Blender is a 3D modeling tool(and much more), but you can’t expect fancy features which can handle big chunks of terrains with millions of objects on it, it has its own bottlenecks and limits, but even back then I could see, that the advantage of having possibility to import terrain mesh and its textures to Blender and start placing environment content much more easier way(comparing to Buldozer) or even modeling content over a terrain is a feature that will never come into Terrain Builder/Buldozer. By sticking together Blender’s default features like sculpting, painting + powerfull API I was basically able to add many time consuming and “Visitor4/TerrainBuilder hard to get implemented” features into Blender. Let’s stop talking for now… check out my talk at BlenderConference2016 about the Blender Terrain Tools(Edit: just currently I changed the name to bLandscapeTools) so you guys can make an image of what I’ve been working on. There are some features which will be really hard(almost impossible) to release because they are closely bound to BI dev content like raw(non-binarized) P3Ds, but on the positive note bLT has some handy features not even mentioned in the video(like quality assurance tools) Why now? After the conference I got contacted by individuals and even teams, asking me where they can download the addon as they would like to have their hands on it and give it a try. So I decided to start releasing the tool bits by bits to people so they, hopefully, can have a fun time play around with bLT. Also, the fact that this year(2017) it's going to be 10 years at BI/BISim or in other words working with the RVengine, as well as, Paul Pelosi(bushlurker) suddenly passing away, made me to do this decision and release the tool. It’s also going to be a challenge and something new to me, releasing my tool to other people, it needs a change of thinking about the tool, fix some parts of the pipeline..etc. and that may take some time. How? There’s plenty of how in the front of me. I need to figure out a way how to share the tool with you guys. Github, Blender market I have in my mind right now. As mentioned already, there are features hard to release(raw P3Ds). In this case I’ll have to ask someone here in BI, if company would be willing to release let’s say at least last LODs of assets so they could be imported into Blender and used within bLT. I use Blender for over 10 years, so I’m pretty comfortable with its workflow, but this doesn’t have to apply to a newcomer. Therefore, I’ll have to take some steps to make bLT even more user friendly than it is right now. I plan to make quite some tutorials how to use Blender and bLT to user’s satisfaction. Currently, Blender development is at the stage where quite a big major changes are being implemented and to be released with Blender 2.8. There’s going to be plenty of great new features such Viewport update(supporting PBR shaders), new Layers, Workflow system and much more. This means that I’ll have to re-think some of the bLT features to support all these new improvements once they’re released. Therefore I don’t want to do any major touches into what exists in bLT now. I hope that the improvements done for 2.8 will take bLT a few steps further again, as it already happened with the transition from Blender 2.4 to 2.5+. So once again, I’d like to ask you to have a look at my talk, if you have any questions please don’t hesitate to ask. It will help me to move on with releasing the tool as well as to know how the features should be done to help you create a map for any RV engine related project. When? Release of the '0-th' or 'Introduction' version is planned on the end of summer holidays. Progress will be tracked here. Subscribe to my personal youtube's channel here. Tools Github's here. Twitter Cheers, Miro

SQF-VM The SQF emulator A fully working, open-source Virtual Machine for the scripting language of the ArmA Games. Links GitHub Repository Discord Invite Discord Bot Authorization Panel (for adding to your server) FAQ How to use this thing? To start using the SQF-VM, you just have to double click the executable. What can it be used for (examples)? Most obvious example is: you are using a laptop while traveling and wanna test some SQF code. More advanced users might even use this for unit-testing their code. Are there command line parameters available to eg. use this for unit-testing? Yes, there are. To get all, start the tool via command line and the parameter -? How to use the debug interface? There is documentation available on the github page inside of Documentation/Debugger. What is supported? To check what currently is supported and what is not, you can use the `help__ "name"` command. If it outputs proper descriptions, the command is fully supported. If it does not, then the command is not yet implemented sadly. I found a bug, what shall i do now? Try to narrow down the problem as much as you can and then head over to the github issues section to report the bug. I got a question that is not answered in here, what to do? Ask your question in this thread or in the discord channel and i might add it to this list 🙂 Downloads All releases can also be found inside of the releases section of the github repository. 1.0-RC1 Alpha 0.1.4 Alpha 0.1.3 Alpha 0.1.2 Alpha 0.1.1 Alpha 0.1.0 Changelog 1.0-RC1 -/-

Marceldev89s original script, from which I forked. Introduction: a3update.py is a simple, lightweight python script that handles: Updating the arma server Installing and updating mods Generating an importable preset.html ideal to accompany @Dahlgren's Arma Server Web Admin which as of yet does not provide those features. Here is an example modpack.html I setup for a friend using this script Download (Github Gist) Requirements: SteamCMD, Python3, Python3-urllib3, a Steam account with Arma 3 Installation (Ubuntu): Follow the initial server installation instructions on the BIWiki `sudo apt-get install steamcmd python3 python3-urllib3` `wget https://gist.githubusercontent.com/Freddo3000/a5cd0494f649db75e43611122c9c3f15/raw/4854ac4a78c7d347ade1e9ab9fcac147d7dbe3e9/a3update.py` Edit the following settings: STEAM_CMD - Point this at your steamcmd installation, alternatively simply enter "steamcmd" STEAM_USER - Your login username STEAM_PASS - Your login password A3_SERVER_DIR - Point this at your A3 server installation directory A3_MODS_DIR - Point this to where you want your mods to be symlinked. If you are using the suggested Arma Server Web Admin, make this the same as A3_SERVER_DIR A3_KEYS_DIR - Point this at the Keys folder in your installation directory MODPACK_NAME - Change this to what the title should be for the A3 launcher imported preset MODPACK_PATH - This will be the output preset.html file. Point this to wherever you wish for it to be stored, such as /var/www/html for the Apache web server MODS - Your list of mods in the format "@mod_folder" : "https://steamcommunity.com/sharedfiles/filedetails/?id=450814997". Avoid special and capital characters SERVER_MODS - List of server mods, only add folder names here. These also have to be present in the MODS list. Server keys will not be copied for these mods OPTIONAL_MODS - List of server mods, only add folder names here. These also have to be present in the `MODS` list. These mods will not get symlinks in your A3_MODS_DIR, but will have their server keys copied. DLC - List of CDLC in format "Name" : "https://store.steampowered.com/app/1042220/Arma_3_Creator_DLC_Global_Mobilization__Cold_War_Germany/" Optional: Install Arma Server Web Admin `chmod +x a3update.py` // Might be a good idea to limit access, as you have your password stored in plaintext Run it! `./a3update.py` Importing preset via URL: Open the A3 Launcher, go to mods, select "PRESET" at the top right and "IMPORT" Copy the link to the modpack.html (Example: https://somewebsite.com/modpack.html) Paste it into the "File name" field and press Open Notes: This has only been tested on Linux, though I wouldn't be surprised if it also works on Windows Known issues: Does currently not handle installation and updates of CDLC Doesn't work well with 2FA due to how steam stores login tokens Optional DLC is not kept when preset is imported With larger mod lists some data may fail to transfer to the launcher, therefore if you intend to keep the server public you'll want to run less than 15 mods. You can increase the amount of transferable data by shortening each mods mod.cpp file, making each mod take less space to transfer. Alternatively, you can use the ACE checkPBOs framework to make sure players are running the correct mods. License: MIT License Credits: @marceldev89 from who I forked this project

Arma Dev for Visual Studio Code Version 0.0.12 - DOWNLOAD | CHANGELOG Building Arma 3 mod made easier using the Arma Dev tooling extension This Visual Studio Code extensions will optimize your workflow on building and signing pbo's, preview dialog controls and automate execution and installation. Features Build your extension or add existing into the Arma-Dev configuration Pack server and client pbo files (incl. signing) with a single command Preview Dialog control files (*.hpp) Generate private keys Install the client mod into the correct game directory Run and debug (using *.RPT file) on the fly Usage Before using the Arma Dev extension, please make sure you have properly installed the Arma 3 Tools from Steam. Open your existing Arma (server / client) and run the Arma 3: Configure command to setup the project. Please refer to the Configuration section for further details Below you can find all available commands Arma 3: Configure: to setup the project Arma 3: Pack: to pack pbos defined in your configuration file Arma 3: Binarize: binarize cpp files from explorer context menu Arma 3: UnBinarize: Unbinarize bin files from explorer context menu Arma 3: Run Server: start the arma3server with server mod path included Arma 3: Run Client: to start the game from your local computer Arma 3: Run Client (With Logging): to start the game and display the logfile Arma 3: Generate Key: generate a private key to sign the client pbo's Arma 3: Transfer Files: transfer server pbos to destination server using SFTP Arma 3: Toggle Code Live: please read the below "Toggle Code Live" section for further details Configuration The configuration file is located in .vscode/arma-dev.json and contains the following options. title: The title of your project (no used yet) name: The short name of the addon (this name is used as output folder) author: author name buildPath: destination folder of all pbo files being generated privateKey: the private key path being used to sign the client addon serverDir: all server directories a pbo files should be created for (E.g. core and core_config) serverUse32bit: use legacy 32bit version of arma3server.exe serverMods: additional server mods being loaded when running arma3server clientDirs: all client directories a pbo files should be created for (ussualy its one or none) clientMods: additional client mods being loaded when running arma 3 version: a version number to track possible changes (not immplemented) ftpConnection: setup SFTP connection using host, username and password (optionally path) ftpConnectionFile: setup SFTP connection by using a separate file postProcess: run some additional scripts once a command has been successfully executed - see "Post Processing" Toggle Code Live PLEASE READ THIS CAREFULLY With "Code live" you can edit *.sqf files while Arma is running. It uses symlinks (refering to its workspace source) and the -filePatching startup parameter. A proper configured $PBOPREFIX$ for every addon file is required So, how to use it Run the command Arma 3: Toggle Code Live to create all necessary symlinks into "Arma 3\x" directory use Arma 3: Run Client to start Arma with all necessary parameters (-filePatching) use Arma 3: Run Server to prepare a server configuration and run it Customize the files defined in your workspace source folder. Open the in-game debug console and either use execVM or preprocessFile* to "reload" the changes. If you use a preInit script (which DOES NOT use compileFinal) you can use execVM too Please be aware of the following Server config.cfg requires allowedFilePatching = 2; (which is ussually the case when running with Arma 3: Run Server) No server side signatur verification will work, so verifySignatures = 0; to bypass it You can toggle Code Live to either use the source or PBO file (located in buildPath) Some commands / settings (like compileFinal / config.cpp) cannot be overwritten (anti cheat) HINT: Use [] spawn { compile preProcessFile "x\youraddon\yourfile.sqf" }; instead of execVM "x\youraddon\yourfile.sqf" from console to update file modifications Post Processing The post processing option (defined in .vscode/arma-dev.json) can be helpful to run additional tasks once a command has been successfully executed. An example of running a script when for instance all files are transfered to the remote can look the following: "postProcess": { "transferFiles": "./restart-server.ps1" } Please note these commands are always executed locally Requirements Arma 3 Tools (http://store.steampowered.com/app/233800/Arma_3_Tools/) Visual Studio Code PLEASE MAKE SURE STEAM IS RUNNING AS IT IS REQUIRED FOR PACKING Extension Settings arma-dev.logLevel: setup the log level (Info | Debug | Error) arma-dev.dialogAxisMode: How to display the dialog control axis (0 = truncated, 1 = original) restart required