[openBVE] SG: East West Line [WB: PSR to JKN]
-
Originally posted by Bryanwee1:
Note to Samuel:
Errr...... Should I add the C751B object? Something like this:
But not only 1 car, as the train is 'incomplete'. So only got 1 car
If that is the case, then dont put the car. I dont want to be half completed product. (By the way, if your UPD has coded until far from main line, you may put it.
-
Originally posted by kenneth1228:
I feel that the EWL's tracks(The Soon's tracks, I meant the stones and the side thingy) was the best, I think all lines should try to upgrade to that kind of tracks. And one day, this day will have all signboards on each station, but that will take a long time, but its worth waiting! ^_^Lol! Actually CGL was the first line to introduce this (Abit different, refer to CGL V0.8) and then EWL introduced it on PSR - SIM.
But AFAIK, NSL wants to use part of these objects from CGL and EWL, as the EWL's one got a short coming of no curve rails. (All rails are straight in shape, and hence the curves are not very smooth) --- How about asking the NSL to do the curve tunnels based on EWL one?
-
Originally posted by Samuel Lee:
No choice. Even the station objects we have decided to use a completely different (The shape / length of each station is different)
Cool, would be fun to "drive" the route. LOL
-
Originally posted by Samuel Lee:
If that is the case, then dont put the car. I dont want to be half completed product. (By the way, if your UPD has coded until far from main line, you may put it.
The whole train looks like that :
This one can hor?
-
Originally posted by Samuel Lee:
But AFAIK, NSL wants to use part of these objects from CGL and EWL, as the EWL's one got a short coming of no curve rails. (All rails are straight in shape, and hence the curves are not very smooth) --- How about asking the NSL to do the curve tunnels based on EWL one?
It will be better if all routes have curved rails to add to the realism... Maybe all three of four teams should team up once the whole route is completed and share similar objects to save space. For example: NSL, EWL should index their objects as "Object/Merger/Curve 1000 Right" Then the play only need to download one object file with everything inside, and then download the route file. Because the route file is very small (~50kb), the download would be faster and it would be more convenient. Anybody agree?
-
Originally posted by Bryanwee1:
The whole train looks like that :
This one can hor?
Sure! You have got it le. By the way, do fix all the errors first.
-
Originally posted by Samuel Lee:
Sure! You have got it le. By the way, do fix all the errors first.
Those errors are the announcements. TIB589B haven't give me the announcements yet.
Coz in the code, he put:
17919
.Limit 80;0;0
;Boon Lay out
17942
.announce ewl\announce xt_EW29.wav
.railtype 0;1
.railtype 1;0
.rail 1;14but there is no nxt_EW29.wav in the sound file
-
Originally posted by FSJZ:
It will be better if all routes have curved rails to add to the realism... Maybe all three of four teams should team up once the whole route is completed and share similar objects to save space. For example: NSL, EWL should index their objects as "Object/Merger/Curve 1000 Right" Then the play only need to download one object file with everything inside, and then download the route file. Because the route file is very small (~50kb), the download would be faster and it would be more convenient. Anybody agree?
I may considering to be a co-developer for NSL in long term so as to merge all the objects. (But personally fond of Object\EWLNSL\XXX.... for objects in East West Line and North South Line while Object\NewGenLines\XXX for NEL, CCL , DTL etc since most likely they are the same maybe with a subfolder of 3rd rail and pantograph. Oh yes, if you go to VivoCity, you will get to see the design of Harbourfront MRT station with CCL, and from what deduced from, yes, the crossover before Harbourfront NEL station on the left will lead to Circle Line overrun / slidings. It is more like NEL train going to CCL direction.)
-
Originally posted by Bryanwee1:
Those errors are the announcements. TIB589B haven't give me the announcements yet.
Coz in the code, he put:
17919
.Limit 80;0;0
;Boon Lay out
17942
.announce ewl\announce xt_EW29.wav
.railtype 0;1
.railtype 1;0
.rail 1;14but there is no nxt_EW29.wav in the sound file
All are announcements? Then it is great! (At least just ask someone to record and tada!)
-
Originally posted by FSJZ:
It will be better if all routes have curved rails to add to the realism... Maybe all three of four teams should team up once the whole route is completed and share similar objects to save space. For example: NSL, EWL should index their objects as "Object/Merger/Curve 1000 Right" Then the play only need to download one object file with everything inside, and then download the route file. Because the route file is very small (~50kb), the download would be faster and it would be more convenient. Anybody agree?
For the curve, do you mean those on the Tsuen Wan TBS?
-
Originally posted by Samuel Lee:
I may considering to be a co-developer for NSL in long term so as to merge all the objects. (But personally fond of Object\EWLNSL\XXX.... for objects in East West Line and North South Line while Object\NewGenLines\XXX for NEL, CCL , DTL etc since most likely they are the same maybe with a subfolder of 3rd rail and pantograph. Oh yes, if you go to VivoCity, you will get to see the design of Harbourfront MRT station with CCL, and from what deduced from, yes, the crossover before Harbourfront NEL station on the left will lead to Circle Line overrun / slidings. It is more like NEL train going to CCL direction.)
Okay, agreeable. At least that will save space and reduce the download size of the route. Because what I observe so far is that most of the routes have almost the same objects.
-
Originally posted by Bryanwee1:
For the curve, do you mean those on the Tsuen Wan TBS?
Ask joeyfjj for the preview.
-
Originally posted by Bryanwee1:
For the curve, do you mean those on the Tsuen Wan TBS?
??? What curve? It is just an imaginary file name. Anyways, I don't know what the Tsuen Wan TBS is
-
Originally posted by FSJZ:
Okay, agreeable. At least that will save space and reduce the download size of the route. Because what I observe so far is that most of the routes have almost the same objects.
But I need the support from jerry (NSL) and willis (CGL)
-
Originally posted by Samuel Lee:
But I need the support from jerry (NSL) and willis (CGL)
Okay, maybe you could combine all the object files together from the three routes and overwrite the same ones. (Last post for the night)
-
Originally posted by FSJZ:
??? What curve? It is just an imaginary file name. Anyways, I don't know what the Tsuen Wan TBS is
Tsuen Wan= A Fictional Line in Hong Kong, uses Trains such as M-Train
TBS= Turn Back Siding means the train will turn around by accelerating by the main driver and reversing the train by the other end of the train cabin driver. -
Originally posted by kenneth1228:
Tsuen Wan= A Fictional Line in Hong Kong, uses Trains such as M-Train
TBS= Turn Back Siding means the train will turn around by accelerating by the main driver and reversing the train by the other end of the train cabin driver.Ohhh. No, I don't mean that. I am just talking about an imaginary rail that turns right with a 1000 metres radius :P
-
It is "getting off topic", I thought there is a Tsuen Wan Line in Hong Kong? (Red colour somemore)
BTW, what EWL seriously need is a rail with curves in shape and not to be forced curve when use a .curve command, since it is a straight rail afterall and hence not smooth rail.
-
eh samuel i doing some touch ups on my BGS RFP le. I dune how to do Upper Tracks =X
-
Originally posted by Samuel Lee:
But I need the support from jerry (NSL) and willis (CGL)
Try putting railobjects into another folder? Like openBVE\Railway\Objects\BVESG_common\railtype?
-
Originally posted by Samuel Lee:
It is "getting off topic", I thought there is a Tsuen Wan Line in Hong Kong? (Red colour somemore)
BTW, what EWL seriously need is a rail with curves in shape and not to be forced curve when use a .curve command, since it is a straight rail afterall and hence not smooth rail.
So, you have to change railtypes everytime you go into a curve? You mean curved rails with different radiuses? If you are talking about that, you can refer to Dennis Lance's tutorial. He has curved rails of different radiuses. All you need to do is just change the rock.bmp and the rail's dimension. Link: http://www.freewebs.com/dennislance/
-
Originally posted by Samuel Lee:
It is "getting off topic", I thought there is a Tsuen Wan Line in Hong Kong? (Red colour somemore)
BTW, what EWL seriously need is a rail with curves in shape and not to be forced curve when use a .curve command, since it is a straight rail afterall and hence not smooth rail.
Ya. I agree. It really need a rail with curves
-
Originally posted by FSJZ:
So, you have to change railtypes everytime you go into a curve? You mean curved rails with different radiuses? If you are talking about that, you can refer to Dennis Lance's tutorial. He has curved rails of different radiuses. All you need to do is just change the rock.bmp and the rail's dimension. Link: http://www.freewebs.com/dennislance/
Yes, that is correct.
And the rails, you need to raise them up by 0.15m.
-
Originally posted by joeyfjj:
Yes, that is correct.
And the rails, you need to raise them up by 0.15m.
Ohhh, no wonder, that is why when I try to change to rock.bmp manually myself, the rails are hidden underneath the rocks. Thanks for telling me that!
-
Originally posted by joeyfjj:
Try putting railobjects into another folder? Like openBVE\Railway\Objects\BVESG_common ailtype?
If I did not recall wrongly, the NSL are in the midest of implementing new rails / viaducts right? Maybe u guys want to use The Soon version as seen in EWL or with some enhancements that the EWL currently dont have. Well --- after that, probably I will be freed from the project and hence i got time for my BVE, and I can do final checking of sectors beyond Bugis and merge them together.
Oh yes, after that I still have to do NEL (Which now still have not contributed a single thing, I am sorry about it) and following that, I suppose u guys should be ready for the next NSL release, and I hope that by then CGL V0.9 or even V1.0 is also ready, so that I can see which version is the best for a particular object and use it.
Ok, BVESG_common make sense, but, AFAIK, some objects in EWL / NSL cannot be used in NEL and I believe that CCL do connect to NEL (Go Vivocity yourself to see it, or wait for me ..... if it is possible).