Trainz Plus Beta 115373 (TRS22) Now available

[Paul_Bert]

I installed TRS22. The patching from 114800 went smoothly. This is probably the first time when updating that I had no assets that showed faulty and no errors, so all the saved routes and session ran without any changes required.

I do not like the new default grid. When I build a route or extend an existing one I like the bare grid so I can easily align new track and other scenery items.

The glare from the sunlight seems to be reduced somewhat, however I need to do more comparisons with the same routes in 114800.

When I open CM it takes a long time for the installed assets to appear. I have build 114800 on the same hard drive and the installed assets appear almost instantly. I don't know whether other testers are seeing this also with TRS22.

I changed my postprocessing setting to ultra and the images seem to be crisper. Time will tell whether I like this look compared to the images in 114800.

During the next several days I will test many of the features in surveyor to see if there are any issues.

But so far so good.

 

[JCitron]

It is important that beta testers know what to look for,
not just look if their content/route still works.
If something gets called a new version, it needs a lot of improvements
it also needs a unique selling/buying argument (not being a few routes)


Have explained a few times why it's not a good idea if I become a beta tester
I generate ideas, do suggestions to improve, collect what the community troubles
then check the final result (omega testing)


I would prefer a split
-1 a final SP4 fix, so later we can all look back and think, dang TRS19 was great
(and not think if you still kept build 100240)
-2 TRS22 , the new and best TRS ever, with Surveyor 2, climate, super water
animated passengers, multi monitor, point lights etc. etc.

You mean you don't want to join in the fun?

Generating ideas and pointing out problems is part of being a tester. During our testing of the new UDS, we pointed out that pausing the program was important when switching back from Driver to Surveyor. Trying to untangle a bunch of confused AI while they're moving about can become a bit overwhelming. After the recommendation was mentioned, this was implemented in the next text round.

In many cases, I have combined references to forum threads and posts back here in the bug reports. That helps a lot when trying to 'splain something in detail because sometimes others have a better way of saying something, and also it shows that I'm not totally whacko and completely out in the left field. I agree testing everything rather than our own work is the way to do it. The problem is we don't always know what to look for in the beta. This time we were given a heads up on what was done so we can look for that as well. I find too that concentrating only on one major aspect isn't good either. Using everything, as in Surveyor, Driver, and Content Manager rather than only Surveyor, for example, will bring up ugly heads from the bugs. I noticed too that sometimes the quirky bugs are those that are interconnected somehow between Driver and Surveyor, especially with the newer UDS interface.

Some of the things in your post above haven't been implemented yet such as those you mentioned in Surveyor. They'll come with S2.0 when that's implemented. The wheel spin issue has been mentioned Tony in his top thread, and the other SP4 issues have been addressed.

There's a TRS2019 beta coming up soon(tm). I think this is what you want where these same issues will be addressed as well. Remember it's the same base code, so fixing something in one version makes fixing things in another relatively easy.

 

[BN1970]

When I open CM it takes a long time for the installed assets to appear. I have build 114800 on the same hard drive and the installed assets appear almost instantly. I don't know whether other testers are seeing this also with TRS22.

I changed my postprocessing setting to ultra and the images seem to be crisper. Time will tell whether I like this look compared to the images in 114800.

During the next several days I will test many of the features in surveyor to see if there are any issues.

But so far so good.

I have noticed that too. CM takes around 30-45 seconds to load my installed assets whereas TrainzPlus CM was almost instantaneous. Was kicking around on other routes (mohave pack for one) and noticed when doing the sessions all the locomotives have their independent brakes locked on at 200psi, hence it will not move. Other routes (C&O Hinton, Coal Country) all sessions must be broken as I get an immediate CTD when loading those. Will have to check the assets there to see if they are the culprit.

 

[JCitron]

I have noticed that too. CM takes around 30-45 seconds to load my installed assets whereas TrainzPlus CM was almost instantaneous. Was kicking around on other routes (mohave pack for one) and noticed when doing the sessions all the locomotives have their independent brakes locked on at 200psi, hence it will not move. Other routes (C&O Hinton, Coal Country) all sessions must be broken as I get an immediate CTD when loading those. Will have to check the assets there to see if they are the culprit.

I'm not sure if the CM issue has been reported using the bug report, but we've all experienced the same. It may not be an issue and only the results of no precaching that's causing that, but there is an issue when switching custom filters such as going from my out-of-date and not payware filter to obsolete and not built-in or payware filter. When switching, nothing happens until I change to the built-in installed filter first.

