Thank you for all your help. I can run it now. However, I am encountering
a new problem. I have been searching via the forum to see if there is any
answer to this problem, but no success yet.
I am able to build and run ioquake3.exe in debug mode. However, when I try
to change the code (ui_cred
Quake3 uses either a DLL or a so called "QVM" file. Ready for the hard part?
You've seen that *.c code is compiled by your native compiler into a *.dll
file. OK. The same *.c can be compiled by a different C compiler (called
lcc) and then converted into VM code. This compiler distributed as part o
On Wed, Sep 21, 2011 at 6:12 PM, Patrick Baggett
wrote:
> Yes, there are 3 things in total:
> 1) ioquake3 binary (EXE) file
> 2) ioquake3 updated PK3 files
> 3) PAK0.PK3 from Quake3 CD.
> I'm currently behind a web filtering system, otherwise I'd just give you
> direct links to what I am saying. F
I mean, compared to the pk3 files that came with the retail CD in 1999/2000,
which is what I have, so I had to update them. I wasn't cool enough to
actually download updates for Q3 later. :D
Patrick
On Thu, Sep 22, 2011 at 11:32 AM, Matt Turner wrote:
> On Wed, Sep 21, 2011 at 6:12 PM, Patrick
http://ioquake.org/forums/viewtopic.php?f=13&t=116
Q: I made some UI changes to ioq3 and recompiled it, but when I go to run
it, I get stock Quake 3 menus/UI! What gives?
A: QVMs probably. QVMs are probably taking precedence, there's a command
line you can use that forces .so instead. From what b
