Hi,I'm currently trying to import a route generated by vroute into ASX (SP2). It failed, even though FSX (Acceleration) was able to read the route. Then, I tried to create a new route in FSX from scratch and have ASX import it. This too failed. After importing a route, depart and dest is empty. The cursor blinks on the alternate ID, and speed and alt is 0.Does anyone know whats wrong, and how I can fix it?Update: ASX on another computer was able to read the flightplans. Perhaps a simple reinstall will fix it...?Frank Olaf

Hi Frank,Not sure here.. one computer is fine the other not? Different language or number format settings? Did you receive an error message during import when this problem occured? Can you share the .PLN?Best,

I checked, and again, its the language settings. The computer on which it worked was set to US, while the one on which it didn't work was set to Norwegian. I tried generating the flightplans on both systems, both with english and norwegian region, but it was not until I switched language from Norwegian to english that ASX was able to read either.In other works, the flight plan export is correct regardless of language, but the import is problematic. You have similar language problems with Xpax (a different bug report), perhaps your code needs some refinement...?

Hi,Yes, we have some number format issues here. Thanks!Can you please provide the .PLN that when used with Norwegian settings causes the error? It would really help..Best,

Sure. They are attached to this post, both the one originally exported from vroute.info, and the other a resave from within fsx of the same file. Both are problematic with Norwegian settings, but work flawlessly with US settings.I'd send them in an email, but you only have a contact form on your web pages.

Thanks for these.. we'll get it solved.FWIW the problem is that some flight plan generators use your number format (i.e. , as decimal separator) for saving, while others always use period (.). When reading a flight plan we assume your current regional settings are valid (, for decimal). While this works in many cases, obviously it does not in others. We'll have to identify when there is a 'mismatch' of regional settings and flight plan saved format and handle accordingly.Look for this fix in the SP3 public beta coming soon.Best,