We've got a problem with the Late, Great Bendorsey's Bridges

J

jordon412

33 Year Old Railfan
This problem extends not just to the three bridges shown, but to all his bridges that have 'lift' or 'swing' in them. As you can see, the bridge on the left, 'Lift_Bridge_1', <kuid2:210518:1176:2> has the TANE Trk Oak, while 'Lift Bridge 44', <kuid:210518:121891> has the Track Invisible. This is obviously a problem when it comes to being featured in a route as you'd see the TANE Oak track instead of nothing when the bridge is raised. In the front is 'Scherzer_Rolling_Lift_4', <kuid2:210518:3103:2> has no spline attachment points nor any invisible track going across it, from one end to the other. Personally, if I was able to, I'd make clones of those with the TANE Oak track, replace it with the invisible track used on the other bridges, and then upload them to the DLS. I know that this is a lot of work to do and with all the content needing to be updated and the small number of members of the Content Repair Group (CRG), the time that these will be fixed will not be anytime soon.
EDIT: According to Content Manager, 'Lift_Bridge_1', <kuid2:210518:1176:2> , has 'Track Invisible', <kuid:-25:893> as its dependency, which is the same for all the other bridges made by bendorsey. It is used for many other pieces of content made by other creators. Why it's showing TANE Trk Oak instead of Track Invisible, which it is supposed to be, I have no idea.
Picture:
My-Trainz-Screenshot-Image.jpg
 
Last edited:
The fix for is straightforward. For 'Scherzer_Rolling_Lift_4', <kuid2:210518:3103:2> add attachment point a.track0b at (0, -44.8, 7.938 )

Then, for both, add an attached track container to the config.

Code: 
attached-track
{
  track0
  {
    useadjoiningtracktype               0
    track                               <kuid:-25:893>
    
    vertices
    {
      0                                 "a.track0a"
      1                                 "a.track0b"
    }
  }
}
 
Last edited:
Meanwhile quick fix change the build version back to 2.4 and add to the config.
Code: 
track                                   <kuid:-10:137>

This smacks of being updated when there was the anyone can repair assets and the track entry was removed as obsoleted in 3.5 works properly then with invisible track.


Guessing the messed up ones have all been updated to 3.5? If you can provide a list of the affected assets, I'll try and get them added to the list or see if they are on it already!


CRG Co-ordinator.
 
clam1952 said:
Meanwhile quick fix change the build version back to 2.4 and add to the config.
Code: 
track                                   <kuid:-10:137>

This smacks of being updated when there was the anyone can repair assets and the track entry was removed as obsoleted in 3.5 works properly then with invisible track.


Guessing the messed up ones have all been updated to 3.5? If you can provide a list of the affected assets, I'll try and get them added to the list or see if they are on it already!


CRG Co-ordinator.
Click to expand...
Sorry for the late reply, but I just got back home from being gone all day. I deleted all the ones that were screwed up after finding out that problem. I just went to download them and it appears that the DLS is screwed up . . . again.
EDIT: It appears that I am also unable to connect to the MyTrainz server, even though my username and password is entered correctly.
EDIT 2: Now I'm able to connect to MyTrainz server and download from the DLS.
 
Last edited:
Ask and You shall Receive

clam1952 said:
Meanwhile quick fix change the build version back to 2.4 and add to the config.
Code: 
track                                   <kuid:-10:137>

This smacks of being updated when there was the anyone can repair assets and the track entry was removed as obsoleted in 3.5 works properly then with invisible track.


Guessing the messed up ones have all been updated to 3.5? If you can provide a list of the affected assets, I'll try and get them added to the list or see if they are on it already!


CRG Co-ordinator.
Click to expand...

