Trainz Update Announcement (SP4)

[pware]

This 3 seconds lag with height brush is a bug which happens only in last update

I have build 126280 and have not experienced this bug.

As a test I converted my largest 10m Grid route to HD Grid. That task took several minutes. EDIT: The CM reports that the HD route is now 1693.4MB in size. The original was 284.8MB

I added a new blank baseboard at HD Grid resolution. I set the brush size to 0.5m and the sensitivity to 1% and started raising the ground height.

The response was what I would expect for a 1% sensitivity setting - there was an immediate change in the ground height but at a very low level (i.e. in how much the height increased). Increasing the sensitivity setting improved the level of response but in no case was there a noticeable time delay.

If there is a bug then its cause is not simply just the new update.

 

[pepperref]

Is there an easy way to revert back to my previous build? This 'bug' or whatever it is, makes the terrain tool practically unusable.

 

[JCitron]

Is there an easy way to revert back to my previous build? This 'bug' or whatever it is, makes the terrain tool practically unusable.

A backup of your previous program install and your database prior to the update. Since you have updated your data with the new build, it's no longer useful with the older one.

 

[pepperref]

Report the bug here with as many details as you can and include a link to a working video. If you use Google Drive or One Drive, use that for the video and that will allow you to upload your route to N3V's QA Team to take a look if they have to.

Trainz Bug Report

Turn data collection into an experience with Typeform. Create beautiful online forms, surveys, quizzes, and so much more. Try it for FREE.

n3vgames.typeform.com

I submitted a bug report as you suggested but they only accepted screenshots, not video.

This is so disappointing, not only that it slows down route building to a ridiculous degree, but I'm not the only one who experienced this.

I never had update problems in the past and always wondered if other users with problems made mistakes at their end, but this really makes me contemplate if I'll ever update the program in the future.

 

[jaur1]

Is there an easy way to revert back to my previous build? This 'bug' or whatever it is, makes the terrain tool practically unusable.

 

[jaur1]

I have in my trainz account a trainz 2019 plus installer. So I saved my current local folder, deleted everything and installed 2019 plus. Then I installed all the updates until I arrived to 123794, where I exchanged the local folder for the one I had saved. It was a lengthy process but I worked, I don’t know if there is an easier way to do it.

 

[JCitron]

I submitted a bug report as you suggested but they only accepted screenshots, not video.

This is so disappointing, not only that it slows down route building to a ridiculous degree, but I'm not the only one who experienced this.

I never had update problems in the past and always wondered if other users with problems made mistakes at their end, but this really makes me contemplate if I'll ever update the program in the future.

You can provide links to videos within the report. The QA Team will contact you in a couple of days and you can send them a copy of a video then.

I wouldn't worry about updating in the future. Like any software, make a backup first prior to updating. This will ensure you have something to fall back on should things fall over. The alternative is to wait a month or two until the product settles down, but again backup your data and your program version prior to updating.

Large external backup drives are available relatively inexpensively from Western Digital and Seagate. You can purchase these online or at local office supply and electronics stores.

 

[slenderman8888]

Sorry if I sound like an idiot for this but as someone who recently switched from TANE to TRS22 PE Steam edition. Is my Steam version on the latest update? The Trainz launcher does not seem to have the feature to download updates in there unlike TANE. I assume N3V set up the Steam versions so that updates are simply dealt with by Steam itself? Also will this be the last versions of TRS22 before no doubt N3V start work on TRS25 or whatever the next new Trainz version will be? Since TANE got its final SP4 update in 2020. Asking because I've already found issues with 22 that were not present in prior versions mostly stemming from the AI system. Iirc it has been reported before but for whatever reason AI drivers will now ignore track direction markers and reverse if their destination trackmark is blocked by another train in the way even though I used a "drive to/via" command and not a "navigate to/via" command. Additionally after I ported my content over AI drivers seemed to treat some junctions as missing levers despite the levers not being touched.

 

[Forester1]

In TRS22 you look for updates by going to the Launch Window button "Content Store" and clicking on the Updates icon in the upper right of the window.

 

[sureshot28]

Has anybody used the latest beta 127058 it is horrible on performance everything takes for ever to populate nothing behind the camera stays has to repopulate. Even with sliders turned down makes no difference. Guess should of stayed with the last update lol.

 

[pware]

Has anybody used the latest beta 127058 it is horrible on performance everything takes for ever to populate nothing behind the camera stays has to repopulate.

That is what beta versions do. They usually have the normal caching operations disabled. Each new non-beta update will also take longer to load a route for the first time, but probably not for quite as long.

Guess should of stayed with the last update

