luki

I dont see what your problem is, you have an rvmat there. Just put .rvmat at the end if you mean that. Otherwise describe exactly whats your problem is. I highly suggest you use mikeros tools.

Afaik Visitor 4 can handle 8192 grid size. The mapframe system of Visitor 4 works probably totally different than in Visitor 3, i guess that problem is solved, long long time ago.

Small very rough example installing p drive and o2 AyShhgsgqnA

Same here, i tried several options and compared with a2 tool setup. I come to the conclusion its something in the exe as it says Arma2 No entry 'config.bin.cfgbuldozer'. Apart from that it works for the momment. Big thx to mikero for Arma3Pv1.7, you get a complete clean p setup with buldozer included.

ever tried to read the readme? and yes it is for arma3 and works flawless.

Theres still a missing ; in your example so its logical that he tells you water class is not there. class CfgMaterials { class Water[color="#FF0000"];[/color] class MUG_water: Water ...... I suggest you cleanup your config and seperate cfgAmbient and cfgLighting, like you can see in A2SM sample terrain config structures, saves alot of space in the config and gives you a clean overview.

Are you talking about some specific lamps or overall from arma2?

If you have objects or roads placed down or buldozer open while you import the png heightmap, visitor can/will freeze till its complete imported. Solution for this is export your objects then delete them, import new terrain and import the objects again. Or just wait till its imported.

Delete your Layer foldier and do a clean import, double and tripple check the pathes in layer.cfg and rvmats and texture layer settings withing visitor project parameters. in the main config.cpp with the ilsPosition[], ilsDirection[],ilsTaxiOff[], ilsTaxiIn[]

I have my rgb 8bit overlay.bmp in my source foldier and can load it without problems. Did you tried with other images and checked the size,transparency and the "bk" button is pressed down within visitor? i usualy use 1:1 sat image pixel size.

Some of them are visible as small red dot and also visible in buldozer. But most of them "i guess" are placed under the terrain and you cant acctualy grab them anymore. (only with replace objects/delete) It makes not much sense to strugle with this atm. My Tip: Wait for Visitor 4 and prepare other stuff like sat/mask, terrain, configs, textures ect. PS: Just checked it... if you create a terrain with 1m high and you place the rocks, you can see them all on 0.0 height.

New Video about the Game World XAbHmE73p7o

The Landscape looks amazing! and finally a medieval RPG with no Dragons, a Dream comes true.

Exactly like Sealife says... just use the include, dont open the class in the main config ......class CfgWorldList { class mb_manaisland {}; }; class CfgMissions {}; [color="#A52A2A"] #include "cfgSurfaces.hpp"[/color]

Amazing initiative! Count me in.

In his case he is using: External Viewer: "C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\arma3.exe" I recommend to put the exe in the arma work dir, so you dont need to care if theres an update or change. my example: http://forums.bistudio.com/showthread.php?168995-A3-Toolsuit-Installation-Issues&p=2564547&viewfull=1#post2564547 External Viewer: "P:\buldozer.exe"

Take a look at the a3 map configs and update/change yours accordingly.

Sounds a bit confusing, your addon name would be custom_map_anims.pbo and @Menutest is just your modfoldier..... If you only want to change that single Intro you can just change the path to your new intro file: Simple example Addon: "TUT_MyCustomAnims.pbo" class CfgPatches { class TUT_MyCustomAnims { units[] = {}; weapons[] = {}; requiredVersion = 0.1; requiredAddons[] = {"A3_Map_Stratis"}; }; }; class CfgMissions { class Cutscenes { class Stratis_intro1 //magic happens here { directory = "TUT\TUT_MyCustomAnims\scenes\mynewintro.Stratis"; }; }; }; And in this case the prefix is tut\tut_mycustomanims

BinPBO is called Addonbuilder now and is actually the gui for the tools afaik. You can simply use Filebank for this job, at least that works for me. You can get all the info you need in the Wiki and use the new A3 Tools. http://community.bistudio.com/wiki/Category:Arma_3_Official_Tools Example of how i use it for testing: FileBank.exe "C:\Users\XXX\Documents\Arma 3 - Other Profiles\ATSCHE\missions\legos.sat_practa" But you can add more options to it. I suggest you take a look at mikeros dos tools, as they are more flexible and easyer to handle.

If you updated your configs to a3 standart then it works in a3, no matter if you used v3 or v4. Also depends on the assest you used for the map. Compatibility wise there are few new functions and features missing, like the new Road Network technique and Normal Map Layer. I personally dont use the normal map layer for now and basicly do the same as in a2 You can manualy do all this, but i would not do to much in visitor 3 atm (as we hopefully get a new version soon), especially when it comes to object placement of the new a3 assets.

You can find the Textures in the Arma Licensed Data Pack. Arma_Licensed_Data_Pack

Did you start your new installed oxygen via steam - tools at least once? There shouldent be any misconfiguration, even if you have the old and new version installed.

As usual the rpt of the exe you use gets stored in the respective appdata folder You have 3 Ways to aproach and minimize errors: First, check Bulldozer rpt (appdata\local as usual) Second, check binarize logfile (where you point it in addon builder) Third, check the ArmA rpt (appdata\local as usual) If you have an error when binarizing then it must show it in the binarize log. Binarize checks also other configs in your project directory keep that in mind. Happend to me several times, that i couldent find any errors in my configs and found out that it was caused by other configs in my project dir.

I use P drive like i always do and have no problems. -What i did was simply just backed up my E:\TOOLS\ArmAWork folder (what represents P drive). (renamed it to ArmAWorkA2 whatever) -Created new empty E:\TOOLS\ArmAWork folder. -Used mikeros arma3p to extract all the content to the new folder. -copy the arma3.exe and req files to the new folder and renamed it to buldozer.exe -Start o2 at least once via steam tools and set the new path in the ext viewer options "p:\buldozer.exe" -window -buldozer -noland dont forget to add the list of files to copy directly in addon builder options *.pac;*.paa;*.rtm;*.sqf;*.sqs;*.bikb;*.fsm;*.wss;*.ogg;*.wav;*.fxy;*.csv;*.html;*.lip;*.txt;*.bisurf;*.shp; Content of my P Drive: I still can use old installed tools this way, withouth deinstall or reinstall something.

Same here, lsd party. I guess its a3 buldozer, old or new o2 doesent matter. But happens too when i just set the time to night in env editor without loading anything.