negke: I tried Clone Brushes and got an exact clone. I tried Copy Brushes and got an exact copy. (Where's your ! gone?)

HeadThump: Seems as though that should work, but... What I end up with is nothing where the door was but I do get a brush created on the 0,0,0 point that shows as a door but with messed up settings. Is there a some kind of CRC going on? 

If its a real complex door it could be efrags. As in the efrags limit? That would cause the ent. to dissappear. But its probably not that cause in Tomaz/Fitz engines it would tell you....

If the map aint vised it could be packet overflow. This would cause it to dissappear.

Again, too obvious....

As for copying the door into world brushes:

Use Worldcraft, copy the door, paste a duplicate and then click "to world"....

Never used BSP editor, sorry :P 

compile the door brushes as a separate bsp object, then call it through the model field of your door entities in the main map. Of course then the lighting would be the same on each one... 

Maybe I misunderstood what the problem is? I imagined all editors to be capable to copying only the brushes of an entity or at least remove the model function from them. (Mike: the ! was deleeted) 

That would be my thinking as well. Can't you just select the door and move it back to the worldspawn somehow via the editor? 

converting the zdoomgl models to Quake there's one thing I couldn't overcome. For some strange reason all models are converted left-handed(?!)

Now I have to change the origin of the laser.mdl I'm confronted with this

org = self.origin + v_forward * 30 + v_right * 8.5 + '0 0 16';

How do I rearange these para's into the opposite shoot direction? 

Ok, here's the explanation bit. Somewhere before that line in the code, there should be a line which reads something like

makevectors(self.angles);

This is a builtin QC function, which does the following:
* Read in self.angles(or whatever angle you give it)
* Find a vector which points in the direction of that angle, normalize it, and store it in the QC global vector called v_forward.
* Then imagine that you are facing in the direction of v_forward, and tilt the screen by the number of degrees in the third component of the angle.
* Now draw a vector going horizontally across the screen. Normalize it and store it in v_right.
* Finally find a vector going vertically up the screen, normalize it and store it in v_up

You can then use these three vectors in your calculations. One way to think about it is that they let you position things relative to an entity. If you want a position which is 10 units in front, 15 units to the right and 8 units up relative to the entity, you'd run makevectors, then use:

self.origin + 10 * v_forward + 15 * v_right + 8 * v_up

So that's great if you want to go right, but how do you go left? Well, there is no v_left because the following would always be true:
v_left = -1 * v_right
So to put the laser on the left hand side instead, just change the sign of the v_right component:

org = self.origin + v_forward * 30 + v_right * -8.5 + '0 0 16';
 

Thanks Preach, that worked.

I was already doing with the v_left factor and then I had an error on the - sign. They're going great now!

thanks again, not only the right line, but also why. (my poor maths)

http://members.home.nl/gimli/quakes.jpg
http://members.home.nl/gimli/kuakes.jpg

lol 

Hey all!

Anyways, I got back into mapping and modding for Quake again. I'm still using WorldCraft, but there is a very critical issue with it that is really annoying me.

I use WorldCraft 3.33, along with WC3 Quake Adaptor patch.

The main problem is that in Texture Application mode (invoked by pressing Shift + A), I can�t seem to be able to pick any faces in the 3D view port. No matter how many times I click on a face, I cannot select it. Even holding down Shift to select multiple faces doesn�t work.

This is annoying me because it worked before, but now it doesn�t, and I'm thinking that the WC3 Quake Adaptor might have something todo with it.

I would not really like to have to switch to GTK or some other editor over such a idiosyncratic issue.

I posted this on Inside 3D as well, so any advice or help is appreciated. 

I think. I use hammer 3.4 which has it fixed (yep, works with the adapter).

I think if there's an option for 3d window configuration for 'Hardware Acceleration' then turn that off.

The adapter's not to blame - the difference between WC1.6a and Hammer 3.4 is a different set of bugs. 

Just tried the whole thing again with hammer 3.4

I still cant select brush faces in the 3D viewport. Is it perhaps that there is an option tunred off by default somewhere? 

Do you have anti-aliasing enabled? I know that screws editors up sometimes when it comes to selection. 

In view of Willem said you should be able to check the global settings of your display drivers, i.e. via Nvidia Control Panel, or Catalyst Control Thingy... Is Anti Aliasing enabled all the time, or does it say something like "let application decide" or even "off" 

No, i dotn have AA on, and on my Catalyst drivers, it says "let applications decide".

I wonder what it could be... 

I should probably mention that I cant place any decals either in the 3D viewport. 

Doesn't support decals . . . 

Yeah, I remember now. But regardless of the decals, I still cant pick individual brush faces in the 3D viewport. I'll give Hammer 3.4 a go and see how it goess. 

Hammer 3.4 has the same issue as WC 3.3. I still cant select individual bursh faces in the 3D viewport. :( 

Are you in "texture application mode" when you are trying this? Enter the texture application mode vis a button on the left margin....

(I know its obvious, sorry...) 

I FIXED IT!!!!!!!! I'M SOOOO HAPPY I COULD CRY!!!!!!!!!!!

ATI driver coders need a good spanking. Turns out I needed an old version of the atioglxx.dll in the WC or Hammer directory, because I have the drivers, which mess WC and Hammer up totaly!!!

Well, that was a fun 5 or so hours. Thnx for your help.


P.S. Here is where I found a number of people with the same problem as me: http://www.chatbear.com/unity2/12/913,1188737745,4371/1054507/20?v=flatold 

I encountered this hammer/drivers bug before, and I know I'm not the only one on here who has. But the only solution I could offer was to regress to a much older version of the drivers. I'm gonna go test this dll out right now, see if it works here... 

Unfortunately, the best solution IS to roll back to old Catalyst drivers. Get hold of Catalyst 7.9, because 7.1 Catalyst drivers still dont work with WC or Hammer.

There is a price you will pay. With the 7.9 Ati drivers, the native windows version of Dark Places WILL NOT WORK, so you will have to use the SDL port.

Dont you just love all this messing about? You have to spend like a day sorting sh*t like this out before you can even sit down and mod. It's still fun though :). 

Maybe I'll just stick with the old 5.12 drivers then, if it ain't broke... 

use wc1.6a like me, running in unaccelerated mode. It's pretty slow, and for some reason I have to disable then reenable catalyst AI to get the 2d window performance to not be utterly shit, but it does the job (just about...)

I haven't had any problems running the source version of hammer btw. 

Everytime I add a new custom entity in worldcraft, I cant compile and run my map, because I get a whole bunch of errors, the core error being:

[code]Error opening C:\Documents and Settings\Owner\Desktop\game development\game projects\fire line mod\fire_line\maps\test1.bsp: No such file or directory[/code]

I added a custom entity in wolrdcraft called "ambient_sound", but I everytime I try to add any sort of custom entity, I get the same problem. Note that I'm adding this entity in WorldCraft, and I'm not adding anything to the FGD file.

I'm not sure if I need to even fiddle around with the FGD just yet, because what I do is I simply add some default entity > right click on it's properites > go to it's class name > type in my own entity that corresponds to the one I coded in QC > add the needed keys and values. I would like to know if I'm doing anything wrong.

Any advice on this would be great. thnx.