Problem with Railwaves Signals causing detrimental effects in Trainz (800 X 600)

shaneturner12

Tutorial Creator
Hello again Trainzers,

I am now having an issue with one of the signals in the Railwaves UK Signalling Pack.

It's easier to show what it is doing, see the images below: (click an image to see the full version - this is due to ImageShack's options not being clear)




The name and KUID of the offending signal is in the first screenshot, but I know it is happening with several.

Strangely enough, this problem only started when I added three of this signal (although only 1 is needed to cause this issue sometimes), and was working fine beforehand.

I like these signals due to their configurability, and their general look.

Does anyone have a solution on why this is happening, as it is causing my framerates to drop significantly at times.

If needed, here are my system specs (from my utility):

PC Information Report
Generated using PC Information Application by Shane Turner
System Information
System Manufacturer:Acer
System Model:Aspire 5542
System Type:x64-based PC
Operating System Information
Operating System Name:Microsoft Windows 7 Home Premium |C:\Windows|\Device\Harddisk0\Partition3
Build:7601(Multiprocessor Free)
Service Pack:1.0
Status: OK
Memory Information
Total/Free Physical Memory (in GB):3.75/0.82
Graphics Card Information
Graphics Card 1
Graphics Card:ATI Mobility Radeon HD 4200 Series
Driver Version:8.892.0.0
Date of current driver:20110908000000.000000-000
Video Memory:0.25 GB (256.00 MB)
Processor Information
Processor:AMD Athlon(tm) II Dual-Core M300 (1.95 Ghz)
Processor Type:64 Bit
Number of Processors:2
DirectX and Drive Information
Detected DirectX version: (This may not match any expected values) 4.09.00.0904
Drive Information:
Drive C:\ : 54.61GB Free ( 221.07 GB Capacity after formatting)
Drive D:\ : 0.00GB Free ( 0.61 GB Capacity after formatting)

Shane
 
Hi Shane

First, thanks for your new PC System Spec shower, it is a very handy tool

Secondly, have you tried contacting RailWaves Directly??

Jamie
 
Hi Shane.
Looks like you have stumbled on another funny one. I use these signals too as they do look much more realistic. I have them on my route built in 06 in between junctions and at most of the small stations, I only use the Bloodnok Signals at junctions as they don't take up resources and time to set them up. My route has been transferred to both Trainz10 & 12 without this problem so I'm wondering if it maybe the fact that you have used the "Set up/Configure" part of the signal as apposed to me who just plonks them down as normal signals?
What and how did you set the signals up?
 
H222:

I will look into contacting Railwaves, but I thought I'd better check here first to see if anyone else has encountered/fixed this issue.

Deano5:

I simply used the Trackside Properties tool (the ? button on the trackside tab) then clicked the tick icon as I did not need to set anything.

I did simply put 2 of them down without doing this though.

Shane
 
Hi Shane.
I just tried them on a test map, put 5 various signals and gave them names and area codes, then drove a LM 321 up and down the line. No problems. There must be something on your route that is causing a conflict, any thoughts and I'll try to replicate it.
What stations are you using and other industries?
What triggers and other scripted trackside objects do you have in use?
 
I am now back at my own system, and as requested, here is the list of all scripted items, apart from trains produced by portals. If this is required, that may take a bit longer.

