Rig settup for smooth use?



Piddy having watched your videos I noticed some tools you use lag on my machine and not on yours.

dual E5420 2.5ghz
4gb ram
geforce 8800 gtx 768mb
x-fi fatal1ty
OS XP 64bit
(load seems balanced between all cores but does not exceed 17% for some reason)

Screen resolution is 1680 by 1050 and I am using two screens set as individual.
I have not tried to change resolutions but I have tried to make the BTB window smaller.

Tool tested was the blend terrain tool.
Overall size in memory for BTB 438mb.

Couple of my buddies experience even more delay and up to 100% of cpu usage. When I use the shift function with the blend tool the tool can not keep up with my cursor and uses 17% of processing power (again spreed between all cores)

Advice welcome, when it comes to "finishing" touches increasing the speed of this tool to act as fast as it does in your videos would be a great help.


Mar 16, 2009
Ive notice that the grid size makes a big different on my end if its set to a small size. (less than 100m) Not sure if this will help with your problem....


Ive notice that the grid size makes a big different on my end if its set to a small size. (less than 100m) Not sure if this will help with your problem....
Just tried this, my setting was 10m (stock), and it didn't seem to help.

I tried turning off grid in 3d view and when that didn't help I set the grid to 1000m

ty for suggestion though


May 4, 2009
I'm one of Damp's Buddies that experiences this problem, I get lockups (~5-10 seconds) every time I click the mouse to add a blend, ~90% cpu usage, ~500mb memory used.

Here are my system specs.
System Information
Time of this report: 5/12/2009, 02:43:44
Machine name: MIANIAK-3D93EC2
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp.080413-2111)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, MMX, 3DNow (2 CPUs), ~3.0GHz
Memory: 2046MB RAM
Page File: 394MB used, 3544MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode

Display Devices
Card name: NVIDIA GeForce GTX 260
Manufacturer: NVIDIA
Chip type: GeForce GTX 260
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_05E2&SUBSYS_82911043&REV_A1
Display Memory: 896.0 MB
Current Mode: 1280 x 1024 (32 bit) (85Hz)
Monitor: Default Monitor
Monitor Max Res:
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.8250 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 3/27/2009 10:03:00, 6186880 bytes
Full dxdiag


May 4, 2009
I have a big problem, I pretty well much can't continue with my track atm due to the "lockups" I'm getting every time I need to move something which is interfering with the flow of the way I do things.
I have tried a few things, I have opened the original project up which is just the track with elevations (I save that separately incase I need to go back to it) and i can use all the terrain tools smoothly, the texture blending too, the move tool etc, they are fast and work fine.
With the full project I removed everything, deleted all the walls, deleted all the string objects, deleted all the trees and extra buildings I had put in and I was still getting lockups. I removed all the texture blending on the terrain and still lockups. Then I started removing terrain till I was down to just the track and a small piece of terrain and still I was getting lockups.
I am at a loss as to why it's doing this and I really need to fix it so I can continue.


May 4, 2009
I was just about to edit my post and noticed you had replied. As usual I spend days trying to figure something out and as soon as I post I find the problem myself.

It's not the undo, it was In the materials tab, I had merged large sections of terrain together to organise them in groups. I just went through and split them all into separate smaller sections and now it works fine. Even without hiding unselected its still smooth.


Ahh yes ... that would slow things down and it would also hurt frame rates on longer tracks.
Looking back I guess the section of terrain I had was too large.

I broke off about 150 polygons from the section I was working on and that seemed very smooth.