Beiträge von Kim_olesen1

That’s why. There are no trains in the routes preload folder tagged as those. Try Intercity, Commuter and coal.

@Fahrleitung

What train category did you set the spawn to?

REAL DRIVE Friedrichsdorf - Frankfurt Süd. We have just released 4 drives for this route.

REAL DRIVES for S-Bahn Rhein Main are out now. See the first post for links.

Thanks @JasonToff. I shared it on the facebook page

Zitat von SÜWEX

Was mir schonmal passiert ist, das der Dispatcher bei zuvielen Wegpunkten überhaupt nicht mehr klar kam und deswegen unbekannter Fehler ausgespuckt hat.Also nicht übertreiben.

Das kann ich nicht bestätigen. Villeicht ist es anderes wenn man Quick Drive scenarien erstelle, aber meine experience sagen, geben niemals der Dispatcher eine wahl.

To avoid “dispatcher disease” i put extra destination markers after a switchpoint if there aren’t any. I make sure that each and every train has via points everytime the dispatcher has choices for where a train can go. That is the only way to avoid stuff like the dispatcher leading trains via the wrong tracks.

Fazit: never ever give the dispatcher a choice.

@JasonToff

Awesome. I will add it to my Real Drive youtube playlist. Can i use it on the Real Drive facebook page?

Nice driving. You were behind regional trains twice i can see.

I am aiming for a release of 4 Real Drives for S-Bahn Rhein Main this weekend. Two drives for s5 and s6 each.

@Matze (RD)

Since the Zwergsignal is reacting to a main signal that is more than 2km away and the magnet is reacting in the same way as the zwergsignal i would say it is too much of a coincidence.

When the zwergsignal shows red the magnet is active, when it shows clear, the magnet is not active. So at least, both things (Zwerg and magnet) are part of the same problem.

A Zwerg that should be showing an aspect for the left mainline reacting to a main signal over 2 km away on the right mainline, that’s not right. Even with my limited TS experience i think that is safe to say.

Anyway you can test this for yourself. Download the quick drive scenario i posted earlier. First run it as it is. Then delete the spawnpoint after 181,0 and see for yourself how the zwerg is showing a different aspect and how the 1000hz magnet acts accordingly.

BUT the most important thing to me: i’ve changed the spawnpoint (moved it a couple of blocks closer to Diepholz) so the real drive players will not get zwangsbremsungs. And that is the important thing to me! So really i am happy with it as it is now. That was why i asked in the first place. To make the Real Drive good for the players.

@Maik Goltz
@bahnjan

Hi there. After some tests this is what i’ve discovered:

1: I tried with the RSSLO Talent 2 and the message i get when the Zwangse happens is “distant signal not acknowledged.

It is definately the zwergsignal to the left of the track at the Ausfahrt from Barnstorf that has an active 1000hz magnet. I know this because of the next test:

2: If there is an AI train after the next main signal (the one located at kilometerstone 181,0) the zwergsignal is red and the magnet is active. If there is NOT an AI train in that signal block the Zwersignal is double white and the magnet is not active, and there is no Zwangse.

So that Zwergsignal to the left of the track at the Ausfahrt from Barnstorf acts like it is a distant signal for the mainsignal at 181,0

So it is not the vR101 that’s causing this. The strange connection between the Zwerg and the main at 181,0 also explains why no one else has discovered this. I am probably the first one to have placed an AI train in there.

The other Barnstorf signalling problem (the entrance main signal not clearing when an AI train is led to Barnstorf 01 can be solved by leading the AI train further on to Barnstorf 07. That problem is not related to the above problem with the Zwergsignal)

I’ll try with Talent 2 this evening. Then we can know if it is the 101 or not.

@Maik Goltz

Ist echt schön das du überprüft. But as you say: TS code is full of strange errors and no ts route will ever be free of errors. So when i am asking these questions it is to make myself wiser, not to make developers update.

I drove past it with 20km/hour to get more precise.
But ofcourse you are right, i can’t know the exact spot, so it is still a guess, just more precise than when going faster.

Here is a link to the test scenario:

https://www.dropbox.com/s/7gs6…20wzangse%20test.rwp?dl=0

I am not sure how to switch on level 3 info. It is. vR101 from steam. Someone said shift-ß but i don’t have ß on my keyboard. But the 1000hz lamp lights up.

Edit: i didn’t have time to try with a different lok. Have to go to work now, but i’ll try tonight.

@Maik Goltz i am sure i discover those things because Real Drives (which are quick drives) require so much testing. Having AI in front of the player train for many signal blocks after the other all those strange things reveal themselves since i am stopped behind most red lights on the route in the testing phase.

What are the chances someone has made a standard scenario that involves any other signalling at Barnstorf than green lights? Probably a very small chance.

it happens exactly where the arrows are. Avtually there seems to be magnets at this place. Even on the right side there is this “mushroom” that is normally associated with magnets.

@bahnjan

If i remember correct version 1,10 is the only update there’s been. If that is the case then yes i am using that.

Edit: Just checked and i have the AS_MUENSTER-BREMEN_v110.exe and i remember running it, so yes i am sure.

I will just run the test scenario and if it is helpful i can upload an rwp of it here?

@SÜWEX

I always clear cache and start the program from scratch, then chose from the real drive from the quick drive scenario page. Quick Drives are not playable from the editor to my knowledge.

There is a main signal just north of Barnstorf that does not clear when the AI train ahead of the player train is led to the platform at the siding. I have to TAB to get through. (See a little earlier in the video). Since that signal does not clear and this happens just at the other end of Barnstorf, could it be related? A signal link gone wrong?

Further testing: i need to do a costum scenario for this so i don’t have to drive 60km for each test.

These drives was with the vR101.
I’ll try with a Talent 2 tomorrow, see if that is any different.

@Matze (RD)

I tried Wachsam because i thought that it might be a falsely active 1000hz magnet that caused it. I drove the RealDrive twice and first time i thought i had just missed a distant signal, so i tried again and got the same result.

Couldn’t it be the signal “pointer” at the zwergsignal that is pointing the wrong direction?

If it is a script thing it should only happen with this loc, is that correct?

I just took the Br01.5 (with 5 DR coaches) from Trier to Koblenz. I am really getting better. No error messages from the lok this time.

Only point of small critique from me is that the engine sounds seem much too low in volume compared to all other sounds.

Other than that, beautiful lok.