It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi everyone I could not find any other topic on this, but when I run this on my surface pro 4 the frame rate dips quite a bit off and on and i'm not sure how to resolve it? Lowering the resolution helps (running at 1600x1200) but it seems unusual that the game would chug at all. Has anybody had this issue and solved it?
avatar
burnsquid: Hi everyone I could not find any other topic on this, but when I run this on my surface pro 4 the frame rate dips quite a bit off and on and i'm not sure how to resolve it? Lowering the resolution helps (running at 1600x1200) but it seems unusual that the game would chug at all. Has anybody had this issue and solved it?
"r_primitives 2" from the console or editing the efconfig.cfg could make the performance better
avatar
burnsquid: Hi everyone I could not find any other topic on this, but when I run this on my surface pro 4 the frame rate dips quite a bit off and on and i'm not sure how to resolve it? Lowering the resolution helps (running at 1600x1200) but it seems unusual that the game would chug at all. Has anybody had this issue and solved it?
When you play at higher resolutions you need to make sure that seta com_hunkMegs "36" is changed to a higher value. PCGamingWiki says 72 works fine. Also make sure seta com_maxfps is set to the framerate you want (60, 144, etc.).
avatar
burnsquid: Hi everyone I could not find any other topic on this, but when I run this on my surface pro 4 the frame rate dips quite a bit off and on and i'm not sure how to resolve it? Lowering the resolution helps (running at 1600x1200) but it seems unusual that the game would chug at all. Has anybody had this issue and solved it?
avatar
Gudadantza: "r_primitives 2" from the console or editing the efconfig.cfg could make the performance better
hmm...I just tried that and it helps. I think it's the integrated graphics, it's only 128 mb. I have my desktop to play on so not a huge deal, if anybody has any other tips let me know, i'll just reduce the res down more lol
avatar
burnsquid: Hi everyone I could not find any other topic on this, but when I run this on my surface pro 4 the frame rate dips quite a bit off and on and i'm not sure how to resolve it? Lowering the resolution helps (running at 1600x1200) but it seems unusual that the game would chug at all. Has anybody had this issue and solved it?
avatar
Berzerk2k2: When you play at higher resolutions you need to make sure that seta com_hunkMegs "36" is changed to a higher value. PCGamingWiki says 72 works fine. Also make sure seta com_maxfps is set to the framerate you want (60, 144, etc.).
I did this as well and it helps but still stutters and frames drop but not as bad, it's gotta be the integrated graphics, thanks for the tips
Post edited September 08, 2021 by burnsquid
the r_primitives 2 editing always helped me in every Q3 Engine game, but could anybody tell me what exactly does? I Never saw any difference graphically or in quality. It just runs better. Smoother. But no idea ow it works.
avatar
Gudadantza: ... but could anybody tell me what exactly does? I Never saw any difference graphically or in quality. It just runs better. Smoother. But no idea ow it works.
r_primitives is the command for setting the rendering method

-1 = skips drawing results in black screen
0 = uses glDrawElements if compiled vertex arrays are present, or strips of glArrayElement if not present
1 = forces strips
2 = forces drawElements
3 = path for non-vertex array testing
avatar
Gudadantza: ... but could anybody tell me what exactly does? I Never saw any difference graphically or in quality. It just runs better. Smoother. But no idea ow it works.
avatar
Berzerk2k2: r_primitives is the command for setting the rendering method

-1 = skips drawing results in black screen
0 = uses glDrawElements if compiled vertex arrays are present, or strips of glArrayElement if not present
1 = forces strips
2 = forces drawElements
3 = path for non-vertex array testing
Oh, thanks for the info. And does it visually change something regarding the quality of the graphics? or is it just an internal method for compatibility conveniences etc...? Honestly I never perceived any lose in quality.

Greetings
avatar
Berzerk2k2: r_primitives is the command for setting the rendering method

-1 = skips drawing results in black screen
0 = uses glDrawElements if compiled vertex arrays are present, or strips of glArrayElement if not present
1 = forces strips
2 = forces drawElements
3 = path for non-vertex array testing
avatar
Gudadantza: Oh, thanks for the info. And does it visually change something regarding the quality of the graphics? or is it just an internal method for compatibility conveniences etc...? Honestly I never perceived any lose in quality.

Greetings
Compatibility. Remember when the idTech3 engine was developed, things like Vertex Arrays while adopted by the OpenGL standards, weren't widely available back then, Quake 3 was designed to run on ancient hardware. Visually there should be no difference, just efficiency behind the scenes.
Renaming the exe to Quake3.exe might also help, though it would break Galaxy integration, if you're using it.

(Q3 multiplayer is played to this day, so it's still pretty well supported by modern GPU drivers. Elite Force runs on the Q3 engine, so we're pretending it's Q3 to get that compatibility. At least that's how I understand it.)
Post edited September 09, 2021 by Samarius
avatar
Samarius: Renaming the exe to Quake3.exe might also help, though it would break Galaxy integration, if you're using it.
You can always point Galaxy to custom executables so it's no big deal.
avatar
Gudadantza: Oh, thanks for the info. And does it visually change something regarding the quality of the graphics? or is it just an internal method for compatibility conveniences etc...? Honestly I never perceived any lose in quality.

Greetings
avatar
TehJohnny: Compatibility. Remember when the idTech3 engine was developed, things like Vertex Arrays while adopted by the OpenGL standards, weren't widely available back then, Quake 3 was designed to run on ancient hardware. Visually there should be no difference, just efficiency behind the scenes.
Thanks for the clarification
I had the same issues but I have a laptop with a RX 5600m, the only why I fix it is just using the free Holomatch mod. Whch you can find by just googling the last outpost Elite Force and a easy why to find servers I use is the Qtracker.