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
Yeah 
to quad to appear, item_artifact_super_damage must be placed. w/o any SF

btw, is it your maps safe1 and safe2? 
 
The item ist most likely too close to a wall or the ceiling (has to be 60 units) and thus falls out of the level. Load the map in developer mode ("developer 1" in the console) and you'll see a warning message if that's the case.

If you're looking for beta testers, post a note in the Screenshots & Betas thread. 
 
Spy: what do you mean with w/o SF?

Yes, I made safe1 and 2 and 3 is pretty much done now as well :P

Oh, developer mode :) Didn't know about that one. Going to try it out now. 
Developer Mode Rocks :D 
Thx, that really helped! Found a DM spawn point outside the level which for some reason caused the quad to not spawn.. odd.. but it works now :D 
Beta Ready 
well, beta is ready now :) Thanks for all the quick responses. I'll make a post on the beta board later. 
Code Question 
So say you had a bunch of quad damages in the room. Currently, they will all rotate exactly the same direction and start at the same angle so they are all perfectly in sync.

Is there a way in QuakeC to start them at random angles or change the rotation speed or do anything, really, to break it up and make it look more natural? 
Randomiser 
I'd add

self.angles_y = random() * 360;

to the spawn function. This would randomise the angle they face initially, which should make them look better differentiated.

You could also set .movetype to MOVETYPE_NOCLIP and then give them an angular velocity:

self.movetype = MOVETYPE_NOCLIP;
self.avelocity_y = 10 - 20 * random();

I wouldn't recommend this though, because it entirely eliminates the benefit of the client-side rotation built into the model. You'll have constant network updates of the rotation, which seems a bit excessive for the feature. So I'd vote for option 1, but that's how either could be achieved . 
 
"self.angles_y = random() * 360; "

Well, I tried that but no luck. I also tried putting that into a one shot think function that executed a second after spawning but that didn't work either. I'm currently thinking that the model is being rotated in the cached model itself and then every time it renders, they all pull from that same value or something? 
 
I should note that I've created a new item using the quad damage model so it's not the ACTUAL quad damage that I'm dealing with here. If that matters... 
Interesting 
Looks like the rotate flag overrides whatever angle you set in qc or the map. The only alternatives are either to remove the rotate flag from the model, and do the rotation using self.avelocity, or to create several frames within the model each with different rotations of the model, and randomise between those frames on spawn. 
 
Bah! OK, thanks. :) 
Stupid 
Installed Quake on an old win98 computer.
A little curious I couldn't get higher video resolution then 320 x480.
So I decided to install the update 1.08 but this didn't help.
So I installed the SOA pak to see, which also didn't help.
Then Fitzquake or glquake but they start up like mud.

How do I get my quake off the phone resolution? 
 
the update 1.08 is dos only
get the 1.06

Try winquake? 
Limited Resolution 
It has something to do with the video option screen.
Normally after installing quake it offers a resolution from 320x240 to 800x600, but for some reason the max only goes to 480x320. 
 
maybe a dumb question, but just how old is this old win98 computer? it's possible the video card doesn't support the higher resolutions? can you find out what kind of video card it has (if any)? 
Er 
well, that last question was retarded... it obviously has some kind of video card, what i actually meant was if it had 3d acceleration of if it was one of those ancient ones. 
Odd 
It's a mobo I caught out of the surplus and plugged in a disk, a video and soundcard, and finaly I can start a win98 program.
I got all these odd warnings about flipages not correckt screen resolution. I remember in the old 98 it had these errors with darkened screens and garbage messages.
So I'm just on the point Quake starts up well, but only with a max screen of 480x320.
It's not the 3d or something with the videocard, it's only the old dosquake version I can't force to 800x600 resolution. 
What Would It Take ... 
to give liquids an angle, a travel direction, like you can do in Quake 2 ?
It would be great to see water coming down or lava floating from one point to another.
Would it be possible to "steal" the code that makes it possible in Quake 2 and put it in a mod for quake 1, or would it involve changing the Quake engine itself ? 
 
quake2 did it with texture flags, which required a new texture format which the engine recognized.

quake could do it by implementing some sort of shader system, probably. 
No 
I can't do that, that would take considerably more programming skills then I possess.

And I guess it would be impossible to have a liquid texture (*) and combine it with a func_wall (+) one ? 
 
Just animate one of the water textures. Four frames are enough already. 
 
Neg, the trouble is that it would look weird in combination with the "real" water, especially with transparent features enabled. 
 
one trick i've seen is to build a river out of func_trains in an endless loop, with each train having water textures on it.

The "pox extras" mod (which also has some other water-based tricks) had an example map that did this, i think. 
Wow ! 
That's a great idea !
I'm going to try it out right now !
Thanks !

And I'll have a look if I can find the Pox mod, I must have missed that one. 
 
It looks fine with the real water since it's the same texture but yeah, transparency makes it complicated. So your options are: compile the map without transparent water, use the animated texture on a func_illusionary with alpha enabled if the intended engine supports it, or use the regular water texture and greatly increase the scale of one of its planes (by 20-30) - this will create a semi-believable flow-like look, at least on actual waterfalls 
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.