2 Engines not appearing correctly, suddenly

[qballbandit]

Hello,
I've encountered a perplexing issue that just started with a pair of engines. First, these engines performed beautifully for 1 year, and I have made no edits to any of the files. I noticed that when in external view, I can no longer see the engines - just the lights, unless I get very close and at tight angles. Panning will make them appear and disappear. Looking at my screenshots, you can see me panning along the engines, and seeing them then losing them along the way.
What could have corrupted the integrity of these engine files, and/or what should I focus on?
Before you ask, "attach an OR log", there is no mention of these engines in the log. All other engines work fine. When I start ORMG, I am sitting in the cab as expected with all views working. Just goes wonky in any external view.

Any ideas? Thank you!

missing 1.jpg missing 2.jpg missing 3.jpg

[R. Steele]

To eliminate something in monogame version, have you tried loading them in the most recent stable version?

[slipperman]

Hi,
Could it be something to do with the vol_sphere entries in the shape file?
This was posted on this site in 2003 - apologies if it's not relevant.

RE: Custom objects disappear when I view them close up.
Have no idea how you adjust this from within TSM, but you can alter the resulting shape file to fix it.

First, make sure that the .s file is expanded into a unicode text file so it can be editted.

Near the top of the file you will find one or more vol_sphere entries that look something like this:

vol_sphere (
vector ( 0.0092603 183.516 0.102753 ) 210.258
)
vol_sphere (
vector ( 0.0092603 183.516 0.102753 ) 200.246
)
)
Make sure that the last number on the vector line, after the closing parens, is set at a value that is at least 110% of the largest of the three values inside the parens. Exact values are not critical.
For example, in the entries above, I could have specified a value of 221.309 instead of 210.258 and it would have done the job.

Martyn T. Griffin

Cheers,
Ged

[qballbandit]

Hi Gerry,

One point - these engines ran fine for a great length of time in the same version of MG that they now have a problem in. It's not that am having a new issue in a new version.

Hi Ged,
Ya, I have some iteration of that same explanation saved - and I'll look into it (and yours above). Again, it's what suddenly burped and caused this issue that I'd like to get a grasp on.

[slipperman]

Hi Neil,
I get your point
I may be wrong but thought at one time I read that Open Rails doesn't use vol_sphere entries. In that case, it could be a change in Open Rails itself. Have you tried using the v1.5.1 Stable version?

Cheers,
Ged

[rdayt]

System update?
I'm pretty sure that's why my map window stopped working right.

Randy

[jbtower]

Hey Neil did you delete the files and then reinstall?

[qballbandit]

Not sure how a System Update would select one pair of engines in a folder to corrupt from a display standpoint. Also, I did not delete and re-install. The unfortunate thing is - I just last week backed up my TRAINSET folder, not realizing this problem had spawned. I have a feeling if I try to re-install from the backup - I will have the same bad set. But, worth a try.

[qballbandit]

Tried deleting, and re-installing the engines which were resent to me by the author. Opened up OR stable v1.5.1, and these newly restored engines don't show either. Bizarro-world is growing.