Thats what it says in PWGen1 but from everything I have done that is completely not it, I've been working on a web based hex data generator to hopefully eventually merge into PWAdmin to allow full editing and item creation all from a pretty web interface
My main issue right now (all my other converters so far work fine) is figuring out how the hell it converts ints to w/e the hex they are using is... I've come up with a few formulas that sort of work but most of the time they don't at all
I have noticed that the hex "numbers" are always the same regardless but always in a different order and can't figure out why or how to replicate that (I did sort of manage to get the part from 0 to 65535 to work though)
So if anyone has any clue how the hell it is actually done it would be greatly appreciated.
15-10-10
ronny1982
Re: dword -> octet
on a fast overview it seems that octets are just simple byte arrays embedded in a class to provide some more properties...
so it could be done with some simple bitconverter operations like bitshifts...
I know what they are for... and I don't think I can achieve the converting needed with bitshifting
What I am trying to figure out is why I get 4D2 using every single tool I can think of for hex conversions BUT the second I use a pw hex tool I get D204 from 1234
OR lets say I use 12345678 this time
Normal Hex Tools: BC614E
PW Hex Tool: 4E61BC00
Which is right for the game but I can't figure out a formula that works for every single possible number which is what is annoying the hell out of me
The other part of what I have created seemingly works just fine but I really don't get it, why make it so damn different from every hex converter out there?
15-10-10
ronny1982
Re: dword -> octet
Quote:
Originally Posted by das7002
What I am trying to figure out is why I get 4D2 using every single tool I can think of for hex conversions BUT the second I use a pw hex tool I get D204 from 1234
OR lets say I use 12345678 this time
Normal Hex Tools: BC614E
PW Hex Tool: 4E61BC00
Simple reversed byte order representation
Int(4Byte): 12345678
Hex(4Byte): 00 BC 61 4E -> math oriented representation
Reversed Bytes: 4E 61 BC 00 -> stream representation (in most hex editors)
Int(4Byte): 12345678
Hex(4Byte): 00 BC 61 4E -> math oriented representation
Reversed Bytes: 4E 61 BC 00 -> stream representation (in most hex editors)
OMG, I seriously can't believe I didn't notice that and I was trying so many other ways to do it :lol:
15-10-10
das7002
Re: dword -> octet
Alrighty then, I've been working a bit more and have every converter working flawlessly now except for the float to oct like how PWGen and the other xml tools I have convert them, since hex doesn't directly support floats I was wondering how something like
3.5 turns into 00006040
I'll continue playing with it but I'm kind of lost as to how its done