[James Ross]

As with all performance things, if it's running well on what you want it to run well on, there's not a huge amount of point working on optimising it further.

Also worth bearing in mind that how OR renders objects can and will change, so something that makes it slow today might be just fine the day after tomorrow.

[captain_bazza]

Thank you to all the informative posters, it's never too late to learn something new.

I've pinned this topic, because it's too important to get lost, so please continue to post here regarding this very important topic.


Cheers Bazza

[captain_bazza]

Quote

Also worth bearing in mind that how OR renders objects can and will change, so something that makes it slow today might be just fine the day after tomorrow.

I agree with James. That is more, or less, my ongoing philosophy, ATM.

Cheers Bazza

[Genma Saotome]

James is correct... as they say on Wall St: "past performance is no indication of future returns". That said, what I wrote, above, while applicable to the current rendition of Open Rails, is, as a FWIW, is also true for MS Flight Simulator: the count of polys and the count of texture files is not the whole story; material types, transparencies, and UV vertices also are part of the total performance cost and more of those you have will cost more in overall performance.

[captain_bazza]

..........which is why the 'grab the latest stuff and never respond, user' downloaders are a pain......we modelers need feedback to tell us that things are going okay on other systems, or not.

Otherwise it's all guesswork; if it works on our machines, then it works okay, is the assumption we have to make in lieu of feedback to the contrary.

Cheers Bazza

:freezing: