Extract stuff again using the two options. The way I stated it is the way it works.

Extract All 1 extracts the stuff and puts them in the directories they were originally organized and placed in.

Extract All 2 extracts the stuff and groups them by their type.

Correct! You get a Star Award!

Oh Rely? XD

Extract All 1:


Extract All 2:


From what I can tell, Extract All 1 organizes the folders based on the "Folder Hierarchy" view in Adjutant. While on the other hand Extract All 2 organizes the folders based on the "Tag Class" view in Adjutant. Meaning that they extract based on the view type. Best way I can figure out how to put it and understand it.
Edited by videoman on Jun 16, 2014 at 01:45 AM

That's what I have been saying -_-

>>>>>>>>


Edited by ElijahB1 on Jun 16, 2014 at 01:48 AM

Not...really. The "Folder Hierarchy" view in Adjutant looks like this:



And that's what Extract All 1 looks like too. Though you said Extract All 2 does that, when Extract All 2 make it look more like that "Tag Class" view. That looks like this:





So I am rather confused what you are trying to say. I know it's sort of a silly thing to go back and forth about, I just thought I would make sure I understand what you are tryin to say here. XD

I can't tell if you are trying to be retarded or just lack common since here... For the 3rd time: Extract All extracts in hierarchy structure like it always has. Extract All 2 extracts all extractable files into there tag class folder. EX: bitmap, render_model, sound, ect.

Umm...how about neither of those? Geez, would you rather me say you are wrong and get all upset? Or trying to be understanding and see what you actually mean? Geez, I guess people these days are rather aggressive.....

I can only repeat myself twice before I lose patience. I have explained exactly what it dose so if you still don't understand I don't know what else to tell you.

Look, word of advise. If you are going to Support a Application or Program that you are working on. Then having patience is a big thing. Even if some people are dense or thick headed, you might want to try and be a bit more understanding. Not everyone understands everything you do. So having a open mind about things helps.

Just...a bit of hopefully helpful advise.

From one gamer to another. :)

someone else's impatience isn't justification for incompetency.

Yes, ture. Though there IS a difference between incompetency and honestly not understanding what someone else is saying, and trying to better understand their intentions.

I was not being incompetent, the opposite however.

It's annoying when I explain it, than you explain it back to me almost the same way but say you don't get it lol. Remember it is extracting only the extractable files, that is why you don't see all the tag classes there after an extraction if that was what was confusing you..



Well, as much as I am frustrated at videoman, posts like this will do nothing to help rectify the situation.

Well....he IS the Master of all Noobs after all. XD

I'm off for the night, you two can go at it. idc. If you have any more questions regarding your issue, inbox me.

EDIT:

I wanted to run something by those who can answer.

Is anyone else having Lock-up issues with 3ds Max 2013 64-bit? Mine freezes up and tells me it has "Stopped Responding". This only seems to happen when applying textures to models. This has happened so far with applying Halo Reach and Halo 4 textures to a model. I can import the model just find though with little to no hang-ups and no Lock-ups at all.

Anyone else experiencing this? Or maybe something similar?

