- drake3011
- |
- Exalted Member
Seriously Oak, Ive been doing this -blam!- for 16 years, gimmie my Friggen starter Pokemon and dont call me till im the champion! ¬_¬
Posted by: MuggyBasilisk
Kira,
Whether you're a troll or not, I just want to point out that your comments as a supposed software developer hold little-to-no water.
First of all, splitting up a mesh file and having some code to re-assemble it would not consume very much space. The sum of the parts of the mesh file would be the same as if the file was in one contiguous piece, and the code to reassemble it would be very small and simple. A very small amount of overhead to disguise something on disc.
As well, you keep saying "if it were on disc, it would have been found by now." There are many simple ways you could hide mesh files... it could easily be compressed on the disc with a modified compression algorithm (thereby re-using the existing decompression code and not "wasting space" as you put it) which would essentially result in it being encrypted. This would hide it from plain sight.
Those are both very rudimentary tricks (all of which you've completely overlooked, despite your *expertise*).
And finally, you say they could not make new armour available because it's hardcoded on a per-map basis. Again, you need to think a bit. For example, say a map is hardcoded to allow armors A,B,C. You say it can't use armor D, because everything would need to be rewritten.
The easier way to do it? Overwrite armor A on the harddrive with armor D (but calling it armor A) and then it will be used. Yes, you'd clobber Armor A, but not a big loss, and a very simple way to implement what you deem is "impossible".
It's the nature of patching software. You replace a binary file with an updated version with the same name. Software development 101 (but you know this, right? :)
Sure, the scenario above describes a situation where the user has installed Reach on their harddrive, but that's not a stretch, and it sure wouldn't be the only HD-only aspect of Reach.
I'm not saying this is what has been done, just pointing out that something you claim is "impossible" would be easy to do.
It was a bungie employee who originally stated the code had the maps hard wired with the armour built into it, which as we've been saying, is very much a backwards move in all accounts for memory allocation (though this was questioned at the possibility of new armour DLC during the Defiant advertising campaign)
I think its more an understanding that the models and meshs are coded in as map objects, ones that if you were to break out of the map you'd be able to find, that the code calls into and adds physical player properties. Like the spartan thats inside the POA
It seems likely this could be wrong, but that seems to be the question at the moment, im still very much a beginner programer so i could be mistaken
But on that note, i was assuming reach is C++, ive got a conditional offer at uni as a games designer, so its something ill have to learn, been playing with some Java recently but working mostly in VB and C# (Baby Steps :P)