104017
After 56 minutes of running the session went into a loop. As the train approached a drawbridge (which was down) it stopped and moved backward then forward, stopped and repeated the process forever. The train had successfully crossed that bridge 30 minutes prior.
On the same session the train stopped at a signal for no obvious reason and sat there for a minute and then resumed the route. There was NO reason for stopping since it was the only active train on the entire route. A railroad stop sign.
Also, another event on the route (different session time) the train, after 15 minutes of running and successfully passing signals, came to a signal that was red for no reason. Again the only train on the route. This one totally shutdown the session. It repeated on two more attempts. I removed the gantry signal and installed a Safetran ground mounted signal. Now it worked ok. This same signal was a problem in the non-beta version.
So, I went to the problem reporting area. Once again I could not find a way to make a report. I was offered the Wiki, a search box, and this forum but no form to make a report. I have successfully made reports but also had this same experience before. After sitting here for an hour watching a route being run I was in no mood to try to find the evasive process to make a report.
Granted, this is a BETA, but very similar issues occurred in the 100240 edition. Ticketing is allegedly non-beta. Windows is up-to-date. I can run a live TV window while also running TRSxx so it is not CPU/memory resource issues. The flight simulator runs ok, etc..
Why use the Beta if problems occur? Well similar issues happened in the previous working version so I thought that they may have been remedied in the beta. The product has become very pretty. Pretty sells.
After 56 minutes of running the session went into a loop. As the train approached a drawbridge (which was down) it stopped and moved backward then forward, stopped and repeated the process forever. The train had successfully crossed that bridge 30 minutes prior.
On the same session the train stopped at a signal for no obvious reason and sat there for a minute and then resumed the route. There was NO reason for stopping since it was the only active train on the entire route. A railroad stop sign.
Also, another event on the route (different session time) the train, after 15 minutes of running and successfully passing signals, came to a signal that was red for no reason. Again the only train on the route. This one totally shutdown the session. It repeated on two more attempts. I removed the gantry signal and installed a Safetran ground mounted signal. Now it worked ok. This same signal was a problem in the non-beta version.
So, I went to the problem reporting area. Once again I could not find a way to make a report. I was offered the Wiki, a search box, and this forum but no form to make a report. I have successfully made reports but also had this same experience before. After sitting here for an hour watching a route being run I was in no mood to try to find the evasive process to make a report.
Granted, this is a BETA, but very similar issues occurred in the 100240 edition. Ticketing is allegedly non-beta. Windows is up-to-date. I can run a live TV window while also running TRSxx so it is not CPU/memory resource issues. The flight simulator runs ok, etc..
Why use the Beta if problems occur? Well similar issues happened in the previous working version so I thought that they may have been remedied in the beta. The product has become very pretty. Pretty sells.