I did not have this issue on another version of Max (can't remember which one though right now). Just thought that maybe someone else might be experiencing this issue. Or not.

Been waiting for the textures to apply for about...5 minutes or so now.

Thanks for any help.
Edited by videoman on Jun 16, 2014 at 07:19 AM

it has to set up the materials. If your computer isn't too great you would be better off just waiting a few minutes for it to apply the textures, and then get on with your life.

That actually reminds me, Elijah, why does Adjutant apply textures in materials so...weirdly? More than half the time the setup messes with Max's rendering, and I end up having to manually redo it. (given, having the MatIDs and a starting point is infinitely better than manually figuring it out)

I don't really think my Desktop is the issue. It's running a i7 Core 2600K with 16GBs of RAM DDR3 and a new Gigabyte GTX Geforce 770, 2048MB GDDR5 (because my old graphics card was going out). So...any other possible reasons why 3ds Max is locking up?

I've got slightly worse specs than you and I usually just wait the 2 or so minutes to load the materials. Depending on the amount of materials it varies a lot. So far the shortest has been 30 seconds and the longest about 8 minutes

What do you mean "messes up rendering"? I've only noticed that speculate levels are a bit high sometimes, but that can be changed in the importing tool dialogue.

As for stuff taking a long time, I know that when importing the model normals is that takes the longest, materials are not really an issue unless its a bsp.

a lot of the time it imports bump maps wrong and it ends up creating really weird seams on the models, even when I weld verts. Usually the only way to fix it is to clear the bump map area and redo it. The other slots don't really affect as much

I know it's possible to extract the skybox textures, because I did that not too long ago.... I suppose last year was more than not too long ago though.
Edited by jabberwockxeno on Jun 17, 2014 at 12:48 AM

You'll need to give an example. Are you sure you are using the most up-to-date scripts? Also you need to make sure your Gamma and LUT settings are off if you are getting lines, it's a silly max thing.





You could always look on the sky box model your self lol... It loads and extracts just fine.

So I am experiencing a sort of odd problem. When viewing the model through the Viewport, it looks just fine. Though when rendering it, curtain parts of the model have solid RGB color.

Viewport:


Render Window:


Any idea(s) on what is causing this or how to fix it?

Thanks.

I just took a look at that. Apparently it relates to the Self-Illumination apparently. I disabled that and it fixed the weird Color/Hue.

So when is the update that is going to fix the Halo 3 sound extraction? I can't seem to extract sound\cinematics\010_jungle\010la\music\010la-music(both extentions) because it is an "unsupported sound type". map is 005_intro.map

When there is a codec that supports it. You could also go buy the soundtrack you know..

I have the soundtrack but I'd like support for the raw files. For reasons. You know.

I'm sure this has been asked before, (maybe even by myself), but what's the obstacle with adjutant being able to extract CEA assets?

Also, do we expect adjutant to work with the MCC when we are able to rip the map files from it?

As I recall it's because CEA's new assets are actually contained and deployed from Saber's own engine that overlays Blam! to provide the fidelity.

CEA is a new engine that sucks and is difficult to crack the code too.

Ah.

You'd (As somebody with functionally 0 coding experience, mind you) think that one would would be able to kinda "reverse engineer" it since we already know how CE's engine works, and then just going from there.

Like, even if it's a whole new graphic engine just running along with the original engine, I'd imagine you'd be able to kinda "solve for X", since the old engine is a known value, following the math analogy

Again though, I really don't know what i'm talking about.

EDIT: Actually, I have a question for you guys that's tangentially related to this. Since H2A is going to use prerendered cutscenes, how do you imagine that's going to work with the back button feature, and do you think the cutscene rooms will be getting a graphic update?

I mean it's a safe bet that they won't want to do any more extra work then they have to, so if when building h2a the new assets are "maually" placed and assinged, then I imagine the cutscenes rooms won't be updated, but if it's more like "All instances of texture x in H2 use texture Y in h2a", then they would be updated.
Edited by jabberwockxeno on Jun 30, 2014 at 03:04 PM

Ok, I have encountered a weird texture error (maybe not error?) with one of the textures for the map called Complex from Halo 4.
You can find out more about it here.

http://halo.wikia.com/wiki/Complex

For what ever reason, all the Building in the model have sky blue texture for their roofs and some of the walls. Here is a screenshot from 3ds Max.



Anyone have any ideas?

Thanks

Edited by ASCENDANTJUSTICE on Jul 15, 2014 at 07:55 AM

Ran into a problem with the Texture Window for applying materials to imported models using AMF format.

Apparently when optimizing a scene in Max (i.e. Deleting Objects) and then applying materials to the left over mesh, it throws up an error and then Max locks up completely. Not sure if this is supposed to happen or not, but it does for me.

Using 3ds Max 2013 64-bit.

Also, I noticed an option in the Texture Window for the Adjutant max script. It says "Selective Import" and it's toggled by default. What does this option do?

EDIT: Was just able to replicate the error a second time. It says:

--Runtime Error: Attempt to access deleted scene object

Edited by videoman on Jul 15, 2014 at 10:58 AM