Loading packages freezes UDK.

Maxim

Hey, I have a material set up for UDK, but every time I try and load it or apply it to a static mesh UDK freezes. I can not even close out and end up having to turn my computer off manually. I am thinking that the texture sizes are to big. With them being at 2048x1024 and a total of 6 textures for a material do you think that could be the cause of it?

Ben Apuna

6 2048 x 1024 textures shouldn't crash UDK unless you've got a super wimpy graphics card.

Maybe a corrupt or missing texture?

Did you make the material in a different version of UDK than the one you are trying to load it in?

Maxim

I didn't use any other versions of UDK, and my graphics card is 512mb, but I have never had any problems with it. Maybe its a corrupt texture. Looks like I would have to delete the whole package because every time I right click on any of the textures in the package its freezes up. I had it work earlier today and had it in my scene and everything maybe I didn't save it right?

m4dcow

How long have you left it to process? I ask because UDK in some cases will have to generate mips for each texture and then I know there is also some sort of shader cache generation thing it has to do all of which takes awhile. Also right click on the package and select fully load before applying and see if that gives an error.

If it does truly crash and isn't churning away at these things, check the UDK error logs for any information. Also try just importing the material itself to a package of it's own, then maps by themselves, then maybe switch the actual maps to dummy maps if you still have problems.

No concrete solutions I know, but all I can think of is to troubleshoot.

Ben Apuna

Weird, working then not... are you using the new June 2011 version? Might be a bug, try searching or posting on the UDK Support Forum.

Maxim

Hmm yes I am using the June 2011 version. It might of been a bug, I dont know if my recent material had to many instructions. I thought it was kind of heavy, but I know for a fact I have seen worse.

Ace-Angel

If your material unclean? As in, does it have many nodes of the same name and/or detached nodes which have input, but no outputs?

One of my friends got their first material crash in UDK, because he had 8 parametric nodes, which all had the same name, but were connected to different functions, so you change one, they all change, and this can be a hassle.

Another thing to note, using a Material Constant = better then actual applying of material itself, did you try that?

Also, what about drivers for graphics card? Latest version updated?