Legacy Mode

[partyspiritz]

It is hard to know what to do now. Its not just the Bacup Branch its the other routes that had plans to finish the Fairford Branch Line http://www.martin.loader.btinternet.co. ... Branch.htm all started with the same amount of care.

I am one of the lucky one's who made a back up of RW2 and that was drummed into me from the days of Rail Simulator. I know that RSC have said they would not make RW2 available. I wish you would reconsider.

Even some of the route building challenge routes don’t look good in legacy mode. This years challenge routes I can not pass judgement on.

Regards


John

[theokus]

It is hard to know what to do now. Its not just the Bacup Branch its the other routes that had plans to finish the Fairford Branch Line http://www.martin.loader.btinternet.co. ... Branch.htm all started with the same amount of care.

I am one of the lucky one's who made a back up of RW2 and that was drummed into me from the days of Rail Simulator. I know that RSC have said they would not make RW2 available. I wish you would reconsider.

Even some of the route building challenge routes don’t look good in legacy mode. This years challenge routes I can not pass judgement on.

Regards


John

I agree with you.
Besides this I have already been cited.
Each route builder will have the same problem with his own made routes "RW2-style".

[CaptScarlet]

And before anyone says, that's down to the model maker, my point is, legacy mode isn't the same as RW2, to me it's more of a "hybrid" mode.
This has been tried on two different PC's in both RW2, ( perfect ) and RW3 legacy mode, ( behaving as above ).

Chris.

I take your point but just so you know it appears and behaves that way in TSX mode as well, so while the model is fine in RW2 it does need updating to look and work properly in any RW3 mode.

John

[theorganist]

Thanks for all the research you have done Kromaatikse and for the time and trouble you have gone to.

I will try the update tonight.

Peter.

[RSBen]

Okay, I just went back over the X1650, making certain that I selected the same settings for RW2 and RW3, and I still have a very clear difference between the framerates under each. This is with tonight's update to RW3, and at full native resolution on my main monitor - the latter strongly suggests that more work per pixel is being done, rather than differences in the number of objects.

Screenshots to confirm settings, complete with both Railworks' and FRAPS' frame counters (which match quite well, actually):

RW2-settings1.png

RailWorksProc2 2011-10-12 05-42-53-00.png

RailWorksProc2 2011-10-12 05-44-25-73.png

RailWorksProc2 2011-10-12 05-46-31-73.png

RW3-settings1.png

RailWorksProc2 2011-10-12 05-51-21-12.png

RailWorksProc2 2011-10-12 05-52-48-56.png

RailWorksProc2 2011-10-12 05-55-50-56.png

Thanks for that, indicates something's happening in TS2012 that shouldn't be / is not visible in legacy, although it's still difficult to see what this could be. If you fly up with the camera, are the draw distances noticeably different? Do you see anything being drawn in TS2012 that isn't being drawn on screen in RW2? Difficult to tell in these screenshots due to fog.

EDIT:

try turning terrain down to low, and turn down water quality. Due to some changes and optimizations made with these, low may be the old medium.

Thanks,
Ben

[nigeltouatievans]

And before anyone says, that's down to the model maker, my point is, legacy mode isn't the same as RW2, to me it's more of a "hybrid" mode.
This has been tried on two different PC's in both RW2, ( perfect ) and RW3 legacy mode, ( behaving as above ).

Chris.

I take your point but just so you know it appears and behaves that way in TSX mode as well, so while the model is fine in RW2 it does need updating to look and work properly in any RW3 mode.

John

Correct me if I'm wrong, but as far as I'm aware there is no 'legacy mode' in the sense that everything should work identically to RW2. What there is is a legacy graphics mode, that allows those of use whose machines are not powerful enough to run TSX to still have RW3 run as well as RW2 (not withstanding that this is seemingly not completely true at the moment), with graphics similar to RW2. The behaviour of doors, pantographs, the dispatcher, trains physics etc should be identical for all RW3 users regardless of TSX being on or off.

[CaptScarlet]

The behaviour of doors, pantographs, the dispatcher, trains physics etc should be identical for all RW3 users regardless of TSX being on or off.

Correct, which is why I pointed out that the example used ( the class 317 ) does need a update as the faults noted were not limited to "legacy" mode.

John

[Kromaatikse]

If you fly up with the camera, are the draw distances noticeably different? Do you see anything being drawn in TS2012 that isn't being drawn on screen in RW2?

With the magic of the scenario editor, I can set up exactly the same view in both versions:

This looks to me as though the same objects are appearing in the same places, BUT the ground is being rendered further, BUT the ground textures disappear into the Orange Sea before the original horizon is reached.

Meanwhile, if I pan the camera up so as to hide the nearby objects, the framerate goes up a lot. So I don't think the distant ground is the problem.

[Retro]

This is what I am seeing in The Central Route regarding the Orange Tinge.
I also have a Yellow Tinge problem in Cab View but only with TSX On
http://forums.uktrainsim.com/viewtopic. ... 0#p1474580
I can't remember an Update in the past that caused so many problems.
Kind regards James.

[theokus]

This looks to me as though the same objects are appearing in the same places, BUT the ground is being rendered further, BUT the ground textures disappear into the Orange Sea before the original horizon is reached.

Successive question.
It is about a composite group of trees, that new feature.
So I thought that the amount of trees would automatically adjust to the surface of the ground.
But I do not know if this was your intention.

[RSderek]

Hiya, as I said in the other thread the brown/orange is the base colour that gets drawn after the terrain textures stop which has always been there.
The distance it mips in has moved closer for some reason, Once i know more i will get back to you.

cheers
d

[Retro]

Thank You Derek. Much appreciated.
Kind regards James.

[Kromaatikse]

It is about a composite group of trees, that new feature.

I'm using Hatchet Hill as a comparison here - it doesn't have the area-fill trees because it predates RW3 (though not by much). I think it does use fixed blocks of trees though - these are also efficient but don't follow the terrain.

It is already a very lightweight route, which makes it convenient for testing GPUs because it eliminates the CPU from the equation.

[theokus]

It is about a composite group of trees, that new feature.

I'm using Hatchet Hill as a comparison here - it doesn't have the area-fill trees because it predates RW3 (though not by much). I think it does use fixed blocks of trees though - these are also efficient but don't follow the terrain.

It is already a very lightweight route, which makes it convenient for testing GPUs because it eliminates the CPU from the equation.

Ah ok, I get the point

PS. I notice the difference in colors....
(blue-gray cast)

[Kromaatikse]

I tried setting the View Distance to "Low" to try to match the horizon:

The horizon does match quite well now, but I've got fewer objects as well - and the framerate is still just as low. This further supports my hypothesis that this is a pixel-side problem, not a vertex-side one.