Atomic Systems

gptech wrote:

photons66 wrote: and keep errors and bugs to factual findings, then I have no problem.

I bet I could cause one.......or several!!

To be more constructive, would a list of known errors/glitches with the route---lets leave scenarios out of it for now--posted in here allow those with the necessary skills/motivation/time to have a look at the ones they think they could fix, and if successful be able to pass the information or revised files to photons, and also amend the list so that the same issue isn't fixed many times?

Sounds like a plan

I managed to get all scenarios working as well as the Chiltern Mainline ones.
The foggy 2013 one is quite an experience ! The route is excellent with just these problems for me.
1. Graphic glitches some miles out of Euston on all scenarios and both routes. I can drive through but they weren't there
in the original London-Midlands version.
2. I don't think anyone can find 321 LM2. The AP 321 is great but is a real resources hog on my system and caused freezes
as it is used by a lot of AI in one scenario.
Fortunately I found a 321 LM 1 somewhere and swapped that which works fine.
3. Strange abrupt speed changes ,mostly on the way from Euston. They don't show as errors on my HUD so no real problem.
4. Difficult for me to get on the main line to Birmingham International from Birmingham NS. I used the AI command in the end (-followaitrain)
which got me onto the right track. The AI is much cleverer than me.
5.Bumpy track sometimes but not too bothered.
Overall a great experience in spite of the above.

It is a great route and Chilterns is great to

Many of the issues seem to stem from a plethora of track rules, coupled with sections that seem to have no rule applied. It isn't a particularly long job to resolve the numbers of rules BUT there are large sections that will need more attention to fully apply those new rules, which would fix the HUD speed limit issues. Trav mentioned the 2 Hagen-Seigen rules that seem not to be used, which seems to be correct in this new version of the route but they were referenced in the original iteration.
If we can sort that out the rest of the glitches should be much easier to resolve.
Clemmo, could you supply grid references for the places where you get the graphics corruption?...this is more likely to be a duff asset on folks PCs rather than a fault in the route but it would help if we can nail it down.

Ok I can give coordinates . I followed the track in the World Editor. Euston-Wolverhampton 2003
First sign is the left half of the sky goes blackish at about 51.53399 -0.20486
Strange pattern start 51.53168 -0.21645
Total corrupted graphics by 51.53143 -0.21807
Clears at end of tunnel 51.53032 -0.22976

Similar problem a bit further
Hope that helps
So it starts about here


Then gets a lot worse till it clears at the end of the tunnel. Another one a bit further.

Do it Gary, sounds like a plan.

JohnM1945 wrote:Note for Traveller54: I can see this route in RW_Info; do you perhaps have an installation fault?
Kind regards, John M

Thanks John - since I had a play around with some of the route files I can see it in RW_Info now as well. One off the list - thanx.

Those graphics glitches were there in the original route and I can tell you that they occur every time the RDSL Class 483 lumodern unit is in the field of vision. as soon as you pass it all returns to normal.

Bongoboy. Check your PM.

bongoboy wrote:Those graphics glitches were there in the original route and I can tell you that they occur every time the RDSL Class 483 lumodern unit is in the field of vision. as soon as you pass it all returns to normal.

Then it's not the route, but the older .Geo used in that particular reskin. and/or the associated missing <wiper pairs> section in the .bin file.

I had the earlier version and there were no glitches for me in that one.
So what would be a good replacement for the old 483 ?

Hi
I use the standard stock pack of Richard Scott and Darren Carter, id 23775. Think this is the number but not on computer at the moment as out and on phone.
Works for me as I don't have IOW.
Thanks
Peter

Yes well done, problem fixed. For the moment I swapped with a 3 car Thomson NSE 455 but I'll find the one Peter suggested.
Thanks a lot.

Traveller54 wrote:When in the editor and using the space bar most of the track around Euton shows as 'Missing Texture' and when investigated there is no trackrule

I know it's going back a couple of pages, but yes Trav--the errant textures will most likely be because no track rule is associated with that particular section of track. Which nicely leads me on to.......

We've made a start on fixing (or at least lessening) the issues but before we plough on it'd be nice to know that we aren't building in more problems so a couple of mugs...errr, volunteers are needed to test what we've come up with:
namely, a new track rule and revised Tracks.bin that should remove most of the issues centred around *missing* track rules--as well as 'tidying' things a bit.
Also, a little revision of the track around Rugby to test the theory on this PC, which did make editing the point work very simple by the way, so if it doesn't screw somebody else's installation up totally it may open the gates for a proper team effort to knock the few rough edges off.
If you have any experience in the editor that'd help, but it really is essential that you're conversant, and happy with, managing files on your own PC.
Lousy rate of pay and long hours I'm afraid, but if anybody's interested just drop me a PM.

Gary

EDIT: If you don't get a reply today it's because I'm on nights this week so don't think I'm ignoring you.

gptech wrote:

Traveller54 wrote:When in the editor and using the space bar most of the track around Euton shows as 'Missing Texture' and when investigated there is no trackrule

For anyone with the problem of 'missing' track textures when in the editor this will fix it?!

1) Ensure that in your assets folder you have these files:-
railworks\Assets\photons66\WCML\RailNetwork\TrackRules - Sieg_Hage_Main_MPH.bin & Sieg_Hage_Yard.MPH.bin

2)Navigate to:-
railworks\Content\Routes\4f0e07aa-7775-4009-96df-5dfdeb588ba1\Networks
... and open the Tracks.bin in RW_Tools.

Click on 'Search and Replace' then 'Find' and in the top paste this text below:-

<Property>
<Network-iTrackNetworkTrackRule-cPropertyValue>
<TrackRule>
<iBlueprintLibrary-cAbsoluteBlueprintID>
<BlueprintSetID>
<iBlueprintLibrary-cBlueprintSetID>
<Provider d:type="cDeltaString"></Provider>
<Product d:type="cDeltaString"></Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString"></BlueprintID>
</iBlueprintLibrary-cAbsoluteBlueprintID>
</TrackRule>
</Network-iTrackNetworkTrackRule-cPropertyValue>
</Property>