MILW Box Cabs and OR Noted and notable Effects
#1
Posted 18 December 2011 - 09:45 AM
I installed OR.7 a few days back and have been running a few trains, and marveling at how far along this version has come from the last time I tried it. But then I tried running my box cabs and was immediately struck at how the models were being rendered, using the latest release version of the E29s and E34s v3 available here in the library. It should be noted that these models consist of a front truck/wag coupled to the body/eng, coupled to the rear truck/wag and so on through each unit. The bodies have a 0.001 meter length in the z dimension to squeeze in between the truck couplings. And this is how they load:
Note the bodies are skewed several degrees to the right and slightly up. They ride like this on tangent track, and depending upon the location on the route, will sometimes straighten out. But once any kind of curved track is entered, the bodies go into a frantic, wild dance. Screen shots don't show this very well, but some idea can be gleaned from this short series:
These shots don't show the extreme fluctuations going on here. Picture these views a hundred times faster in a couple of seconds. It's pretty wild.
This one shows the bucking bronco effect pretty well.
But the clincher is when the units enter a turnout, OR crashes to a grey screen.
Here is the last log entry, although I don't know if that's any help.
OpenRailsLog.txt (11.86K)
Number of downloads: 233
Also here's a thumbnail of my system specs.
This illustrates the arrangement of the consist of each unit, as outlined in red bounding boxes:
As an aside, I also ran a test of my earlier version of the box cabs that have a slightly different consist arrangement. The v1 models' bodies have the rear truck integral, while the front truck is a .wag coupled ahead. They do a less violent jitterbug, almost imperceptible compared to their younger versions. The v1 front trucks "over-animate" through curves, like this:
Anyhow, this is for the team to be made aware of for future reference. Docket it for later. The team has done a great job so far, thank you.
Also, as another aside, I have been considering a total rebuild of these units from the ground up. The current models are using some old textures and odd mapping, and alpha'ed truck frames I'd like to model in 3D, plus make some other improvements.
Thanks again.
#2
Posted 18 December 2011 - 09:51 AM
#3
Posted 18 December 2011 - 10:05 AM
#4 Inactive_mestevet_*
Posted 19 December 2011 - 11:37 AM
Steve
#5
Posted 20 December 2011 - 08:39 AM
I did some testing last evening with Tim's boxcabs and the original Boxcab files. I compared their behavior on two different routes - NEC v4 and PRR Eastern Region. In both cases, the jumping and up & down or side-to-side movement was significantly less than on RMD. Camera #2 perspective also jumped at many of the same times as the Boxcab parts moved, which leads me to think that it's related to the trackwork. I'm speculating that perhaps "rougher" trackwork on the RMD is causing the issue to be more obvious?
On all routes, when the models ran through tight curves the rotation of the main driving wheels bogie appeared to be excessive. Nor I have compared the models running MSTS versus OR. I will try to capture the differences on a video.
#6
Posted 20 December 2011 - 09:19 AM
In the meantime, here's another little problem. The Milwaukee "Little Joe", also a three-part locomotive, when paired, opens like this, a kind of "Super Joe":
A 2-D+2-D-D-2! There's another D-2 hidden in there somewhere! ;)
The same consist in MSTS:
2-D+D-2~2-D+D-2
A single Joe opens correctly.
#7
Posted 20 December 2011 - 10:25 AM
Straight Track, just before curve, Valley T:
On curved track, Valley T:
Straight track, Scalerail, Pacific Electric 2:
The box cabs danced through a very sharp turn, then crashed OR to grey window shortly after this shot.
Also note overhead wire out of alignment, which has been seen in various locations on the PE.
Thanks again.
#8 Inactive_mestevet_*
Posted 20 December 2011 - 12:04 PM
A couple of thoughts come to mind... does Open Rails make use of the MSTS "default.wag"? Something about this started making me think of some issues that came up with "bouncing" rolling stock (of mine) in MSTS when a tester was using a different set of values in their default.wag. Just a shot in the dark.
Another question, since it does seem like maybe there could be some 'route dependence' on this... what I'm thinking is, do these routes have any odd "gravity compensation scale" setting? or some other setting I'm not aware of that could be contributing to this? The reason I'm saying this is that I have run the E29 and E47 set on the NECv4, and my own route (which not surpisingly uses essentially the same setup as the NECv4) and had no sign of this, through curves or otherwise.
Steve
#9
Posted 12 January 2012 - 12:08 PM
timmuir, on 20 December 2011 - 09:19 AM, said:
In the meantime, here's another little problem. The Milwaukee "Little Joe", also a three-part locomotive, when paired, opens like this, a kind of "Super Joe":
Open Rails 2011-12-20 07-36-36.jpg
A 2-D+2-D-D-2! There's another D-2 hidden in there somewhere! :good2:
The same consist in MSTS:
Image1.jpg
2-D+D-2~2-D+D-2
A single Joe opens correctly.
I noticed that every engine in the consist needs a pointer to a real and existing cab view in the .eng file, otherwise it will not be visible in OR.
I had about the same problem with the EL-2B engine, changing the pointer in every .eng file to the .eng file in the cabview folder made the whole engine visible.
Hope this was any use
#10
Posted 20 May 2012 - 06:15 AM
The locomotives are made up of 3 cars, one for each bogie and one for the body in the middle. The middle car has length 0.001m. It has two bogies (positioned where the other cars sit) but no wheels defined, and this is where OR was tripping up. I've adjusted it to work with this situation of "bogies but no wheels".