Feature request: optional chromosome output

[Lotharsson]

As far as I understand floating values exports as 64 bits double (zlib packed and rebased).

Kind-of. The doubles are "cast" to 64-bit ints before being compressed, and back again when uncompressed (as demonstrated in my Java code). Casting to/from 64-bit ints are specified to be lossless operations in both Java and (IIRC) Flash.

May be there is some extended -> double conversion or any other conversion just before export data? Or just after import?

I don't know what happens in the Flash code, and whether it might do anything like this on some platforms. Ryan may have more info.

[bokomatic]

OK. I still do not sure that the problem is in platform-depended double realisation.
Because I have the same platform before export and after import and I have copy/paste issue.

Actually I worked on genetic algorithms when got my master degree. And I did export/import too.
And I know very easy and robust solution to make it work properly.
Just export chromosome to internal text string and import it back before running simulation for each individual. It guarantee that we will have correct text string for any car ^^

This trick can be also used for debugging. Save original chromosome, export/import it through internal string, then compare result. If they differs debug here)