[MrEWhite]

I would like to see everyone's software renderer framerate at the start of E1M1 along with there computer specifications and resolution and type of build you are using, 32-bit or 64-bit.

Just simply boot up Duke and start Hollywood Holocaust and open up console (~ key) and type "r_showfps 1" and report the framerate after the dukecar crashes.

For me, the framerate is 200 FPS with the 64-bit build with an i7 4790k @ 4.6 GHz, GTX 980, and 16 GB RAM @ 1866 MHz.

If you can do this, massive thanks to you

[Fox]

1600 x 900, average 87 fps (64-bit).

[Inspector Lagomorf]

1920 x 1080, average 355 fps.

AMD FX-8350 @ 4.3 ghz
NVIDIA GeForce GTX 960
8GB RAM (G.Skill 1866 Mhz)
Windows 10, 64-bit
Samsung 850 EVO (256 gb)

This is on a 32-bit build so I imagine the framerate would be much higher on a 64-bit build.

[Hendricks266]

State whether you're using a 32-bit build or a 64-bit build of EDuke32. It's hugely important.

[MrEWhite]

Hendricks266, on 15 February 2016 - 04:26 PM, said:

State whether you're using a 32-bit build or a 64-bit build of EDuke32. It's hugely important.

Forgot this.

[MrEWhite]

Inspector Lagomorf, on 15 February 2016 - 04:22 PM, said:

1920 x 1080, average 355 fps.

AMD FX-8350 @ 4.3 ghz
NVIDIA GeForce GTX 960
8GB RAM (G.Skill 1866 Mhz)
Windows 10, 64-bit
Samsung 850 EVO (256 gb)

I can't get near that. You sure you aren't using polymost or polymer?

[Mblackwell]

64bit build on Ubuntu Linux (not sure it matters)
i7 4770k @4ghz
1920x1200
Average of about 95fps.

Spoiler

Investigating, the game only ever uses 1 CPU core which is fine except that it's doing both logic and rendering, and getting stalls apparently.
When the game is able to offload its rendering somewhere like the GPU (AKA Polymost) the framerate skyrockets, although CPU utilization is the same.
In Polymost my framerate was 1222fps.

[MusicallyInspired]

Will give it a shot when I get home.

[Mark]

65 fps during animation 70 fps after crash ( software )
85 and 120 fps with Polymer and HRP ( my preference )
Eduke32 version 5628 32 bit
1680 x 1050
Nvidia 750ti
Vista 32 bit
Intel core2duo 3.0ghz 4 GB ram

[MrEWhite]

I am asking what is your framerate at the very start of E1M1, that's the only framerate I need.

[MusicallyInspired]

155 fps on the roof of E1L1 in 8-bit software rendering using latest EDuke32 64-bit synthesis build (5628).

Intel i7-2600k @ 3.40GHz
8GB RAM @ 1600MHz
GeForce GTX 460
1920x1080 full-screen

[Mark]

Comstock DeWitt, on 17 February 2016 - 04:02 PM, said:

I am asking what is your framerate at the very start of E1M1, that's the only framerate I need.

Then your instructions should be to turn on the fps counter BEFORE running the map if you want the framerate at the instant the map starts. By the time someone types in the command in the console the dukecar will have already crashed and give a different reading. Thats why I gave both readings. So I guess my answer is 65 at the instant the map starts but then immediately changes.

[Mblackwell]

You shouldn't run with the HRP if you're comparing between the renderers or your not getting a correct reading.

[Mblackwell]

MusicallyInspired, on 17 February 2016 - 04:21 PM, said:

155 fps on the roof of E1L1 using latest EDuke32 64-bit synthesis build (5628).

Intel i7-2600k @ 3.40GHz
8GB RAM @ 1600MHz
GeForce GTX 460

What resolution?

[Mark]

Mblackwell, on 17 February 2016 - 05:42 PM, said:

You shouldn't run with the HRP if you're comparing between the renderers or your not getting a correct reading.

I know but it was too much effort to disable it just for the test. I threw it out there in case anyone else wanted to compare something other than software rendering. The thread is a neat idea and I thought I would expand on it a little.

[Hank]

hopefully I did this testing right.

Intel Xeon E5-2630 v3 with nVidia Quadro 4000
Win 7
eduke 64 bit


results:
Software (8bit) gives 238 fps and (32bit) gives 420 fps, @ 1280 x 960, windowed mode.

[MusicallyInspired]

Mblackwell, on 17 February 2016 - 05:43 PM, said:

What resolution?

Edited.

[MrEWhite]

Edited the OP.

[TerminX]

This isn't a particularly useful metric unless you specify which resolution to test at...

[Forge]

64bit eduke
windows 10 64 bit
AMD FX 8320
16 gb ram
GTX 650 TI

1280x960 full screen
classic = 200fps
polymost=2177fps
polymer=503fps

[Gambini]

so that means polymer is twice as fast as the software renderer. case closed!

[Fox]

Ten times.

[The Mechanic]

