New stable version bringing new error messages

Hi there. I've just downloaded and installed OpenBVE 1.8.4.4 after weeks of using 1.8.4.3, and for some reason, the new version doesn't handle properly the MSTS shape based externals. I added the MSTS ActHU MÁV Bombardier Talent shapes as the exterior of my Talent for OpenBVE, and it worked great when I used it in 1.8.4.3. But now, in 1.8.4.4, an unexpected error occurs for all of the shapes.

Code:

20:31:14  Plugin Object.Msts.dll raised the following exception at CanLoadObject:A(z) „System.Runtime.CompilerServices.Unsafe, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” fájl vagy szerelvény, illetve annak egyik függősége nem tölthető be. A megtalált szerelvény jegyzékdefiníciója nem egyezik a szerelvény hivatkozásával. (A kivétel HRESULT-értéke: 0x80131040)
20:31:14  No plugin found that is capable of loading object D:\Old-PC\openBVE\UserData\LegacyContent\Train\H-Start_Bombardier_Talent\Object\acthu_5342-1.s

In Hungarian the error text means something like "the file or train, or its plugin is unable to get loaded, the note definition of the train found doesn't match with the link of the train, the exception HRESULT rate is this".


Can you dig into it and find a solution if possible?

Thanks in advance, and have a good weekend!

Marcell

Now that's really odd :/
I've no idea why updating a completely unrelated package broke that binding redirect.....

All downloads are now fixed, although this should only have affected Windows.

Just installed the 23.01.26 nightly build and I confirm the MSTS shape rendering now works again as it has to. This new build can be marked as stable and this topic as solved. Thanks for the fix!

Done that already, not bothered to bump the version number though

(It's not actually anything to do with the code, just a couple of lines in one of the .dll.config files)

Hi there. I've recently downloaded openBVE 1.9.0.2 from openBVE GitHub, and it always puts up an error message: "The original X Parser has been deprecated- Using the NewXParser".
The problem is that it even happens on routes using no DirectX objects at all and shows up as if there would be an error in the route, while there isn't...
So just a suggestion: could you modify this message to be handled as an "INFO" instead of an error, just like "Using the Japanese compatibility signal set" isn't an error as well but an INFO, before putting the 1.9.0.2 on the official website?

Changed to information, although you could also have just changed the XParser option in the main menu to silence it.

TLDR:
Michelle's original X parser was just becoming more and more of a maintenance headache, and also has the no clear licence problem of much of her original code.
It's been removed, but I'm always a little wary of something I haven't found yet breaking as a result.

(Note that 1.9.0.2 isn't a full release, rather a 'testing' release, suggested to try and work out the kinks before pushing something to the main site)