Beiträge von Kim_olesen1

Thanks TomB 😀

Hi everyone. Just bought a Logitech Saitek Flightthrottle and i’ve set it up for use with TSC and Raildriver and Joystick interface. Easy setup, all is fine.

But the thing is, after driving with real levers, i can never go back to using the keyboard. Levers are SO much more fun. But i want one for each hand just like in real life.

So here is my question. Can i run two units of Logitech Saitek Flightthrottle? Will the interface be able to tell them apart?

If Rivet Games should decide to come back to TSC and make a Swiss normal gauge route, it's autobuy for me.

I stand corrected.

I think it happens because ALL the italian signals are fake. They have no script whatsoever. I’ve never seen one of them change. Am i wrong here?

BR-218

The routes i list now work at first, but at some point the spawnpoints will fail. So you will have to build for some time. Which is why i suspect it is a memorybug that happens when the scenariotracks.bin gets too large (+4gb).

It happens at the precise point where you cannot open the scenario in the 32 bit editor as well (getting OOM crash in the 32bit when spawnpoints fail in the 64bit editor).

So i am seeing this because i build larger quick drives than anyone else.

BUT after the update i am getting it much more. Where before-hand it was reliably precisely at the 32bit limit, now it also sometimes happens with fresh scenarios.

So you might not be able to reproduce it.

Try putting a Spawnpoint just south of Spittal in the right track going south.

I am having problems on all big routes, but not predictable. Drautalbahn is the first “small” route where it has failed me.

Anyway; DTG knows the bug is there. Now it’s up to them. And is i’ve said before, the more reports, the bigger the chance of a fix. Remember it was MY push for a signal fix for Frankfurt Koblenz that led them to fix it and switch to Schuster signals.it happened because a lot of people from THIS forum posted on theirs. So if people want more Real Drives, as i said, report it. Because it actually does make a difference, despite what most think.

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.