Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Due to the extremely large number of traincars and stations that did not make use of the attachment culling function, we have set the culling/max draw distance for commodity assets (may also affect passengers, I don't have time to verify this right now) to a maximum of 1000m so as to ensure that performance is not too greatly affected by large numbers of passenger objects. As such it is not possible to cull them at a greater distance.Culling/LOD
-Please put back adjustable Attachment culling (a.attachmentpointname:Cull) via lm files
Both of these are the same issue, and are currently being looked into, and should be fixed in the next update. Unfortunately this was not reported to us until after TRS19 SP2 was released.--View broken assets (that CM does not show red) CTD
The 'performance' tool needs to load and render a large number of instances of objects to provide this function. As such there may be a delay or lag when loading this, depending on the content used. If you have a reproducible case of a specific asset that loaded quickly in TRS19 SP1, but is very slow in TRS19 SP2, then please submit a report via the above bug report form. Please ensure to include specific assets so that we can test these here.--[Performance] on the preview hangs (was good before)
We have updated the TRS19 Main Menu route to make use of more of the new TRS19 content we have been working on (combination of in-house and stock models). We understand it may not suit every region/train, however the aim here is to showcase the abilities of Trainz, and to allow you to see a train of your choice in a highly detailed environment.Main Menu
-A more neutral TRS2019 main menu (or choice)
-A route menu bottom (like it was in SP1)
As noted, this has been passed on to the team, but at this point appears to only be an issue in the 'preview asset' tool. If you are able to reproduce this issue within Surveyor or Driver, then please also submit a bug report via the bug report form for this.-A fixed PB15 (flickering strip on boiler)
The texture size of the F7 cab is necessary to provide the variety of liveries required for a prototypical F7 unit. This is achieved through a tag in the config.txt file of the locomotive using the cab view, and a texture swapping system, so that you don't need to have multiple versions of the same cab view installed (which would require even more space).-Less textures(size)(<50mb in total) in new F7 cab and also RightSide/km/h
Could you please confirm for me the assetID of the 'car 02' object you are referring to?-New Car 02 needs scaling up 50%
Please see my reply to you in your other thread regarding this.-All new buit-in content textures unlocked (according to Zec has no locked textures, but they have)
As noted previously, this is expected behavior so that session data is saved. Otherwise it becomes confusing for users when the data that would be saved to a session doesn't get saved.-A fix for the double save when exit a route/session (confusing for users)
Simply you can sort this using the included filter tools. To show only PBR textures, you would add the 'minimum build version' filter and set this to '4.6'. To show only non PBR textures, you would use the 'and not' filter, then the 'minimum build version' filter and set this to '4.6'.-A fix or sorting for groundtextures, no PBR/Parallax artifacts
This should be resolved in the next update for TRS19.-All scroll bars on every screen in every version should actually be visible
As outlined to you previously, this is an issue with the design of this driver command. As it wasn't made by us, there are limits on what we can do here. However extending the timeout is not an option, as this increases the risk of crashing/freezing Trainz (as well as increases to stuttering and other performance issues).-A fixed wait for Trigger drivercommand (=built-in, and not working(on bigger routes))
if its a timeout, extend the search time, if there is a max, raise the max.
if Too many loco make sure they are inactive(not searched) when no driver
Unfortunately it's simply not possible for us to ensure that every community made asset will always work. This does include assets that become 'builtin', as these only become builtin due to their use in routes/sessions that are included in Trainz or included in a DLC pack. Please keep in mind that content marked as 'builtin' does not indicate that the content is included with the core Trainz installation, it will include content from the DLS that is included in DLC packs.-All basic built-in Driver commands should work, no matter who made them.
We may sometimes have test assets in the Content Store for testing of features/functions/updates here.Content Store
-The new content store often shows items like "demo package #2" probably where people test something
1 time it even led me to a screen with malware on it, make sure they do testing in some offline module.
Could you please double click on this DLC pack, and then tell me what the 'ID' for the DLC pack is so that we can check it here.-Check if all content store item actually have a title, i see a canadian route without 1
This DLC pack was provided for an earlier release of TRS19. IT is no longer required, but may still appear for some users; it can be safely ignored, and won't cause any issues if it is installed.-there is a free package called TRS19 Content fix sc545, if you click
[List Featured Assets] it shows nada
Where possible we provide these details on the relevant script functions in the wiki. Not all obsolete methods use obsolete functions, but rather the method may be problematic in specific situations and as such a newer/better method is provided to prevent this. The 'wait for trigger' command is a good example of a script using a function that is still allowable, but has a better alternative available. In specific situations, the older method will fail, but still works outside of those situations and is likely still useful for many other commands...Required info (supply the basics, the community will write it)
-a page in wiki, stating all obsolete script commands, the reason why,
with just as good alternative and example how to use the new ones.
Unfortunately due to the nature of the development of TRS19 SP2, we simply weren't able to provide a complete changelist. We do hope to make improvements here in the future, but we cannot guarantee this for every update.-a detailed list of all changes SP2 brought and why.
If you want to be able to rollback, then you should create a backup. We do not actively provide support for older releases of Trainz (ie we currently only actively provide support for TRS19 SP2, or updating older versions to TRS19 SP2).Easy Rollback
-if people want to use an older version, TRS19 original or SP1 this should be possible
should be possible to download older version to reinstall.
This has been made very simple by making the builtin content in TANE available for you to download via the content store.Migrating from TANE to TRS19
-if people have a payware/built-in item in TANE, it should be easy to use also in TRS19
the lock should be lifted on import in TRS19.
If you have a reproducible case for other objects (apart from passenger commodities) not respecting the cull value in LODs, then please submit a bug report via the bug report form, and include an example asset that shows this.Culling and LOD
-it was good before SP2, the .lm file has parameters
any Content Creator expects the set parameter will do what they should.
-as posted a few times, i asked for a better (built-in) passenger product,
that makes use of textureatlasses(what N3v promotes), less drawcalls and LOD
As not all locomotives that use the F7 cab (as this replaces the old default one) have this option enabled, and not all locomotives that use an F7 cab are actually an exact F7 (or will exactly match the outline of the F7 cab) this isn't a reliable option for the cab view...Cab F7
-outside-visible-from-cabin 1, + good design and you don't need the various liveries
Thanks, I'll look into this to get it corrected.Car 02 <kuid:942115:105> (built-in since SP2)
place it next to any other car and check scaling
For simplicity we are using a standard license in the assets, that is generated by the config creator tools we have released via the http://contentcreation.trainzportal.com/ website. It doesn't necessarily mean that every part of the asset will always be editable, especially where we are legally not allowed to allow modification of this asset (but we still allow you to open it for edit in Content Manager to see how it is configured).All new built-in content textures unlocked
if you don't, then change the included license
current: This asset is for the Trainz Community. The Trainz Community can create other variations of this asset to be used within Trainz.
should be: this is built-in content, we do not allow modification
If we didn't test in live games, we wouldn't be able to reliably test these against each one.Content Store
-don't let people test in the life game
-It kinda looks very unprofessional as it is now, many (free)content creators websites look better
-make sure it is categorized /tabs\ better Fi:
-Routes
-Loco's (30 of the same US loc, that could easy have used texture-library and texture replacement)
-Trainsets
They can install the assets as part of the DLC pack in the Content Store. If they own TANE, they will own access to the DLC pack version in the Content Store. But you must install the complete DLC pack.Migrating from TANE to TRS19
If people have TANE, they already OWN the assets, it should be easy for them to reuse them in TRS19
The bug report form takes about 5 minutes to fill out, so about the same time as you posting here. If you can post here, you can fill out the bug report form.I don't have time to beta test (or nothing would ever be released)
I do not have the time to bug report anything
Still hoping we get an answer on the original topic question
Will there be a SP2 fix or SP3? and I mean for all versions.
Currently SP2 is not the wise choice to use for Route building or Content Creation
this can be read in many threads (philskene, kotangagirl etc. etc.)
The current team-focus seem to be on mac?
how many mac versions are sold compared to PC versions?
Another issue popped up
-if you try to use SP2 4.7 saved routes/sessions in earlier versions
you loose all layers except Route and Session, so everything on those (other) layers is not visible/gone
(workaround 3457: first merge the layers to pure Route and Session)
All trains in the session are gone, the driver commands lists are still there
Then you also seems to loose all turfx.....(probably cause they are on special layers)
I realize the (save)format have changed, but that makes it even worse to use SP2 as your route building installation
Because of the spline point issues, I don't dare to change anything anymore in my main route
so the question..remains
greetings GM
For our Platinum and SP2 users we're also working on an update which will include the latest bug fixes as well a few tweaks such as a high contrast scroll bar and updates to the Content Store.
The update will be released first as a Beta (to check there are no regressions) and then as an official release soon after. It will also include the Metal and Silicon support for Mac users.
Still hoping we get an answer on the original topic question
The current team-focus seem to be on mac?
how many mac versions are sold compared to PC versions?
Excuse me here, the Mac versions needed some love for years now, and we get it. You are questioning things because we get a little love? Macs were stuck in a catch 22, not as much usage because hardware wasn't as powerful and not much usage causing software lagged behind and unable to take advantage of hardware. It isn't very encouraging to keep hearing promises. With these updates, we can take advantage of our hardware and we know there is a future.
G.M. -
Respectfully - You are making too many assumptions here. Add also that some people may choose not to use newer versions for various reasons. Many people are still using pre-TRS19 versions (Tane and earlier). Does that mean TRS-19 should not be used? Of course not. Focus on what works for you and don't make judgments for others.
The spline point issue is being addressed according to Tony.
May be i am getting something wrong but i did not read anything about NOT to use TRS19, wich is a fine program altogether.
-snip-
Thanks
IMPORTANT NOTE:
Track laid in 470 will change alignment in the next update. This won't be noticeable in the majority of cases, but will be seen in curved track with a large distance between spline points.
A recent bug fix introduced new behaviour for track splines (most often noticed when doing a bulk replace, but they would happen any time you replaced old track with new splines). After a detailed investigation we will be reverting the recent change.
What this means is that you should not attempt to realign track using your current or previous Trainz Plus Beta builds. To be safe, avoid laying any track that is important to you.
Note that this issue relates to alignment only. Spline nodes and heights are not affected and only the curvature between points is affected.Is this the spline issue you refer to?