|
Title: Hex is the same, but is not the same? Post by: NOTORIOUS VR on February 27, 2012, 12:22:01 PM I've stumbled upon this a few times now where the hex will be the same in both files but the maps will display something completely different.
I am using a defined d@mos to help me locate maps in an undefined box, but this keeps happening to me... I will located the correct location, the hex/value will be identical in both bins (red boxes) but it will show different results in the defined map then in the working d@mos. Anyone have any ideas? screenshot of what I'm talking about: (http://i.imgur.com/Q8aqH.jpg) Title: Re: Hex is the same, but is not the same? Post by: Rick on February 27, 2012, 03:02:25 PM You have defined the syntax (LoHI HILo), factors, sign, etc ?
Title: Re: Hex is the same, but is not the same? Post by: B234R on February 27, 2012, 03:04:14 PM Absolutely normal behaviour ;D
You need to transfer the conversion factor/precision as well (from the damos project to the other project) Look at the map properties in the damos project to see factor/offset/precision/sign. Then transfer them. Then they will display exactly the same. HTH S. Title: Re: Hex is the same, but is not the same? Post by: NOTORIOUS VR on March 20, 2012, 10:40:39 AM just saw this.. thanks for the info! :)
Title: Re: Hex is the same, but is not the same? Post by: robin on March 21, 2012, 09:57:58 AM use the "transfer map" function, and it'll copy over all the relative conversion and factor data for you :)
Title: Re: Hex is the same, but is not the same? Post by: NOTORIOUS VR on March 21, 2012, 10:35:32 AM Actually I just re-read what that guy wrote... and I did tuse the map transfer function... that screen shot is with the proper factors already. I actually think it was fixed by moving to an even ending address number... or something like that...
|