EasyRoads3D V3 Beta Manual





When I select the main Road Network game object a crossing prefab gets selected

This will happen after you created a new crossing prefab and instantiated it in the scene. Make sure to finalize it when you are ready tweaking it. You can do that by clicking the Exit Prefab Editor button in the Inspector or by clicking one of the toolbar tabs at the top in the Inspector. You will be asked to save changes to the prefab if there are changes. Afterwards the main Road Network game object will be selected automatically. As long as the new crossing prefab is not completed. this prefab will be selected when selecting the main Road Network game object.


Roundabouts are not correctly instantiated and connected to the first or last marker of a road

For now avoid instantiating a roundabout directly to the first or last marker of the selected road. Instead use the other way to Instantiate intersections in the scene, by selecting the crossing prefabs tab . Select the roundabout from the list of available crossing prefabs, hold the SHIFT key and click in the scene where you want to position this roundabout. You can now connect roads to the prefab or start new roads by dragging the red roundabout connection handles. For full details click here.


The Roundabout geometry does not update after changing to the radius, resolution or after adding / changing a connection

Before creating/ adding the connections of a roundabout it is recommend to first set the radius and resolution correctly. The number of possible connections depends on the resolution and the radius and the width of the connections. If you make changes to the radius or resolution when connections already exist it could be possible that connections cannot be rebuild. You will see warning messages in the console when this occurs. You can try repositioning connections, starting at connection 1, by carefully checking the white middle handle and outer green handles positions. The green handles turn red when that connection cannot be created because it is either to close to the start or end of the roundabout (the white outer handle at the fixed position) or because it is overlapping another connection. But the easiest way to solve this, is by removing all connections first and then start adding new connections, the geometry of the roundabout will rebuild.

This will be further optimized, for now it is recommend to avoid this situation by first setting the radius and resolution correctly. In this case the roundabout geometry will only not rebuild when the currently selected connection overlaps another connection. You can fix this by either changing its position using the position slider or by changing the width of the connection.


Roads connected to a crossing bend to fast affecting the shape of the road

This will be further optimized, for now, try positioning the first marker closer to the crossing.


The connectsd road sidewalk do not update after activating / deactivating the sidewalk on the connection prefab

This will happen when the road is connected to a connection prefab on both ends. This will be fixed. For now, please check the other connection sidewalk settings on the corresponding road side and make sure they match.


I can't select road markers outside the terrain boundaries

When a marker for some reason is positioned outside the terrain boundaries you can select it by carefully moving towards the marker over the road mesh.


Road marker cannot be attached to crossing connection, the road geometry and the crossing connection geometry matches but the connection shows in red

This can happen when sidewalks are active but the outer sidewalk handle is disabled (meaning no sidwalks for the attached road). Select the specific crossing and make sure the outer corner handle is green (active) when the road on that side does include sidewalks.

This will also happen for custom crossings when the geometry structure of the road does not match the custom crossing connection.


The terrain is clipping through the road or the road is floating above the terrain

There are several situations that can cause this:

1) the Unity terrain object stores height values in decimals between 0 and 1, meaning it is impossible to apply negative height values. The roads must be at or above the terrains game object Y position.Also take into account the nature of spline shapes. When you place two markers (A and B) exactly on the terrain objects Y position and a third (C) raised a bit higher, the road shape (spline curve) between A and B will go slightly below the terrain objects Y position, the terrain will be rendered above the road in this area because it cannot be pushed lower. Random tilting & Bumpiness values below 0 should also be avoided with road at terrain y = 0.

2) the Unity terrain object is grid based, it is impossible to add terrain points for more detail. The bigger the heightmapscale (terrain size vs heightmap resolution) the less flexible you are with road shapes. Enough terrain points must be available to adapt the terrain to the road shape changes in that area. This for example will clearly become visible in sharp bends with also significant height changes in the bend. Possibly the same terrain points are used to adapt the terrain to the road height at position A and the road height at position B which is not good. You can see this when zooming in and switch the scene view to for example Texture Wire which will also show the terrain geometry.

3) the same can happen when roads or road segments are to close too each other, at least two terrain points must be between the two roads, one leveled to road A, the other leveled to road B.  When the same point is used on both roads it is very likely the terrain will either pop through the lower road or the higher road floats above the terrain at that position.

[show clearly screenshots also divining the critical area (the area between the indent values)]

4) Also please check the status of the Left and Right Indent Alignment dropdowns in the marker section of the road. The default value is "Align with the road". One of the other options will result in a small or larger gap between the road and the terrain. The purpose for these option is custom terrain deformation when walls or terrain mesh overlays near the road edges are used. One thing that have an automated affect on this are side objects marked as Terrain Surface Object in the side object manager? Assuming that the specific side object shape will cover that area for more terrain detail it will keep the terrain itself more at the original height.