Why do so many people install beta versions expecting to use all the latest "tricks and treats" without any of the "bugs" and performance "hits" that are an absolutely certainty?
And why do so many people install the beta over their retail version and not as a separate install?

My beta motto is:

---

• If you are NOT prepared to take on the responsibility of reporting the bugs
• If you are NOT prepared to accept the pain of the bugs and performance hits such as the constant assertion messages
• If you do NOT have the disk space or knowledge on how to install a second and separate Trainz copy

Then DO NOT INSTALL A BETA VERSION.

---

Addendum: Always read the official announcement posts in the Beta Sub-forum of the current Trainz Version Forum. And especially read the Known Issues section - don't just stop reading after the New Features section.

 

[wreeder]

I agree with you 100% but the problem is that is not how N3V sells Trainz Plus. They sell it as a complete usable game with the option to take part in beta testing. The plan was for there to be stable builds every three months but by my count there has been one stable build released in the last year. Asking users to pay the full price of the game every year and then wait for stable updates that rarely come on time is asking a lot of people. The temptation is strong to switch the update stream to beta just to see what is new and not read the announcement thread before clicking the update button when it is presented to them.

 

[pware]

The temptation is strong to switch the update stream to beta just to see what is new and not read the announcement thread before clicking the update button when it is presented to them.

Yes, I take your point but that was been the case before Trainz Plus came along. I recall answering one users complaints (in T:ANE if I can recall correctly) about these strange message windows popping up at odd times when he was using the program. The messages were Assertions and I had to explain what they were, why they appeared and why they were important. He did not realise that he had installed a beta version and did not know what a beta version was.

 

[poolboy]

If you have already paid for game, why should have pay to beta testing?. This build 127058 is a shocking build like wrecking ball. N3V shouldn't have released in this in its currant state. Of course one expect bugs in a beta build but not to extent were game basically unusable.

 

[pware]

If you have already paid for game, why should have pay to beta testing?. This build 127058 is a shocking build like wrecking ball. N3V shouldn't have released in this in its currant state. Of course one expect bugs in a beta build but not to extent were game basically unusable.

No-one is forcing you to beta test.

I will repeat, in case you missed it, my Beta Motto from a few posts above.

---

• If you are NOT prepared to take on the responsibility of reporting the bugs
• If you are NOT prepared to accept the pain of the bugs and performance hits such as the constant assertion messages
• If you do NOT have the disk space or knowledge on how to install a second and separate Trainz copy

Then DO NOT INSTALL A BETA VERSION.

---

Addendum: Always read the official announcement posts in the Beta Sub-forum of the current Trainz Version Forum. And especially read the Known Issues section - don't just stop reading after the New Features section.

My copy of build 127058 works well enough - it is certainly not "unplayable" and I use it frequently.

My advice - delete your current beta copy and continue with your retail copy (you did install the beta as a separate app didn't you?). Wait for the next retail update.

 

[poolboy]

Pware, its rather just ensure that there beta builds are stable and again Of course one expect bugs in a beta build but not to extent were game basically unusable. hopefully N3V will a more stable soon.
Also Yes there obligation to test beta builds but on other hand N3V are promoting subscriptions with the game and are liking people test even when theres no obligation the point here is why should have pay for bugs?
when there customers would expect a sable build.

 

[pware]

just ensure that there beta builds are stable

And how exactly do you do that? You would need to test it on an impossibly wide range of systems, system configurations, driver versions, installed assets (many of which could be from non-DLS/DLC sources), etc. Unless you have the resources of Microsoft (and even they do not always get it right) the only way to test is to release the beta "into the wild" and hope that testers report back. N3V are a small operation with only a few programmers.

on other hand N3V are promoting subscriptions with the game and are liking people test even when theres no obligation

As you just said it. They invite anyone to become a beta tester, not just a restricted cadre of trusted users, and there is never an obligation to become a beta tester. Their beta announcement posts always make it clear what the dangers are and the precautions that testers need to take. What more could they do?

Perhaps they should follow a fairly standard approach used by some in the software industry of insisting that all testers sign a non disclosure agreement, that way we would never get to hear (and complain) about the bugs and problems.

 

[poolboy]

Perhaps N3V should not charge to beta test pware.

 

[paulper]

Perhaps N3V should not charge to beta test pware.

Using a beta version is entirely voluntary. You're not being charged to use it.

 

[pware]

Perhaps N3V should not charge to beta test pware.

If you have set up the beta in the recommended way, as a separate install, then you are only being charged for your original retail version, not the beta. I have 3 beta installs on 3 different computers and I am not charged for any of them.