I haven't experienced any CTDs, but I have in the past due to exactly the same issue. I had a failing hard drive munching a way at my content without my knowledge until I opened up the assets. A lengthy EDR, after replacing the hard drive and copying the data back, found multiple hosed assets.

To run an EDR, press the CTRL-key when selecting Repair Database from the developer menu on the Launcher.

 

[1611mac]

It is important that beta testers know what to look for,
not just look if their content/route still works.
If something gets called a new version, it needs a lot of improvements
it also needs a unique selling/buying argument (not being a few routes)


Have explained a few times why it's not a good idea if I become a beta tester
I generate ideas, do suggestions to improve, collect what the community troubles
then check the final result (omega testing)


I would prefer a split
-1 a final SP4 fix, so later we can all look back and think, dang TRS19 was great
(and not think if you still kept build 100240)
-2 TRS22 , the new and best TRS ever, with Surveyor 2, climate, super water
animated passengers, multi monitor, point lights etc. etc.

All very good points and comments. The "split" view is a good one. But obviously N3V has already made their decision on how they will move forward. As for beta testers.. I think we know why beta testing is open to anyone with no rules attached. Also, (and sadly,) releases seem to happen with reported issues still open. Releases seem to be geared toward generating excitement and sales (buy Plus and you too can have this....) rather than waiting and getting everything fixed.

 

[HPL]

I can confirm CM is quite slow in TRS22 vs. TRS19: about 5 or 6 seconds before it displays "Installed" assets (was almost immediate before).

 

[Paul_Bert]

I wanted to see if anyone else has these two issues before I report it.

First issue.

I use portals in my routes. In surveyor when I go to the "objects" tab and then "Edit Properties" (the ? symbol) the window opens and I can edit the properties. But when I try to exit the window things freeze up for about 30 seconds before I am returned to the main surveyor window.

This works fine in 114800.

Second Issue.

I think someone else has seen this also. When you place an object, like a building, and try to rotate it, the rotation guide with the numbers comes and goes during the rotation.

 

[Paul_Bert]

I am finding a color issue on the 3DZ ETR 1000 train. If you look at the Sebeno Lake Route and the Pro Trainz ETR 1000 High Speed Run Session, I am finding that some of the cars are a dirty maroon and some are the bright red. For example, 3DZ ETR 1000 1 is the dirty maroon while 3DZ ETR 1000 3 is the correct bright red. It's not the route/session that is the problem but the consists themselves since I use this consist in several of my routes and have the same problem. Everything was fine in build 114800.

 

[deneban]

I can confirm CM is quite slow in TRS22 vs. TRS19: about 5 or 6 seconds before it displays "Installed" assets (was almost immediate before).

I'm not sure if the CM issue has been reported using the bug report, but we've all experienced the same. It may not be an issue and only the results of no precaching that's causing that, but there is an issue when switching custom filters such as going from my out-of-date and not payware filter to obsolete and not built-in or payware filter. When switching, nothing happens until I change to the built-in installed filter first.

I noticed the CM lag installing SP4 - (see this post). The developer apparently made refreshing all open CM windows synchronous and prerequisite to the main simulator window; whereas before the CM windows refreshed asynchronously on a separate process thread that did not hold up the simulator. The developer would never know the difference since he/she sits right on top of the DLS server, so there is no apparent effect at N3V, but a bit a of a lag for us out in the world.

I asked Tony to discuss this with the developer in this post, and in this post, but never got a response.

Are you finding this CM lag is holding is momentarily freezing the simulation in TRS22?

 

[JCitron]

I noticed the CM lag installing SP4 - (see this post). The developer apparently made refreshing all open CM windows synchronous and prerequisite to the main simulator window; whereas before the CM windows refreshed asynchronously on a separate process thread that did not hold up the simulator. The developer would never know the difference since he/she sits right on top of the DLS server, so there is no apparent effect at N3V, but a bit a of a lag for us out in the world.

I asked Tony to discuss this with the developer in this post, and in this post, but never got a response.

Are you finding this CM lag is holding is momentarily freezing the simulation in TRS22?

I wonder why they did that? The DLS is actually located in the US in Texas the last time I looked. It's not like we don't have the CPUs today that can handle more than a single process at a time as well as networks with the capability of opening multiple asynchronous communications channels unless this is a bit of mobile code in there doing that due to mobile communications being different than desktop wireless or wired for that matter.

