Poor performance

[tobspr]

Poor performance

[rdb]

@funcelot that has nothing to do with Python or Panda3D, but it's because the RenderPipeline is using deferred rendering. That means most of the shaders run in postprocessing, once per fragment, and so any doubling in resolution will result in a quadrupling of the render time of the entire postprocessing pipeline, which adds up quickly.

4K has a lot of pixels to render. Most games that use deferred rendering do not run well in 4K, and typically render downscaled and then upscale in a postprocessing pass.

[tobspr]

Hi,

can you run pstats and see which parts of the pipeline are running slow?

[RodrigoMedeirosRS]

Spstatus + Sys Monitor

1280 x 720

800 x 600

In both cases, i have many, many lags when i move the camera, but, the frame rate never drops.

[rdb]

It would be very helpful to see the pstats charts. If you have the pstats process running, press 1 in the pipeline to enable it.

[RodrigoMedeirosRS]

Sorry, i confuse the pstats and stats gui.

Here is the PStats:

1280 x 720

800 x 600

[tobspr]

Could you open the gpu graph and check which parts take the most time?

[rdb]

Also, keep in mind you can double-click the labels on the left to get a more detailed subdivision of that category of the graph. For example, clicking the "Draw" label will open up a new chart showing how the draw time is divided up.

[RodrigoMedeirosRS]

Note: My pc use's a APU technology - https://www.youtube.com/watch?v=ER_u3yLccBU

So i have made a print for every graph option i will post the most critical first:

1280 x 720
* AMD(TM)R7 Graphics:

* Draw

* Draw -> Primitive

* App

* Cull

* Time

* Wait

800 x 600
* AMD(TM)R7 Graphics:

* Draw

* Draw -> Primitive

* App

* Cull

* Time

* Wait

[tobspr]

Thats weird, it looks like everything is too slow. Are you sure you are not running it on an integrated gpu or so?

[rdb]

Yes, an APU has integrated graphics, so make sure that it has been switched to use the external graphics card.

Are these the CPU charts you're showing or the GPU charts? (The GPU charts are available under the "AMD Radeon… > Frame" menu.

Which version of Panda do you have?

Is there any improvement from adding 'gl-version 3 2' in the pipeline Config.prc?

[RodrigoMedeirosRS]

Yes, i am using the integrated Graphics, my integrated graphic is a Readeon R7 250 with 2gb vram and 512 stream processors, my integrated Graphics are running the Unreal 4 into cinematic quality and CryEngine 5 in best no 4k quality. The external card works only into the Crossfire, but the AMD crossfire crashe's all OpenGL applications, and work only into the DX11 applications.

The AMD(TM)R7 Graphics charts are showing my integrated card.

[default-writer]

I have 1080 ti, and funny part that in small window, it is 400fps+ but in 4k, any scene of almost any complex is no more than 40 fps, seems that python doing some weird staff with paints windows background, cause it is bitbltm the more sureface are, the more ms is spend on purpouseless repaint of transparent background, anyway this is a window and borderless window preoblem on any of the samples. It looks like this is a problem with Pandas3d itself, can you take a look and fix it? @tobspr

[default-writer]

@funcelot that has nothing to do with Python or Panda3D, but it's because the RenderPipeline is using deferred rendering. That means most of the shaders run in postprocessing, once per fragment, and so any doubling in resolution will result in a quadrupling of the render time of the entire postprocessing pipeline, which adds up quickly.

4K has a lot of pixels to render. Most games that use deferred rendering do not run well in 4K, and typically render downscaled and then upscale in a postprocessing pass.

Is that the same technique i seen in Cyberpunk2077 wher image seems crispy and make somewhat more detaild in one sec or so? Got your point, thanx

[default-writer]

@funcelot that has nothing to do with Python or Panda3D, but it's because the RenderPipeline is using deferred rendering. That means most of the shaders run in postprocessing, once per fragment, and so any doubling in resolution will result in a quadrupling of the render time of the entire postprocessing pipeline, which adds up quickly.

4K has a lot of pixels to render. Most games that use deferred rendering do not run well in 4K, and typically render downscaled and then upscale in a postprocessing pass.

I saw down scaling & posptrocess upscaling in Horizon Zero Dawn, where i play in 4K, but can postprocess in 1080p, using 50% or 25% scale

[default-writer]

Can you provide upscaling / downscaling example using you pipline renderer @tobspr ? That would be really aswesome to see 120 fps on 4K, indeed :)

[tobspr]

There are multiple ways of doing that, IIRC the pipeline supports it natively though, you can set resolution_scale in the config:
https://github.com/tobspr/RenderPipeline/blob/master/config/pipeline.yaml#L26

To e.g. 0.75, the pipeline will then render at 75% resolution and scale up