openBVE playing BVE5 routes

I've seen some people sending images which claimed that the openBVE development build is now able to play BVE5 routes,but I don't see any news from here and even if I downloaded the nightly build,it just won't load.Is this feature officially implemented?

It’s not an official release. Though what I do know is that the build has been privately circulated from a Japanese group i believe. I don’t happen to have a copy myself but I know someone who does. He sent me a screenshot. Though I am unaware of who the developer of the BVE5 route parser is, what I do know is that it’s still a work in progress as some BVE5 routes do not load.

Yes and no

I built a BVE5 parser about 18 months ago. It's in the GitHub PRs somewhere, but it's not 100% functional, and only has the basics implemented.

S520 / Midnightexpress1981 have been doing some further work with this, but it's nowhere near ready for public consumption yet.
It'll get there at some stage, but when dunno

https://github.com/leezer3/OpenBVE/pull/154

Now, S520 , I(ginga81) and F81_tec200 are creating BVE5’s route direct loading parser.
The route parser is very difficult to create, and have to check a lot of issues.
Recently, we are started the OpenBVE Japanese local community at Slack.
This community is open, but we need to maintain easily, so we chosen.
This time, we are check that what route can read, and to find a lot of trouble, we got help with the Japanese community.
Before the commit to Github, we have to solve some issues.

1.Memory allocate issue
This BVE5 parser is adopt with FreeObj technology.
OpenBVE cannot set a lot of FreeObj now.
https://github.com/leezer3/OpenBVE/issues/328

2.If committed, and adopted the PR, the route perser's base technology cannot change easily.
So, before the PR, we have to choose the parsing engine such as Irony(BVE5's), or any others.

3.the Another Trains
The BVE5's the Another Trains were not to run at OpenBVE.
Recently, OpenBVE add the new Function 'TrackFollowingObject'.
The demo movie is here.
https://youtu.be/D4K3iRoBmXg?t=150
The TrackFollowingObject can run on the RailX freely.
We will push to PR, after adopt the this technology.

So, please wait to PR at Github.

I was told by OmegaZeroKiller about this. I believe you had some difficulties with parsing the cant Rail data from centimetres to metres. Never thought the BVE5 formatting would work in openBVE. I initially thought this would be a convertor type program acting sort of the reverse to the BVE4-BVE5 convertor

SP1900 wrote:I was told by OmegaZeroKiller about this. I believe you had some difficulties with parsing the cant Rail data from centimetres to metres. Never thought the BVE5 formatting would work in openBVE. I initially thought this would be a convertor type program acting sort of the reverse to the BVE4-BVE5 convertor

Formatting isn't so much the problem TBQH

The issue is far more that much of the original design and internal structure of openBVE is 'fixed' and makes assumptions about the input data, which are no longer valid in BVE5.

The most siginficant of these is actually the 'block' concept. In prior versions of BVE, everything works on the block length, and the current codebase is full of stuff which makes assumptions about this. Just for example:
Build yourself a route with a sharp curve in it (Say ~400m), as this is the easiest way to see this.
Create a 1m long rail object.
Place this every 1m.

If you look at the attached picture, you'll see that BVE5 calculates the position dynamically around the curve, wheras BVE2 / BVE4 place the objects along the axis of the block.

There are lots more examples like this.

I download the BVE5 parser,But I don't know how to put in openBVE and Use,Can someone tell me?

At the minute, there is no working public BVE5 parser.

Progress is slowly being made on that front (The most recent version moves the entire route loading process into a plugin and adds a lot of the framework and backend bits to let this happen better), but please do not expect anything public or working in the near future.

Thanks.