Finn1707822223 Posted January 11, 2023 Share Posted January 11, 2023 CAN THIS BE PINNED TO THE TOP OF THE FORUM PLEASE? This is a list of bugs that have been reported to RailMaster support and have been acknowledged by a return email. Please feel free to add to this list with the following details. 1, Number of post - Use the next on from the previous reported bug.2, Bug Name - Give it a name for us all to refer to.3, Date reported to RailMaster Support - To help keep track of how long a fix hasbeen needed for.4, Version of RailMaster installed - let us know if you have the pro pack as well.5, Detailed report of problem - Give a good full report of what the problem iswith screenshots or photos if possible.6, Update the post with any responses from RailMaster support. Link to comment Share on other sites More sharing options...
Finn1707822223 Posted January 11, 2023 Author Share Posted January 11, 2023 BUG No 1.Scale Speed Error.Reported 20/06/2021Railmaster version 1.74.2 When trying to configure the Speed Factor settings on Railmaster there is an error on the configuration page.On the dropdown box select the 6.274m (OO/HO Hornby) option and set up the x8 R603 3rd radius double curve trac sections as listed on the Speed Factor box when this option is selected.When the track is assembled, it soon becomes obvious that x8 sections of R603 track is not 6.274m long.The Railmaster guide has a screen shot of the Speed Factor popup box that was different to the one that is seen in the software, this box showed the time to travel 6.274m requiring “Oval of 4 R603 Long Straights + 8 R8262 4th radius double curves”.The track was assembled using the SCARM software to check that the length of this oval, was in fact 6.274m long and the software confirmed this.RAILMASTER SOFTWARE v1.74.2 RAILMASTER GUIDEThe question for this section is, should this test be done on a circle of 3rd radius track as stated (a distance of 3.173m), or should it be done on an oval measuring 6.274m long?This may seem an obvious question, but it will depend on what is written into the code for the measurement, is the distance 6.274 used or is it 3.173 in the calculation for Speed Factor.After more testing with the scale speed and would like to share with you my findings.The loco for the test was a Hornby R3269 CLASS 43 HST Pack.The test track was 4 x R603 long straights & 8 x R8262 4th radius curves, a track length of 6.274m.Hornby Railmaster version is v1.74.5.Timing and speed calculations done with https://www.entwinesolutions.co.uk/scalespeed/ speed calculator. After the loco had been warmed up for two minutes the scale speed settings were set to: Real Loco Maximum Speed (MPH) = 255 Time to travel (drop down list) = 6.274m (OO/HO Hornby) Time to travel (Numeric Entry Box) = 45 These settings were set so the loco would run at its maximum speed around the track and gave a lap time of 5.93 seconds.The track distance of 6.274m and time of 5.93s per lap gave a scale speed of 180.26mph. Next I altered the scale speed settings to: Real Loco Maximum Speed (MPH) = 125 Time to travel (drop down list) = 6.274m (OO/HO Hornby) Time to travel (Numeric Entry Box) = 5.93 I saved the settings, restarted Railmaster and ran the loco at the new maximum speed of 125mph and got a lap time of 10.56s.The track distance of 6.274m and time of 10.56s per lap gave a scale speed of 101.25mph.With the measured speed of the loco at full speed the new values entered into the T to T Numeric Box should have slowed the loco down to give a scale speed of 125mph, it took it below the correct calculated speed to 101mph.It is not until I enter a value of 6.65s into the “Time to Travel” Numeric Box do I get a speed close to the 125mph of 127.66mph with a lap time of 8.38s.It is odd that a longer lap time of 6.65s rather than 5.93s gives the faster speed, normally a shorter lap time would indicate a faster speed.Can you check the code that the “Time to Travel” Numeric Box feeds into as it looks like the calculations that work out scale speed that are affected by this input have an error in them.REPLYS FROM RAILMASTER SUPPORT.07/07/2021HelloWe will let you know when we have an answer for you as this requires some time to be spent setting up the example loops, then testing a variety of locos with controllers for timings and double-check the lengths.Rest assured that we have not forgotten about you and will let you know our findings as soon as we have finished looking into this.RegardsRailMaster Support06/01/2022Dear *****We are currently incorporating several fixes and improvements into the next version of RailMaster and all must be working correctly before the update is released.RegardsRailMaster Support11/01/2023Dear *****We cannot give you a date for the udpate as quite a lot of work is involved with it, not just including the software.As soon as it is ready, the program will let you know.RegardsRailMaster Support11/01/2023Dear *****Due to the amount of work involved in what we are doing, we dare not publish a date, or even an estimated one. Let's just say that it will be this year.We may issue an intermediate maintenance udpate to deal primarily with new locos, accessory decoders and loco decoders.RegardsRailMaster Support Link to comment Share on other sites More sharing options...
gilbo2 Posted May 28, 2023 Share Posted May 28, 2023 First signal number visibility persistence.Reported 28/05/2023 (By email, RM wouldn't send support request)Railmaster version 1.74.5Ref forum post Signal number still visible when option "show point numbers on plan" is cleared. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now