MasterTracklayer
Well-known member
Please read the last edit above, even if you`ve already seen the message.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Good to hear. TrainzUtil doesn't output much in the way of information when run from the command line. By default, it sends the output to the screen in the program, meaning the log that we can't save.Update: I now have TrainzUtil.exe commands running successfully from inside jEdit. I should soon be able to edit my script files in jEdit and commit them to the trainzbase without exiting the editor. Reviewing errors and warnings will also be possible, as will many of the other Content Manager commands, although some of them would work better if I could see the command`s progress as it runs, and having the editor able to see and process them on-the-fly would also be useful, but I don`t see any way to do that with any of the editor`s scripting facilities I am familiar with. At least it is working, whatever the inconveniences.
Thank you.Good to hear.
That all depends on which command you run. Some of them generate huge quantities of output.TrainzUtil doesn't output much in the way of information when run from the command line.
/* beanshell commands:
source(".jedit/macros/_Custom/Trainz/Library.bsh");
trainzInstallFromPath(TrackLibLibraryPath);
trainzCommit(TrackLibLibraryKUID);
trainzValidate(TrackLibLibraryKUID);
*/
runTrainzUtilCommand(String Command)
with the command mentioned in the name and the data supplied in the parameters. runTrainzUtilCommand
always dumps the output into a new buffer.TrainsUtil Help
output and one that runs a DataBase Rebuild.Something seems to be wrong with my trainzbase. Something seems to be so wrong with my trainzbase that a DataBase Rebuild refuses to complete. Something seems to be so very wrong with my trainzbase that an Extended DataBase Rebuild refuses to complete.
Good to hear, Annie. It could be that it's a fresh installation without all the extra baggage that comes with it when upgrading. I found that on my own installation that even though the old one crashed badly, the new one has been a dream to use, albeit, for the reported bugs we're all aware of and hope N3V will fix them soon(tm).I now have the retail version of TRS22 PE installed in Debian Linux using the Lutris interface with all available update patches loaded in. All is good, - very good in fact. To tell the complete truth that surprised me since recent updates for TRS22 caused all kind of problems for some Trainz folk. Perhaps I got away with it because I'm not running Windows or DirectX.
Still running Debian Linux on my older model HP Z200 Xeon computer and it seems to be coping Ok.
Overall, it's pretty stable. I have found that doing a large bulk update of textures does hang the program. This was reported and I was told it was my route, and now there are reports of others having the same issue. Since that's an issue, I do this carefully and save often so not to lose anything. Driving as you know is hit or miss and I think this is related to the new TLR initiative they're on. Hopefully, that will be resolved soon(tm) because that's really frustrating. If you can live with the caution and not fire your drivers, you'll be fine.So far it's all good John. I installed TRS22 PE to help out with some route testing on a large WIP project and a build 5.4 install was necessary. By the time I'm finished I should have a fairly good idea just how good TRS22 PE actually is.
I did manage to figure out the issue with the automatic fireman. It can't be saved anymore as a permanent setting in Surveyor and now has to be done each time in Driver when an engine is used. Somewhat of a nuisance, but at least it is still available to be used. So far I've been driving engines myself and I haven't tried setting up any AI runs yet so I haven't struck any problems. From what I can see here on the forums the TLR thing is a buggy mess that's barely fit for purpose and since it's spilled over and is affecting ordinary non-TLR AI sessions I can see why everyone is annoyed about it.Driving as you know is hit or miss and I think this is related to the new TLR initiative they're on. Hopefully, that will be resolved soon(tm) because that's really frustrating. If you can live with the caution and not fire your drivers, you'll be fine.
Nice, another thing broken probably by the TLR code as that seems to affect the drive-ability outside of that realm. You are being kind. A buggy mess is an understatement.I did manage to figure out the issue with the automatic fireman. It can't be saved anymore as a permanent setting in Surveyor and now has to be done each time in Driver when an engine is used. Somewhat of a nuisance, but at least it is still available to be used. So far I've been driving engines myself and I haven't tried setting up any AI runs yet so I haven't struck any problems. From what I can see here on the forums the TLR thing is a buggy mess that's barely fit for purpose and since it's spilled over and is affecting ordinary non-TLR AI sessions I can see why everyone is annoyed about it.
I'm running Debian Linux on an almost ten year old HP Z200 Xeon computer with 16Gb of RAM and a 4 core Xeon processor that would eventually become the precursor for the i7 CPU. Scarcely cutting edge.I was wondering if you guys can tell me something about this...
Does it appear to use less, more, or about the same amount of memory (RAM) when running on Linux?