[Experimental App] Emergence
Re: [Experimental App] Emergence
Ah. I know those exact blank spots. They really are confusing. I thought you meant blank spaces in guerilla exe data. I wonder if it's restricted to a certain set of tags or if it's randomly distributed through the tag set.
Reminds me of the USTR tag data which has some pointer information that would work if only there wasn't a different set of data also in the USTR tag. Weird stuff.
Reminds me of the USTR tag data which has some pointer information that would work if only there wasn't a different set of data also in the USTR tag. Weird stuff.
Disclaimer: I am no longer active. Any posts, PMs or other communication I use has no guarantee of accuracy or follow up.
Download Eschaton: Mediafire
Download Eschaton: Mediafire
Re: [Experimental App] Emergence
More like lazy programmers rather than weird stuff. Can't really blame them, I'd go crazy too if I had to create all these tag formats.
'Course you go crazier trying to reverse them...
'Course you go crazier trying to reverse them...
Re: [Experimental App] Emergence
Modzy, you might be interested in Monk34's experiments with my actr plugin. I labeled a hidden set of entries for experimentation, and Monk did that. He found that changing the values had a similar effect as changing values in other tag types, but of course there involves a hierarchy issue with actor-related tags (actv, actr, bipd).
Feel free to use my plugin set as a reference for those tags that have these minor alterations to expected setup. I'm testing everything, so I'm not making any mistakes with offsets. You can go back and check my work yourself, if you like, but it would really save you time if you trusted my work... as it is, I don't trust any automatically-generated plugins, which is why I've created maps with tag types that include values for each element within each tag, and then am testing the plugin offsets to make sure that the correct values appear.
Alt, discrepancies occur in Guerilla only between subcategories of elements, for example, between the Looking and the Berserk subcategories within the actr tag type; and also between types, most usually after a dependency type or short type. Enums also use an extra byte after their actually-used 1 byte, so they maintain the even structure. I see a logic to the whole thing, it doesn't seem at all like lazy coding. It's more like open-ended coding, allowing for more features than Gearbox marked in their HEK applications. Some of it is padding in order to make the code more legible in Hex (go figure) and to maintain even-numbered offsets (like power of 2 used by images).
Offsets are thus generally ending in 0, 4, 8, and C, and floats are pretty much always like this, as is anything else using four bytes.
Feel free to use my plugin set as a reference for those tags that have these minor alterations to expected setup. I'm testing everything, so I'm not making any mistakes with offsets. You can go back and check my work yourself, if you like, but it would really save you time if you trusted my work... as it is, I don't trust any automatically-generated plugins, which is why I've created maps with tag types that include values for each element within each tag, and then am testing the plugin offsets to make sure that the correct values appear.
Alt, discrepancies occur in Guerilla only between subcategories of elements, for example, between the Looking and the Berserk subcategories within the actr tag type; and also between types, most usually after a dependency type or short type. Enums also use an extra byte after their actually-used 1 byte, so they maintain the even structure. I see a logic to the whole thing, it doesn't seem at all like lazy coding. It's more like open-ended coding, allowing for more features than Gearbox marked in their HEK applications. Some of it is padding in order to make the code more legible in Hex (go figure) and to maintain even-numbered offsets (like power of 2 used by images).
Offsets are thus generally ending in 0, 4, 8, and C, and floats are pretty much always like this, as is anything else using four bytes.
Either you are groping for answers, or you are asking God and listening to Jesus.
Re: [Experimental App] Emergence
What you're referring to is byte alignment and those aren't a huge problem. The problem we're talking about exceeds that. There's parts that go far beyond that. And other things that look more lik parts were hacked to make things work. Check out the USTR code. There's some data in it that would work in a linked-list IIRC if only some other data that performs the same function weren't there. That's just unusual as all get out.
Disclaimer: I am no longer active. Any posts, PMs or other communication I use has no guarantee of accuracy or follow up.
Download Eschaton: Mediafire
Download Eschaton: Mediafire
Re: [Experimental App] Emergence
Perhaps Gearbox had to do some makeshifting. They said they were using Shark for optimization, so maybe they were trying to optimize it or make workarounds. It's all speculation! Blargh.
Either you are groping for answers, or you are asking God and listening to Jesus.
-
- Veteran
- Posts: 409
- Joined: Fri Aug 07, 2009 6:54 pm
Re: [Experimental App] Emergence
Posted. Now lets watch the massacre
Re: [Experimental App] Emergence
You mean my favorite map...could be played now...
Converting time!
Converting time!
Mota-Lev wrote:Its like watching an Asian girl crush a cats brain through its eye socket with high heels.. Its horrible but I just can't look away :/.
Who is online
Users browsing this forum: No registered users and 3 guests