Atomic Systems

alanch wrote:If anyone else is seeing this, could you please email support@railsimulator.com so that I'm not on my own.

Problem is, e-mailing someting to that address seems to be a hit-and-miss affair whether or not you'll get a 'human' reply (or possibly whether it gets read at all..) - every e-mail I've sent recently seems to have been ignored completely.

USRailFan wrote:

alanch wrote:If anyone else is seeing this, could you please email support@railsimulator.com so that I'm not on my own.

Problem is, e-mailing someting to that address seems to be a hit-and-miss affair whether or not you'll get a 'human' reply (or possibly whether it gets read at all..) - every e-mail I've sent recently seems to have been ignored completely.

Please cut out your negativity - it isn't helpful and just gets boring.

The whole point of my post is the I did get a reply - several replies - and I'm asking anyone else with the problem to email support to show that I am not the only one with this issue.

But as long as RSC is obviously extremely selective about whose e-mails they answer (or possibly even read) it might not be that others are that lucky.

In all honesty mate, if I was working for RSC or in charge of the support email system, the longer you keep up the constant bad mouthing, the more I would bin your emails or even set you to "block". Not to suggest RSC do that, but I wouldn't hesitate if it was me. You are maybe even overloading the system!

USRailFan wrote:But as long as RSC is obviously extremely selective about whose e-mails they answer (or possibly even read) it might not be that others are that lucky.

They have stated many times over and over again that every single one is read. Given the tone that many people exhibit in this forum I would call even reading every single one a courtesy, let alone hitting one of the auto-replies or typing out a human reply.

USRailFan wrote:But as long as RSC is obviously extremely selective about whose e-mails they answer (or possibly even read) it might not be that others are that lucky.

Really getting bored now of this sniping , all your posts are becoming identical, has Otto been teaching you..

Back on topic @ alanch, sorry but I cant recreate it either, all I can suggest is somethings got the same bin/mapping

All emails get read, not everyone gets a reply, we try but sometimes it just does not happen.
Some folks just like to email us and tell us how we should be doing things along with some colourful metaphors, one or 2 are quiet funny.


If you have pointed out an error or a bug then it gets added to our database
You can believe me or not.

Now what happens to that bug/issue depends on rather alot of factors of what the issue is, how critical it is, who can fix it and what needs to be done to fix it/test it and then release it again.

DLC bugs we try to fix sooner rather than later. Core issues have to wait for a code release that happens once every quarter or so. (However It also depends on the issue.)

regards

Derek

alanch wrote:

davveb wrote: This problem always affected my freeware class 86, so it's probably down to something in my original script, rather than an rs.com creation. I never did work out what was causing it, just learnt to live with it. I doubt it's due to control mappers conflict.

Unfortunately, as they have told me more than once, no-one else has reported this error to RS, so at the moment as far as they are concerned it is an isolated problem.

If anyone else is seeing this, could you please email support@railsimulator.com so that I'm not on my own.

I am definitely seeing this sometimes - and as it seems it was also a 'feature' of the freeware 86 I'm a bit surprised no one else has seen it. For me it seems to happen when I tap 'D' quite rapidly (and may be more common when I'm getting low frame rates, but I'm not altogether sure). I will investigate what I need to do to reproduce it fairly reliably and send off an email to support.

nigeltouatievans wrote:

alanch wrote:

davveb wrote: This problem always affected my freeware class 86, so it's probably down to something in my original script, rather than an rs.com creation. I never did work out what was causing it, just learnt to live with it. I doubt it's due to control mappers conflict.

Unfortunately, as they have told me more than once, no-one else has reported this error to RS, so at the moment as far as they are concerned it is an isolated problem.

If anyone else is seeing this, could you please email support@railsimulator.com so that I'm not on my own.

I am definitely seeing this sometimes - and as it seems it was also a 'feature' of the freeware 86 I'm a bit surprised no one else has seen it. For me it seems to happen when I tap 'D' quite rapidly (and may be more common when I'm getting low frame rates, but I'm not altogether sure). I will investigate what I need to do to reproduce it fairly reliably and send off an email to support.

Thanks Nigel - I know you aren't the only one. I can recreate it very consistently - just have to have the Tap Changer lever on hold with a few notches set, tap D a couple or three times, and the lever moves to Run Up (is that what it is called?) on the second or third tap.

The camshaft on the real machine moves quite slowly whether you use the "Step" or "Run" settings - which is why you see drivers in the few available cab videos making very deliberate movements of the handle.

As such you should similarly space out your keypresses if you want individual steps up. I think the steps take about 1 second each to apply, so use your favourite second-counting technique to time it, and then the script won't see double-presses and get confused about what you want.

To RSC: one thing that might help make this intuitive to new drivers is to lengthen the animation of the handle to and from the step positions. A quick tap of the key should be enough to trigger it, but there does need to be feedback of some kind that it takes more time than button-mashers might expect.

I can confirm that I am also having this issue where the tapper will set itself to runup position when I am tapping the "D" key. Also, I have noticed that whenever I return from a saved game, that the Tapper is in runup position, the reverser is in reverse and the visors are in the down position. It does not matter what position they were in when I saved the game. This only seems to effect the animation files for the controls as the actual contol values seem to be correct and when you touch the keyboard the controls often "snap" back into the correct position.

I have never installed the freeware class 86 version so I do not believe that this is due to some kind of conflict with existing freeware content.

pikehkr

Kromaatikse wrote:The camshaft on the real machine moves quite slowly whether you use the "Step" or "Run" settings - which is why you see drivers in the few available cab videos making very deliberate movements of the handle.

As such you should similarly space out your keypresses if you want individual steps up. I think the steps take about 1 second each to apply, so use your favourite second-counting technique to time it, and then the script won't see double-presses and get confused about what you want.

I have been timing myself - not one second but 10 as a minimum - but I still get the problem I have described.

pikehkr wrote:I can confirm that I am also having this issue where the tapper will set itself to runup position when I am tapping the "D" key.

I have never installed the freeware class 86 version so I do not believe that this is due to some kind of conflict with existing freeware content.

pikehkr

Could you please make Railsimulator Support aware that this is happening to you as well, by emailing them.

There is no possibility of a conflict with the freeware version - the lua scripts are in different folders, and believe me, I've looked at all the relevant bin and lua files. This was a red herring proposed without any evidence.

I've had a little go at reproducing this, and for me at least it does seem to mainly happen when I'm pressing 'D' during a hard disk access stutter. I had a go driving through the countryside at 30+ fps and couldn't get it to go wrong at all, but near Motherwell I could get it to do it fairly easily. I have passed this on to RS.com support, so we'll see if they can fix (or even reproduce) anything.

In that case it may be due to the timing going wrong when the framerate is low. This is really nothing new - I get considerably less precision on control adjustments with diesel trains when the framerate is low as well - especially frustrating with the 37's very fast brake handle.