Search the Community
Showing results for tags 'ArmA3P'.
Found 2 results
I am trying to start Buldozer from Terrain builder, but i am getting the error as shown below: I already tried: This tutorial: Using arma3p Reinstalling Arma 3 Tools Restarting computer Following youtube videos Buldozer Configurator PMC Wiki arma3.exe instead of buldozer.exe Changing command-line args x64 version of buldozer I didn't try: Object Builder PS: Starting buldozer directly doesn't work as well, but starting arma3.exe directly in buldozer mode works, but arma3.exe gives the same error when i try to set it up on terrain builder, even copying the same arguments and the correct path. I am using latest Windows 10 build, and the latest version of Arma 3 tools My current Terrain Builder config regarding Buldozer is: Exe file path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe Launch Parameters: -buldozer -window -exThreads=0 -mod= -noAsserts -nologs -profiles=P:\Buldozer -cfg=P:\Buldozer.cfg -name=Buldozer Data directory: P:\ The P:\Buldozer.cfg file exists and was generated by Buldozer Configurator, i already checked the file and seems ok Any thoughts or ideas?
Hello, IÂ´ve installed the tools again yesterday and set up everythings Properly (P was set and A3p ran through fine). But as soon as I want to run Buldozer I get this f****** Errormessage that absolutely makes no sense. As from what I understand is that the error must rest somewhere in the command line, but it doesnt matter whether I leave the startup Parameters by default (as they come right after installation) or if I remove everythings. The errormessage is always the same (except for the removed entries from the Startup Parameters Commandline. Only one thing always remains the same. ItÂ´s this part of the errormessage quoted below. This part always stays the same, anyways what I do. So what the hell is that errormessage supposed to mean and why doesnt any attempt to fix it do absolutely nothings. - changed the Buldozer path as suggested after A3P ran through - I ran A3P meanwhile a couple of times - I changed the Buldozer.cfg that IÂ´ve recieved from someone where it works absolutely fine - I changed P - reinstalled ArmA3 tools - ran integrity check for the steam tools and for ArmA3 - I ran Buldozer with an absolutely clean Commandline ItÂ´d be great if someone knows whats causing this issue. I never ever ran into this in all those years before. May be itÂ´s a simple solution, but I cant see it at the moment. Thanks and regards Memphis