I searched for bridges made by bendorsey on the DLS using the keywords "bridge", "swing" and "lift" in both the title of the item or in the description of the item, which resulted in finding 339 items.
Here's a list of the items that have the TANE Oak trk:
Bobtail_Swing_Bridge_1 <kuid2:210518:1380:2>
Lift_Bridge_1 <kuid2:210518:1176:2>
Lift_Bridge_2 <kuid2:210518:1177:2>
Lift_Bridge_3 <kuid2:210518:1178:2>
Lift_Bridge_4 <kuid2:210518:1179:2>
Lift_Bridge_5 <kuid2:210518:1180:2>
Lift_Bridge_6 <kuid2:210518:1181:2>
Lift_Bridge_7 <kuid2:210518:1182:2>
Lift_Bridge_8 <kuid2:210518:1183:2>
Lift_Bridge_9 <kuid2:210518:1184:2>
Lift_Bridge_10 <kuid2:210518:1185:2>
Lift_Bridge_11 <kuid2:210518:1186:2>
Lift_Bridge_12 <kuid2:210518:1187:2>
Lift_Bridge_13 <kuid2:210518:1188:2>
Lift_Bridge_14 <kuid2:210518:1189:2>
Lift_Bridge_15 <kuid2:210518:1190:2>
Lift_Bridge_16 <kuid2:210518:1191:2>
Lift_Bridge_17 <kuid2:210518:1192:2>
Lift_Bridge_18 <kuid2:210518:1193:2>
Lift_Bridge_19 <kuid2:210518:1194:2>
Lift_Bridge_20 <kuid2:210518:1195:2>
Lift_Bridge_21 <kuid2:210518:1196:2>
Lift_Bridge_22 <kuid2:210518:1197:2>
Lift_Bridge_23 <kuid2:210518:1198:2>
Lift_Bridge_24 <kuid2:210518:1199:2>
Lift_Bridge_25 <kuid2:210518:1200:2>
Lift_Bridge_26 <kuid2:210518:1201:2>
Lift_Bridge_27 <kuid2:210518:1202:2>
Lift_Bridge_28 <kuid2:210518:1203:2>
Lift_Bridge_29 <kuid2:210518:1204:2>
Lift_Bridge_30 <kuid2:210518:1205:2>
Lift_Bridge_31 <kuid2:210518:1206:2>
Lift_Bridge_32 <kuid2:210518:1207:2>
Lift_Bridge_33 <kuid2:210518:1208:2>
Lift_Bridge_34 <kuid2:210518:1209:2>
Lift_Bridge_36 <kuid2:210518:1211:2>
Lift_Bridge_37 <kuid2:210518:1212:2>
Lift_Bridge_38 <kuid2:210518:1213:2>
Lift_Bridge_39 <kuid2:210518:1214:2>
Lift_Bridge_40 <kuid2:210518:1215:2>
Lift_Bridge_41 <kuid2:210518:1216:2>
Lift_Bridge_42 <kuid2:210518:1217:2>
Lift_Bridge_43 <kuid2:210518:1218:2>
Lift_Bridge_46 <kuid2:210518:1221:2>
Lift_Bridge_47 <kuid2:210518:1222:2>
Lift_Bridge_48 <kuid2:210518:1223:2>
Lift_Bridge_49 <kuid2:210518:1224:2>
Lift_Bridge_50 <kuid2:210518:1225:2>
Lift_Bridge_51 <kuid2:210518:1226:2>
Lift_Bridge_52 <kuid2:210518:1227:2>
Lift_Bridge_53 <kuid2:210518:1231:2>
Lift_Bridge_54 <kuid2:210518:1232:2>
Lift_Bridge_55 <kuid2:210518:1233:2>
Lift_Bridge_56 <kuid2:210518:1234:2>
Lift_Bridge_57 <kuid2:210518:1235:2>
Lift_Bridge_58 <kuid2:210518:1236:2>
Lift_Bridge_59 <kuid2:210518:1237:2>
Lift_Bridge_60 <kuid2:210518:1271:2>
Lift_Bridge_61 <kuid2:210518:1272:2>
Off_Center_Bridge_1 <kuid2:210518:8367:3>
Off_Center_Bridge_2 <kuid2:210518:8368:3>
Scherzer_Rolling_Lift_1 <kuid2:210518:3100:2>
Scherzer_Rolling_Lift_2 <kuid2:210518:3101:2>
Scherzer_Rolling_Lift_3 <kuid2:210518:3102:3>
Scherzer_Rolling_Lift_5 <kuid2:210518:3104:2>
Scherzer_Rolling_Lift_6 <kuid2:210518:3105:2>
Scherzer_Rolling_Lift_7 <kuid2:210518:3106:2>
Scherzer_Rolling_Lift_8 <kuid2:210518:3107:2>
Scherzer_Rolling_Lift_9 <kuid2:210518:3108:2>
Scherzer_Rolling_Lift_10 <kuid2:210518:3109:2>
Scherzer_Rolling_Lift_11 <kuid2:210518:3110:2>
Scherzer_Rolling_Lift_12 <kuid2:210518:3111:2>
Scherzer_Rolling_Lift_13 <kuid2:210518:3112:2>
Scherzer_Rolling_Lift_14 <kuid2:210518:3113:2>
Scherzer_Rolling_Lift_15 <kuid2:210518:3114:2>
Scherzer_Rolling_Lift_27 <kuid2:210518:3126:2>
Scherzer_Rolling_Lift_28 <kuid2:210518:3127:2>
Scherzer_Rolling_Lift_29 <kuid2:210518:3128:2>
Scherzer_Rolling_Lift_30 <kuid2:210518:3129:2>
Scherzer_Rolling_Lift_31 <kuid2:210518:3130:2>
Scherzer_Rolling_Lift_32 <kuid2:210518:3131:2>
Scherzer_Rolling_Lift_33 <kuid2:210518:3132:2>
Scherzer_Rolling_Lift_34 <kuid2:210518:3133:2>
Scherzer_Rolling_Lift_35 <kuid2:210518:3134:2>
Scherzer_Rolling_Lift_36 <kuid2:210518:3135:2>
Scherzer_Rolling_Lift_37 <kuid2:210518:3136:2>
Scherzer_Rolling_Lift_38 <kuid2:210518:3137:2>
Scherzer_Rolling_Lift_39 <kuid2:210518:3138:2>
Scherzer_Rolling_Lift_40 <kuid2:210518:3139:2>
Scherzer_Rolling_Lift_41 <kuid2:210518:3140:2>
Scherzer_Rolling_Lift_42 <kuid2:210518:3141:2>
Scherzer_Rolling_Lift_43 <kuid2:210518:3142:2>
Scherzer_Rolling_Lift_44 <kuid2:210518:3143:2>
Single_Swing_Span_1 <kuid2:210518:8377:2>
Single_Swing_Span_2 <kuid2:210518:8378:2>
Single_Swing_Span_3 <kuid2:210518:8379:2>
Single_Swing_Span_4 <kuid2:210518:8380:2>
Single_Swing_Span_9 <kuid2:210518:8386:3>
Swing_Bridge_1 <kuid2:210518:1228:3>
Swing_Bridge_2 <kuid2:210518:1229:3>
Swing_Bridge_3 <kuid2:210518:1230:3>
Swing_Bridge_4 <kuid2:210518:1238:3>
Swing_Bridge_5 <kuid2:210518:1239:3>
Swing_Bridge_6 <kuid2:210518:1240:3>
Swing_Bridge_7 <kuid2:210518:1241:3>
Swing_Bridge_9 <kuid2:210518:1243:3>
Swing_Bridge_10 <kuid2:210518:1244:3>
Swing_Bridge_11 <kuid2:210518:1245:2>
Swing_Bridge_12 <kuid2:210518:1246:3>
Swing_Bridge_13 <kuid2:210518:1247:2>
Swing_Bridge_14 <kuid2:210518:1248:2>
Swing_Bridge_15 <kuid2:210518:1249:2>
Swing_Bridge_16 <kuid2:210518:1250:2>
Swing_Bridge_17 <kuid2:210518:1251:2>
Swing_Bridge_18 <kuid2:210518:1252:2>
Swing_Bridge_19 <kuid2:210518:1253:2>
Swing_Bridge_20 <kuid2:210518:1254:2>
Swing_Bridge_21 <kuid2:210518:1255:2>
Swing_Bridge_22 <kuid2:210518:1256:2>
Swing_Bridge_24 <kuid2:210518:1258:2>
Swing_Bridge_25 <kuid2:210518:1259:2>
Swing_Bridge_26 <kuid2:210518:1260:2>
Swing_Bridge_27 <kuid2:210518:1261:2>
Swing_Bridge_28 <kuid2:210518:1262:2>
Swing_Bridge_29 <kuid2:210518:1263:2>
Swing_Bridge_31 <kuid2:210518:1267:3>
Swing_Bridge_35 <kuid2:210518:1273:2>
Swing_Bridge_36 <kuid2:210518:1274:2>
Vertical_Lift_Bridge_1 <kuid2:210518:1284:2>
Vertical_Lift_Bridge_2 <kuid2:210518:1285:2>
Vertical_Lift_Bridge_3 <kuid2:210518:1286:2>
Vertical_Lift_Bridge_4 <kuid2:210518:1287:2>
Vertical_Lift_Bridge_5 <kuid2:210518:1288:2>
Vertical_Lift_Bridge_6 <kuid2:210518:1290:2>
Vertical_Lift_Bridge_7 <kuid2:210518:1291:2>
Vertical_Lift_Bridge_8 <kuid2:210518:1292:2>
Vertical_Lift_Bridge_9 <kuid2:210518:1293:2>
Vertical_Lift_Bridge_10 <kuid2:210518:1294:2>
Vertical_Lift_Bridge_11 <kuid2:210518:1295:2>
Vertical_Lift_Bridge_12 <kuid2:210518:1296:2>
Vertical_Lift_Bridge_13 <kuid2:210518:1297:2>
Vertical_Lift_Bridge_14 <kuid2:210518:1296:2>
Vertical_Lift_Bridge_15 <kuid2:210518:1299:2>
Vertical_Lift_Bridge_16 <kuid2:210518:1300:2>
Vertical_Lift_Bridge_17 <kuid2:210518:1301:2>
Vertical_Lift_Bridge_18 <kuid2:210518:1302:2>
Vertical_Lift_Bridge_19 <kuid2:210518:1303:2>
Vertical_Lift_Bridge_20 <kuid2:210518:1304:2>
Vertical_Lift_Bridge_21 <kuid2:210518:1305:2>
Vertical_Lift_Bridge_22 <kuid2:210518:1306:2>
Vertical_Lift_Bridge_23 <kuid2:210518:1307:2>
Vertical_Lift_Bridge_24 <kuid2:210518:1308:2>
Vertical_Lift_Bridge_25 <kuid2:210518:1309:2>
Vertical_Lift_Bridge_26 <kuid2:210518:1310:2>
Vertical_Lift_Bridge_27 <kuid2:210518:1311:2>
Vertical_Lift_Bridge_28 <kuid2:210518:1312:2>
Vertical_Lift_Bridge_29 <kuid2:210518:1313:2>
Vertical_Lift_Bridge_30 <kuid2:210518:1314:2>
Vertical_Lift_Bridge_31 <kuid2:210518:1315:2>
Vertical_Lift_Bridge_32 <kuid2:210518:1316:2>
Vertical_Lift_Bridge_33 <kuid2:210518:1317:2>
Vertical_Lift_Bridge_34 <kuid2:210518:1318:2>
Vertical_Lift_Bridge_35 <kuid2:210518:1319:2>
Vertical_Lift_Bridge_36 <kuid2:210518:1320:2>
Vertical_Lift_Bridge_37 <kuid2:210518:1321:2>
Vertical_Lift_Bridge_38 <kuid2:210518:1322:2>
Vertical_Lift_Bridge_39 <kuid2:210518:1323:2>
Vertical_Lift_Bridge_40 <kuid2:210518:1324:2>
Vertical_Lift_Bridge_41 <kuid2:210518:1325:2>
Vertical_Lift_Bridge_42 <kuid2:210518:1326:2>
Vertical_Lift_Bridge_43 <kuid2:210518:1327:2>
Vertical_Lift_Bridge_44 <kuid2:210518:1328:2>
Vertical_Lift_Bridge_45 <kuid2:210518:1329:2>
Vertical_Lift_Bridge_46 <kuid2:210518:1330:2>
Vertical_Lift_Bridge_47 <kuid2:210518:1331:2>
Vertical_Lift_Bridge_48 <kuid2:210518:1332:2>
Vertical_Lift_Bridge_49 <kuid2:210518:1333:2>
Vertical_Lift_Bridge_50 <kuid2:210518:1334:2>
WP&W_Swing_Bridge_(std_ga) <kuid:210518:1266>

