Railworks America

Hi all,
I had Bills Mojave Trona route running fine on my older pc. I bought a new computer and activated steam on it with a fresh install of Railworks and it has been working well.
I setup Mojave-Trona on the new rig but am having troubles when I approach Cajon, from either within a scenario or in route edit mode with the aerial camera.
As soon as I go past the junction at Cajon, from any direction, I get a dmp file created and the game shuts down. Other than that I have run scenarios from Mojave to Barstow
without an issue, but I can't go any near Cajon.
Would anyone have any idea what may need fixing.

RobK

I suggest setting up logmate start somewhere near the point of the game crash and see what causes the failure. Also you might try running Lattimer's tutorial on third party routes (in the library)
and see if that clears up the problem. In fact I would do that first.

Thanks for the info Buzz. I ran logmate.
Here is what it states at the time of the crash.
I'll check out the tutorial next and see if it helps.

Cheers,
Rob

[RunTimeError 6:36:09 PM] Verify failed:
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM] cNetworkVertexManager.cpp : 161
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM] Expression: vxCount < VX_BUFFER_SIZE
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM] Verify failed:
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM] cNetworkGeomObject.cpp : 110
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM] Expression: mVxBase != -1
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM]
[RunTimeError 6:36:09 PM] Trace mdump.cpp : 282 = Dump taken

You should also check for our old nemesis, "PONtrack.bin" Look here: http://railworksamerica.com/forum/viewt ... =34&t=9915 (fourth post down) This zero byte file seems to creep into a lot of third party "stuff".

I've spent a large chunk of the day using RW tools running the 3rd party route tutorial. Then I went through the supplied assets folder that came with the route, matching assets with the Railworks assets.
There was nothing out of place there. Logmate reports a missing Route.bin file during an activity right up to the crash. I have Tracks.bin and Tracks.bin.MAINLINE.LIGHT in the Networks folder.
I searched for PONtrack.bin and can't find any instances of it anywhere, not even on the old rig. So, I'm guessing it could be a graphics card issue possibly. I will leave the route in situ and try again when the next Nvidia update occurs. I have an old Nvidia GTX 580
I could swap out the GTX 650 and see what happens. From the specs of both cards, the GTX 580 looks better in some regards. On the upside, I can still run trains across the top of the route and I could use Cajon Pass for coming down
to San Bernadino. Still frustrating though.

RobK

Hi All,
I thought I'd post an update of my findings on The Mojave Trona route. As stated before, I have run Lattimers RW tools 3rd party route tutorial on the route and it found nothing wrong. I decided to reinstall Steam/Railworks 2014 back onto my i5 Computer. I had the route running flawlessly on this rig before. After setting it up with a fresh install of Mojave Trona, it is repeating the same flaw. I cannot fly past the Cajon switches without the game taking a dump and shutting down. This rig has an ATI Radeon 6670 card installed, as opposed to an Nvidia 650 on my i7 rig. So I guess I can rule out video drivers as the cause. I should mention, that originally, the i5 rig had Train Simulator 2012 installed and was upgraded over time to TS 2014 as the updates became available. I can only conclude that the upgrades have introduced a flaw that causes this route to crash at Cajon Pass junction.There is no sign of PONtrack.bin on either computer. The Logmate report at the point of the crash is identical on both computers. I can't see that the original creator of the Mojave-Trona route would have changed anything at this point of the route when he was extending its range, yet I have no problems in the Cajon pass route running trains or cameras in the editor past this trouble spot. Is anybody else having this problem?

Cheers,
RobK