News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread: https://www.celephais.net/board/view_thread.php?id=60097
First | Previous | Next | Last
OK 
Not wanting to sound retarded, but this is actually a recurring bug. I have experienced it marginally on both my old GPUs, but the majority of the time it is fine.

When it happens, just to verify, when you put the cursor over the 2D view does it become a hand instead of an arrow?

Usually a reboot sorts it out on my PC, and it hasnt happened to me for ages, but others have had the same/similar troubles.

Another thing which may help would be the check you are using up to date drivers / drivers which work..... ?

Also out of curiosity, what GPU are you using? 
Also 
Instead of "hardware acceleration" tab, there is one which is imply called "filter textures" or "filtering" or something. I think that does the same / similar thing. 
Question 
you don't have to convert wads when you use hammer 3.5? 
Drew 
yes, you're still have to convert wads for using hammer 3.5, but it's much easier then converting via qadapter 
Hmm 
hardware acceleration was the only thing tempting me to move away from 1.6, but the above few posts don't make that look too promising! 
I Would Upgrade From 1.6 Because ... 
Texture use is much easier in 3.3.
If you rotate something the textures stay in proportion if you use texture lock. I find the "fit" check box easy as well. It allows you to fill out texture on a brush that is not quite the right size, but close enough to look silly.

Another thing I love is the option of making arches. You get a preview screen before the item is placed, where you can change the shapes and other stuff. It's really cool for making curved hallways.

I found the vertex tool a bit easier to use as well.

So, can anyone tell me what version 3.5 adds for Quake mapping ? 
>correction< 
NOT to look silly, I meant ... 
 
God, what an atrocity. I grabbed a version of Hammer 3.5 that basically works but I can either:

(A) Have proper texture view and no selection abilities or...

(B) be able to select in the 3D view but the textures are drawing all skewed and such on the faces or...

(C) be able to select in the 3D view with proper texture application but it's horrifically slow

Fuck it, let's see what the BSP editor is like. 
It's 
A 3d Driver / GPU issue - you're on ATI I guess.

You need to turn off Filter textures in the 3d View options and paste a .dll into the worldcraft folder.

http://rapidshare.com/files/138119760/atioglxx.dll

Basically if the dll exists then it stops WC from trying to use the hardware and retards it back a few generations. Which works.

Or you can just buy Nvidia :P 
I Mean 
It forces software rendering - visually it looks the same as hardware acceleration, can't say I've noticed it being slower either. 
 
ijed

Thanks but I tried that. That's what makes it abysmally slow. I'll probably try to set up my other laptop soon (an nvidia machine). The BSP editor seems kinda cool though. Maybe I'll try this for awhile. But, of course, the texture tools are pretty bad. 
WC 
Is a pain in the arse to set up - the real reason to use it is the very good texture handling and visually simple frontend.

Vista also hates it with a passion. 
 
Ahh, being on Vista might be part of the problem them too.

No worries, BSP actually seems to be pretty good now that I've meticulously set up the preferences the way I want them. I don't think it has rotational texture locking which is the one thing I really wanted Worldcraft for. I can get by without it though... 
Willem 
Now you know why you should have written ToeTag crossplatform in the beginning. 
 
Spirit

So much work. :)


I forgot my main complaint with BSP - the 3D camera controls. Horrible. So horrible.

But Worldcraft isn't much better, so, no loss there. 
Did You Try 
different drivers? 
 
I can't be bothered, to be honest. I'm done with installing different versions of drivers to make things work. :) Thanks for the suggestion though. 
CCC 10.2 
I've been all over that s@#*

http://www.amd.com/us/Pages/AMDHomePage.aspx

The newest ati drivers are actually pretty neat. Massive performance increases and everything! Got to be worth a try....

See it occurred to me - the hardware accelleration mode of Hammer likely uses the hardware within your computer.

And seeing as you have told me yourself that you never use your computer for gaming then it would make sense that your drivers aren't up to date. I mean they release new drivers every couple of minutes nowadays. And they release these "updates" to operating systems also.

Maybe thats why I never have any real problems with these things - I recognise the fact that I have to take it upon myself to make sure that I am using the correct tools for the job. I cannot entrust this task to Dell or Hewlett-Packard, they frankly suck. Taking value from the end-user product at every possible turn.

So seriously, if you are serious about mapping with an editor which works well and has all of that magical texture locking stuff which makes it about as easy as Lego bricks, then atleast try installing the latest drivers for your GPU. If that doesnt work then fine, stick to the manual and time consuming method, I'm sure its no big deal.

But its got to be worth a try hasnt it?

If you have some kind of horrible OEM GPU in your box then I'm sorry, I cant offer any advice other than dont buy hardware from these big firms who dont give a c@#p about their customers (HP grrrrr.....) 
 
Look, I appreciate the help but understand that I've been tinkering with PCs for over 20 years now. I understand all about getting the latest drivers and all that jazz. I got it. I just can't be bothered at the moment.

I'll maybe take another shot at it later this week but I've already lost several hours to getting Hammer working and, frankly, I'd rather be working on my brushes. 
Hmm 
Any ideas?

GTK 1.4

(seriously) 
 
Last time I tried it, GTK was almost as large of a farce as this Worldcraft adventure has been. Does it have a simple installer and does it "just work"? 
You're Being Shady 
about your platform, whilst yelling "farce" and stuff, man. You ask for help then you tell me you "might" try again later.

I dont understand. I defend the editor because I have been using it ever since I upgraded from WC 1.6.

What features does Hammer have that Worldcraft 3.3 doesnt anyway? AFAIK they are extremely similar, the interface and button icons and everything are identical. But the Quakeadapter was meant for WC 3.3, but you used Hammer. Why?

Also, for future reference (for me) please tell me what platform you are using? Im only asking because in the future someone will complain that they have the same problem, and if you find a solution ever then I might be able to help them, or atleast be able to say that this happens with GPU x or OS y, and that using driver z helped, or whatever.

Do ya get me?

I understand that it sucks when stuff doesnt work out of the box so to speak (took me ages to get Bioshock DX10 to run on my Windows 7 rig, and yeah - I was frustrated, tired, had a million other things to be thinking of.

But anyway, if you get a minute, or ever decide to attempt mapping with this software ever again like could you let me know your GPU, OS, driver version and things please :) 
Yes 
Absolute noob on compilers, but the one time I tried to instal GTK radiant I got lost in different versions my computer didn't like.
Win98 user - Dos fan.

GTK 1.4 worked right away. 
 
Ricky

Again, thanks, but I'm going to try BSP for a bit and see how it goes. It works. That's all I ask from this stuff. :)

MadFox

I might try Radiant again but I remember a similar clusterfuck with it. Different versions, different feature sets, stuff to install, ... blech! 
Willem 
What is the problem with the 3D camera controls on BspEditor? 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.