to get blender to remember that you enabled a plugin, you need to save user settings, otherwise it will only be available until you load another file or select file>new. Some things like this are quite annoying. 

the problem is not Blender nor Windows or Linux,
addon is working fine in both.
Fucking OSX...Grrrr...most expensive one is least useable one,
me pukes... 

 

http://graphitemaster.github.io/gmqcc/index.html 

http://www.youtube.com/watch?v=71H69yDZ6W4 

Will have to try it out sometime. 

Ok, no problem. I may have to go back there within the next coming year, so maybe another attempt would be possible ;) 

Whilst on holiday. I must be cray cray. 

question so dumb you'll wonder how it's possible I need to ask (arg, many similar versions of same map):
is there a command (or an easy way) to find out exactly what bsp file a demo is loading when it loads

I don't want to haveto delete all the versions I think it might be and check if it works heh. 

Run the demo through lmpc and it'll be in there somewhere... (or run "strings $demo_file | grep bsp" or equivalent). 

The 23,000 post award. holy shit that allot of bs for 1 thread 

Sorry to keep spamming about this. I've created a thread over at Blender Artists about the importer, with a link to the latest version etc.

http://www.blenderartists.org/forum/showthread.php?297143-Quake-(1996-game)-bsp-import-script

I doubt I will work on it anymore unless more bugs are found, but there is a list of possible improvements in the readme. This includes filtering models by entity type, importing lightmaps and welding vertices on import.

Also, as a side note, the best path I found for getting it into Maya seemed to be via dae if I remember correctly. If you want to do that, there are a bunch of export options, so if dae doesn't work well, just try dxf etc. until something works. I definitely had dm7rmx in maya though. 

getting it into maya -> getting imported bsps from Blender into Maya. 

Two tool posts in a row. Well, this is more of a micro-tool...it's a little bit of python code which lets you turn a directory of files into a pak file on the command line:

http://tomeofpreach.wordpress.com/2013/06/22/makepak-py

In case the usage isn't obvious from the code: save the text to "makepak.py" then call it like so:
makepak.py mydir pak1.pak

There's no error checking or anything, it's a 40 line program, but it's kinda neat. 

cool stuff. Whilst I do all my Quake stuff in Windows at the moment (not that I've been particularly active over the last few months), I am gradually trying to switch my pc use over to linux. I realised that although there are a couple of Linux editors (notably Trenchbroom, YAY!), there aren't m/any tools for working with pak files, wads, mdls etc.

Given how easy writing these kind of tools is, I thought it might be worth making a few simple applications to do so. Good to see you made a pak creator. Can it extract files and list pak contents too? 

It's a very one-time bit of code, written to do a single task cheaply. It's probably not too hard to adapt it though, if you understand the "struct" module in python.

The quakewiki entry on .pak files is also very good:
http://quakewiki.org/wiki/.pak
It has some sample c code for accessing pak files and extracting a particular file, which would be very pretty easy to adapt. 

http://www.gamers.org/dEngine/quake/spec/quake-spec34/qkspec_3.htm#CPAK0

I normally use this page for quake stuff, even though it's out of date and contains a few errors since it was made before the final version of Quake was released.

To extract pak files, this works: http://pastebin.com/8hxV0vvk 

http://pastebin.com/JhJTNTkj

does actually work. 

http://www.quakeforge.net/ has nice commandline tools. I added some more to http://quakewiki.org/wiki/Quake_tools#PAK_Editors

I can recommend both QF's pak and par. 

 

Next year it gets legit:

http://www.bluesnews.com/s/142741/out-of-the-blue

;) 

Referring to the conversation about Macs and operating systems above:

I sincerely hope your boss wasn't really offering to buy you a Powermac, because the last model came out in 2006. He probably ment Mac Pro, but that too is a silly choice: the current model is vastly outdated - a new Mac Pro is coming out later this year and if you need/want a powerful Mac workstation right now, a fully decked out iMac is a much better choice.

As for operating systems, as long as it runs the software you need it to run, it's just a matter of taste. Windows 7 and MacOS X are both great.

That being said, unless Microsoft comes to their senses sometime soon, it might now make more sense than ever to consider switching to a Mac. Win8 is shit and in the coming 8.1 update instead of listening to the userbase, they are actually doubling down on the things people hate.