And here's the ones with the attachment point missing:
Bann_Lift_Bridge_5 <kuid2:210518:10912:3>
Cape_Cod_Lift_Bridge_2 <kuid2:210518:11383:1>
Chicago Canal Bridge 4 <kuid2:210518:7634:4>
Chicago Canal Bridge 5 <kuid2:210518:7641:3>
Port_Clinton_Lift_Bridge_3 <kuid2:210518:11385:1>
Rail Boat Bridge 1 <kuid2:210518:1592:1>
Scherzer_Rolling_Lift_4 <kuid2:210518:3103:2>
Selby Swing Bridge 2 <kuid2:210518:1506:1>
Selby Swing Bridge 4 <kuid2:210518:1510:1>
Selby Swing Bridge 6 <kuid2:210518:1513:1>
Swing_Bridge_37 <kuid2:210518:11427:2>
Vertical Lift Bridge 52 <kuid2:210518:1348:1>
Willamette_Draw_Bridge_3 <kuid2:210518:11384:1>
 
I might be missing the point, as I only checked the first bridge out of the opening post, but I get the impression the solution is changing / adding one line of code to the config file:

Code: 
useadjoiningtracktype               0

Is that correct?

If so, I am sure it is something that the CRG could do, but it will be a enormous amount of work as the big Ben D. created a lot of bridges.
That is... if the CRG can keep uploading content for TS12 (since that is no longer supported). I noticed a lot of his assets (probably all of them) also give LOD warnings, so when TS12 is no longer an option, the CRG would have to create LOD meshes for all those bridges. Good luck finding someone who has a few years of spare time to do so.
 
