[Weter]

Hello to ET forum members.
I have another question to developers of ORTS.
The "model instancing" option, as I understand in-Manual description, can accelerate the gpaphic, but actually, in some routes, the game freeses completly, if that box was checked.

This log was written when option is OFF
[attachment=104982:OpenRailsLog.txt]
This - when ON
[attachment=104983:OpenRailsLog.txt]
In case of other routes, more or less slow-down is observed too.

[vince]

Try running in a route without all those database errors and see if it still fails.

vince

[engmod]

Given the low level of your computer, I am surprised that you can run OR at all.
There is no point running the LAA version in 2GB of ram, just run the stock 32 bit version.
You have not changed the 185% traction either.

There have not been any other reports of model instancing problems.

There is no point running datalogging options with your machine. It only uses up diskspace.

[Weter]

Hello, Vince and Derek, Thanks for assistance.
I have couple of questions:
Is "database errors" about signalling, You mean, Vince?
But why without "model instancing" checked, it gOes at 7-9 FPS at worst case(at station wich most dence populated with objects, catenary etc.) and even smoother at other locations; but when checked, I can't see, the reversor is changed for bringing train to movement, still I've pressed Esc to start te game?

What is "stock" and "LAA" version?
As I understand, I have to uncheck "Large address allocation", as it not give any benefit at my 2GB RAM, right? (at 2009 that laptop's characteristics looked not so poor, But, I can say, that ORTS goes much more smoothly, rather than MSTS)

"data loging" is not "error log", it describes parameters of ride, and have to be unchecked at Options menu, right?
(I've not set adhesion from 185 to 100% as I didn't use OR to play yet, but, of cource, It's interesting for me to try new setting, So,great, that You remind to me about before-yesterday mistake!)

But, how hat "instancing" actually works, if it causes simulation to freese completly?

[engmod]

>Is "database errors" about signalling, You mean, Vince?
Looks like it.

I would not worry about model instancing with only 2GB of ram, no amount of changed settings is going to improve your experience.
You need to run as low as possible to get any sort of simulation.

>As I understand, I have to uncheck "Large address allocation"
yes

>"data loging" is not "error log", it describes parameters of ride, and have to be unchecked at Options menu, right?
yes

[Weter]

Searching Forum, I've find, that "Model instancing" decreases amount of draw calls, but increases the memory usage, so it maybe ineffective with "Small" RAM size.

[Genma Saotome]

 engmod, on 15 June 2020 - 06:55 PM, said:

There have not been any other reports of model instancing problems.

Not so. I had a severe problem with several unique objects placed many times over and instanced. It resulted in them all jumping and down, oh 18-24 inches, up in one frame, down in the next. It was quite a dance. There were a whole lot of each one in the scene and James and I could never figure out the cause -- too many placed objects? Too many polys? The phase of the moon?

The problem was solved by cloning and renaming the shapes so one was changed to A, B, C, D, and E and them randomly changing the names in the world files. The jumping problem went away.