Two PC's (#1 is where I do most of my Duke'ing) so here goes (all at initial start pos of S1E1 after animation completes, all running full screen)

#1 : Intel Core2 Duo T5250, 1.5GHz, 2GB RAM, Win7 64bit
Intel 965/963 Graphics Media Accelerator 2.0.0 - Build 8.14.10.1930, 1280x800 screen

r5628, 32 bit, 800x600 => 115
r5628, 64 bit, 800x600 => 108
r4500, 32-bit, 800x600 => 88
r5628, 32 bit, 1280x800 => 54
r5628, 64 bit, 1280x800 => 52

For comparison, using polymost
r5628, 32 bit, 800x600 => 205
r5628, 64 bit, 800x600 => 202
r5628, 32 bit, 1280x800 => 134
r5628, 64 bit, 1280x800 => 135

Polymer = no-go. In fact, r5628 is the first version of Eduke to be able to run polymost on this h/w (iirc r5588 does NOT work). I only tried these modes as it was the first time I tried the 64-bit versions on that m/c and was amazed when it worked (as did latest 32bit too).

#2 : Intel i5-3230, 2.6GHz, 4GB RAM, Win8
Intel Intel® HD Graphics 4000 4.0.0 - Build 9.17.10.2867
All using r5628

64-bit, 800x600 => 351
32-bit, 800x600 => 290
32-bit, 1280x960 => 123
32-bit, 1920x1080 => 73

Polymost comparison (all 32-bit Eduke)
800x600 => 720
1280x960 => 454
1920x1080 => 301

Polymer comparison (32bit Eduke)
800x600 => 656
1280x960 => 410
1920x1080 => 260

Gambini, on 17 February 2016 - 11:15 PM, said:

so that means polymer is twice as fast as the software renderer. case closed!

And polymost a faster still

However, the real story unfolds after Duke drops to the bottom of the shaft at the start of E1L1 and faces the burning dumpster (number in brackets is frame rate at very start of E1L1):

S/w renderer : 342 (351)
Polymost : 528 (720)
Polymer: 113 (656) <=== Sucks ! 3 times slower than the software renderer.

TTFN,
Jon

[Inspector Lagomorf]

We should just design a graphics stress test like Counter-Strike: Source has, for this very purpose.

[Forge]

The Mechanic, on 19 February 2016 - 05:54 AM, said:

However, the real story unfolds after Duke drops to the bottom of the shaft at the start of E1L1 and faces the burning dumpster (number in brackets is frame rate at very start of E1L1):

S/w renderer : 342 (351)
Polymost : 528 (720)
Polymer: 113 (656) <=== Sucks ! 3 times slower than the software renderer.

same specs from my previous post, but at this location:

classic; 233
polymost; 1494
polymer: 289

(averages - classic and polymer only bounced maybe +/- 10, but polymost had a range of +/- 20)

[The Mechanic]

And for an encore ...

Linux Mint 17.something (xfce), 64-bit
Acer Aspire One (Intel Atom N450, 1.6GHz)
Integrated graphics
1024x600 screen
Eduke r5628, built from source

Have to admit I wasn't expecting very much but it is actually running well. Frame rate at start of E1L1 (number in brackets = at bottom of shaft), running full screen plus I assume I'm running 64-bit eduke since 64-bit OS ? (I'm not a Linux expert)

800x600 => 64 (64)
1024x600 => 52 (57)

For comparison, polymost:
800x600 => 114 (90)
1024x600 => 94 (84)

Polymer ? Yeah, right

One thing I've noticed with the linux version is the opening theme tune seems to play 50% faster plus sounds much cleaner, more instruments as well ? Rocking!

So far been impressed by Linux Mint - ok, so their site just got hacked but that 'aint the OS's fault. (cough-Wordpress?-cough)

TTFN,
Jon

[pmw]

i7 960
GTX 650Ti

98fps @ 1920x1080.

Using pretty old version..EDuke32 2.0.0devel r5412 (32-bit) C++ build..huh.
Okey, I tried with a newest version, now I'm hitting 100fps.

I wonder does Eduke in classic mode use GPU ~at all? By monitoring GPU, it doesn't seem to do much. I wonder how much GPU affects to fps in this game.

[Mblackwell]

It shouldn't really be using the GPU at all in classic.

[TerminX]

Yeah, the only thing in classic that hardware acceleration might affect would be the actual composition of the rendering output onto the screen by the OS and video driver. There is no direct usage of the GPU at all by EDuke32 in classic mode.

[X-Vector]

Rooftop after spaceship crash
Classic: 270 FPS (230 lowest during crash)
Polymost: 1480 FPS average (1050 lowest during crash)
Polymer: 1800 FPS average (300 lowest during crash)

Street down below
Classic: 300 FPS
Polymost: 1100-2000 FPS (not facing walls)
Polymer: 230-700 FPS (not facing walls)

Eduke32 build: r5344 64-bit

Core i7-2600K (3.4GHz)
HD6950 2GB
8GB RAM
Windows 7 64-bit
Catalyst 13.1
1280x960