32bit mapping BUG!!!

[volljari]

Looking at a file for a 32bit float map, editor only takes the first 3 bytes then the fourth byte is placed in the second cell. the second cell takes two more.

Not true 32bit number cell, more of a 24bit number cell.

[Mangus]

Looking at a file for a 32bit float map, editor only takes the first 3 bytes then the fourth byte is placed in the second cell. the second cell takes two more.

Not true 32bit number cell, more of a 24bit number cell.

Hello -

There are known issues with 32bit editing at the moment. These issues will be worked out in version 5.

[Tommi]

Looking at a file for a 32bit float map, editor only takes the first 3 bytes then the fourth byte is placed in the second cell. the second cell takes two more.

Not true 32bit number cell, more of a 24bit number cell.

Hello -

There are known issues with 32bit editing at the moment. These issues will be worked out in version 5.

BTW when we can expect it? will it support Ostrich 2?

[Mangus]

Looking at a file for a 32bit float map, editor only takes the first 3 bytes then the fourth byte is placed in the second cell. the second cell takes two more.

Not true 32bit number cell, more of a 24bit number cell.

Hello -

There are known issues with 32bit editing at the moment. These issues will be worked out in version 5.

BTW when we can expect it? will it support Ostrich 2?

The latest version of TunerPro on the website supports Ostrich 2. In fact, so do previous versions of TunerPro.

[Tommi]

Hello -

There are known issues with 32bit editing at the moment. These issues will be worked out in version 5.

BTW when we can expect it? will it support Ostrich 2?

The latest version of TunerPro on the website supports Ostrich 2. In fact, so do previous versions of TunerPro.

and what about address tracing? will it be supported by TunerPro?

[Mangus]

and what about address tracing? will it be supported by TunerPro?

Yes, eventually. Next major release, most likely.