Pictures were taken with DP+QRP.

For compilation I use Lordhavock's hmap2.exe (and Radiant 1.5 for building the stuff). 

To make Darkplaces textures look even more awesome use these two console commands:

r_glsl_offsetmapping 1 r_glsl_offsetmapping_reliefmapping 1

If you use this light tool:

http://celephais.net/board/view_thread.php?id=60480&start=10

You will probably find your lighting problem has gone.

And if you use this QBSP tool:

http://quaddicted.com/tools/txqbspbjp.zip

It might fix the vis error.

Please try it and report back here :) 

re QRP - not my fav, but looks very nice in game with regular textures! 

You have to take the replacement textures into account while you map.

You have to map for the QRP textures, ie use Quake textures whose QRP replacements look good together. If your vanilla textures are a jumbled mess, the QRP will highlight that.

Try using a more cohesive style, and test your map with QRP enabled so you can detect problems early, and it will look great with QRP.

e1m6rq was made for the QRP. The vanilla textures are just placeholders in the editor. Dev textures pretty much. 

I'm a sucker for texture combinations and this map looked ace (Not so much with QRP though as gb said). Tastefully done colored lighting too, I liked the sparse fulldark areas.

The pitch black 'dead end' opposite the NG seemed like a good place for a ROS maybe(?). Unless it was your intention to not use any powerups. 

I will add later second .bsp to archive, which will be ffa and include Quad (or sth else). Thanks guys for all feedback, I will take care of things you mentioned, and will post new version soon. 

Ok guys, second beta:
http://dl.dropbox.com/u/16372046/q1shw1_b2.rar

I've used that light compiler RickyT23 mentioned, it seems ligth issues are gone. Also I fixed some small things, all I could think about atm. I'm pretty content about the map right now, thanks once again for feedback. 

I highly suggest that you post about this on quakeworld.nu since that is where the multiplayer community sits (for quakeworld). There also is quakeone.com where netquake players from the US go. 

Yep, I know both, will do soon. 

Love it, awesome, very different, fresh...except This

The ledges blocking the arches just look wrong, really-really wrong. Or maybe, it's just me? 

Tidy (but still not finished) screenshots:

http://www.zealousquakefan.com/images/arrival/zqftest03_construction46.jpg outside

http://www.zealousquakefan.com/images/arrival/zqftest03_construction39.jpg corridor

http://www.zealousquakefan.com/images/arrival/zqftest03_construction40.jpg supply

http://www.zealousquakefan.com/images/arrival/zqftest03_construction43.jpg upper corridor


Very very WIP screenshots:

http://www.zealousquakefan.com/images/arrival/zqftest03_construction44.jpg gold door

http://www.zealousquakefan.com/images/arrival/zqftest03_construction41.jpg roof

http://www.zealousquakefan.com/images/arrival/zqftest03_construction42.jpg crane 

 

That's looking good, the refinement and details are really helping. The last upper corridor shot shows it well, good base build quality.

The very WIP shots show progress and I'm sure you know about the textures and stuff. Not sure about those spindly pylon things.

Keep at it dude. 

I've posted quite a few shots of it so I'll stop posting them up as much now.

Having said that will try to have a beta ready soonish for gameplay purposes :E 

Hey again. When running the map (Devastation - see few posts up) under WinQuake I have those strange Vis issues:

http://shadowsdomain.files.wordpress.com/2011/01/quake01.jpg

Part of the main room is dissapearing while moving around it. No problems under Darkplaces or Ezquake. 

The Winquake program was designed to play the original Quake maps, which were designed to run on a 486 system with 8MB of RAM. As a result it will only draw so many of the nearest world polys at once. There is a console command to increase this, but I cant remember what it is.

Any modern engine should run the map just fine! 

Yes, as I said DP and ezq runs it great. So there is no thing I can do from mapping point to help this under WinQuake? I mean like adding some copmile/worldspawn command option? 

That looks like if your map is too detailed/complex for winquake. iirc r_speeds must stay below ~800 or things will be greyed out. players can increase r_maxsurfs and r_maxedges to work around this. 

are

r_maxsurfs (default 1000)

and

r_maxedges (default 2000)

The changes require a map-reload. This makes it difficult to use a Quoth info_command trigger to cause this to happen. You could fire those commands in a smaller start-map I suppose. Then when you start your actual map the commands will be activated. But users on non-Winquake engines might get wierd console messages like "unknown command" or something.

Not many people use WinQuake really. You can make Fitzquake and GlQuake etc look like Windquake if you so desire. 

I know that WinQuake isn't really popular ;). Just wanted to get it clear that I can't do anything with it before releaseing the map.

I simply try to test the map as much as it possible. 

You can do something about it. Question is if it's worth it. The map has many texture combinations on walls, all of which use individual brushes. You could take some of the more frequent ones, for example the bricks with the grey concrete trim on the upper and lower parts and merge them into a new custom texture. This would turn three brushes into one. And if you do this in several location, you can lower the polycount enough to make the grey flash go away in Winquake. Alternatively, you could inspect the area with r_showtris 1 (in Fitzquake; DP only with its native culling disabled) to see if what is rendered from that POV and if it can be changed by some vis blocking.

And there are still (few) people who use software QW engines. As crazy as that sounds - it's that entire frame rate++ crap. 

This gives me ideas like forcing "gl_texturemode gl_nearest_mipmap_nearest" on map load. Are those things really possible with Quoth's *_command? I don't think so (I hope not). :D


Obviously ShadoW is not looking for such tricks though. 

But why would you want to do this? 

Thanks guys. It is really not serious issue for me. I can live with it, as you said it yourself - nobody really use winquake, me neither. I asked about it only because to get clear it's engine/port thing. So case is closed ;). 

But that is when I was tailoring a map to fit within the limits of the engine. I was happy enough that the maps loaded in Winquake, and didnt crash it. But I got the same issue that you are experiencing. I think anyone who does use Winquake will probably know to set their draw distance higher. And you can always put a line in your README explaining that Winquake users must use those console commands.....