I have noticed that if a view has been built and CM is closed, then opening up CM again the data-load is quicker and more like we're used to.

 

[deneban]

I wonder why they did that? The DLS is actually located in the US in Texas the last time I looked. It's not like we don't have the CPUs today that can handle more than a single process at a time as well as networks with the capability of opening multiple asynchronous communications channels unless this is a bit of mobile code in there doing that due to mobile communications being different than desktop wireless or wired for that matter.

I agree. For some reason in SP4 TRS19 stopped taking full advantage of those asynchronous capabilities - specifically the CM refresh working in parallel with the simulator action. It may have been done to ensure the CM windows are absolutely accurate before allowing the simulator to proceed (aka a bug fixer), but it did drag on the simulator a bit at certain specific I/O points in the program (such as requesting available route sessions). I am asking if that persists in TRS22 - does the refresh of all open CM windows hold up (i.e. temporarily freeze) the simulator action?

 

[pware]

I think someone else has seen this also. When you place an object, like a building, and try to rotate it, the rotation guide with the numbers comes and goes during the rotation.

I just tried that and did not notice any "flickering" or otherwise of the rotation figure tooltip. I am not using a particularly fast or flashy system with a high end GPU.

 

[JCitron]

I agree. For some reason in SP4 TRS19 stopped taking full advantage of those asynchronous capabilities - specifically the CM refresh working in parallel with the simulator action. It may have been done to ensure the CM windows are absolutely accurate before allowing the simulator to proceed (aka a bug fixer), but it did drag on the simulator a bit at certain specific I/O points in the program (such as requesting available route sessions). I am asking if that persists in TRS22 - does the refresh of all open CM windows hold up (i.e. temporarily freeze) the simulator action?

I haven't seen any performance hit with CM open and the sim running in either version. When I'm building routes, I always have Content Manager open as I check for assets there as well as download assets if I need any. The operation then is seamless.

I noticed, though with TRS22 that after I let Content Manager load up the assets that the second time, I changed views the process was quicker. I wonder if this is due to the lack of precaching with this version. There is a bug, I think, with switching views which I mentioned above. I need to test that before I can send that into the QA Team.

 

[brucem56]

Doors on these JR Engine Shops no longer operate.
_

 

[hiawathamr]

I've tested those and they work on my end without issues. Make sure surveyor is unpause.
Cheers

 

[brucem56]

Ok, they work but I have to go into driver mode to see the changes. Previously I could open/close the doors without leaving surveyor.

 

[JCitron]

Ok, they work but I have to go into driver mode to see the changes. Previously I could open/close the doors without leaving surveyor.

Does unpausing Surveyor help?

 

[brucem56]

Does unpausing Surveyor help?

I didn't know you could "pause" surveyor. I'm assuming the "P" shortcut works the same as in driver?

If so, I tried that and it didn't seem to help. I can only see my adjustments once I switch to driver.

Not to worry, be playing with S20 soon anyway, will try again there.

Thanks for the help.

 

[clam1952]

I didn't know you could "pause" surveyor. I'm assuming the "P" shortcut works the same as in driver?

If so, I tried that and it didn't seem to help. I can only see my adjustments once I switch to driver.

Not to worry, be playing with S20 soon anyway, will try again there.

Thanks for the help.

Pause in Surveyor is in the Tools menu top Item, untick it.

 

[Tony_Hilliam]

1. Texture replacement not working - known issue (being investigated)

2. Content Manager not refreshing - known issue (fixed)

3. Re: Content Manager loading times

Could anyone having a problem please provide details of how many assets you have installed (filter on Installed in CM), and how big your assets.tdx file is (found in the local data folder), and how long it takes to open CM.

4. Mouseover tooltips for rotate - known issue (fixed)

5. Deneban, I did reply and I'm waiting for your full report:

"If so, please provide a step by step example with the assets you have open in CM and in-game, and what the time delay used to be and what it is now. Any change in performance or time to execute anything is unintended so having a test case before and after is required."

In response to that you also said you'd post a youtube video but I don't have a link for that. I would suggest submitting your information via the Trainz Bug Report form so that it can be followed up through our official process rather than 7 different forum threads where things will be lost.

I can reiterate that we're based in Oz so no where near the server, so this isn't related to the issue you're seeing. Just stick to spelling out the problem in details and we can let the dev team work out the cause and how to resolve it.