 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
aguirRe is the one to listen to, he would know as well, probably better than anyone what the story is, just consider my ramblings as just that :)
http://www.disenchant.net/ and send him an email :P
to re-light Invein (i.e. keep the lit and then use my Light) and then load it in JoeQuake (refused to load lit - invalid size) and Fitz (psychedelic lightmaps).
So I'm pretty sure it doesn't work. It's been a long time, I did mess around with it once before, thinking about it know, there must have been problems, but it's a long time ago. It does work for me in a little box test map, as far as the colored lighting goes, all looks as it should and everything is in place, until . . . you place things like func_wall's _door's etc, then the func_eee stuff starts to happen, disco, psychedelic lightmaps as mentioned above etc etc.
Oh well, looks like it's just one or the other, sorry RickyT23, wild goose chase. So I'm pretty sure it doesn't work. That's good enough for me Until I smash engine limits and only AguirRe's engine will run my map, I'll just stick to Tyrlite!!
I have figured out how to make lightning gun lightning which I can put in my level and then trigger to fire (almost) forever, as part of some sort of generator-type-machine, but isnt shambler lightning prettier?
Have been reading through Teaching Old Progs.dat New Tricks! How would I change Lightning gun lightning for Shambler lightning? http://celephais.net/board/view_thread.php?id=37116&start=11&end=11 What would I have to change in my info_notnulls? You'd use
http://celephais.net/board/view_thread.php?id=37116&start=14&end=14 instead. The particular function you'd want is CastLightning. Rather than setting "enemy" "1", which would make the lightning shoot at the player, make another info_notnull. Find out the edict number of this info_notnull, say 23, using the 'edicts' command in the console. Then set "enemy" "23" on the lighting shooter. Be warned, this kind of hack can be hard to pull off when you have skill levels, because if monsters etc. get removed, the entity number of the lightning target can change. One way to avoid this is to ensure that the lightning target is added before any monsters, so nothing can be removed earlier than this entity. The other way to do it is to have three copies of the setup in your editor, one that only appears in easy skill, one for medium and one for hard. Then work out the correct entity number for each skill level. I edit the
Thnx BTW :) The first way would certainly work, except that you'd have to do this each time, which would be a pain. It's better to make sure that the entities are in order in your editor, which in worldcraft means adding them first - no idea about other editors. I think the latter way of doing it(one version for each skill) is gonna be easier in the long run...
As it happens, I havent put any enemies in the map yet! I think what I'll do is use Weapon Lightning for the mo as a marker type thing, and then right at the end (after all testing and stuff) change it for shambler lightning. Anyhoo, its good to know I've got options here!
Thnx again!!! If there's nothing in the map that's gonna get removed by spawnflags yet - that's the perfect time to sort this out! You won't have many entities to look for in your list of edicts, and you won't have to worry about anything getting removed. Just don't delete any entities currently in the map and all should(fingers crossed) continue working in the future. So I'd recommend change it now, get it working, then continue adding monsters etc.
I hope so. I mean I'll try it. I dont know much about the transition between an
I believe that what Im gonna do is make the level to a point where I need some testers, cause that way after I have sorted out the gamepley, I can fix up the lightning using Notepad!!! - Then do it all again for the final version :|
Yes, I believe I have popped my Worldcraft 3.3 Nice GUI and texture alignment stuff, but if you export a I got the lightning sussed. I moved the targetted info_notnulls to where the first few entities start after all of the world stuff, then use AguirRes engine to look at the edicts, get the number, then change the 'enemy' key appropriately. I have also discovered how you can clean up a Worldcraft and notepad dont work in unison very well tho! Worldcraft takes stuff out and adds stuff in like extra keys on import!! So backups have been essential!! - I have to resume building on an un-hacked version. The experiment worked, but I will have to re-do it all again anyway cause I can't resume working on the hacked version :( I only messed around with 1.5 briefly, I prefer 1.4, but anyway, is it called something else? materials or something maybe? What happens if you press the T key, does that bring up the texture browser?
and the texture window will come up. Personally, I only use 1.5 for creating prefabs but not for texturing. I hate the new texture methodology here because of the fewer options and the less intuitive set up. Why screw up something that had worked well since QeRadiant?
they moved the texture menu down so that it is part of the texture viewer portion of the screen. (I think)
any of the Radiant builds can be used for Quake mapping. This is I do it - I set Radiant for Quake 3 Arena, I convert the Quake wad I'm using to the Targa format and place them in my Quake 3 directory like this:
Quake3/Baseq3/Textures/Armagon Next, you'll need the definitions file, go to Quake3/BaseQ3/Scripts folder and replace the entities.def file with the Quake1.def file. Which you can find here: http://mortisville.quakedev.com/quake1.def (Filezilla is the greatest!) You'll have everything you need to build a map file. You'll run into a few things that might cause you trouble. Don't bother with the curve tools, they wont translate over to Quake 1, and Quake 3 texture alignment is more flexible than Q1 native so it is best to experiment in this area to see what you can get away with. Part I
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |