Announcement
Collapse
No announcement yet.
(Poll) Main reasons for using GLProQuake rather than DarkPlaces
Collapse
X
-
I remember the good old days when the "raspberry" emoticon looked like you were actually sticking out your tongue and not just doing a goofy toothless grin.Originally posted by RocketGuy View PostWrong
If I use rcon on a ProQuake server it kicks me
Leave a comment:
-
It works, believe me. Note that the port variable is not changed by doing this.Originally posted by ORL View PostYes it should, but it doesn't. Not with Darkplaces anyway. Thats the issue I'm bringing up. It's not switching over to port 26003 like it should.
I was surprised when I tried connecting to a server using proquake recently because it said it changed port.
Leave a comment:
-
Connect coop.runequake.com:26003 works but isn't that server down right now?
Maybe ORL is doing it the "old fashioned" way doing Port 26003; connect coop.runequake.com
Leave a comment:
-
Well its working for me, but maybe LordHavoc has an idea why it does not for you.
Leave a comment:
-
I have found another annoyance in DP.
When you try to connect to a server, say for example coop.runequake.com:26003 by console, DP doesn't switch over to port 26003. It stays at 26000. If you want to switch the port, you have to do it at the multiplayer: join game menu. I always connect to servers using console, its much quicker.
Leave a comment:
-
Changed to match proquake, I had been misinformed by the person requesting the feature in the first place, a web search did not reveal any engines that use the single parameter version, so I don't know why the person gave me an example using a single parameter.Originally posted by RocketGuy View PostI would also like it if the bestweapon command was changed to be like PQ (bestweapon 1 2 3 4 5 6 7
because current bestweapon behavious is incompatible with my autoexec.
Leave a comment:
-
I would also like it if the bestweapon command was changed to be like PQ (bestweapon 1 2 3 4 5 6 7
because current bestweapon behavious is incompatible with my autoexec.
Leave a comment:
-
Canadian youre spot on, and I apologize for the tangent, just some pet peeves kept being stepped on, and lately Ive not had the most patient of a voice. Thanks for keeping me in check.
Leave a comment:
-
Concise summary of the above post:
If someone gets 1) good FPS even in an intense battle and 2) can see clearly in DarkPlaces, they are going to like it. #2 seems like a complete non-issue with the new menu.
Leave a comment:
-
I think the emotion evoked in discussions regarding DarkPlaces work like this:
1. Everyone wants something better.
2. Everyone wants something new and fresh.
3. How can we get from point A to point B.
4. Frustration that we aren't at point B.
When a new player loads up an engine for multiplayer, really they mentally do this:
1. You need to get a constant 60+ FPS to do well in Quake. If your FPS ever dips below 60 (I mean *EVER*), you cannot shaft AND you cannot defend yourself. A player, consciously or not, will notice if they are a hopeless frag. With DarkPlaces, this can be an issue, but in GLPro it is pretty much a non-issue.
2. Then a player will probably turn as much stuff on they can while still meeting criteria #1.
3. A player will also need to be able to see clearly. Moving the brightness settings to Options = (b) (b)
When I say that at least for Quake you need a constant 60 FPS, what I mean is that if the FPS dips below 60 there it is always going to be when they are attacked and have rockets exploding by them, it won't be in empty room :d
If the FPS dips to, say, 25 to 37 when rockets are exploding around them, chances are the FPS dip will guarantee they get fragged. This is why on really bad computers, players use wqpro instead because wqpro is virtually impervious to performance issues of any kind.
Also, if the FPS dips below 60, you can't keep the lightning gun locked on someone -- it is simply impossible.
This is sort of thinking out loud while I try to figure out what the deal is with my DarkPlaces not connecting. Right now, my DarkPlaces seems to not connect due to my config for some reason. If I go into a sub-menu and set something or turn something ON or OFF (I haven't identified what it is), I can no longer successful connect to NQ servers.
At this point, I'm thinking the problem isn't that I "can't connect" but rather other setting is hosing DarkPlaces when a map changes or is initialized -- which looks similar to a "can't connect" but is actually some other issue in disguise.
Leave a comment:
-
I don't want to see this thread stray off topic as I do see the benefits to this discussion. The purpose of this thread was to hear the opinions of non-darkplaces users on why they prefer other engines (in this case, glpro). This way LordHavoc would be able to use that feedback to enhance the engine if he could. I have been keeping quiet on other people's opinions in this thread because I'm a darkplaces user and would not contribute to this discussion with a bias towards darkplaces.
With that being said, please carry on.
Leave a comment:
Leave a comment: