simonjackson1964

There are two solutions to this that I can see.. A simple one and a complex one. Simple solution: Manually check the orientation of the cargo pads attached to the wagons (ot the wagons themselves if you aren't using cargo pads on them) and make sure they are all pointing the same way as the cargo pads on the trucks when they pull alongside. This solution will only work if you have a loco run-around at both ends of the layout or you use a return loop at one end and either a return loop or a virtual depot with the train reversed on release at the other (unless you are happy to have the train pushed in rather than pulled...) Complex solution: use Lua to set the wagon or cargo pad to the correct orientation as the train stops.

I've noticed this behaviour too, I think that the best way to avoid it is to rotate the logs (or other cargo) yourself by 180° manually, before the crane picks it up. (And save the layout with that change made!) I have just checked, and this works. Make sure that the logs have the same z rotation as the container floor (or other target) they are being lowered onto, before they are picked up.

I'm not sure if this would work, as I've not tried it but there might be a way to store the name of the keyword on the triggering point/turnout and then reference it in the iteration meaning you only need one event. To be honest a lot of building a working layout in MBS is about deciding whether you want to do a lot of fiddling about with variables and keywords, and have a simple and streamlined event module, or whether you want to save time and effort at the build stage and put that time and effort into a more complex and repetitive collection of events. There is no correct or wrong answer, and it's really just personal preference. Personally I go for streamlining the EV as it always seems wasteful to me to have a whole load of events that are doing the same job. But to have one event for each occurrence of the "event" might make sense in a given scenario...

Is there a reason you're using road traffic lights rather than railway signals? The railway signals have a track contact built in (from version 6 onwards) and from V7 on the route system basically handles the signalling and interlocking for you. I have to say, it's almost certainly something in your code that is causing the contact properties to change.

@hmclay Just reading this, and I have a feeling it might solve your problem of positioning things at different heights: The text was automatically translated from German by Firefox so the word choices are a bit off, but the message is that if you create a layer with a height limit equal to the height of the platform and set it as the default, all objects you add to the layer will go at that height.

Train routes are the flip side of road targets, You create your routes in advance by assigning a start and end way-point. A good rule of thumb is parity between routes and signalling blocks - As train signals have a track contact on them they can be used as waypoints, as can anything else with a track contact. When you select the route (either manually or using an event), it automatically sets all the points and signals. If there is a conflict with another train movement the routes automatically interlock to prevent a collision. (With one exception - diamond crossings need to have a switch added to them to prevent trains crossing from both directions at once!) This is seriously good as it means you no longer have to do all the signal and point interlocking in the EV.

What Goetz said. Basically when a contact is triggered you assign the triggering vehicle a new target contact. You can also use the same event to control the vehicle's indicators if you feel flashy. (Pun intended!)

If a KS multi-section signal is showing KS2, and there is an approach signal and/or a distant repeater signal in advance of the multi-section signal, what should those two be showing? My thought is that the next main signal, the multi-section, is showing "Proceed, expect stop", therefore the approach signal should be showing "Expect Proceed" - KS1. and so should the repeater. The multi-section signal's "Expect stop" applies to the main signal after this one, which will be HP0. Wenn ein KS-Multi-Section-Signal KS2 anzeigt und es ein Annäherungssignal und/oder ein entferntes Repeater-Signal vor dem Multi-Section-Signal gibt, was sollten diese beiden zeigen? Mein Gedanke ist, dass das nächste Hauptsignal, der Mehrfachabschnitt, "Fortfahren, Halt erwarten" anzeigt, daher sollte das Anflugsignal "Fortfahren erwarten" - KS1 anzeigen. und so sollte der Repeater. Das Signal "Erwarteter Halt" des Mehrabschnittssignals gilt für das Hauptsignal nach diesem Signal, das HP0 sein wird.

I am assuming that you are using V7 or V8? In either case I would suggest, rather than using an Event to change the switch in the road, use vehicle targetting. It's much more efficient and doesn't change the route too early. That said there are some vehicles that the auto acceleration and auto deceleration doesn't seem to work properly on...

You aren't the only one... I have never understood the need for layers or what they do, until recently. I still forget to use them, until I come across something that would make them really useful, and think "Oh *bleep*, I should have put that on a different layer!"

Yes, I think you have too many tracks in one place. You have a situation not dissimilar from one I encountered waaaaay back when I first started with this hobby. (This was V4 so, yeah....!) I tried to make a double cross-over by placing two LH and two RH points together. This resulted in the trains pirouetting randomly between the routes because the program couldn't assign a valid route from those available. I would suggest moving the railway points that are in the road to the side of the road. and make sure thay a single length of rail track covers that entire junction. Also I notice a length of virtual track sticking up? If you are using virtual track within the streets, and you want the vehicles to follow the virtual routes, I suspect that you may need to edit the streets to remove the routes built in to them, to avoid conflicts.

There are actually ramps - one for road and one for rail - that smooth the transition. Please will you upload the problem causing layout - or at least, duplicate the bit that's causing the problem. I have tried to recreate the issue from what you have described and can't.

I have had this happen so often! The best solution I've found is to put strict controls on all junctions to make sure that vehicles turning left only do so when there is nothing coming the other way. Right turns into the side road shouldn't be affected as long as traffic turning left into it is controlled. Right turns out need to have the priority set depending upon the yellow diamond being present or not, dictating who has to give way. One thing that can happen is that a vehicle can insert itself between tractor and trailer... Traffic lights will usually solve the issue if set up correctly... otherwise a set of track contacts counting entry to and exit from the junction. The condition: "Vehicle is heading towards a track/contact" is useful to determine whether a vehicle is turning or going straight (and can also be used to set indicators!)

All platform versions have a variant without the canopy. The height of every object is obtainable from the object information window. Bettina is getting dizzy standing on the roof, she has no head for heights... So if we set her Z-coordinate to the height we found earlier of the platform without a canopy: She is back down where she belongs. QED ======== Or the other way of doing it which works better for putting passengers and drivers in vehicles that don't have contact points: Put the passenger/driver on the ground. Z = 0. The vehicle beside her line them up to face the right way. Then move the vehicle over the person, not the other way around. Lower the vehicle to the required height so he person is sitting in the seat. Finally, link the person to the vehicle - if there is no contact point you will have to do so anyway for the person to stay in the vehicle as it moves, and then pu the vehicle on the track The gizmo allows you to position things as an analogue. The X, Y, Z coordinates allow digitally accurate positioning to the millimetre (at 1:1 scale).

For putting people on a platform, use the "automatic height adjustment - stacking" setting If, for some random reason, you want to put Achim on top of the platform canopy, there is a neat little trick: Copy the height of the object you want to place the other object on top of, then paste that into the Z coordinate of the object being placed. This technique is great for getting things lined up exactly. For example, positioning a buffer on the end of a length of track when it's not the one with the auto-positioning. The first thing to remember is that for reasons that will never be disclosed, the buffer is oriented 90° to the track at 0° Z-rotation. so we have to adust for that. With the track oriented at 11.03° Z, the buffer needs to be 11.3° - 90° = -78.97° Then transpose the X and Y coordinates (and Z if not 0) from the track to the buffer This will place the buffer right in the centre of that length of track. NOTE For this to work, the length of track must be straight. Then use the local gizmo to slide the buffer along the track to the end. This is definitely the easiest way to make sure things that need to line up, are lined up.

Not necessarily. Obviously the further apart they are, the less items you will have on the layout and the quicker it will load and run, but there's no rule that says the poles have to be a certain distance apart. (Or if there is it doesn't apply to a model...!) On my (WiP) layout of the real Furstenburg (Havel) station (as opposed to the model that is nothing like the real station), I measured the spacing between the masts using the measuring tool on Google Earth. Many of the posts are between 45 and 65 metres apart. The model catenary spline will only extent to just under 40m before the centre "pops up" to demand a new support. Point being if you want a prototypical spacing you will need to do what I did and use two of the tunnel entrance variants end to end. And believe me when I say that is a lot harder than it sounds! So, do whatever you think looks right. The masts will need to be closer together on curves and at junctions/crossovers to keep the pantograph on the wire, but on straight track it really doesn't matter,