AI Routing Priority Marker,<kuid:-3:10190>
AJS Invisible Station 1T 3.5,<kuid2:122285:3401:3>
AJS Invisible Station 4T 3.5,<kuid2:122285:3404:3>
AJS Invisible Station 6T 3.5,<kuid2:122285:3405:3>
AJS Invisible Station 8T 3.5,<kuid2:122285:3406:3>
AJS Station 2x110s,<kuid2:122285:3325:10>
AWS Permanent Magnet Bidirectional,<kuid2:60850:23052:5>
AWS Ramp,<kuid2:60850:23050:5>
AWS Ramp Bidirectional,<kuid2:60850:23054:5>
AWS Ramp Dual Signal Bidirectional,<kuid2:60850:23053:5>
Brick Station large,<kuid:-16:22999>
Brick Station small,<kuid:-3:10211>
Catenary trigger (UK),<kuid2:75134:77001:1>
Class 150/1 DMSL - Central Trains,<kuid:179051:150071>
Class 150/1 DMSL - London Overground ex Silverlink,<kuid:179051:150067>
Class 150/1 DMS - Central Trains,<kuid:179051:150070>
Class 150/1 DMS - London Overground ex Silverlink,<kuid:179051:150066>
Class 150/2 Central Trains,<kuid:179051:150008>
Class 150/2 Central Trains, Anglia livery,<kuid:179051:150012>
Class 153 London Midland livery,<kuid:45317:102828>
class 165 DMSL Chiltern,<kuid:45317:102694>
class 321 DTCO London Midland,<kuid2:45317:1970:1>
class 321 DTSO London Midland,<kuid2:45317:1971:1>
Class 390 Pendolino DMRF Car 1 (updated),<kuid2:45317:2092:1>
Class 390 Pendolino DMSO Car 9 (updated),<kuid2:45317:2441:1>
Class 390 Pendolino MF City of Lichfield - Car 4 (Updated),<kuid:45317:2436>
Class 390 Pendolino MF - Car 2 (Updated),<kuid:45317:2433>
Class 390 Pendolino MS - Car 6 (Updated),<kuid:45317:2438>
Class 390 Pendolino MS - Car 8 (Updated),<kuid:45317:2440>
Class 390 Pendolino PTF - Car 3 (Updated),<kuid2:45317:100501:1>
Class 390 Pendolino PTSRMB - Car 7 (Updated),<kuid2:45317:100604:1>
Class 390 Pendolino TS - Car 5 (Updated),<kuid:45317:2437>
Class 66 EWS,<kuid:79563:1236>
Class 67,<kuid2:75134:67001:4>
Clickety Clack Trigger,<kuid:76656:70000>
Coal Stage,<kuid:187586:28156>
DB departure board custom,<kuid2:177792:1029:1>
Didcot Parkway Station,<kuid:67906:28227>
EWS Hevy Haul,<kuid:131788:1501>
FGW class 166 DMCL,<kuid2:45317:101736:1>
Industrial hanger animated door,<kuid2:70337:27004:10>
Industry Airport,<kuid:-3:10043>
Industry Link,<kuid:122381:10007>
iPortalTunnel,<kuid2:30671:23500:1>
Junction Link,<kuid:122381:10003>
LMS Combined Semaphore,<kuid:4468:24300>
LMS Combined Semaphore RH,<kuid:123327:24300>
LMS Distant Semaphore RH,<kuid:123327:24200>
LMS Dual 1 Combined Bracket,<kuid:4468:24370>
Multiple Industry,<kuid:-3:10123>
Multiple Industry New,<kuid:-19:10165>
NSE Clock,<kuid2:60850:28100:1>
Platform 350m,<kuid2:151900:100170:1>
Portal,<kuid:-3:10192>
Portal Basic,<kuid:30501:22006>
Power Station 2,<kuid:66277:10099>
Re-rail Portal,<kuid2:116387:5:1>
Re-rail Portal Basic,<kuid2:116387:6:1>
sig 2aT dorman RH Terminating standard round post,<kuid:45317:1606>
Sig 2AT Gantry OHL,<kuid2:125145:24001:1>
Sig 3A BR Post Platform Offset LHS,<kuid2:60850:24135:3>
Sig 3A BR Post Platform Offset RHS,<kuid2:60850:24145:3>
Sig 4AT BR Post Elec RHS,<kuid2:60850:24187:3>
Sig 4AT BR Post Offset RHS,<kuid2:60850:24207:3>
Sig 4A BR Platform Post Elec LHS,<kuid2:60850:24239:3>
Sig 4A BR Platform Post Offset RHS,<kuid2:60850:24149:3>
Sig 4A BR Post Std RHS,<kuid2:60850:24019:3>
sig 4a dorman (mesh) for OHLE sig gantry,<kuid:45317:2161>
Sig 4A Gantry OHL (modified trackside),<kuid:45317:2565>
Sound Horn BiDirectional,<kuid2:60850:23112:4>
Station Clock,<kuid2:62310:30043:1>
Station Moreton 1,<kuid:1942:28158>
Station Platforms 01 155m,<kuid2:60850:22008:1>
Station Platforms 01 210m,<kuid2:60850:22009:2>
Station Platforms 01 260m,<kuid2:60850:22010:1>
Station Platforms 02 130m,<kuid2:60850:22001:1>
Station Platforms 02 130m island,<kuid2:60850:22013:1>
Station Platforms 02 130m 4wide,<kuid2:60850:22004:1>
Station Platforms 03 140m,<kuid2:60850:22005:1>
Station Platforms 03 155m,<kuid2:60850:22002:1>
Station Platforms 03 160m bay 110m,<kuid2:60850:22011:1>
Station Platforms 04 190m terminus,<kuid2:60850:22015:1>
Station Platforms 04 210m,<kuid2:60850:22003:2>
Station Through 4t,<kuid2:1942:28175:2>
Turbostar DMS Central Trains,<kuid2:67906:2270:1>
Voyager 220 DMF,<kuid2:67906:2204:3>
Voyager 220 DMSL,<kuid2:67906:2201:3>
Voyager 220 MS(A),<kuid2:67906:2202:3>
Voyager 220 MS(B),<kuid2:67906:2203:3>
Voyager 221 DMF,<kuid:67906:2401>
Voyager 221 DMSL,<kuid:67906:2402>
Voyager 221 MS(A),<kuid:67906:2403>
Voyager 221 MS(B)1,<kuid:67906:2404>
Voyager 221 MS(B)2,<kuid:67906:2405>
VSB NSW Surveyor Only,<kuid2:61119:22007:1>
W Whistle Board,<kuid2:68236:11025:1>
W Whistle Sign v2,<kuid2:68236:11026:2>
323202 DMSO LM livery,<kuid2:45317:101970:1>
4A Signal,<kuid:67906:24617>
5 platform 7 track station,<kuid2:101243:28043:1>
5 platform 9 track station,<kuid2:119746:28041:1>

Shane
 
Shane,

Take a look at your Jetlog.txt file.

All kinds of useful information about your route's operations are listed in this file including script error references.

John
 
Just had a look, and cannot see any reference.

I have just reinstalled the affected signals though, and am now re-trying them.

If it works this time, I think the problem is with always-controlled.

Shane
 
I think I have a result...

I have just re-tested the route after reinstalling the UK Signalling Pack (the pack that the signals are part of) and the script errors appear to be gone.

I have a feeling that it's something to do with either the build number, or the always-controlled tag.

Shane

EDIT: Spoke too soon - the errors have started to reappear. Only had 3 of the error so far, but it may increase.
 
Last edited:
Back
Top