# Designing issues
# Levees are jumbled and crossing over.
**Symptoms**:
When you create levees in T3RRA Cutta, Ditch or Levee, the levee lines seem very ‘messy’. There are frequent line endings and levee paths sometimes appear to cross over each other
**Cause**:
The levees are spaced very closely. T3RRA software uses an algorithm that looks at the edges of individual raster pixels and problems can occur if the levee lines are spaced at a width of equal to, or less than, the pixel size.
**Solution**:
Resurface the survey data at a smaller pixel size. Then re-do the levees. The correct pixel size will depend on the slope of the land, and the required vertical distance between levees.
# Imported SWP+ ditch track names are too long.
**Symptoms**:
After importing SWP+ ditch tracks, you see that their assigned names are too long and cover most of the surface.
**Cause**:
Previously assigned names are imported along with ditch tracks.
**Solutions**:
Return to the Surface step and use the Edit Drains button to rename.
Click on the pencil and paper icon, rename drain, choose Ok, then Close.
# Drain Design freezing and/or producing jagged profile view OR Small Field design has jagged edge and difficult to see changes in elevation.
**Symptoms**:
After Applying drain design, the tablet freezes.
Profile view of drain is jagged.
Small field design has jagged edges.
Small field not defined enough.
When I am in the Drains Design step, the profile view of my surveyed drain appears ‘jagged’ and ‘corrupt’. I know what I am viewing in the drain profile window is not an accurate representation of the original surface.
**Possible causes**:
Pixel size is too large for thin drain.
Drain is long and the drain width is thin.
A drain survey was collected OVER a field survey (or visa versa).
**Solutions**:
Change Pixel size.
Change width of drain (only if the change will not affect implementation).
Image of profile view of drain with jagged drain line:
Image of small field with large pixel size:
Image of small field with small pixel size:
Solutions if drain and field surveys overlap:
Delete the field elevation points directly under the drain path of drain surveyed points.
Resurvey in Field survey mode pausing field collection of points when traveling over the drain path then change to Drain survey mode to collect the drain path that is clear of field elevation points.
# Attempting to save a PDF report throws an error.
**Symptoms**:
When attempting to create a PDF report on a tablet running Windows 8.1 an error message appears and no report is created.
**Cause**:
Windows 8.1 is missing some critical files the PDF creator relies on.
**Solution**:
Install the VC++ 2015 Redistributable files. These are available at [www.microsoft.com](http://www.microsoft.com). Use a search engine to find them. Choose the version that matches your tablet (32 or 64bit). Install on the tablet. The PDF creation process should then work.
# Markers not visible.
**Symptoms**:
Markers are not visible on the map surface, and you believe they should be present.
When you have created markers (Bench Marks ) in T3RRA Design and have exported your control file for T3RRA Cutta or T3RRA Ditch.
**Cause**:
A marker may have been given an incorrect elevation value, causing it to be well above or below the surface. This can happen for instance if the design was made in T3RRA Design and the marker was given an elevation of zero.
The markers have been exported without a height set, therefore will only show up in 3D underneath the surface.
**Solutions**:
1. Check to see that the marker is actually present. This can be done by tapping the ‘Delete marker’ button in the bottom right of any map-screen and seeing if the marker of interest is in the list to be deleted. If it is then close that dialog and then zoom as far out as you can. You will likely see the marker a long way above or below the surface. If the ‘Delete marker’ button is not present it means there are no markers available on the map.
2. There is currently no way of changing the elevation associated with a marker. Go back to the original source software and fix the issue there. If this is not a satisfactory solution please contact T3RRA to explain the use case and we will examine ways to achieve your goals.
3. When creating markers in T3RRA Design always make sure that you enter the value and tick the “Lock value” before exporting your control file. 
# My cut/fill map is totally a single color representing no cut and no fill.
**Symptoms**:
In the implementation or design phase of T3RRA software, you view a cut/fill map and it is a uniform green or gray color representing no cut and no fill (depending on your cut/fill color schematic selected in Settings). When you touch part of the map it shows the Cut/Fill value as being 0.
**Cause**:
1. Your original surface and your design surface are exactly the same. This happens if no design has been created. When surfacing first completes a “blank” design is created that matches the original surface exactly. As a cut/fill map is the difference between the original surface and the design surface it will necessarily be a map of zero values.
2. Your ‘Zero Cut/Fill Range’ is too large.
**Solution**:
1. Go to the design step of the wizard and create a new design.
2. Open **Settings > Application** and lower your ‘Zero Cut/Fill Range’
# There is an ‘offset’ cut area beside my drain.
**Symptoms**:
When burning a drain profile into a surface, one or more side cut areas appear that seem disconnected with the actual drain path.
**Cause**:
The side batter from the drain rises up through an existing surface that undulates in such a way that both cut and no-cut areas result.
**Solution**:
Increase the batter angle, or smooth the field surface before creating the drains (and create the drains based on the DESIGN, not the ORIGINAL surface). Alternatively, simply ignore the offset cut area.
# Drain Design error message ‘not downhill all the way’
**Symptoms**:
When designing a drain, you receive an error message:
**Cause**:
Parameters entered do not allow drain to flow downhill all the way.
**Solutions**:
Change parameters until they produce a drain that will flow downhill all the way. i.e. increase Max Cut.
# Drain Design error message ‘drains were affected by this operation’
**Symptoms**:
When designing a drain, you receive an error message:
**Cause**:
1. Elevation data was collected from low to high elevation where another drain connects.
2. Drain was split with the Split Drain tool.
**Solutions**:
Swap AB before designing so the drain is designed from high to low elevation.
