Access Violation error

[4ndylloyd]

Good evening fellow Trainz fans from a rather wet South Wales UK.

I have started getting the hardware access violation error message on one of my routes. I have not posted details of the error because it has been posted many times before by other users but despite following the advice in previous posts I cannot get rid of it.

I am running TRS06 with SP1 on Vista and it has run faultlessly until now. I seem to get the error everytime a train moves off from a certain part of the route. I have a terminus station which a train will depart from but will stop momentarily at a signal at the station throat and just as it starts to move off the game crashes and I get presented with the error dialogue box. Strangely though it wil only happen when another train is running torward the terminus from the other direction, even though it may be a scale 10 miles away?

I have thought about deleting and relaying the track or removing and replacing the signalling but wanted some advice, if any was available, before I reached for the Beeching axe!

Thanks in advance, Andy

 

[baz66]

Andy. Had the same thing when I was running 2006. Do you have all the upgrades I can only suggest that a certain asset is causing the problem. For what it,s worth. My way to fix. Go into CMP. Click on the route or session that is the problem. Click on main screen and look for assets that have missing deps or are faulty. Make a note of these assets. Go back into trains and load the routesession again and manually check each of the faults. You may take hours but IF theres a problem, You should find it. Let us know if it was such a result
baz

 

[Neil_1997]

same problem

i had that same access violation fatal error thing. it happened with bloodnoks level crossing, everytime i attatch some track to the crossing trs2004 closes
and displays an annoying error message

 

[ColPrice2002]

Hi,

I do remember some problems with sound files - and hornz.

You may have something similar....

Try reducing the session to one consist, when that's ok, use that consist for all the activities - repeat until you find the culprit....

HTH

Colin

 

[4ndylloyd]

Thanks for the advice

Hi all,

Thanks for the advice. CMP tells me that the route has two faulty assests so I have sorted that by replacing them with updated versions on the DLS and quite interestingly I have recenly added a number of hornz triggers as the route is still a 'work in progress'

I am just going to load Trainz and see what happens

Thank again, Andy

 

[4ndylloyd]

Hi again, and many thanks to Colin for pointing me in the right direction. I have found out what is causing the error but I dont yet know why.

My route is double track from a portal to a terminus and back to a portal, there are a number of hornz activators along the way. I have found that I am having the problem with one particular engine which I can watch from portal to terminus and then back to portal without any problems, sounding the whistle as it passes each hornz marker without a problem but if the same engine is running from the portal down to the terminus and I am watching an engine on another part of the route, the access violation error message occurs as soon as the engine travelling towards me (but in the distance) passes over a hornz marker. I have deleted and moved the hornz markers without any effect.

If I dont use the particular engine in question then I dont have the problem but I am rather fond of it and dont want to exclude it from my route. Is it possible that the engine's config file has an entry relating to the 'distant' sounding of a whistle that I could edit or delete to solve this problem??

Thanks Andy

 

[rjhowie]

It's an odd zilch. Ihave had it only rarely - thank goodness. It cropped up on those rarities when I have been working on track and they jump and fuse together

 

[clam1952]

Hi again, and many thanks to Colin for pointing me in the right direction. I have found out what is causing the error but I dont yet know why.

My route is double track from a portal to a terminus and back to a portal, there are a number of hornz activators along the way. I have found that I am having the problem with one particular engine which I can watch from portal to terminus and then back to portal without any problems, sounding the whistle as it passes each hornz marker without a problem but if the same engine is running from the portal down to the terminus and I am watching an engine on another part of the route, the access violation error message occurs as soon as the engine travelling towards me (but in the distance) passes over a hornz marker. I have deleted and moved the hornz markers without any effect.

If I dont use the particular engine in question then I dont have the problem but I am rather fond of it and dont want to exclude it from my route. Is it possible that the engine's config file has an entry relating to the 'distant' sounding of a whistle that I could edit or delete to solve this problem??

Thanks Andy

Just a thought but how about trying a different horn sound for the loco? could well be the sound that is at fault and somehow causing the problem, bound to be a least one similar sounding horn I would think?

Malc

 

[Billegulla]

Is the culprit a steam loco? If it is, does it show a plume of steam when the horn sounds? If the answer is YES to both have a look in the loco's config for a reference to "whistle.tfx"; if that is present exit the config and find the whistle.tfx file and rename it to whistle. (You can always replace the .tfx later.)
This will remove the steam plume when sounding the horn, but it may solve your problem.

Bill.

 

[4ndylloyd]

Hi Bill,

I guess that you are spot on with your advice. The engine is steam powered and does have a plume associated with the whistle. I will fiddle with the config file and see what the result is

Many thanks, Andy

 

[4ndylloyd]

Thanks to billegulla

Bill,

Just a note of thanks. Your advice was perfect, I renamed the file and it has solved my problem with access violation errors

Thanks again, Andy :clap:

 

[Billegulla]

You're welcome. I had the same problem and was put on the right track by Bill69.

Bill.