Auran/N3V...
(Sorry my english is not so good...)
What you provided to the user/customer as Tane is an imposition!
Each update brings a little improvement but many more problems.
After last patch SP2 HF1 to version 90945, Tane is spinning even more.
I make a database repair/rebuild after the update. Then I had over 1700 faulty objects. Built-in objects were suddenly modified and was faulty.
Luckily, i could revert it back to original content. But other which was installed by the DLS, was suddenly also faulty. So I has delete this content. And i has re-download and install it.
In some cases, the content are correct in large part. But I had to repair some objects myself, as far as possible.
But it goes even further...
My father has the same problem.
Only, that he had over 2800 faulty objects.
The strange thing is now... objects which we both has installed from the DLs are faulty in tane from my dad. And in order in my tane.
And to put the whole still the crown... if I click "view errors and warnings" in my content manager, by content which are ok. Suddenly this objects are also faulty.
It's really a cheeky thing to offer the customer such a product.
They should have make/drawn a stop-line and saying that is now a complete new version of Trainz.
This Trainz is not compatible to the older versions and content. You make/build something together to make it backward compatible and gived it a new name: "T:ane".
If I were asked, I would have preferred a new version of Trainz, which worked flawlessly. And not a version that only has unnecessary problems.
Also, you can not expect from the content creator, that they always adapt/repair her whole objects for Trainz or Tane. Nobody is perfect. Above all, if there is never give a proper explanation.
And once they have finished with her 300-1000 objects, there is a new Trainz version and they have to adapt everything to the new version again...
We love Tane/Trainz. But, it is all the more a disappointment that it is not possible to bring out a correct version. Instead, you are already tinkering on a next new "beta" version... T:ane 2018!
(Sorry my english is not so good...)
What you provided to the user/customer as Tane is an imposition!
Each update brings a little improvement but many more problems.
After last patch SP2 HF1 to version 90945, Tane is spinning even more.
I make a database repair/rebuild after the update. Then I had over 1700 faulty objects. Built-in objects were suddenly modified and was faulty.
Luckily, i could revert it back to original content. But other which was installed by the DLS, was suddenly also faulty. So I has delete this content. And i has re-download and install it.
In some cases, the content are correct in large part. But I had to repair some objects myself, as far as possible.
But it goes even further...
My father has the same problem.
Only, that he had over 2800 faulty objects.
The strange thing is now... objects which we both has installed from the DLs are faulty in tane from my dad. And in order in my tane.
And to put the whole still the crown... if I click "view errors and warnings" in my content manager, by content which are ok. Suddenly this objects are also faulty.
It's really a cheeky thing to offer the customer such a product.
They should have make/drawn a stop-line and saying that is now a complete new version of Trainz.
This Trainz is not compatible to the older versions and content. You make/build something together to make it backward compatible and gived it a new name: "T:ane".
If I were asked, I would have preferred a new version of Trainz, which worked flawlessly. And not a version that only has unnecessary problems.
Also, you can not expect from the content creator, that they always adapt/repair her whole objects for Trainz or Tane. Nobody is perfect. Above all, if there is never give a proper explanation.
And once they have finished with her 300-1000 objects, there is a new Trainz version and they have to adapt everything to the new version again...
We love Tane/Trainz. But, it is all the more a disappointment that it is not possible to bring out a correct version. Instead, you are already tinkering on a next new "beta" version... T:ane 2018!
Last edited: