Search found 19 matches
- 24 Sep 2021, 17:51
- Forum: Maybe it's a bug
- Topic: Placement of road shapes in error
- Replies: 11
- Views: 37597
Re: Placement of road shapes in error
Ok, after going down several dead end alleys (writing a couple of posts and then some days later deleting them) I think I've got to a point where I can describe an actual problem. I need to start w/ my latest tsection data: TrackShape ( 25528 Filename ( MR_All_n1B_21x025m.s ) NumPaths ( 2 ) SectionI...
- 06 Sep 2021, 18:14
- Forum: Feature requests
- Topic: Remove max value of 10 for StaticDetailLevel
- Replies: 6
- Views: 24596
Re: Remove max value of 10 for StaticDetailLevel
Yeah... that or postpone implementing more than 10 values. Have you settled on a new numbering scheme yet? I know I want the files in \global\shapes to all have the lowest numbers and that I want roads and track to have different numbers but I'm not sure a using only 0 and 1 are the right move (not ...
- 05 Sep 2021, 17:28
- Forum: Feature requests
- Topic: Remove max value of 10 for StaticDetailLevel
- Replies: 6
- Views: 24596
Re: Remove max value of 10 for StaticDetailLevel
Open Rails now will allow and use values up to 99.
- 22 Jun 2021, 03:50
- Forum: Maybe it's a bug
- Topic: Transform error
- Replies: 1
- Views: 15224
Transform error
If the camera is one side of a lite boundary and the object to be transformed is on an adjacent tile a change to either the x or z axis values will cause the object to move to the tile where the camera is located before applying the transform. The practical effect is the transformed object seems to ...
- 04 Apr 2021, 21:45
- Forum: Feature requests
- Topic: Adding Markers
- Replies: 0
- Views: 22326
Adding Markers
Perhaps this is already a feature that I have not found... it would be very handy if TSRE could append an entry to a marker file. There are many times I'm somewhere in a route and need to move away (or stop altogether) and I'd like to return to that location later on. Being able to add a marker (and...
- 13 Jan 2021, 19:50
- Forum: Maybe it's a bug
- Topic: Placement of road shapes in error
- Replies: 11
- Views: 37597
Re: Placement of road shapes in error
TSRE doesn't use any .325m offset. Never saw it and also it would look ugly. Yup... that's every MSTS track shape every made. I guess I didn't write clearly enough. The path trains follow is always 0.325m above the origin point of the track shape. ALWAYS. This is defined by KUJU who picked that dim...
- 12 Jan 2021, 05:56
- Forum: Maybe it's a bug
- Topic: Placement of road shapes in error
- Replies: 11
- Views: 37597
Re: Placement of road shapes in error
A bit more information. The tsection file has a parameter value for path elevation above the shapes origin point. It has almost never been used and it seems in those few cases where it has been use it had the same problem as I described in this thread. What is particularly interesting about this is ...
- 08 Jan 2021, 22:23
- Forum: Feature requests
- Topic: Transform tool
- Replies: 3
- Views: 19062
Re: Transform tool
Just adding another thought. I'm dealing with a problem right now trying to get building models to move up to sidewalks. The problem is at street intersections where there are sidewalks at 90d. The transform tool can move the building towards one sidewalk but that results in moving away from the oth...
- 29 Sep 2020, 04:25
- Forum: Feature requests
- Topic: Minor ease of use suggestions
- Replies: 2
- Views: 17650
Re: Minor ease of use suggestions
Problem : Clearing an area of lots of objects is a tedious, one by one task. Solution : Allow user to drag mouse to select a quad area. Next action (e.g., move, delete) applies to all. Problem : Some descriptions for objects (ref file) require more space to display completely. Solution : Make objec...
- 12 Sep 2020, 04:51
- Forum: Feature requests
- Topic: Minor ease of use suggestions
- Replies: 2
- Views: 17650
Minor ease of use suggestions
Problem : Selecting track or roads within the boundaries of a large tree area can be difficult... you tend to select the tree instead of the track because it's bounding box is large. Suggestion : Display only objects whose StaticLevelDetail() value is less than or equal whatever value the user sets...