Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSTS .s files no longer loading in ObjectViewer #1134

Open
soyachoin104 opened this issue Mar 23, 2025 · 5 comments
Open

MSTS .s files no longer loading in ObjectViewer #1134

soyachoin104 opened this issue Mar 23, 2025 · 5 comments

Comments

@soyachoin104
Copy link

At least since the March nightly builds (currently using the 23rd March build), MSTS .s files no longer load in openBVE. Attached is a screenshot of the error message. What could be the problem?

Thanks

Image
@leezer3
Copy link
Owner

leezer3 commented Mar 24, 2025

I can't reproduce this.

Please can you link me to the object file that's no longer loading. (It's probably animation related)
There have been a lot of internal changes with regards to MSTS objects to support animations.

@soyachoin104
Copy link
Author

https://www.mediafire.com/file/dt63ecxuezypfdw/Ale5_CaravaggioTrenord_2025.zip/file Sorry for the delay, here is the one I have been trying to load

@leezer3
Copy link
Owner

leezer3 commented Mar 24, 2025

That's an interesting one.

MSTS expects the bogie matricies to be at BOGIE01 BOGIE02 etc.
This object is using an underscore to add additional comment data at the end, which I wasn't taking account of. This now works, but the object is definitely rather slow. (~5fps here, and this is with a 3060)

Loading a 47mb textual file isn't clever either.

Let me do some more work with this one and see if I can get things any faster.

@soyachoin104
Copy link
Author

I have noticed that models built for OpenRails are built a little differently to older MSTS specific models. I don't know if that has anything to do with the problem?

@leezer3
Copy link
Owner

leezer3 commented Mar 24, 2025

Possibly, I haven't really investigated the differences.

The build from today implements face squashing into the shape parser itself. This makes your model run in the simulation at a sensible speed :)
(It's still rather slow to load mind)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants