There is a problem with both BI3 and MIN industry tracks that only happens when certain conditions are met which is why it has gone unnoticed until now. I discovered this while testing one of my BI3 Industry Tracks and the root cause of the issue was confirmed through extensive testing by Paul Cass (pcas1986) who also came up with a way to fix the issue.
If two products have the same exact same in the product list for the BI3/MIN track then strange things will occur in the "Track" tab. In this case the issue was with the following two products of Dave Snows that had the exact same name:
<kuid:101046:101876> Lumber Load for Gondola DES (Product)
<kuid:101046:101772> Lumber Load for Gondola DES (Product)
They are both included in the <kuid2:439337:105605:2> SAP_BI3_Wood_and_Lumber product list. When I attempted to select another product in the track tab of the BI3 track it listed another product that I did not want. Here is the explanation for this from Paul:
"Let me start with an explanation of the problem: In your config.txt for this asset you have 41 queues with 41 products. All the products have unique KUIDs but two have exactly the same name – “Lumber load for gondola DES (product)”. Both assets are by Dave Snow and they appear to be the same product although one is “packaged”. One is queue 12 and the other queue 15. In the Tracks panel and when you click on the + icon, a popup list appears of the product you want to add. The code to build that list looks for duplicates and, since queue 12 and queue 15 have the same name, the second product is left out of the list. The list is then sorted in alphabetical order. When a choice is made, the code identifies the product name and the index of that product. The code that actually adds the product together with the Mode and Queue, rebuilds the product list but does not look for duplicates. So this means the new (internal) list is one item longer and the result, in this instance, is that the wrong product is added to the Tracks list. There is an anomaly where the code will often return the right product. If the chosen product is ahead of the duplicated product in the list then the result will probably be correct."
I ran a test this morning of the <kuid2:439337:105605:2> SAP_BI3_Wood_and_Lumber track after one of the two identically named product listed in that track was changed and the problem was solved so this is a confirmed solution to the problem at this point.
What to do if you run into this problem: If there are any products listed in the products list for the BI3/MIN track that have identical names then the simplest way to fix this problem is to modify one of the names of the two identically named products to something else. This then fixes the issue.
If you create products for Trainz: If you create products for Trainz please ensure that they do not have the same name as an existing product in Trainz or this issue will popup if two products with the same identical name show up in the same BI3 or MIN industrial track.
BTW Dave Snow has submitted the product (ie; <kuid2:101046:101772:1> Lumber Load 2 for Gondola DES (Product)) with a changed name to the DLS today which will fix the issue with the <kuid2:439337:105605:2> SAP_BI3_Wood_and_Lumber track.
My thanks to both Paul Cass and Dave Snow for their help in resolving this issue.
Bob
If two products have the same exact same in the product list for the BI3/MIN track then strange things will occur in the "Track" tab. In this case the issue was with the following two products of Dave Snows that had the exact same name:
<kuid:101046:101876> Lumber Load for Gondola DES (Product)
<kuid:101046:101772> Lumber Load for Gondola DES (Product)
They are both included in the <kuid2:439337:105605:2> SAP_BI3_Wood_and_Lumber product list. When I attempted to select another product in the track tab of the BI3 track it listed another product that I did not want. Here is the explanation for this from Paul:
"Let me start with an explanation of the problem: In your config.txt for this asset you have 41 queues with 41 products. All the products have unique KUIDs but two have exactly the same name – “Lumber load for gondola DES (product)”. Both assets are by Dave Snow and they appear to be the same product although one is “packaged”. One is queue 12 and the other queue 15. In the Tracks panel and when you click on the + icon, a popup list appears of the product you want to add. The code to build that list looks for duplicates and, since queue 12 and queue 15 have the same name, the second product is left out of the list. The list is then sorted in alphabetical order. When a choice is made, the code identifies the product name and the index of that product. The code that actually adds the product together with the Mode and Queue, rebuilds the product list but does not look for duplicates. So this means the new (internal) list is one item longer and the result, in this instance, is that the wrong product is added to the Tracks list. There is an anomaly where the code will often return the right product. If the chosen product is ahead of the duplicated product in the list then the result will probably be correct."
I ran a test this morning of the <kuid2:439337:105605:2> SAP_BI3_Wood_and_Lumber track after one of the two identically named product listed in that track was changed and the problem was solved so this is a confirmed solution to the problem at this point.
What to do if you run into this problem: If there are any products listed in the products list for the BI3/MIN track that have identical names then the simplest way to fix this problem is to modify one of the names of the two identically named products to something else. This then fixes the issue.
If you create products for Trainz: If you create products for Trainz please ensure that they do not have the same name as an existing product in Trainz or this issue will popup if two products with the same identical name show up in the same BI3 or MIN industrial track.
BTW Dave Snow has submitted the product (ie; <kuid2:101046:101772:1> Lumber Load 2 for Gondola DES (Product)) with a changed name to the DLS today which will fix the issue with the <kuid2:439337:105605:2> SAP_BI3_Wood_and_Lumber track.
My thanks to both Paul Cass and Dave Snow for their help in resolving this issue.
Bob
