I noticed with a speeder that, in a regular terrain, to get from one corner to another, it takes:
200 km/h = 13 minutes
400 km/h = 7 minutes
Fair and good. But, it also takes:
600 km/h = 7 minutes
1000 km/h = 7 minutes
1500 km/h = 7 minutes
So what's the deal? Obviously I should need less time going 3x as fast as beforehand (1200 km/h over 400 km/h), not the same time. Otherwise, it does not make sense to even have a vehicle that goes more than 400 km/h. So why is this so?
“
4.1 Ground Movement Calculations
Ship Speed: Maximum 200 km/h
Vehicle Speed: The maximum speed for vehicles is 200 km/h (or less if the vehicle speed is lower) when inside a city. Vehicles can use their full speed when outside a city.
Character/NCP Speed: Characters and NPCs may move at a speed between 4 and 24km/h. (4 *(Speed Skill + 1))
Distances: Each grid square within a City/Terrain is a 2km x 2km area (44km x 44km Total)
Time to Move: Distance / Speed
Aborting Ground Movement: Travel on the ground can be aborted at anytime, it is instant, and you will stop at the square you are currently in. Travel is also aborted if the pilot leaves or boards a ship or vehicle within the ship/vehicle. ”
No, Neth, that's not it. The rules are correct, and I am not in a city (I did say terrain, not city).
Edit: But I do wonder about what you said, Orion. I've never heard of a planetary speed limit, so I'll try to find something in the rules about that.
Edit 2: I searched the rules, but I couldn't find anything close to what you said, Orion. If you could provide the source of your statement, that would be great.
Meanwhile, I'll bugbase this.
Edited By: Cesodevo Avina on Year 9 Day 148 3:36 ____________
I remember that thread, that was regarding something different. That was regarding the max speed of vehicles, something I had also once brought to attention and bugbased.
The bug is in getSurfaceCountdownMaxValue(), I'll try to figure a way of writing a fix, although the problem here is that getSurfaceCountdownMaxValue() is also used for calculating your ETA with the javascript functions, and returning a travel time less than 1 minute would mess up the way it runs.
Edit: This has been fixed, wait for sync. (I added new high res timer for speeds over 400 km/h.)
Edit: I tried it out, and it indeed still does not work. The ETA in the travel screen (where you choose coordinates and speed) is correctly updated, but the actual ETA that is there when I hit "Go" is still at 7 minutes for anything above 400 km/h.
Edited By: Cesodevo Avina on Year 9 Day 151 16:03 ____________