oknotsen said:
I might be missing the point, as I only checked the first bridge out of the opening post, but I get the impression the solution is changing / adding one line of code to the config file:

Code: 
useadjoiningtracktype               0

Is that correct?
Click to expand...

No. The version must be updated to 3.5 and that requires the track part container and other changes. Some will require new attachment points. It's not a big job for someone who knows how to edit multiple assets, but the CRG has lost its best contributors due to arbitrary and pointless changes to their rules.

It has to be done by someone who understands how to make the support pylons extend to ground level whatever the depth.
 
Last edited:
SailorDan said:
No. The version must be updated to 3.5 and that requires the track part container and other changes. Some will require new attachment points. It's not a big job for someone who knows how to edit multiple assets, but the CRG has lost its best contributors due to arbitrary and pointless changes to their rules.
Click to expand...

My understanding is there is NOW only 4 guys that are still actively doing any CRG work. From what I can gather after speaking to one of them a little while back, is that it is a pretty time consuming, thankless task. Very few Trainzers seem to show or express there appreciation for all the hard anonymous work these guys do..

If I was N3V/Tony, I would atleast be offering them some sort of reward for all their hard work. Eg; free TS2019 or DLC, or FCT, or some sort of cash incentive...

Cheers, Mac...
 
With Ben's unfathomable amount of bridge contributions (et al), yes it will likely be a dreadfully daunting task for the CRG; but we must try to keep Ben's grand legacy alive! No one can make a bridge like Ben, and is the first person I'd think most people think of when we we're lookin' for just the right bridge, to place in a given area of our routes. I sure would hope... and think something could be done! :(
 
