Bulk asset update issue

[pware]

However, the point I was making is that this was never an issue with any versions before TRS22 SP4

It has been in Trainz Plus for some time now, well before SP4 was released. I cannot recall when the Bulk Update for S20 first appeared but it was one of the first things I noticed.

I just tested it using Surveyor Classic as the Trainz Plus interface and it was exactly the same process, in the time taken, as in S20.

The size of the layout also affects the time taken.

Yes, that is correct. In my largest layout the process took about 2 minutes but individual experiences may vary.

There has been a retrograde step.

As @grazlash pointed out there were issues with the old classic bulk replacement process, a few of which I encountered over the years as well. If this newer process does a more thorough and accurate job then the extra time taken is a progressive step, in my opinion.

I presume that someone has sent a message to the help desk?

Better still, have you filled out a bug report?

 

[bolivar]

@pware. I will in the morning, but how about you fill one out too! Two complaints are better than one!

 

[pware]

but how about you fill one out too!

To be honest, I have no complaints about the new process and its delay. As I stated in my last post ...

If this newer process does a more thorough and accurate job then the extra time taken is a progressive step

So I do not consider it a "bug" but a necessary change in the operation of that feature.

I recently submitted a "Bug Report" about a change in the behaviour of another feature - setting the default colour in the Color Effect Layer (Trainz Plus only). The response from QA made sense to me in that any previous behaviour (from some time ago if I recall correctly) did not match what should actually be happening so the new behaviour is actually the correct one in that case.

I suspect that their response in this case will be the same.

My thoughts.

 

[JCitron]

To be honest, I have no complaints about the new process and its delay. As I stated in my last post ...


So I do not consider it a "bug" but a necessary change in the operation of that feature.

I recently submitted a "Bug Report" about a change in the behaviour of another feature - setting the default colour in the Color Effect Layer (Trainz Plus only). The response from QA made sense to me in that any previous behaviour (from some time ago if I recall correctly) did not match what should actually be happening so the new behaviour is actually the correct one in that case.

I suspect that their response in this case will be the same.

My thoughts.

No, this is an awful bug and I've actually had Bulk Update freeze after doing multiple bulk-update iterations. I reported this to N3V, along with the really, really slow processing which showed up after they started playing around with adding the dumbed down version to S2.0.

When I reported the issue, I was told it was my route that was causing the problem and not Bulk Update, but that didn't make sense because the really slow processing and hanging only occurred after they monkeyed around with things to make it work in Surveyor 2.0

To test their theory, I tried on multiple routes and the processing varied from very quick on a few baseboards to a very, very, long time on larger routes and the hanging issue was still there on a very large route after making multiple updates.

I also reported the weird selection issue in Bulk Update when selecting tracks. This was kind of sort of repaired. When selecting tracks, a whole swath of them is selected instead of the ones that are selected as if there's an invisible radius around the selection tool.

When I reported this again, I heard nothing. The blinders have been put in place and apparently there's no intention to fix this for Classic Surveyor.

What I have issue with is not everyone can or has the ability to use Surveyor 2.0. Sure, they want to move forward but what about those that are using standard TRS22 and the fact Bulk Update doesn't work in the same way Surveyor 2.0 as it does in Classic with its additional features in the tool. To be blunt, this is typical of N3V developers. Break something, leave the dust behind, and then come out with something new, and in the meantime, gaslight the community with nonsense when issues are reported. I've been here going on 21 years, and this has been the same since at least TS2009.

 

[bolivar]

"What I have issue with is not everyone can or has the ability to use Surveyor 2.0. Sure, they want to move forward but what about those that are using standard TRS22 and the fact Bulk Update doesn't work in the same way Surveyor 2.0 as it does in Classic with its additional features in the tool. To be blunt, this is typical of N3V developers. Break something, leave the dust behind, and then come out with something new, and in the meantime, gaslight the community with nonsense when issues are reported. I've been here going on 21 years, and this has been the same since at least TS2009."

Unfortunately in the twenty years of playing this game, the summary of the situation, by @JCitron, is accurate.
@pware. So the bug has been reported by @JCitron. I will not venture to report the bug as N3V knows about the issue and has done nothing to fix it.

 

[pware]

The above as reported by @JCitron is different from my experiences but that does not invalidate any of his observations.

What I do find lacking in S20 is the original ability to only use the Bulk Replace on some baseboards and the rotation options when replacing textures - for those I go back to the Classic Bulk Replace operation.

Other areas where the processing delay has been introduced is in merging and moving layers in both S20 and Classic. Merging is even slower on large routes (in my experience) than the Bulk Replace. Since the order of layers within each group is totally unimportant then moving layers is only needed when you want to merge two layers (in S20 they must be one directly above the other for some unknown reason but not when you switch to Classic) or to move a layer to a different group (i.e. from Session to Route). Although the Classic Move and Merge Layer operations do not give you the option to cancel.

Clearly these are still a WIP with a long progress period. But filling out bug reports is a useful method of reminding N3V even if you get no response. In fact I have just decided to fill one out on why in S20 the layers to be merged must be positioned directly above each other but the same two layers can be merged from any positions in Classic.