That seems wrong indeed, assuming all other data is the same. Please share the full request we can investigate the issue, preferably with some screen shots. If you do not want to share here, you can also email to info@routexl.com
While writing you the mail with the request I think I may have found the issue? It parses to ¶meters[type]=“car”, could the quotes be causing it to default to some other type? I’ll still send you the mail with the full request
The vehicle type is indeed not correctly set to the default value when the input is wrong. The fallback mechanism gets triggered, resulting in routes as the crow flies (straight lines). We’ll correct that.