Beiträge von Kim_olesen1

Zitat von fliegeroli

Gab heute schon wieder ein neues update.
RW_NightFoggy ist nun auch neu. Dann klappt es auch mit dem Nebel ab 17.00 (denke ich)

this relates to quick drives only:

Well both yes and no. According to AP there is no way to make fog work at night (i wonder, did fog work at night in quick drives in the standard TS weather?)

So the solution in the latest update is that weather patterns fog and stormy (which used fog too) always have a daylight sky. So now, no matter what time you set the clock to, it looks like 12:00. This looks really strange since if you set the time to 00:00 the sky is bright daylight, but everything else is night.

So in effect AP fog and stormy only have one time of day, which is 12:00. The daylight does not get weaker as night time gets nearer like it does in clear, cloudy and overcast.

I wonder how standard TS weather made this work when AP can’t? Or perhaps it never worked with standard TS weather either?

For snow the solution is better. After 17:00 the fog part of the snow weather pattern has simply been removed, so at least the sky is dark.

My suggestion to him was that for weather patterns stormy and fog he could just use clear and explain in the manual why stormy and fog is only appears in daytime. This would be a better solution because when you set the clock to midnight, the sky being set to 12:00 while everything else looking like 00:00 looks wonky.

A manual solution might be to enable dynamic clouds if you run stormy or fog quick drives after 17:00. This sometimes switches the weather to standard TS weather.

Not sure i am happy, i might still return to standard ts weather and consider my money lost.

That was one of the errors i reported to AP so that is good news. We are in communication about the “no fog after sunset” in QD error too.

@marcus
Those are rain patterns not fog patterns.
Quick Drive does not use any of those. It uses the Fog variant 1 pattern which should work without restrictions.

@jpvdveer

Thanks. That was a really great read

Ouch. Looks like RSSLO himmel.

@jpvdveer

I will probably hear from AP soon too. I don’t have any UK routes (i am only playing TS for german and austrian routes, that is where my heart is). So it looks like this might not be fixed. I will then revert back to my TS backup and consider my money lost.

@marcus

I just read through the manual once more. Please show me the quote where it says that fog patterns does not work at night.

Hi there. I’ve been wondering why the German and Austrian signalling systems are almost the same. What is the historical reason for this?

@Myulu

Ahh sorry. Mein fehler.

@marcus

Nowhere in the manual does it say that you can’t have fog at night in a quick drive.

He is very active on facebook. In fact he just made this statement: “All weather patterns can be used at night except for the ones with fog.“

I would liked to have been told of this before purchase.

@-setter-

I know, it was just in response to the ones who named vr101 as their worst purchase. I just can’t imagine what would make that lok anyones worst purchase.

vR101 is one of the best buys i’ve done. It is the one lok i always return to.

Has anybody heard from AP regarding weather errors in quick drives?

Köln airport link. Quick Drives mostly unplayable. The regional trains installs them selves in the blueprint of other routes and via that changes the AI traffic in other routes.

Witachtalbahn. Too slow for me. The Br86 instals itself as a regional train in other routes so you have an old single steam locomotive running the s-bahn line. Etc etc That is a no go. Only way to get rid of that is deinstalling the br86. But then you can’t really play the wutachtalbahn.

Black forrest journeys. No pzb magnets and missing tracks.

Algaūbahn. Missing tracks.

The rest i am happy with. That includes all the rest of the german routes on steam plus Inntal. Arlberg, Münster Bremen, and even Dresden Schöna.

@Maik Goltz

Genau.

Already a couple of days after ts19 came out i wrote here in this forum that something in the dispatcher code had changed. I noticed it behaved differently and more unpredictably.

I’ve been working on Real Drives for the Arlbergbahn during the hollidays. Here is Innsbruck - Landeck

Clearing cache is also recommended.

I’ll specify version 1.03 in the PDF.

The “unable to resolve clash error” happens for a nymber of reasons. I am very meticolous when it comes to routing AI and player trains, and i add in more destinations so nothing can go wrong. So if this message comes up it is because the dispatcher dismisses a route i specified for a train. Why on earth the dispatcher sometimes does this i don’t know. Another probable reason is the dynamic allocation of wagon numbers. If two wagons by accident have the same number this gives the same error mesage.

I’ve had this error with qd scenario where there only was two trains and their routes was more that 100km apart. A train clash was impossible but yet that was the error message i got.

Old TS code getting fragile.

@StS
Hi there.
1- First try quitting TS opening it again and run the scenario again. Sometimes the dispatcher just freaks out for no reason. Also try using a different loko.
2- Are you using the version purchased from Steam or Aerosoft? I only have the steam version so maybe something was changed from the Aerosoft version.
3- Can i ask you to try re-installing the rwp again? Missing destinations is a form of datacorruption that sometimes happen.

As i said, i have a backup. I never mess around with my ts installation without backing up first.

But i’ll have to check out that GenericModEnabler thing. Sounds like a very good tool to have.