Recent content by llebrez

Then, there is the case of a missing dependency that is Payware. But yesterday it was not. By yesterday I mean in an earlier edition. So, you smart the system and import that asset from your old install. But when it arrives to this one, it is faulty or converted to payware! (*) And then the...

Must Watch..

I stand wrong in my assumption of Drive to not being there. But in my built, it was faulty! How a built in command can be faulty? I solved the problem by converting from Texture to TGA. And now it shows and works as it always was. Gremlins making things to work today accepting Texture...

You don't specify what command you are instructing the train to follow. Is it Drive to Track Mark, or Navigate to TM ?. With Navigate To TM, it will do that. Then there is the other issue: Are you directing the train to go to an industry? or TM. If it is an industry, tough luck. N3V decided...

Interesting: when I search for asset versions, there are several, with numbers increasing, all obsolete. The one I have as modified, is the :9 and this is the one that I can't make it work (makes no difference, but original uses TEXTURE and I tried converting to TGA). Same no go.. However...

This rule works quite well in TANE. Imported my route with one session to TRS19, built 111951 and it does not work. Tried to re-install this rule and still does not work. Here is the detail: Go to edit rule and select a schedule. then go to upper right corner and try to select a driver...

There is some truth to all this. Buil in assets all have Texture files and these are not shown red or faulty in CM. If I convert them with PEV, they are now TGA, and no faults. Is it worth to modify these? or better leave them alone. If not broken, don't try to fix...

Indeed: Since I have all my assets backed from long ago, I am replacing the latest ones with the old ones. Visually I can't tell any difference. And they work! It just takes time and more clicks on the mouse. However, the old ones have mostly Testures, and the updated ones are TGA, and I...

Thanks for clarifying. Then, I assume that SP3 should open routes with 4.6 and or below? And, SP1 will not open 4.8 Further, changing these numbers in the config file does not convert to whatever number I select. Is there a way to convert the build number in a route?

Just a far off thought: Note my text on the start of the thread. I installed my back-up of the route. This back up happens, or I do once a week, so it is made on a route that was installed on build 111951 TRS19 Latest update. The new install is raw, has not been updated yet. Is it possible...

John: I forgot to mention that in content manager, my route appears in black and white, and others in red. Can't find what the difference of colors mean. Will an EDBR helps? or may damage more things..?

Interesting issue with built numbers: I had to re-install TRS19. Left it without any patch, so it is 105096. It works fine with all the built in routes. Some of them show in the config file as build 4.3 others as 4.6. I import my own route with 4.6 with all the dependencies. As far as I...

Yes! Method suggested by John works. I am able to change letter and path. I did it and my route and sessions show in the routes menu on the launcher. Now, when I try to open the route, it throws an error and freezes the program. All the other routes (built-in), works as always. Content...

Took me awhile to analyze the situation. Let me explain: In my base computer I plug the external drive. Verify the path and it shows the assigned letter E:\ and the path leading to built xxxx Single route with 3 sessions and all the corresponding assets. I am able to edit and play the...

Indeed: One of those methods are the way to do it. And I thought I was doing it correctly. But my mistake was that I was editing the Local data folder in install while this external drive was still connected to the primary computer. When you think it is OK, I moved the SSD to the second...