5) When using customized terrain deformation settings, tilting on the roads and reasonable road height differences in that area, it is more likely that the terrain will poke through the terrain. This will be further optimized. For now try to lower the road tilting and/or height differences.

6) EasyRoads3D uses Layer 31, do you have other objects on this layer?

7) Z-fighting, the roads are laid out on top of the terrain. Make sure to set a "Raise" value in the Inspector in Build Mode, especially when shaders with no Offset are used.

Please contact us if all this does not apply to your situation.


Road type and side object preset names in the Inspector are displayed in characters / numbers and are unreadable

This can happen when Assets Serialization in your Unity project editor settings (Edit > Project Settings > Editor) is set to "Text" instead of the default setting "Mixed".


A workaround to fix this is the following:

Create a new empty project (Assets Serialization is set to Mixed), import the package, switch to Force Text and export the full assets folder to a new package. Import this package in your project that uses Force Text.


The road objects are rendered black

This will happen in Unity 5 when normal maps are used and no tangent info is available in the generated mesh. Please make sure "Calculate Tangents" is activated in the Build Settings and optionally in General Settings > Scene Settings.


The Delete key destroys the Road Network game object

Since in general the Road Network game object is selected the delete key will target this game object. When the scene view window has focus, pressing the delete key will becaptured and you will be asked for a confirmation. This will work just fine unless the Hierarchy window has focus. So far we have not found a way to capture key events in the hierarchy window, if you have a suggestion it would be very much appreciated to contact us.


Keyboard shortcuts do not work

For actions such as Shift + R (remove the selected marker) please make sure the Scene View window has focus.


The normals at connection points between the road and a custom connection prefab are not smooth

This is most likely due to the geometry structure between the connections as both ends of the road not being identical. Although the road connects well it is possible that there is a difference in normal groups between the two connections. Therefor it is impossible to smooth the normals correctly.

You may want to double check the smoothing groups in your modelling app. Another reason why this can happen is when using "Calculate" in the import settings of the model. You can verify this by checking the vertex count for the specific mesh asset after clicking "Apply". Unity will rebuild the mesh based on the selected smoothing angle which will result in a different number of vertices. Another way to check the normal groups is by opening the custom prefab in the Custom Prefab editor window and select the specific connection from the dropdown. The number of normal groups will be listed in the stats window. For exact normal group info you can open the UV editor window and select each node one by one. When the "Hard Edge" checkbox is on a new normal group will start at this node. This is all according the geometry structure of the source mesh.


I cannot set the Indent values below a certain value

The minimum indent values are based on the terrains heightmapscale (size vs heightmap resolution). It is required to ensure the best possible terrain deformation according the road shape because the Unity terrain object does not accept additional points for more detail in certain areas. When using lower values the terrain will pop through the road or the road will float above the terrain. The bigger the heightmapscale the higher the Min Indent values.

The default values for each marker match the globally stored Min Indent values in General Settings > Scene Settings.

So if these Min Indent values are high in your project, this is probably due to your terrain settings.


New Markers do not snap to the terrain

This can happen on large cam zooms further away then 5000 units from the click point. This is unlikely to happen but if it happens it will result in markers floating far above the terrain. In that case, please zoom in a little bit more to the terrain.


The Inspector toolbar is not displayed

This is most likely due to the Inspector being in Debug Mode. Click the down arrow (next to the lock icon) at the top right in the Inspector and make sure that "Normal" is selected. Additionally users have reported that working with two Inspector panels with one in debug mode does effect the Scene View functionality. Please avoid doing this if you experience similar behaviour and use one Inspector panel only, this is according the default unity settings.


The Unity editor is unresponsive or slow after road changes

This can be a result of "Auto" being selected in the Unity Lighting window. The lighting will be recalculated consistently in the background which can cause delays on slower computers. Switching off "Auto" temporarily while working on the road network will fix that.


EasyRoads3D Alert: [ref: SO01] Missing Side Object info

This alert message is usually related to package upgrades in a project using the custom setting Text Mode for Asset Serialization instead of the default Mixed Mode. Please do not save the scene if this is the case, instead follow the instructions pointed out here. Please contact us if your project does not use Text Mode for Asset Serialization.


Build Terrain progressbar doesn't update

Unity progressbars can only be used and updated through editor scripts. Because the Build functionality is also required for the scripting API, this code currently does not run in an editor script hence why the progressbar only updates per terrain and does not show progress on processed roads. This will be improved, meanwhile please be patient during this process, work is being done in the background.