News | Forum | People | FAQ | Links | Search | Register | Log in
Q1SP: "White Room"
�A biohazard outbreak at this facility has left the former occupants in a bad way. Enforcers have been sent in to clean up the mess but don�t get in their way. They aren�t on your side and will attempt to clean you up as well.�

http://wantonhubris.com/levels/WhiteRoom/shot01.jpg
http://wantonhubris.com/levels/WhiteRoom/shot02.jpg
http://wantonhubris.com/levels/WhiteRoom/shot03.jpg

This level was an extension of an idea that I had about creating a Quake level in an abstract way. Keep the usual shapes but take away the textures. I like how it turned out and it was great fun to experiment with using color in a much stronger way than is normally done in a Quake level.

This level is being released as a mod because I wrote a bunch of QuakeC to support it. To play it:

1) Create a directory in your Quake directory called �whiteroom�
2) Copy the �progs.dat� and �maps� directory inside the ZIP into that new directory.
3) Start Quake with the command line: �-game whiteroom +map whiteroom�

That should do it! Here are the downloads:

Player Pack
http://wantonhubris.com/levels/WhiteRoom/whiteroom.zip
(contains the level and the associated progs.dat)
(and all the usual random MacOS gumph files that keep getting included with Willem's maps ;))

Developer Pack
http://wantonhubris.com/levels/WhiteRoom/whiteroom_src.zip
(contains the source materials - the map source, the QuakeC source code and the WAD)

Enjoy!
First | Previous | Next | Last
Crashes In Fitz 0.85 
SV_TouchLinks: next != L->next - this would happen sometimes right after the map was loaded, sometimes a second after the elevator started 
Onetruepurple: 
does it actually crash, or just display that message and keep going?

FYI: that message indicates that fitzquake attempted to repair the linked list rather than hanging right then as previous engines do, but doesn't guarantee that the list is actually repaired and it might crash or hang later in the list anyway. The problem is caused by questionable QC practices. For more discussion, see the i3d thread here:

http://forums.inside3d.com/viewtopic.php?t=1431 
To Clarify 
Fitzquake freezes after that message displays in console.

/me replays this in 0.80 
Hmm... 
okay, that sucks if this actually causes a hang in cases that used to be okay in previous versions. I'll investigate a more proper way to fix this situation for next time. 
Just Tested... 
yes indeed, looks like my fix just caused more problems. 
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.