MS Route Editor crashes Throws me out with an exception pop-up
#1
Posted 19 October 2016 - 04:51 AM
Number of downloads: 1
#2
Posted 19 October 2016 - 05:08 AM
Have you noticed any "funnies" with other programs?
One possibility is a faulty memory chip.
If you are using a PC with more than one memory card and if you are able to, try swapping them over - this applies equally to desktops and laptops, although it's normally slightly easier with the latter.
Cheers,
Ged
#3
Posted 23 January 2017 - 09:31 PM
slipperman, on 19 October 2016 - 05:08 AM, said:
One possibility is a faulty memory chip.
If you are using a PC with more than one memory card and if you are able to, try swapping them over - this applies equally to desktops and laptops, although it's normally slightly easier with the latter.
Cheers, Ged
Thanks for reply Ged. I ran an overnight Windiag which showed nothing. I suspect something interesting is going on. I put a Flush Memory link on my desktop yesterday
http://helpdeskgeek....s-memory-cache/
which seems to help... local computer repair guy is "thinking about it all"...
Timothy
#4
Posted 23 January 2017 - 11:29 PM
If one, you've probably got something really wrong in a lot of your terrain files. If all routes then I'd suspect your hardware.
Which is it?
#5
Posted 24 January 2017 - 01:53 AM
#6
Posted 24 January 2017 - 02:01 AM
Genma Saotome, on 23 January 2017 - 11:29 PM, said:
If one, you've probably got something really wrong in a lot of your terrain files. If all routes then I'd suspect your hardware. Which is it?
Thanks for replying Dave..
It has gradually got worse over a year... now apparent when exporting with TGATool..
#7
Posted 24 January 2017 - 02:23 AM
copperpen, on 24 January 2017 - 01:53 AM, said:
Hi Mervyn - I am still using XP.. I have asked the local computer guy to put a series of bootable memory tests on a flash stick to see if I can get some clues..
#8
Posted 25 January 2017 - 03:08 PM
Yesterday I went through Control Panel, System, Performance, Advanced without finding anything unusual.. or being able to stop the memory "leak"
Today... put in 4GB RAM though XP only says 3.5GB since that is all it is allowed to admit to.
Also chased the computer guy about his supplying me with a XP Pro back-up disk instead of XP Home when he installed a new hard drive a few years ago. I have been unable to run scannow and revert all settings which should do the trick..
#9
Posted 27 January 2017 - 07:38 AM
I then updated page sys size to be half available memory... this has improved the situation a step further..
No sign of computer guy on a Friday afternoon but now I can tackle some jobs I had put aside...
#10
Posted 27 January 2017 - 08:37 AM
MSTS has known problems when in terrain-adjust mode. One tip is to try and keep the camera pointed at the horizon and definitely avoid pointing it anywhere near straight down at the terrain. I also try to keep the terrain vertex of interest away from the edges of the viewport when I'm adjusting them. Some have had luck getting the RE/AE to work more reliably by putting their display into 16-bit color mode, though I am not sure that this is one of those circumstances. Some routes seem more prone to this than others, in my experience, but I've never been able to nail down exactly why beyond superstition.