Jump to content
Sign in to follow this  
lecks

Can't start Terrain Builder

Recommended Posts

Hi,

I've tried everything I can think of but can't get Terrain Builder from Arma 3 tools to start at all (nothing happens when I go to start it). The log files in TerrainBuilder\Logs show the following:

=====================================================================

== D:\Steamapps\SteamApps\common\Arma 3 Tools\TerrainBuilder\TerrainBuilder.exe

== "D:\Steamapps\SteamApps\common\Arma 3 Tools\TerrainBuilder\TerrainBuilder.exe"

Exe timestamp: 2014/12/06 16:53:49

Current time: 2014/12/29 13:39:10

Type: Public

Version: 124233

=====================================================================

Debugger info - Unhandled exception.

=======================================================

-------------------------------------------------------

Exception code: C0000005 ACCESS_VIOLATION at 0157DA7C

Version 0.00.124233

Fault time: 2014/12/29 13:39:10

Fault address: 0157DA7C 01:0046CA7C D:\Steamapps\SteamApps\common\Arma 3 Tools\TerrainBuilder\TerrainBuilder.exe

Prev. code bytes: 7C 64 83 78 08 00 7C 5E 83 38 05 7D 59 8B 4E 60

Fault code bytes: 8B 49 14 8B 49 60 85 C9 74 0C 8B 56 58 50 52 FF

Registers:

EAX:00E0F8E8 EBX:0F6FDD99

ECX:00000000 EDX:00000600

ESI:09268020 EDI:01DA66A8

CS:EIP:0023:0157DA7C

SS:ESP:002B:00E0F8D4 EBP:00E0F96C

DS:002B ES:002B FS:0053 GS:002B

Flags:00010293

=======================================================

Call stack:

Stack 00E0F8D4 00E0F9BC

Debugger info - Applying offset 1113b70 to mapfile

mapfile: D:\Steamapps\SteamApps\common\Arma 3 Tools\TerrainBuilder\TerrainBuilder.map (empty 1)

Debugger info - Generating minidump please wait.

note: Minidump has been generated into the file Logs\TerrainBuilder_2014-12-29_13-39-10.mdmp

Arma 3 Tools Diagnostic is as follows:

http://pastebin.com/KWbnY9Ji

I'm using Windows 8.1 64 bit. 32gb ram. Plenty of HD space. Arma 3 tools are in D:\Steamapps\SteamApps\common\Arma 3 Tools . Steam is on C:\Steam .

All other Arma 3 Tools seem to work properly, as does Visitor 3.

I have tried:

- Uninstalling Arma 3 Tools / deleting remaining files and registry entries, and reinstalling.

- Setting up P: several different ways. Currently have it as a physical drive with all the Arma 3 files unpbo'ed in there (using Mikero's tools).

- Running terrainbuilder.exe directly and via the Arma 3 Tools Launcher (through Steam and just from the .exe).

- Running everything as Admin or as a normal user.

- Installing Windows 7 64 bit in a Virtual Box, then installing Arma 3 Tools in Steam on it, and mounting the P: drive I use on my normal machine. This worked (although it doesn't display properly).. so it's obviously something to do with my Windows 8.1 setup. I really don't want to do a fresh Windows install.

I just can't see what I'm doing wrong.. if anyone can help it'd be greatly appreciated.

Share this post


Link to post
Share on other sites

You have installed your P drive with the A3 tools from Mikero, normal this works perfect! (if it was done right)

(small guide) if you do not know how to install:

when your Pdrive is installed correctly only launch TB directly from the .exe ,not from A3 tools Launcher.

Share this post


Link to post
Share on other sites

Thanks for the response. I believe I have the P drive set up correctly. It works using the same P drive when launching Terrain Builder from the virtual machine. Pretty much the only things I haven't eliminated (because I'm not sure I can) are:

- My steam folder setup? Having Steam on a separate drive to Arma 3 Tools/Arma 3. I have tried with arma 3 tools in my normal steam folder with the same result.

- Some bad registry entry somewhere? I tried deleteing all the bohemia/arma ones I could find and starting from scratch to no avail.

- Some kind of permissions issue? I generally run Steam and Arma 3 in adminstrator mode. I've given full permission to arma 3 tools, arma 3, and P: drive to 'Everyone'.

- Windows 8.1 issue?

If you have any other ideas, please let me know.

Edit: I have followed that video from scratch too.

Edited by Lecks

Share this post


Link to post
Share on other sites

Thanks for the suggestion, I hadn't tried that but I just did now and it didn't work (nothing happens when I click the shortcut).

Share this post


Link to post
Share on other sites

Try this, delete your TB folder and then go to the steam library right click on your ARMA 3 Tools and choose properties, then on Tab local files, then verify integrity of tools cache, and let it reinstall your TB folder. See if that helps

Share this post


Link to post
Share on other sites

I have deleted the whole arma tools folder (as well as tried uninstalling it) and let steam redownload it, but unfortunately it didn't help.

I also tried copying the Arma tools folder from the Virtualbox PC (where it launches successfully), and that doesn't fix the issue.

Just to be sure, does anyone else run Terrain Builder on Windows 8.1 64 bit?

Share this post


Link to post
Share on other sites

You have probably already done this but a lot of people overlook these when reinstalling or doing a fresh install, have you made sure all the VisualC++ x86/x64 and .NET redistributables are installed correctly?

Share this post


Link to post
Share on other sites

@Uro1: I hadn't thought of that but I just tried 'repairing' them all (just doubleclicking on all the files in arma 3 tools\_commonredist) but it made no difference :(.

Share this post


Link to post
Share on other sites

I can't seem to find the thread but someone was having problem with the Poseidon editor and it turned out he was missing some Visual C++ runtimes. I think he was on Windows 8.1 as well. The runtimes he was missing were not the Arma ones. Actually, we might be able to figure out if this is the problem by checking which ones you have installed against mine.

-edit

Behold :P

hNMsspV.png

You probably don't need all of them so if you're missing some, I'd start at the most recent and work your way down from there. Hope this helps.

Edited by BadLuckBurt

Share this post


Link to post
Share on other sites

Damn, I thought you were on to something then BadLuckBurt. I had significantly more redistributables in there than you have, but uninstalling the extra ones didn't help.

before: http://snag.gy/uLHe2.jpg

after: http://snag.gy/KMZQM.jpg

Same stuff in the log after fixing it to look like yours.

I have also tried all sorts of compatibility modes including Windows 7/Windows 8.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×