When I open up Hammer, and now that it uses materiels, I open up the materiels browser to look at the different textures to select the one I want, and because there are so many, and the preview cannot be reduced any smaller than 128 by 128, the textures end up overlapping in the browser and causing system strain and lag.How do I help fix this stupid problem, any suggestions would be appreciated.ty.

format.

format? could you please give a little more info, I am not sure what you are talking about.

I don't think a format would solve this. What resolution are you running?

for my desktop 1024 by 768.

Hmm, I'm running 1280x1024, if you are able to, maybe change the resolution and see if that helps? It sounds kinda stupid, but I think that would solve it.

That did not help. I'm not surte if you guys are understanding my problem properly tho.:confused:

You are prolly right.

This is a problem I had with the old Hammer, it was summit to do with the number of textures Hammer was trying to display.

Yes ... it lags your PC out trying to look at textures, I also get this.

Try the VERC forums, you will get more mappers that have used the new tools posting there.

I run hammer at 1600 x 1200 and still get bogged down with the texture browser.

Try using the filter to display the textures you want to see instead of trying to browse through all of them at once.

This method is great for reducing the system lag, but its only of use if you know what filter value to use.

To find out what filter name goes with what texture family, its useful to see all the textures listed at once - so you are right back to where you started :(

I doubt if this will fix your problem, but it might point you in the right direction for checking out the textures you really want to see.

Pix

The higher the res the more bogged down it'll be...you're showing more at a time, it would only make sense that it'd take more resources.

I'm running a pretty high spec PC, graphics card and memory. At the resolution I quoted, there should be no real problem - but there is.

I've played around with lower res settings just to see if there is any difference and tbh I havent noticed much.

I think Hammer loads all the material stuff into memory and then dumps it to the screen. This is where the bottle-neck occurs, its not so much what is on-screen as whats waiting in memory to be scolled up or down.

If you filter out the textures you dont want and ask for those you do, there are a fraction of the textures in memory and the whole thing works a lot faster.

Pix

yes same here...
i hope an update comes soon :hammer out of resources crash (http://www.chatbear.com/board.plm?a=viewthread&t=567,1103748551,14373&id=760734&b=4986&v=flatold)

so i can start mapping :\