I was gonna type here, but I get sick of sounding like a blabber-mouth!! :-)
Are you selecting "Texture Application Mode" by clicking on the icon or shift+a as Than describes? Then you click on the face in the 3D view, you can ctrl+select to select multiple faces.

About once every blue moon WC3.3 throws some bug at me. The other day I was unable to get out of this mode where I couldnt select any brushes and I was only able to drag the 2D views around with the mouse (navigation style). Restarting the program wouldn't fix this (god knows, I probably pressed some button or something) but restarting Windows did!

Sometimes I get an error message something like "OpenGL shutdown failed" or something when I exit WC3.3.

Generally it's great though! I hope you get it working Quakis, cause the texture application features of WC3.3 are second to none! ('fit' - yes please!!)

OK so I am a blabber-mouth :-| 

Pretty much I can't select anything in the 3D view, that includes the brush itself - only from the 2D views it allows me to. Therefore, even in texture application mode it doesn't select a single face I tell it to. 

You have to turn off 3d acceleration. Or another option that's in that same window. T remember this being an old WC bug with certain video cards, but I thought it was limited to 1.6a and fixed in Hammer.

Give it a try though. 

I checked through all the options in WC3.3 and found nothing related to 3D/Hardware accelertaion for me to uncheck.

I also installed a copy of WC1.6a test if it does the same. I set it up and made sure hardware accelertaion was unchecked and everything works fine in the 3D view for this version.

Sorry if I sound like I'm pestering, I just don't like giving up too soon on things. 

I've stuck with 1.6a - the features of later version of hammer not being a sufficient draw as oposed to the various problems caused - having to convert textures, no texture packs above a certain size etc.

I just assumed 3.3 would have the same tools/options/3dviews - thought it did from my time messing around with HL1. 

Try tools => options => 3D Views => Filter Textures (in 3.3)

I think that probably has to do with the hardware accelleration . . . ?

What graphics card are you using? You could try altering the settings in either the NVidia Controll Center or the Catalyst Contoll Center if you have NVidia/ATI hardware, there could be a global setting which is interfering with WC3.3

Make sure all of the global settings are default or "let the application decide" or whatever....


?

(let us know how you do...) 

We've had problems here and there in the past with anti-aliasing messing up selecting things in UnrealEd. If you've forced that on in your video card settings, that might be it. 

Unfortunetly, it doesn't seem there's anything on my video card settings that seems to cause it. I also check anti-aliasing but I don't even have it forced.

@ijed: 3.3 camera movement feels a lot more nicer than in 1.6a, and I can go about texturing things much quicker and have a better workflow than the camera movement in 1.6a, amongst a few other things which help. 

I didn't find the software overall improved enough to go through the rigmarole of changing over. And I'm lazy. 

Your last post - half of it sounded like you still were stuck, the other half sounded like you have fixed the problem (?)

Ijed: I would try it, you might like it (+ it is easier than installing WARPSPASM, even the wadconveter thingy, you wouldnt notice it!!)

;-D

PS - I respect everybody has their own way.... 

I gave it a try the other day, but I'm not very pleased. Firstly, I don't like the fact that you HAVE to install it in Program Files/Worldcraft, otherwise it will not work.

I'm not all crazy about having to convert the textures in hlwad format every time either. I guess that's not a big deal, but still.

And lastly, I couldn't find the menu option to increase texture brightness. It's not where it should be, as it is in 1.6a.

3.3 does have a very fast 3D window though, and that can be important especially in big maps.

But in the end, I still stick with 1.6. Thats not to say I don't like 3.3, but I'm more comfortable with 1.6 

Seriously, the texture alignment features of WC 3.3 are what sold it for me. And the ability to copy and paste multiple brushes and then rotate them WITHOUT LOOSING THE TEXTURE ALIGNMENT INFO :D :D :D

I too also had problems with the 3D window being too dark, but I ran the NVidia display optimazation wizard (with the Monitor brightness/contrast settings on max, as it says to do) and the I realised that I was getting a better PC picture for it too :D

And why does everybody complain about the texture converter? OK so if you have a texture over 1024 then you need to mess around a bit, but I dont use huge textures. I guess some people like biiiig textures.....

Whatever? :D 

1024 in pixel size, but the Qauntity of textures inside a single WAD. And there's alot of Wads that contain more than 1024 textures. 

But I CAN'T live with abnormally dark textures, not being able to see whats what.

You Were Never One For Meticulous Texture Alignment Though...

Maybe not in the past. But in my latest maps, once they're released, you will see I have taken the extra time to make sure everything is aligned. 

@Ricky - No, the issue still persues. But I'm using a mix of the two. 3.3 to construct, 1.6a to texture. It's a slower process due to 1.6a's awkward camera but better than nothing. 

Did you try unchecking the "filter textures" tab in the 3D part of the options menu?

Apart from that Im foxed. (?)

Orl - Have you tried getting fixing up the brightness/contrast settings of your video card? Try it with the monitor brightness/contrast BOTH on 100%, then you'll have a colour correction module somewhere.....

I dunno, I respect that everybody has their own way, I'm only trying to help. 

I can adjust my monitor and video card brightness, both are at 50%. At 100%, I can see the textures fine, but everything else is way to bright. I shouldn't have to change the brightness every time I want to do some mapping.

I know WC 3.3 has the option to adjust the brightness for the 2D view gridlines, but none for the 3D view? Wheres the thought in that.

I'm only trying to help.

I know, and I am glad you are, believe me :)
But I'm content with 1.6 and its super slow 3D view and no auto alignment. It suits me well. 

Humour me:

1 - Turn monitor contrast/brightness to 100%

2 - Go into your graphics card's software, and find the colour correction module. There's bound to be one if you have hardware from the last 5-6 years. On my system theres a wizard which gives you a red/green/blue line, and you have to match up the colour's tones. Also you have to do an exercise where you have a group of lines going through shades of black to white. The two darkest strips have to both appear black.
I would imagine you have a similar option somewhere on your computer.
Click on windows desktop with the RMB, then click on properties, then go to the settings tab, then click on "advanced". There's probably something there. On my computer it's the NVidia Controll Panel, on ATI computers its the Catalyst Controll Center.

I found after doing this my games also looked better. And it's easier to see the picture on my monitor in sunlight too.

If you either can't be bothered to try this, or already have, or dont have the option then I'm sorry. I give up! All I can say is it worked for me! 

I too had the same problem as your'e describing, and experienced the "washed out" look. In XP all of the beige/grey type areas of the windows seemed very white, and dazzling. But when I figured out how to set the monitor up properly I found it to be better than ever before! 

do I delete the weaponvieuw for screenshots? 

r_drawviewmodel 0 

I did a quick google search and found this thread;

http://www.chatbear.com/unity2/12/913,1188737745,4371/1068645/0#7

States exactly the same problem with the same card. Someone mentions a temp-fix that seems to work, by disabling the card, then re-enabling. Though is this practical? Since I don't really want anything to... mess up. 

metlslime. 

Just tested the solution in the link I mentioned above and it works. The only issue is a drop in speed, but nothing unbearable. Hopefully this can be helpful to anyone else that comes across the same problem. 

r_drawvieuwmodel 0

unknown command.