We have received your request and our team will get back to you shortly. You can log in to the helpdesk to review the status of your request, or check your email for further updates.
[TABLE="width: 930"]
[TR]
[TD]General Information
[/TD]
[TD]
[/TD]
[/TR]
[TR]
[TD]
[/TD]
[/TR]
[/TABLE]
[TABLE="width: 100%"]
[TR]
[TD]Ticket ID
[/TD]
[TD]#XZY-707-81697
[/TD]
[/TR]
[TR]
[TD]First and Last Name
[/TD]
[TD]urgul
[/TD]
[/TR]
[TR]
[TD]Email
[/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Type
[/TD]
[TD]Support
[/TD]
[/TR]
[TR]
[TD]Priority
[/TD]
[TD]Medium
[/TD]
[/TR]
[/TABLE]
[TABLE="width: 930"]
[TR]
[TD]Subject: Merge (fusion)and TurfFx
[/TD]
[TD]
[/TD]
[/TR]
[TR]
[TD]
[/TD]
[/TR]
[/TABLE]
[TABLE="width: 100%"]
[TR]
[TD]Hello
When merging routes with effect layers, only the effect layers painted on the first route will be kept in the merged result. This is exactly the same as when merging routes with sessions - only the session that was loaded with the first route will be retained in the resulting merged route and session.
Under these conditions, how to join several modules (Routes) without having to repaint the effect layers on one of the joined routes ???
It is really disappointing that this fusion does not keep the layer effects on the two joined routes (but on only one whatever the tests, see test below) !!!!
As much as this can be understood for the merging of sessions for operating reasons of 2 separate sessions merged into one, as much as it is not understandable for the placement of assets, even dynamic ones, since the ground textures are placed with a similar technique...
Do you plan to improve this operation in order to be able to take full advantage of the TurfFx effects?
Hoping that a quick solution can be found so that we can continue to fully enjoy Trainz.
Below are the tests performed by “Pware” from the auran forum
I have been doing some experiments on this issue.
I created two new routes, each consisting of a single bare baseboard.
Experiment 1:
On Route 1 I added (painted) three TurfFX effect layers (call them "A", "B" and "C") from my existing presets (built-in effect layers or ones I have created and saved as presets). I saved the route.
On Route 2 I added (painted) a single TurfFX effect layer (call it "D") modified from one of the existing presets but not saved as a new preset. I saved the route.
I exited Surveyor and reloaded Route 1. I then successfully merged Route 2. Layers "A", "B" and "C" were still present and visible in the merged routes. Layer "D" was not visible (painted) on the merged route.
Experiment 2: Repeat of experiment 1 but this time I saved the new TurfFX effect layer "D" as a new Preset.
On Route 1 I added (painted) three TurfFX effect layers (call them "A", "B" and "C") from my existing preset (built-in effect layers or ones I have created and saved as presets). I saved the route.
On Route 2 I added (painted) a single TurfFX effect layer (call it "D") modified from one of the existing presets and then I saved it as a new preset effect layer. I saved the route.
I exited Surveyor and reloaded Route 1. I then successfully merged Route 2. Layers "A", "B" and "C" were still present and visible in the merged routes. Layer "D" was not visible on the merged route but it was present in the list of Presets and it could be "painted" into the merged route.
Experiment 3: Repeat of experiment 1 but using the same effect layers in each route.
On Route 1 I added (painted) three TurfFX effect layers (call them "A", "B" and "C") from my existing presets (built-in effect layers or ones I have created and saved as presets). I saved the route.
On Route 2 I added (painted) a single TurfFX effect layer ( "C" from Route 1). I saved the route.
I exited Surveyor and reloaded Route 1. I then successfully merged Route 2. Layers "A", "B" and "C" were still present and visible in the Route 1 part of the merged routes. But layer "C" was not visible in the Route 2 part of the merged route.
Conclusion:
When merging routes with effect layers only those effect layers that are painted on the first route will be retained in the merged result. This is exactly the same as when merging routes with sessions - only the session that was loaded with the first route will be kept in the resulting merged route and session.
[/TD]
[/TR]
[/TABLE]