Testing v8.005

[eric]

The same functionality for the textures folder would be quite useful as well

I'll consider it if it's available. The file listing is a byproduct of another activity that happens during the route's loading. I don't know offhand if textures follow that same logic.

[landnrailroader]

I reset some of the values in the startup file to those in my older version, such as mouse speed etc. One thing I did not find was which parameter it is that changes the background color on the edit screen. I was using black text on a white background which is easier on these 85 year old eyes. I noticed the comment about textures and in releasing a few routes over the years, I noticed that most of the large size is from textures more than objects.

Jerry

[eric]

Open Rails also supports rectangular textures with sides divisible by 2. Is this supported by TSRE 8.xxx?

do any of the TSRE v0.8.004 test versions already support non-square texture sizes?

Pecho Lata KS44HUN I've tested this in 8.005f and non-square textures does work, provided the values are divisible by 2.

In my testing, 168 x 128 works as expected. 167 x 127 will not work.

I've been able to open my test shape with the 168x128 texture using TSRE Shape Viewer, Consist Editor and have used the Route Editor to place it in the world as a new object.

If others have rectangular texture they'd like to test, please let me know the results.

capture_5100008.jpg

capture_5100010.jpg

[weichenpfleger]

I tested the list of unused shape files and found that at least in the “Dynatrax files” the “Dynatrax files” listed in the “World files” and therefore used are also listed. The list should therefore be used with caution.

Greetings

Weichenpfleger

[eric]

Yep, I see that. There was logic to ignore track objects. I'm going to roll that back to include the track objects and write those out as a separate file: tracksUsed.txt

[weichenpfleger]

erik, thank you for your great work.

Greetings

Weichenpfleger

[eric]

Testing version 8.005g is out -- fixes the track section and Dynatrax mentioned above, and also prepends the route name for the three text files being created with the listFiles option.

[eric]

Testing version 8.005h will be out tonight -- allows ORTSAICrossingHornPattern to be retained in activity files, and will only create the Used/Unused files if LoadAllWFiles is also true.

[wmuzeke]

Using version - 8.005h
With regard to the Activity Editor, when saving it is keeping the ORTSAICrossingHornPattern entry, however it is changing it to ( 80 ) and not ( US ). The trains seem to blow the correct pattern, nonetheless. The issue I am having is if an activity has ORTSAICrossingHornPattern ( US ) the services, traffic file, events, and loose consists don't show up in the editor. Basically it is ignoring everything after the horn pattern line. If I change it to ( 80 ) everything shows up correctly. It took me a while to figure out what was happening, but I've tested it with several activities and routes.

[eric]

I'll take a look - it might be forcing the value into an integer instead of a string incorrectly.

[eric]

Sorry for the lag in versions -- I have been out of town for the last two weeks, and not able to recompile anything until tonight.

Verion 8.005J fixes the value issue for the horn crossing pattern, and also exposes it on the Activity Settings page so that it can be added to a service file.

[wmuzeke]

Thanks for the update!

Some observations.

Consist Editor
- It's now showing include files that are in the ORTS_EOT folder.

Consist Editor Wish List
- A refresh button (F5, etc.) to reload contents without having to restart.
- A way to filter the contents by folder. For example, typing in "5Pak17" into the search would display only the contents in that folder.

Activity Editor
- Timetable Editor - The calculate function doesn't display the times when they go past midnight, but I don't think this ever worked. Can it be fixed?
- Is there a way to add functionality to adjust the left column width to the Service, Traffic, and Timetable Editors? The Timetable editor has a left-right scroll at least to see the full file name, but the others don't and the longer file names are truncated.


timetable editor.png

[GokuMK]

Hi Eric. I read sometimes your posts and you are doing nice work with all those new features, but you should never ever touch core editing functions, especially those from TDB class, if you are not a master of MSTS engine or don't have an army of testers.

You did some scary changes. Some you already found to be disasters, like this one:

Suspected Root Cause: Gaps in the TDB TrackNode values (left after disabling "DeleteNulls" in v8.003) were occasionally resulting in the TrackNodes value stored at the top of the TDB being larger than the number of actual TrackNodes, and that was causing the Index Out Of Bounds error in OpenRails.

Some you didn't, and someone will have his route destroyed. Well, Open Rails is very forgiving and if we ignore MSTS then the risk is lower and it is not that a big deal, but if someone wants to preserve MSTS compatibility, I would avoid this "8" version at all cost. It is scary.

[eric]

Thanks for stopping in, and I appreciate the comments.

I haven't actually touched the TDB or terrain editing - the bulk of changes have deliberately avoided those.

We do need to add a TDB rebuild function and an ability to try and retain higher resolutions textures after terrain painting. Those are two areas I don't plan to touch without a design document or some better commenting within the code. Both would be better done if guided by you, but that also assumes you have the time.

I've also been pretty clear there are risks associated with testing versions. After almost a year of changes, there's been one critical flaw which you highlighted, and that wasn't an intentional change as much as it was commenting out a function call in error.

[GokuMK]

I haven't actually touched the TDB or terrain editing - the bulk of changes have deliberately avoided those.

I gave you one example of reckless TDB edit abve. Other example that I remember now is change in floating number precision.

Those are two areas I don't plan to touch without a design document or some better commenting within the code. Both would be better done if guided by you, but that also assumes you have the time.

If you want to make any changes in TDB functions, ask first on OR development forum what they think about your suggestions.

Terrain editing is not as risky as TDB editing. If you damage something during terrain editing, only one tile is destroyed in the worst case. And it is usually easy to fix or restore from backup. Also terrain errors are usually instantly visible, unlike TDB errors, when some interactives / signallling issues can be unseen for weeks and later too difficult to fix.