OpenBVE icon indicating copy to clipboard operation
OpenBVE copied to clipboard

[Suggestion] built-in Uchibo objects for complement use, want to freely use it for freeObj

Open ginga81 opened this issue 5 years ago • 2 comments

When I am going to release the TrackFollowingObject's sample route, I choosed my Tohoku-Shinkansen's objects. Certainly, I think that the most of users are can install and check it. But I thought that OpenBVE has already have a lot of objects for complement use for Uchibo Objects. Additionaly, the railway crossing sound has already builtin!

So, I want to suggest that the built-in Uchibo objects and sound can use for multiple numbers and different object category with freeobj, rails and sound. When we want to use built-in Uchibo's object, the Rail and FreeObj's number and filepath is set to the same number and filepath as Uchibo. This is naturaly result at the case for complement use. But, when we are creating the new original route, FreeObj, Rail number, and filepath want to change freely.

In my suggestion, virtual Uchibo files can referlence is good solution.

complement use: With Structure .WallL(3) uchibo\BridgeL.csv .WallR(3) uchibo\BridgeR.csv .Rail(22) uchibo\tr_bal300r.csv .FreeObj(46) Uchibo\lim45r.csv

My Idea: With Structure .FreeObj(123) uchibo\BridgeL.csv .FreeObj(124) uchibo\BridgeR.csv .Rail(1) uchibo\tr_bal300r.csv .FreeObj(1) Uchibo\lim45r.csv

At my idea, if the same real file is put at Railway/Object, it is conflict. So necessaly to check the exist real file. But, if we can freely use built in Uchibo object and sound, at the case of TFO's sample route is easy to install (using package system). Not only for complement use, if we can use for create the new route, these objects are more useful. Please consider about this.

ginga81 avatar Sep 23 '19 06:09 ginga81

I'm sure something can be figured out, although they weren't initially intended for this purpose.

Perhaps something like the following: .FreeObj(0) $BuiltIn\Uchibo\BrigdeL.csv

Where the $BuiltIn represents the built-in object path. The potential issue I see here is that if the object referenced is missing, we'd have to decide whether checking the main object folder is a good idea or to simply error out.

Let me think about it and play with things a bit.

leezer3 avatar Sep 23 '19 11:09 leezer3

Yes! I imagined such as this too! I think that at the help document and tutorial, built-in object is useful for the sample. This feature is now not hurrying, at the future of the good timing, please consider this.

In this case, all of $Builtin objects are built in from the another real folder. So, unless intentionally delete from real OpenBVE's built-in Uchibo's file, I think that missing trouble is not happen. In my idea, If at the real main Object folder checking is not find, and if the file path is matched, complement from $Builtin files. If filepath is not matched, write to errorlog. If these are difficult, I think that as you say, simply to write errorlog with 'not found'.

ginga81 avatar Sep 23 '19 14:09 ginga81