Beiträge von Kim_olesen1

I don’t think the routeproperties is the cause of the page two bug. Why:

Because i tried to make two real drives (qd) on the Drautalbahn. The first (Klagenfurt Spittal) went ok, i made the drive with no page two bugs appearing.

Then when i tried to make a drive for Spittal Klagenfurt, i couldn’t even set one spawnpoint without the page two bug.

The day after i wanted to correct a thing on the first drive. All spawnpoints now had a frozen page two, eventhough they were working the day before. If route propertis played into this i should either be able to access page two or not. It should not be a random bug.

There are no schienenbus stuff in the standard rsslo routes. And not much Kuju either (except for a few trees).

Solte eigentlich nicht sein. Dynamische Wolken ausgeschalten AP Wetter komplett.

Start with the SFM Torino route. Braucht kein Fremdenassats. It’s quite good.

Midnightblue If i recall correct i had to copy in the tod somewhere in the Kuju folder as well. Some routes rely on the files in the Kuju folder.

don’t forget to BACKUP before you do anything though.

I’ve been trying to get RSSLO to improve the speed of their scripts for years. Nothing happens. That’s how they earn money, focusing on their next project, without correcting bugs.

I am surprised DTG finally corrected some of the issues on Koblenz Köln. But that was after a shitstorm on their forum. Notice that after that they never used Kuju signals again, but switched to Schuster.And they didn’t go back and fix Norddeutche Bahn or S Bahn Köln.

I had this problem (to a lesser extent) with the old version too. This is why no RDs from Münster Bremen ever emerged. I am not putting in hours of work, only to be stopped midways anymore. So either this bug gets fixed or i’m done.

TSC is going to move forward towards new code anyway. I would be locked with the old version forever, and that is no go for me either.

So as i said elsewhere. Help me by using two minutes to push DTG! Make them aware that you would like to see this problem fixed.

They will have to fix this. Otherwise they can’t even make QDs themselves.

So BR-218 come give a helping hand and help the push. Even if you have been dissapointed before. It only takes 2 minutes of your evening.

BR-218

Would you please do so just one more time? For the sake of actually getting new Real Drive content. Would be for the benefit of thw whole community after all.

bahnjan  Dijon-Senf Report the error. It for sure wont get fixed if you don’t, because then they wont even know about it.

It seems that a lot of things is running very smooth after the recent updates. HOWEVER some bugs seem to have gotten more fequent.

V200.1 Please please please report the QD erstellung bug to DTG. It wont be fixed if it’s only me reporting it.

Point still stands. It happens when the scenario eats up more than 4gb ram. You have driven my advanced drives (i think) you know how much is going on. Far more than standard quick drives. And yes, the latest version has made it even worse.

The bug is acknowledged by DTG. It’s been reported by others, so it is not a unique issue.

My drives are too ram hungry to open in the 32bit editor. They crash it.

This is why no more REAL DRIVES are coming your way. Unless more people put pressure on DTG and ask for this bug to be fixed. I can’t open page two in the QD AI spawn point.

I think Rivet Games has washed their hands of TSC. Unfortunately.

Midnightblue That looks very wrong. Looks like a mix of the old Kuju skydome and AP weather.

LONG REAL DRIVE: Düsseldorf - Frankfurt.

The minimize to tray in fullscren is mildly annoying, but the gain is greater than the pain.

If i remember correct, it only happens when you put in the first trigger.

Wie bevor gesagt. Steht in Handbuch. Man muss damit leben.

I’ve had a couple of questions regarding future Real Drives. So a little update from me: Currently i can’t make any. TSC has a bug where sometimes page two of an QD AI spawnpoint is broken. It used to happen when the scenarios began taking up a lot of memory. DTG has acknowledged this bug. However after the latest TSC update, this bug is no longer a “sometimes bug” but has become persistent and chronic. I can now no longer even put in a single spawnpoint. Without AI traffic, no Real Drives. So either this bug gets fixed sometime in the future, or it is the end of it for me. All i can do is wait.

Maybe a bug in the Cloud pack? I haven’t tried myself, since, as you all know, the more randomisation i can get, the better.