Before you do anything more, it would be wise to give the OP and the included "Help" file a read.
(Help file is located in the Help menu in Adjutant).
Edited by ElijahB1 on Dec 1, 2014 at 03:33 AM

what is the decryption key?

Mega is having issues at the moment, defer to the Halo Maps link.

Edit:
Mega now working if you copy/paste the link.
Edited by ElijahB1 on Dec 6, 2014 at 10:31 PM

will there be model support for cea? or no?

At some point, maybe.

I downloaded from mega.co.whatever and it didn't include the .exe file? Don't know if just an error on download or what. Halomaps one is working.

Mega has been dumb today, I re-uploaded it so you should not have any more issues.
Edited by ElijahB1 on Dec 7, 2014 at 12:13 AM

Aw sweet dude.

Thnx Elijah!



Edited by SS Flanker on Dec 7, 2014 at 01:39 AM

i want CEA campaing in CE :/

So i got a question Why are the textures like super small?

Most of the character textures for CEA are like 64x64 or don't go any higher then 256x256

If you are looking on the level s3pak files such as a10 you are only looking at the lod bitmaps. You need to extract the full res ones from pak_stream.

Ah okay thanks, but i can't seem to find that file.
Edited by clonetrooper163 on Dec 7, 2014 at 02:50 PM

I'm not sure if it's just me and or if it occurs on any other maps and models other then this, but on the Halo 4 map m90_sacrifice, the scenario_structure_bsp 00_trench_a in the model viewer, the camera movement speed is really slow and can't be changed to go past 5.

Can't wait to get on my PC and DL the new version. Gonna extract some mp maps and try and in game them.

The Halo 2 support is great. Any chance of having the application convert the P8_bumps into standard normals on extraction? I'm sure many would rather not convert the palette by hand.

I believe Entity 1.6UE had a similar function.

let me know if I missed something

http://haloce3.com/xmf/

No plans like that at the moment. There is an app called "CrazyBump" that can convert them pretty well though.



Looks good to me.

Eh, Crazybump is just making a normal from the extracted bitmap. H2 normals aren't actually heightmaps, they are palettized 256-color images.

Anyway, Great work to all involved.

Right but there is no color data, it's just a gray scale from black to white with 254 shades in between.

I thought there was 50?
You guys see what I did there? XD

Haven't really noticed that.

I think the increase speed and decrease system is a little awkard within the model viewer perhaps setting the + key for higher speed and the - for a lower speed would be more convenient if you have the time elijah?

That's already been assigned to FoV, and really I think the scroll wheel is the best way to go about changing camera speed. I know about the issue on that BSP and we are looking into it, however if you are really intrested it it you could just open it in max.
Edited by ElijahB1 on Dec 9, 2014 at 09:17 AM

Some bsp's take upto 14 - 15 minutes to load up within max however.

Shouldn't if you disable normals.

Judging from some of the textures (fuelrod, shotgun, sniper rifle, plasma rifle, maybe more), some of the models are using the same or slightly edited version of textures from reach models. That doesn't necessarily mean the models are identical, but if any of them are, you'd have the "end result" of a decrypted model, just going off the textures. Not sure if that's helpful, but it may be a good starting point to look at decrypting the model data if you know where the endpoint is, since it looks like adjutant can see the start and endpoint of the data values per model.

Just a hunch
Edited by NeX on Dec 11, 2014 at 12:24 AM

they dont use this for ripping everyone elts dus

So I don't know what's happening. In both 4.0 and 3.5.1.1 I've had this issue where the reach weapon models I export have skeleton issues like when I try to move the bolt on the sniper rifle model either a portion the model itself goes with or it just acts as if I'm rotating it. I've tried both AMF and EMF but both have the same problem

That's because they're bones. Max and Maya think of the weapon's skeleton as if it was a bipedal skeleton, so it'll automatically assume that they're constrained to one another as it would inside a living creature. You can copy the node names and replace them with spheres rather than bones, or you could skip that nuisance all together and use link constraints.

Ohhhh. You just made my hour.

Not sure how but you're welcome?

Uncheck "SetBoneEnable" when importing.

Okay did that, but I am still having an issue with the model being taken with the skeleton points. (an extreme I know but the mag is a big thing

You'll need to post images or be more descriptive because I am not 100% sure what you are talking about...

If you want a model with out any bones uncheck "Import Nodes"
Edited by ElijahB1 on Dec 14, 2014 at 03:42 PM

Thought I had an image guess it didn't work. http://tinypic.com/usermedia.php?uo=nvlS1L5AwLPDZeMgxfSic4h4l5k2TGxc#.VI4L1nuVX4Y
well here's the link as I don't know which link to use lol. What happens is if I try to take the mag out the bone is also stretching the main body of the gun with it hopefully the link works and you can see what I'm talking about

Edit: Also something that I noticed is that the models function properly in autodesk maya but I'm told that 3DS Max is the recommended software as it supports all the meshs. so what do I do?
Edited by DivineMedia on Dec 17, 2014 at 01:33 AM

Download 3dsmax 2014?