meatloaf747 said:
My understanding is there is NOW only 4 guys that are still actively doing any CRG work. From what I can gather after speaking to one of them a little while back, is that it is a pretty time consuming, thankless task. Very few Trainzers seem to show or express there appreciation for all the hard anonymous work these guys do..

If I was N3V/Tony, I would atleast be offering them some sort of reward for all their hard work. Eg; free TS2019 or DLC, or FCT, or some sort of cash incentive...

Cheers, Mac...
Click to expand...

. "Very few Trainzers seem to show or express there appreciation for all the hard anonymous work these guys do.. "

Well since we don't know who they are and its not mentioned that they are doing this work, it hard to recognize them. It is a thankless job , perhaps NV3 might give them more recognition in their newsletters, they seem more interested in spruiking great looking screenshots, understandable as that's what drives sales, but the core of Trainz is the assets and if a lot of them don't work, it puts people off.


BTW there is a thread https://forums.auran.com/trainz/sho...ld-you-own-content-items&highlight=ben+dorsey
which mentions that any of Ben's items can be updated in blender etc if run through some payware software as it is all public domain, in theory it can all be updated to 2019 standards but again, who is going to undertake that huge task ?
 
Last edited:
You must log in or register to reply here.

Similar threads

S
Single Track Lift Bridge
Replies
14
Views
872
KenRuof
K
J
Differences noticed so far with upgrade to build 122734
Replies
2
Views
396
JCitron
J
W
Bridges? Track Types?
Replies
2
Views
666
jjslll54
J
L
Rail spline with check rails
Replies
6
Views
673
Lewiscc65
L
P
ATLS crossing
Replies
8
Views
286
lukewc
L
Back
Top