Official v645 Thread

[GoGoran]

I've been unable to get any Loader Process > 25% whilst trying this so it's not immediately clear why you'd have "late" scenery. Could you repeat it with F5 showing "DEBUG INFORMATION" and see what the various Process values are when you first notice that the scenery is prematurely stopping?

I had the debug information on all the time. Render process was around 55% with very little waiting time, a few percents. Loading process was 100% during loading and 0% prior to that. Sound was at 20 - 25%, but only since several sounds were missing, i.e. not loaded correctly by OR (they do work in MSTS alright). Otherwise the sound process would have been at 50 or even 100%, as it always seems to be on other routes/rolling stock. The framerate was anywhere between 25 and 32 fps. I can repeat the journey and log all the data into a file (i.e. let OR do that automatically).

I think this is really odd, since the NEC is not exactly a complicated route. In MSTS with BinPatch, there's no stutter or blips at all, even if i drive straight from Washington all the way to Philly, at 400kmh speed. Nowhere and never.

I just repeated the trip, same settings, and continued on a bit further - and voila, the same phenomenon repeats itself all over again, almost every quarter mile, however not as bad as the first time - one time the track blips out for a second, then, ten seconds later, the scenery disappears for two seconds, then, after another quarter mile, the train runs into a complete void again, for three seconds, until everything pops up again. Frustrating.

Although the NEC is one of the six stock routes of MSTS, I still love it for highspeed runs with trains of all sorts, from the Shinkansen to the Acela. Hence i know exactly how flawlessly it works in MSTS. Like most other routes, by the way, but the NEC is an especially easy one, in terms of its complexity and hardware demands.

I am not a programmer, but I think it might be a while until the OR team adds the antislip parameter as the team is now focusing on reports by members of the train simulator community who cannot get the latest version of OR to work. Not to sound like a killjoy, but OR will get there in due time with adding additional features such as the antislip parameter in due time.

That's OK, Walter. Just wanted to have this point noted somewhere in your long to-do list. And eventually tackled in one of the upcoming releases.

[kox]

for who cannot get the latest or to work, the answer is usually very simple: "Read readme, and install .net 3.5 SP1

[mikephfl]

Mike,
You can always go to the OR log file on your desktop. It logs all that stuff you see go flying by in the DOS B&W screen.

OK, that's where it is. It's complaining about something on line 84 of carspawn.dat, count mismatch. I think I know what that means. The number of spawners at the top doesn't equal the number of lines. I think I can fix that. Thanks for the note about the log location.

Mike

[longiron]

I just noticed that the power for the eng was set at 9200kW, which is twice the original value. I now set it at 6000kW, which is equal to the power of the HHP8, with which the Acela engines are related.

Hi, the Acela engines were rated at about 6,000 HP max (got this data from Wikipedia for the US version) which translates to about 4,476Kw using the HP x 0.746 = kW formula.

On a separate topic, can you please let us know what the Sound Process is when you set your Sound Level Details setting to "0" when doing your high speed thrill rides? :>)
thanks

[OTTODAD]

for who cannot get the latest or to work, the answer is usually very simple: "Read readme, and install .net 3.5 SP1

Very funny !

It was required before !

O t t o

[twpol]

I had the debug information on all the time. Render process was around 55% with very little waiting time, a few percents. Loading process was 100% during loading and 0% prior to that. Sound was at 20 - 25%, but only since several sounds were missing, i.e. not loaded correctly by OR (they do work in MSTS alright). Otherwise the sound process would have been at 50 or even 100%, as it always seems to be on other routes/rolling stock. The framerate was anywhere between 25 and 32 fps. I can repeat the journey and log all the data into a file (i.e. let OR do that automatically).

I think this is really odd, since the NEC is not exactly a complicated route.

Indeed, it's certianly not expected - and I don't think common - behaviour on any of the original MSTS routes. The loading work is very minimal and takes only a couple of seconds per tile (about every 2km) for me and it would need to take much, much longer to cause the missing scenery you're experiencing. Something certainly isn't working normally.

Do you have a similar problem with other original MSTS routes? What about 3rd party routes?

[mbrisben]

I just installed ORTS, tried to run it, and only got a maximum of two FPS running any train on any route. Is there something I'm missing here? In previous versions of ORTS, I got 20-30 FPS.

[2slow4u]

I wanted to point out another glitch I found. It seems that the 640 version does not recognize the path of some routes:

OR 360, all is fine...



OR 640, same route but path are missing...



Thanks!

[GoGoran]

Do you have a similar problem with other original MSTS routes? What about 3rd party routes?

I haven't done extensive testing yet, since OR v0.645 has just come out.

I did use a third party route for the DynamicShadow framerate test, see the dedicated thread, but it's a German payware addon, "GR (German Railroads) Biggetal edition 2006" as found on the comprehensive "GR Gesamtausgabe 2010"-DVD (a real bargain at 30,--, by the way, with a dozen routes and countless German high-quality rolling stock items - basically a sell-out since the company has stopped its MSTS activities for the time being). A medium-complicated route. I did not get any missing track or scenery parts there during reloading, but quite noticeable stutter and a 50% drop in framerates - and it always took five to ten seconds to reload. I repeated that two dozens of times, so it's not a random anomaly caused by a background program or such (besides nothing else is running in the background - firewal is set to block all traffic during gaming, antivirus program is deactivated).

MSTS does not even blink an eye on the same routes, reloading takes places almost unnoticeably (/mem:2048, BinPatch 1.8).

...

I guess there's a chance that this issue is related to the sound implementation of v0.645, which seems to be faulty (high process load, many missing sounds). v0.360 was working alright in the sound department, so whatever changes you might have made there could well be at the root of this problem.

[GoGoran]

I wanted to point out another glitch I found. It seems that the 640 version does not recognize the path of some routes:

I have a similar glitch, when I use the classic OR menu you displayed in your screenshots, but in my case the consists are all missing !
I did not mention it up to now, since in the kindergarten-style menu everything loads and displays just fine.

[ericmp]

One thing that I am curious about is that when I run a diesel locomotive, the exhaust appears to be white, where as in the release video, it appears to be darker in color. Is this normal?

[OTTODAD]

Running routes and scenery being reported disappearing I tested my PRR - East Region MINI which ORTS lets me run as it does the Bernina MINI, but not routes in the MAIN MSTS.

No problems until ORTS crashed with this error shown below, it does not in MSTS.

A lot of hard work ahead yet for the ORTS team !

O t t o

[PORU333]

I honestly have no problem running routes that are in the Main MSTS folder.

Only problem I have had so far is, in one consist, a engine is missing, while in MSTS, it is there. But I am still able to run the consist in ORTS.

[longiron]

Running routes and scenery being reported disappearing I tested my PRR - East Region MINI
No problems until ORTS crashed with this error shown below, it does not in MSTS.
O t t o

Otto,
There are known problems with OR and PRR-ER, due to the creative solutions the team used to make it work in MSTS. In some areas it works fine and in others ... you see what happens. We don't test against PRR-ER, nor is the OR team currently spending any time figuring out how to make the PRR-ER work.

Sorry.

[mnjrr]

Just to add to what Chris said, the issue of the tunnel entrances occurs in the other routes. I believe the OR team has the tunnel entrance issue on the To Do list to fix.