Official v128 Thread

[Train-a-Mania]

Nick,
Sorry for the back and forth. What sound card HW are you using?
chrisvw

Sound Blaster Audigy

[mnjrr]

Is anyone, who is encountering the "External Component has thrown an exception message," running in 64-bit? Feedback to this question may be useful to the Open Rails team to diagnose the cause and a possible solution to this error message. Thanks for your feedback.

[csantucci]

I would like to say that I was very impressed about the improvements that already now OR has introduced with respect to MSTS, e.g.:
- high resolution support: looking at the sim on a 1600x900 display is spectacular
- manual adjust of cloud overcast: very realistically done, also the change of lighting on terrain and objects
- possibility to throw every switch on the route, and not only the ones in front and behind you: this opens noticeable room for more interesting activities, together with the possibility of uncoupling wagons also from AI trains.

Thank you to the OR development team: who knows what will be next step?

I have a small hint referring to Passenger view: when in Passenger view, hitting again key 5 could lead to the Passenger view of next carriage having one, and so on. When in last carriage, hitting key 5 could revert to Passenger view of first carriage having one.

Carlo

[dancio]

Issues and Errors

Where does someone report an issue or error?

I noticed that pressing CTRL-Down Arrow will bring the world view below grade and you can see the underside of the rails and train without the ties. Not sure if this is by design or not.

Pressing 5 displays the passenger view. Then pressing 4 (trackside view) is initially from inside a passenger car.

[longiron]

Hi

On the GN_HI-line_V3 route going Westward down the hill I'm seeing some locations where the train suddenly runs level even though the track is still descending. Eventually the loco and cars reach a location where they drop (one end at a time) back down to track level. It's fairly easy to observe, use the "2" view close to the rear of the loco at railhead level.
GaryG

GaryG,
I would like to quote one of our developers - basically we're reading the TDB that Kuji built. It doesn't correctly compute the y coordinates, thus there's an abrupt change as OR reads the next track node.

Here's the developers explanation:
"Let's say you specified an "elevation" angle of 1 degree downward for this section. Here's Kuju's approach: They pivot the whole sheet of plywood down 1 degree. For the elevation change ("rise"), they multiply the "run" by the tangent of the elevation angle. (For small elevation angles, the tangent is approximately equal to the angle in radians, 0.017 for 1 degree.) The problem is that Kuju uses the distance of the end point of the last subsection from the hinged edge for the run. That turns the 176-meter straight's contribution to the run into 162.11, whereas it should be 176.

A rail-pair doesn't stay level throughout a large-angle curve on a grade; in fact, at the far end, it is tipped most where it joins the next section. The grade throughout a curve is not uniform as it should be; a 90-degree curve starts with the specified angle but finishes level.

We must apply a correction to any world file that comes from MSTS because Kuju's elevation angle does not reflect the rise (elevation change) divided by the run (distance traveled along the train path)."

[longiron]

Where does someone report an issue or error?

Please use the forums as OR doesn't have an external bug tracking mechanism at the present time.

[eric]

Possible bug....

When I reach the end of the track, the train continues on the last vector and doesn't derail.

Walked away from a session for a few minutes, and came back to trains floating thru downtown Chicago the other night after over-running Northwestern Station.... backed them into the station with no problems....

Later, I deliberately went off the end of the line in Harvard, let it go for a while, and then reversed. Never did find the track again.... Lat/Long were incrementing/decrementing, but the tile display didn't.

Hardly worth trying to fix, as it was quite fun having an F40 in hover mode....

[muskokaandtahoe]

Possible bug....

When I reach the end of the track, the train continues on the last vector and doesn't derail.

We aware of that one, thanks.

It can be interesting to go wandering around beyond the track.

[sniper297]

Need to put a steering wheel on the engines and we'll be all set. BTW, the correct pronunciation for ORTS is "Oh, RaTS".

[TBlake]

Can't get OpenRails to run yet (Nvidia Video card) problem.

But, I do like that left folder idea



TBlake
'Tony'

[OTTODAD]

Can't get OpenRails to run yet (Nvidia Video card) problem.

But, I do like that left folder idea

Me too , being the father of MINI routes !

What does ORTS report when trying to load a route's activity ?

It creates an OpenRailsLog.txt file on your Desktop you could attach to your message and if larger than 19 Kb ZIP it first.

O t t o

[muskokaandtahoe]

Where does someone report an issue or error?

I noticed that pressing CTRL-Down Arrow will bring the world view below grade and you can see the underside of the rails and train without the ties. Not sure if this is by design or not.

Not a bug, still a to-do.

What needs to happen is for us to add some code to compare the camera altitude against terrain altitude and where the difference is small, say less than 1m, bump the camera upwards. We could also to that sort of comparison against the bounding box of models so the camera doesn't pass thru all the shapes but that would probably result in too much jumping over trees... there not being any good way to tell a tree from a brick wall. So we'll probably just leave it a keeping the camera out of the ground.

[OrangeBlossom]

1: The number of frames per second has been drastically reduced. Where once there were 50 or 60 fps, now suffer from 5 to 15.

I second this result. My FPS topped at 80 in the previous release, it was no greater than 2 to 5 fps with this release.

[OTTODAD]

I second this result. My FPS topped at 80 in the previous release, it was no greater than 2 to 5 fps with this release.

Not here.

ORTS frame rates have been consistent since the beginning, in Window as well as Full Screen mode, most of the time toggling between 38 and 77, FRAPS showing those below.

O t t o

[longiron]

I second this result. My FPS topped at 80 in the previous release, it was no greater than 2 to 5 fps with this release.

Please post your system specs. Understanding your HW will help the OR team diagnose your lack of perfrormance.
Thanks