So far to good!

For scenery, the best tip I can offer is experiment, Assuming you're using V8, play with the raise and lower tools. I find having the raise power set high and a "faded" circle size of around 20m (at 1:1). and moving the mouse constantly in smallish circles works best to produce realistic hills and mountains. For trees use the new auto-copy feature that lets you vary the height and orientation randomly (there was a plug-in that did this on previous versions, but it was complicated and in German). Catenary, it really depends on the number of tracks and the spacing between them, evert one of the support structures can be modified to change the length. Have a look at photos of real German railway lines too. There are two catenary wires available in different variations. The realistic ones remain straight, even on curves and the pylons must be placed closer together to keep the pantograph in contact on tighter corners. Then there is the "model" version which follows the curve of the track , staying in the centre. Better for keeping the pantograph in contact but not very realistic A tip on how to lay the pantograph, place the boom first, it will lock to the track. Add the mast and adjust the length of the boom to put the mast where you want it, Place the next boom the same way, and with automatic connection turned off, position the catenary to line up with the second boom, then turn auto-connect back on and extend or shorten it onto the first boom, using both the curve widgit and the flex widgit to ensure it snaps into place correctly. The new transverse system that was introduced at V8 is a bit complex, and while I have figured it out, I'm not sure I could explain it. With track, a tip I have is to place a short straight (Normalgerade) every few metres where track is to curve, in the direction you want the curve to go, rather than relying on the flexible spline to put the track where you expect. It won't! In fact if you put short straights every 15-20 m along the curve, you can then extend each one in turn onto the next. For twin tracks the spacing can be kept by making a "dummy crossover" that you move from place to place. This will ensure that the tracks keep the same centres (Of course you can use the W790/10R in place of the 10L). To avoid flicker where the straight tracks overlap, set the "normal" angled straight to variant "G16 Gleis mit niedriger bettung" - Track with lowered bed. Circles? Just keep adding curves until you get back to where you started...! There are four curves "StandardKries", "Innenkries, "Außenkries" and "Großkries". Standard, inner, outer and large, in both 10° and 5°. 36 of the 10° ones will get you a circle. The inner and outer curves basically fit inside or outside the standard curve at the correct centres. The gross curve is a different angle and radius. Hope that's of help? Simon PS: It's a great way to learn German!

