Beginner help
Moderator: InsideQC Admins
6 posts
• Page 1 of 1
Beginner help
Hello!
It's been a few years since I've played around with the qc-code, and things have changed a bit. Darkplaces have been released and it seems like the engine to use, is that right?
I've downloaded sv_user.qc and tried to include that and dpextensions.qc to progs.src, but I get errors on both and can't compile. What do I do wrong?
I used FrikQCC but I read on these forums that it was a bit limited, so I downloaded QCide, but I still can't compile.
Thankful for help.
It's been a few years since I've played around with the qc-code, and things have changed a bit. Darkplaces have been released and it seems like the engine to use, is that right?
I've downloaded sv_user.qc and tried to include that and dpextensions.qc to progs.src, but I get errors on both and can't compile. What do I do wrong?
I used FrikQCC but I read on these forums that it was a bit limited, so I downloaded QCide, but I still can't compile.
Thankful for help.
- clejs
- Posts: 3
- Joined: Tue Jun 28, 2011 12:37 am
Can you copy and paste the error messages you got ? BTW I use DP and FrikQCC without any problem.
I know FrikaC made a cgi-bin version of the quakec interpreter once and wrote part of his website in QuakeC
(LordHavoc)
-

frag.machine - Posts: 2090
- Joined: Sat Nov 25, 2006 1:49 pm
I think the intention with dpextensions.qc is to keep it compatible with any QCC, more specifically FrikQCC ought to be okay.
its possible that recent versions have unintentionally used features provided only by a certain other compiler, which would explain why ceriux needs to comment out some lines.
I doubt that it is intentional though, as I can't imagine LH not at least insisting on preprocessor to retain compatibility with frikqcc for the remaining extensions.
its possible that recent versions have unintentionally used features provided only by a certain other compiler, which would explain why ceriux needs to comment out some lines.
I doubt that it is intentional though, as I can't imagine LH not at least insisting on preprocessor to retain compatibility with frikqcc for the remaining extensions.
- Spike
- Posts: 2892
- Joined: Fri Nov 05, 2004 3:12 am
- Location: UK
Sure, here are the error messages.
dpextensions.qc
dpextensions.qc(300): error: ")" is not a type
dpextensions.qc(301): error: ")" is not a type
dpextensions.qc(302): error: "URI" is not a type
dpextensions.qc(303): error: "key" is not a type
sv_user.qc
sv_user.qc(51): error: Unknown value "bound"
dpextensions.qc
dpextensions.qc(300): error: ")" is not a type
dpextensions.qc(301): error: ")" is not a type
dpextensions.qc(302): error: "URI" is not a type
dpextensions.qc(303): error: "key" is not a type
sv_user.qc
sv_user.qc(51): error: Unknown value "bound"
- clejs
- Posts: 3
- Joined: Tue Jun 28, 2011 12:37 am
void(string name) gecko_navigate( string name, string URI ) = #489;
ehehe, nice bug.
just comment out those 4 lines.
the sv_user.qc issue will be fixed by the use of dpextensions.qc before it.
ehehe, nice bug.
just comment out those 4 lines.
the sv_user.qc issue will be fixed by the use of dpextensions.qc before it.
- Spike
- Posts: 2892
- Joined: Fri Nov 05, 2004 3:12 am
- Location: UK
6 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest
