Atomic Systems

Thanks colin,

best regards

Derek

riccardino wrote:

cwgaskell wrote:
Mike,

The only current problem, is that RW crashes when "T" is pressed near the northern border of a 1x1 degree HGT file.
The data values show no anomalies, and the interfaces between adjacent files match exactly.
I have looked, and looked, for anything that could be wrong and found nothing.
So at this moment, I see no problem with the new converted data that will be uploaded in a few days (I hope), other than these crashes.
You will be able to examine them yourself soon.

All the best

Colin

I really don't understand. RS team clearly stated to have fixed this bug. See http://forums.uktrainsim.com/viewtopic. ... &sk=t&sd=a
It's looks like the cat thrown out the door coming back in through the windows

If I remember rightly that particular bug caused a crash when you tried to extract the DEM anywhere

FoggyMorning wrote:

riccardino wrote:

cwgaskell wrote:
Mike,

The only current problem, is that RW crashes when "T" is pressed near the northern border of a 1x1 degree HGT file.
The data values show no anomalies, and the interfaces between adjacent files match exactly.
I have looked, and looked, for anything that could be wrong and found nothing.
So at this moment, I see no problem with the new converted data that will be uploaded in a few days (I hope), other than these crashes.
You will be able to examine them yourself soon.

All the best

Colin

I really don't understand. RS team clearly stated to have fixed this bug. See http://forums.uktrainsim.com/viewtopic. ... &sk=t&sd=a
It's looks like the cat thrown out the door coming back in through the windows

If I remember rightly that particular bug caused a crash when you tried to extract the DEM anywhere

Railworks crashes at anytime it is random now laying track,split tool, join tool placing anythink there needs to be a update to fix this,if you speend 2 hours doing a route and this happens you lose all the work you have done.

balloonist2009 wrote:...if you speend 2 hours doing a route and this happens you lose all the work you have done.

[PantoDame] Ohhhh, no you don't... [/PantoDame]

hertsbob wrote:

balloonist2009 wrote:...if you speend 2 hours doing a route and this happens you lose all the work you have done.

[PantoDame] Ohhhh, no you don't... [/PantoDame]

Is that because you've looked behind you - and pressed F2?

Where????

I don't think I've ever pressed F2 in my life, except in Excel/Windows Explorer...

However, I tend to press the play arrow very frequently and, as far as I'm aware, when you're route building you can pretty-much tell when things are going to go wrong, and when they do I just close down the RW Window thus losing 5 minutes at most. Had I been building for 2 hours without saving my work I'd be fully expecting to lose the lot!


I've been trying to DEM Nottingham recently, and every time I try the border between N51 and N52 with the new files I get a SBHH error, by the way. But I guess that's the point of this thread.

Cheers

Bob

FoggyMorning wrote: If I remember rightly that particular bug caused a crash when you tried to extract the DEM anywhere

This is the bigger one that has been introduced an fixed in the two July releases.
But most of us (not everybody I see) are pretty aware that there is another one that occouurs only with SRTM-1 DEM data and only at some boundaries between latitudes (e.g. 45N 46N in my case). This bug is there since the first release of RS.
RS.com should be aware too of this problem and its support mailbox I'm sure received many reports about.
What I really don't know is if they put it in the to do list and at which priority.
This question as been asked here many times too. Just make a search in this forum for "T key crash"

Regards

Hi,

For those interested in this problem, it looks like we will have to wait for some time, as RS.com have higher priority tasks to tackle before this one, i.e. from an e-mail I received today they said:

"I can only apologise that RS.com cannot provide any resources in this area at the present time (all will become clear soon).

If you could provide the crash dumps I will hold them to one side for a chance to get examined, but sadly I cannot tell you when that chance will arise, so it could be days, it could be weeks. Code time is very in demand and thus very expensive at RS.com.
"

At least they recognise there is problem to be solved.

All the best,

Colin

alanch wrote:

hertsbob wrote:

balloonist2009 wrote:...if you speend 2 hours doing a route and this happens you lose all the work you have done.

[PantoDame] Ohhhh, no you don't... [/PantoDame]

Is that because you've looked behind you - and pressed F2?

Hi its ok to push F2 but it happens at random times, i did just 10min work and it crashed and again after 1 hours work there is a problem with the DEM dater in railworks witch RS.com are looking into.

balloonist2009 wrote:Hi its ok to push F2 but it happens at random times, i did just 10min work and it crashed and again after 1 hours work there is a problem with the DEM dater in railworks witch RS.com are looking into.

Are you saying that RW crashes when you press T to DEM the terrain? If so, make sure you always save by pressing F2 before you press T. As far as Colin and I Know, this only happens for a short distance at the east-west degree boundaries e.g. when you move from 52N to 53N between 52.08N and 53.02N.

alanch wrote:

balloonist2009 wrote:Hi its ok to push F2 but it happens at random times, i did just 10min work and it crashed and again after 1 hours work there is a problem with the DEM dater in railworks witch RS.com are looking into.

Are you saying that RW crashes when you press T to DEM the terrain? If so, make sure you always save by pressing F2 before you press T. As far as Colin and I Know, this only happens for a short distance at the east-west degree boundaries e.g. when you move from 52N to 53N between 52.08N and 53.02N.

Hi no when i push T it dont crash, but if i lay track or use the split and join tool or place things it crashes at random, some time i can work on it for 2 hours and nothink happen it happens at random times.

balloonist2009 wrote:

alanch wrote:

balloonist2009 wrote:Hi its ok to push F2 but it happens at random times, i did just 10min work and it crashed and again after 1 hours work there is a problem with the DEM dater in railworks witch RS.com are looking into.

Are you saying that RW crashes when you press T to DEM the terrain? If so, make sure you always save by pressing F2 before you press T. As far as Colin and I Know, this only happens for a short distance at the east-west degree boundaries e.g. when you move from 52N to 53N between 52.08N and 53.02N.

Hi no when i push T it dont crash, but if i lay track or use the split and join tool or place things it crashes at random, some time i can work on it for 2 hours and nothink happen it happens at random times.

So that has absolutely nothing to do with this thread, then.

Colin/Alan - would your new techniques make it worth revisiting the ASTER DEM data for non-UK routes? At the time this came out the view was that it was very flawed, but perhaps some of these flaws were due to issues with the hgt conversion process.

longbow wrote:Colin/Alan - would your new techniques make it worth revisiting the ASTER DEM data for non-UK routes? At the time this came out the view was that it was very flawed, but perhaps some of these flaws were due to issues with the hgt conversion process.

Hi,

When the ASTER Data was examined, it had hills and valleys in the wrong place, although it did also have a lots of nasty spikes and holes as well as those massive trenches that were in "alanch"'s version - created by BILxSRTM.
It even had what I think I called phantom mountains, such as a mountain over 2500m hight with a base of 300m. I doubt that BILxSRTM or any part of the conversion process would have created that, but who knows, maybe it did.

So in general the quality of the original data was poor. If I have time, and can access the data (if I have not deleted the copy I downloaded, etc) I will have another look at it. I will have to write some new code to do the Lat/Long conversion, and find a reliable conversion algorithm.

The key problem was that until I found the conversion software on OS's own site that I could use (only for Great Britain and Ireland), every time I tried an example of some algorithm, it gave slightly different answers.

All the best

Colin

Thanks. If you were to experiment you might do so on N43E117.hgt, as that's a tile I know well.