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
Indeed 
I endorse Fitzquake with overbrights and GL_NEAREST for all your je ne sais quoi needs

Oh absolutely, but for me it doesn't quite tickle the nostalgia glands in the way oldskool 8-bit rendering does, the way it uses the colormap and whatnot.

Be nice to see an option in the fitz-type engines that uses a shader to simulate the 8-bit rendering.

necros - for whatever reason, I can't run super 8 on my pc. 
 
Except in extreme cases, you're safe to go to the Fitzquake doubled map limits at the very least.

You won't get any argument here from me on this. Way back in the early 00's I was saying that r_speeds were going to be less and less of a concern in the future. Of course I really had no idea that people would still be mapping for Quake as much as they do over a decade later, but I did know that the common PC was going to be able to handle a much larger and more detailed level design without even breaking a sweat.

Moores law and all of that stuff. 
Moving Objects? 
I have a question regarding doors and platforms... from what I have seen in quake 1 they tend to move one direction and set distance correct? Or is it possible to have them follow paths / move one direction and then another? Have a door shift backwards and then down into the ground as an example. Or a platform on a looping track? 
Doors Not Func_Trains... 
Unless I have to use that as a hack? 
 
Outside of secret doors, no. Everything moves in a linear fashion from A to B. func_trains are the only option for anything fancier. 
 
Func_train and func_path are what you will need to do. Group the brushes that you want to use into one object then give it a func_tran attribute. From there place a func_path at each point where you either want it to turn or want it to wait.

Keep in mind that odd shaped platforms may need some tweaking with the func_paths to keep the platform from disappearing into walls or whatever. The func_train is also just like a func_wall in many respects (no shadows cast by the train platform itself for example) and that whatever shadows fall on it when it spawns into the world will always be on it so be careful about where you start it off from so that it has the right lighting cast on it from the start. 
Danget Map Limits! 
I thought I saved it but I know some helpful person on this forum made a map for quake1 that was the maximum size possible that you could load up in any editor to check if your level was outside the world limits. Anyone know where that link is? :) 
Max Map... 
http://www.quaketastic.com/files/single_player/maps/hugemap.zip

This is the maximum size map you can make for standard bsp quake. 
+-4096 
4096 units in each direction is pretty much the limit, afaik. 
Radiant On Windows 8.1 
Radiant On Windows 8.1 [EDIT]

Posted by AcidicVoid [109.91.58.71] on 2015/01/10 17:25:50
I was wondering if there is a version of Radiant for Quake 1, which runs on Windows 8.1.
I have already tried several versions, but neither GtkRadiant nor netRadiant software runs under Windows 8.1.
Can someone help me with this problem ?



#1 posted by Lunaran [99.112.162.57] on 2015/01/10 18:51:34
Have you tried Radiant 202? It was the last MFC build before the dark times. You'll have to do some gymnastics with texture folders and sleepwalkr's mapconv.exe to use it for quake1 but once you've set it up it becomes an invisible part of the process.

sikkpin also updated the original QE quite a bit, and that's still MFC so it might also be adequately windows future-proof. Works great on 7, at least, and it's what I use. Harder to find, but still essentially Radiant.

#2 posted by AcidicVoid [109.91.58.71] on 2015/01/10 19:51:13
Nope. I can't install the 202 on Windows 8.1.
The installer won't start. 
Radiant On Windows 8.1 
I managed it to install version 202 on Windows 8.1 but it seems just to work for Quakw 2 and 3. 
Classic Radiant 
Sorry ;-) 
 
I imagine the reliance on MFC is part of the problem. Talk about an albatross. :) 
Tyrutils 
Dunno if it helps, but tyrutils qbsp can apparently read q2 mao format, so that could save an extra conversion step 
DERAIL 
MFC is just a wrapper for the windows API, I thought? What makes it so awful to use?

EDIT

googled "MFC sucks," 632,000 results
http://www.jvoegele.com/software/mfcbeef.html 
 
Haha, yeah. Also, it's dead (as in Micrsoft is no longer supporting it) so newer versions of Windows are going to have shittier and shittier support for it. 
Latest Netradiant Works Fine For Me (windows 8.1) 
You can grab the latest NetRadiant here: http://www.icculus.org/netradiant/files/netradiant-1.5.0-20120301-win32-7z.exe

I have no problems using it in windows 8.1 
That's Not The Latest Version 
Well Bugger Me With A Bargepole 
ok fair enough 
Classic Radiant ;-) 
 
Ok 
Well, the actual newest netradiant version (posted by negke) also seems to work fine on my windows 8.1

However they still haven't fixed the fucking clipper (it doesn't draw the 1,2,3 numbers on clip points) since it broke years ago. 
Radiant On Windows 8.1 
The linked version (http://www.icculus.org/netradiant/files/netradiant-1.5.0-20120301-win32-7z.exe) doesn't work for me.
I still get this: https://i.imgur.com/DwU4XQr.jpg
Usually nothing happens afterwards.
Sometimes it starts but crashes after a short while. 
AcidicVoid 
I think it hangs like that for a long time when you start it up for the first time.

Have you tried just letting it sit like that for a bit?

After the first time, it should start up normally. 
Oh Just Read Your Second Sentence 
well, if you do wait until it starts, but it then crashes, then I dunno. 
 
Sometimes it seems to work but the 3D viewport and some hotkeys keep glitching.
I can't find the problem... 
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.