Terrain is a case of practice making as perfect as possible, and not being a perfectionist. Remember that unless you are one of those guys that is an expert with blender or some such model making software, you are limited to what is in the catalogue. But the catalogue does include a lot of models with variations. I used to absolutely suck at scenery and landscapes, but now I think I'm pretty good. https://community.3d-modellbahn.de/forums/topic/7839-colours-of-the-switch-rails-farben-der-weichenschienen/#comment-101097 Another thing that's available in the catalogue are the "primitives" - flat planes, squares and circles, spheres, boxes, cylinders, and ramps. A bit of practice and patience and you can build pretty much anything. Animating it is another matter - that requires additional skills and software I don't have. But as an example of what can be achieved: It's by no means perfect but it's as close as I'll get it (except I forgot the pancakes sign). It's build almost entirely from primitives (exceptions like the clock, satellite dishes and benches) As for track, I switched to using the "Model-Oriented" track system a while ago. It's a lot more versatile and has a lot of variants. If you aren't using it, I recommend giving it a go. Be an "impressionist" model maker. You're not taking a photo, you're making something new. If you get frustrated (and we all do), walk away and do something else, and come back to it an an hour, a day, a week.... Have two or three layouts "on the go" and do the one you feel like doing... This is how I maintain my enthusiasm.

Trial and error? Ha ha! Seriously though, it's not like you're spending a fortune on track and accessories like you would if it were a real model... (which in itself is almost an oxymoron) My best advice is to play with the parts, see what they do try all the variations and if you build something and it doesn't look right, just start again. After all, it's the building that's at least half the fun.

Short answer: The booms have a length animation. You can also use the concrete pole variant (Beton-mast) of the route mast to stand on the platform.

And the Royal Navy, because tradition is what the Navy is based upon.

Hi Pete. I tried something similar a while ago, and just as a tip, I used actual track, on its own layer that I set to invisible, because virtual track doesn't have points/turnouts/switches/junctions (depending on what part of the world you're from!) and I found making my own was a) a pain, and b) didn't work properly with routes, when having more than one ship moving at a time... By the way, a ship will usually tie up with the port side to the dock. This is long standing tradition and is to avoid damaging the "steering board" that used to be on the other side of early sailing vessels (Steer board became starboard over time). It's something that isn't necessarily followed these days and I know there are lots of examples on the internet where it isn't true, but certainly the RN follows it still, wherever possible.

I had this exact problem at V6, and realised what was causing it. Move the acceleration contact or signal further away to allow for the length of the train, as @Herman says As for lining up objects, I use the X, Y and Z coordinates, copy them from the item you have placed, and paste them into theitem you are positioning, then using the local gizmo, slide the new object until it is where you want it, or it snaps into place.

Yup, that's google translate for you... Searching for "Turntable" actually works on the English version. @Dad3353 Yep that would work - I'lll give it a go, thanks for the suggestion. Yup, das ist Google Translate für Sie ... Die Suche nach "Turntable" funktioniert tatsächlich auf der englischen Version. @Dad3353 Yep, das würde funktionieren - ich werde es versuchen, danke für den Vorschlag.