Currently in TSW2, there is a mismatch between the speed at which you get deducted points and the speed at which the speedometer (on the HUD or LED screens) changes value. If the speed limit is 100 km/h and you travel at 100.5 km/h the overspeed logic will round up the value to the nearest integer (101 km/h) which means you will get points deducted. At the same time the HUD or LED/LCD speedometer logic is to only change the value when you hit 101.0. This means that you may be traveling at what you think is the speed limit, with a white speed indication on the HUD but still getting deducted points. At least this is what I think is happening because I can't tell you how many times I have had the AFB set to whatever the speed limit is, and my LED/LCD speedometer will read the right number and same with the HUD (white indication), but I see in the top right corner that I'm apparently over speeding. This mismatch in logic forces the player (if they want to not get over speed penalties) to travel at least one integer below the speed limit, which means if they are using a cruise control mechanic they need to set it to the nearest number below (usually 5 km/h or 5 mph below). This just creates an unrealistic constraint that isn't very enjoyable (imho). My suggestion is for DTG to change the speed at which the game penalizes the player to be 1 whole speed unit (mph or km/h depending on route units) above the speed limit. I.e if the speed limit is 100 mph the penalty does not kick in until the train is traveling at least 101.0 mph. If you disagree with my suggestion: why?
You're right. This is sometimes a pain. I am learning not to fall into such extreme perfectionism and I can (I swear!) not destroy furniture if I am not at the station on time, without losing points. These may be stupid jokes, but in my opinion, it is an important element of the game for many players. Competition with yourself. It would be good if the game did not interfere with this.
I believe that was changed in a recent update (like before SEH was released or something but I can't remember). You were able to go like 15.9 mph when the speed limit is 15, but after that update you can only go up to 15.4, which is confusing as the HUD won't show anything.
2 remarks on this. -we rarely drive exactly what the speed limit is, usually 2-3 below, we only "run the needle" when catching up lost time. -afb usually does the same, at least our eurosprinter does (no idea if traxx acts the same) but if i for example set it to 120 it rarely does exactly 120,only when it's down hill at which point the dynamic brake comes in. Anyone with some real traxx experience who knows how the afb acts in real life?
I did The OP wants to travel bang on the margin and always have the train at that speed on cruise control. Even if I agree that the logic is wrong it's wrong because it should trip at 0.00000001 over the speed limit, not 1 over
This suggestion is more of a gameplay aspect though. In Sweden it is not uncommon for drivers to run 4 km/h above the speed limit if they are running late or for a short time if the speed limit will increase shortly. At 5 km/h above the ATC will beep, but not until 10 km/h above will the ATC brake the train down below the speed limit. I'm sure there are different rules in the UK and USA etc so you can't fit all types of rules with one gameplay "penalty logic". But I think it is fair if the game will penalize you only when the HUD actually says you are over speeding. This can be either when actual speed is at least one whole digit above or rounded up (but then HUD and penalty should agree, not be a mix). Also, if you want to argue that it should be when rounded up, I would be interested to know which railway operator or country railway administrator will discipline drivers if they travel 0.5 km/h or mph above the speed limit
Sounds like another "localisation issue" which COULD be addressed (but unlikely it will be) It's also a "core game" issue, so who knows... I'm sure the UK media would have a field day if a train had an incident and they found the driver was over the limit in any way...
No, I did not state that. Whatever the cruise control does should represent what it is capable of IRL. However, I definitely disagree with you that traveling epsilon above the speed limit should cause a penalty. That seems both unrealistic (by all means show me a real TOC that disciplines drivers for this) and a bit draconian I think it should match whatever the "change in digit"-logic is of the HUD. Why have two different systems? That doesn't make sense to me.
The system encourages certain behaviors, discourages others, and punishes bad behavior. It rewards driving under the speed limit with max AP. It discourages driving slightly over the speed limit with half AP. It punishes excessive over-speeding with 0 AP. Given the middle tier, of half AP, I don't agree the game logic needs to change at all. You shouldn't be getting the maximum AP available if you are over-speeding in any way, it seems fairer to me that you get half AP for doing so, because it's not the worst possible driving behavior, but it is not the best either. I can agree AP needs looking at, perhaps an overhaul, but in this case I'm on the side of the game logic.
If you're happy that each loco then takes longer to develop whilst they program an individual cruise control for that loco, then fine I'm talking about rules and regs rather than what you can get away with. I can drive at 57 in a fifty 90% of the time without penalty near where I live, but just once I'll get pulled over. To the letter of "the law" you should be driving at 49."something" rather than 50.2 Me too. As soon as it reads what the limit is, you should be marked as speeding
No problem with this, they can add this. The problem still is the discrepancy between HUD and the points given. That's the main problem. If you get 15 AP instead of 30 as soon as you go 100.00000001 MPH in 100 MPH zone and the bar goes yellow as well, that's fine. The problem is one indicator being ok and the other one punishing you. They need to act the same regardless of how strict limits we talk about.
And one solution is don't speed... Agreed another solution would be the HUD and AP teams getting together to ensure everything meshes, but the simple workaround is as mentioned
The other main issue is that the speedometer used to change colour at the same speed as the penalty occurred but the penalty actually occurs now much sooner as they are now two separate systems. So where the colour change happens at roughly the same point, 30.5, the penalty is incurred sooner at 30.1 whereas it used to apply at the same speed as the colour change, and there is now no indication that you have been speeding. At least before you would see the colour change and know that you had just incurred a penalty, now you have to check the points updating each time. The most important thing from a player’s perspective is that the two systems match and that can either be at 30.5 or at 31.0 for a 30 limit (I would prefer 30.5) but they must match up otherwise the colour change indication is a useless feature. Penalising the player at 30.1 or 30.01, wherever the cutoff currently is, is just not on.
In real life this can happen too. In the mr08 you have 2 speedometers (each using different methods, one on rotation of wheels and on on ground radar) one is the main one and the other is a small number on sidescreen (only used if the main one doesn't work) the smaller one works with comma's. Your main one could read 100 and the small one 100,4 but once it reads 100,5 the main one jumps to 101,maybe this could be a good method for the hud, only jumping to the next digit if it goes over x, 5.
