r300 Camera problems

[Enjay]

I have noticed that GZdoom can sometimes seem to run slower when using the view from a camera than it used to. This is usually more obvious with a moving camera as the view seems to jerk slightly sometimes. However, until now I've had difficulty getting a level that demonstrates this because it seems to require the camera to be having to do a lot of work (ie lots of resources on screen) before the effect can become noticeable.

However, in this thread:

http://forum.zdoom.org/viewtopic.php?f=3&t=20864

(which also raises another potential camera issue with GZdoom) the WAD runs much slower with r300 than it does with 1.1.6. With 1.1.6 I get my usual 100fps, with r300 I get 2-3 fps after flicking the switch .

I realise that the WAD is making a specialised use of cameras and camera textures but I hope that it is illustrating the point I'm trying to raise.

The other problem mentioned in the thread (ie the main reason for the thread) also seems like it might be a GZdoom bug as the WAD works as Firewolf wants in Zdoom but not in GZdoom.

I've attached a copy of the file in case you have problems with FileFront.

[Enjay]

Oh, and for info, if I set texture filtering to linear or off with r300 the FPS doesn't drop quite as far (it drops to about 24 fps). With bilinear or trilinear, it drops right down to the 2-3 FPS mentioned. With 1.1.6, I don't get these drops at all.

[Graf Zahl]

It runs perfectly at >85 fps for me.

[Enjay]

Strange





As you can see, there is a significant difference between the 2 versions. With r300, everything is slowed (as you'd expect with such a slow frame rate). Even calling up the menu to quit is delayed. Has anything obvious changed between these versions relating to how this might be getting handled?

(And any idea why the on-screen camera texture effect isn't working, because it does in Zdoom. Also, FWIW, I get no FPS difference between Zdoom 2.2.0 and r1424)

[Graf Zahl]

That's weird. When running this in 640x480 I get far more than 100 fps when I turn of VSync. I haven't changed anything about the camera texture code.

In fact, I only have done minor changes to the GL code. The biggest change is the texture scaling that has been added but tha is not done for camera textures and doesn't make any difference for me.

Can you do a 1.1.6 build of your own and see how that behaves? The most significant difference between these versions seems to me that you build one and I did the other. But your r300 build works fine for me.

[Enjay]

I'll try and do a build later on to see what happens.

For the moment, I think I may have uncovered another minor problem. I was wondering why my FPS was always coming up as 100 despite the fact I didn't have VSync on (at least I didn't think so). So, if I type vid_vsync at the console (1.1.6 or r300) it reports "false". However, if I then type vid_vsync 0, my fps value jumps up to over 300. So, it would seem that GZdoom is capping my FPS somehow. When I quit and restart, I am back to 100 FPS until I type vid_vsync 0 again. In both cases, my ini has vid_vsync=false.

[edit] Incorrect figures reported. Please see the next post. [/edit]

[Enjay]

Oops, I originally posted figures taken with texture filter mode 2 in 1.1.6 and r300 in mode 4. Here are some better figures

1.1.6 Texture Filter Mode 2
When first starting the game, clamped at 100 FPS
After typing vid_vsync 0, 343 FPS (varying slightly) whilst standing at the P1 spot
After hitting the switch and just standing still with vsync still set at 0, 136 FPS

1.1.6 Texture Filter Mode 4
When first starting the game, clamped at 100 FPS
After typing vid_vsync 0, 324 FPS (varying slightly) whilst standing at the P1 spot
After hitting the switch and just standing still with vsync still set at 0, 66-84 FPS

r300 Texture Filter Mode 2
When first starting the game, clamped at 100 FPS
After typing vid_vsync 0, 334 FPS (varying slightly) whilst standing at the P1 spot
After hitting the switch and just standing still with vsync still set at 0, 24 FPS

r300 Texture Filter Mode 4
When first starting the game, clamped at 100 FPS
After typing vid_vsync 0, 351 FPS (varying slightly) whilst standing at the P1 spot
After hitting the switch and just standing still with vsync still set at 0, 2 FPS

[Enjay]

And with my own build of 1.1.6 the figures are very similar to the official build

1.1.6 Texture Filter Mode 2
When first starting the game, clamped at 100 FPS
After typing vid_vsync 0, 348 FPS (varying slightly) whilst standing at the P1 spot
After hitting the switch and just standing still with vsync still set at 0, 134 FPS

1.1.6 Texture Filter Mode 4
When first starting the game, clamped at 100 FPS
After typing vid_vsync 0, 334 FPS (varying slightly) whilst standing at the P1 spot
After hitting the switch and just standing still with vsync still set at 0, 90 FPS

[Enjay]

Oh, I should have mentioned. I went through trying all the gl_ and vid_ cvars to see if any would make a difference and the only one that made a noticeable difference was gl_texture_fliter.

[Graf Zahl]

If I had a vexing bugs forum I'd put this there. I have no idea what's happening and so I can't do anything about it.

Sorry.

[Rachael]

Ask and ye shall receive. I dunno if there's anything else you wanna put here, but here it is.

[Graf Zahl]

Enjay, can ypu please tell me what graphics card and driver version you are using?

I just read something that makes me suspect NVidia having screwed up their drivers for software not using the most modern rendering approach.

[Enjay]

Well, I don't know which driver version I was using when I first reported this, but I just checked with my old and my new computer and the current SVN GZdoom (r339).

Old computer. Geforce 6200 driver 185.85 Win XP
GZdoom running at 1024x768 Trilinear filtering. Switched vsync off for the test.
FPS before hitting the switch 391.
FPS after hitting the switch 2.

New computer. Geforce 285 GTX driver 185.85 Win Vista 64 bit
GZdoom running at 1920x1200 Trilinear filtering. Switched vsync off for the test.
FPS before hitting the switch 1681.
FPS after hitting the switch 989.

Incidentally, I also noticed when going into the video mode menu that I couldn't get it to display some video modes (specifically, the one that I wanted - 1920x1200) is this the known problem of the aspect ratio thing?

[Graf Zahl]

So it's the old graphics card I presume. The drop in the second test is normal and I get the same relations with lower FPS values though.