Itoo Software Forum

Author Topic: Pylon cable padding issue  (Read 991 times)


  • Newbie
  • *
  • Posts: 2
Pylon cable padding issue
« on: October 07, 2015, 07:36:18 PM »
I'm just starting to use Railclone (2.5.0) and I'm having difficulty getting the power cables to connect properly at each Pylon/segment.

I've attached screen grabs to demonstrate the issue.
As you can see from Side view 1a, there is one tower segment that seems to be working but either side of it the cables are floating about 1.5m below the next tower connection points.

Is there any way to fix this?

In Side View 2 you can see another problem though this one only affects a short run of the spline path, the lines disappear completely and some floating lines on one side of the pylon. Again any ideas how I might resolve this. Though I could manually fix this given it is just a limited area, the first issue is throughout the entire spline.

Hope someone can help


Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1818
Re: Pylon cable padding issue
« Reply #1 on: October 08, 2015, 12:27:20 PM »

This is related to the generator's bevel mode. This tells RailClone how to deal with default segments on a corner. As you don't want the cables to bevel at the corners, change this setting to None and the problem should be solved.

I hope that helps.

Many thanks,

Paul Roberts
iToo Software


  • Newbie
  • *
  • Posts: 2
Re: Pylon cable padding issue
« Reply #2 on: October 17, 2015, 05:00:50 PM »
Thanks for the reply Paul

Had to move on to another job and didn't get a chance to come back on here in the meantime.

I had actually got it working myself eventually by changing the Linear 1S Properties>Rules from Default Mode>Scale to Default Mode>Count and then dropped the count number from 2 down to 1.
That seemed to get desired result for me. Doing that seems to disable the Bevel Mode setting so I guess it was doing the same thing that you suggested by a different means.

I've added a screen grab of the settings for anyone who is having a similar issue.