This thread is dedicated to 3.5 (+the patch) performance.

Feel free to take a your own screenshot and post it below with your system spec's.
Press [CTRL]+S to bring up the preformance into on the top left (the white text - top left on my screenshots)
You do not need to go as in depth as i will.

My specs are:
Msi GX60 Laptop
CPU: AMD A10-4600m APU
GPU: AMD Radeon HD 7970M
RAM: 8GB

Game settings:
Ultra - DirectX - 1920X1080 screen - 100% - Enabled - Disabled - Disabled - Disabled - 8X

DirectX

DirectX continued:

OpenGL continued



Well, that's it than.

last one ! I need it !
Is it copyrighted ? I'll make a great abstract painting with it !

Thank you for the overview.

Here for completeness is an explanation of the performance parameters:

FPS:
The actual framerate. Maximum 60 fps (Under Oculus maximum 75 fps).
This value is in most cases the minimum of FPSR and PPSR.

FPSR:
The framerate that is possible with your GPU (not the CPU).
A value of e.g. 121 mean you are well above the 60 fps, so your graphics card is not the bottleneck.
This value is only well-behaved if V-Sync is disabled in display settings, because otherwise the sync lowers this value.

PPSR:
The framerate that is possible with your CPU.
A value of e.g. 80 mean you are well above the 60 fps, so your CPU is not the bottleneck.
CPU somewhat of a simplification of this value. The memory and bus speed also has impact on this value.
On an Intel i7 2600 CPU 3.40 GHz this value should be well above 60 fps in 99% of the time.

If your PPSR is lower that 60, than e.g. having less cloths on the girls (or less girls) can help.
But best is to run XSP on a faster system.

SPSR:
Not relevant for performance.
It is the performance of the thread synchronization and is well above 60.

CPS:
An runtime estimate of your processor cps.
(So if this value is lower than what is said on the CPU box you have been cheated )

Mode:
The graphics mode. There can be a large performance difference between OpenGl and DirectX.
So if your FPSR is the bottleneck, try another render mode to see if that helps.

Ahaha, no but seriously i gotta figure out whats up with that...



This is probably the most erratic/non-logical one for me, as proven in the sreenshots.
0 Girls = 120?
1 Girl = 210?
Verry stange for it to change like that.
Also there is a GPU usage stat the "GPU : X%" the seems to jump about too. sometimes hitting 100% while staring at a wall???


Yeah there's a clear drop in PPSR as i add more girls in the screenshots:
0=~230
1=~80
2=~45
3=~30
4=~25

Makes sense.


Is it weird that i thought this was sound processing? lol.

Anyway, i feel the CPU usage needs work. At least the threading dose.
You can clearly se the HUGE difference in cpu usage between the cores.

The worst is with 2/3/4 girls.
Core 3 hitting 80-90% while the others sit below 30%

Would it be possible to split whatever thread is being put on core 3 into 2 parts?
I'm no programmer but this looks to be an issue.

Most likely due to V-sync being on. This can cause errors in GPU framerate.



The issue here is memory access. To fetch data from memory takes time, so the CPU's are therefore sometimes waiting for it.
That is why they are not fully loaded. Adding threads will not help in this regard.

Ill try disabling it.


Ah yes i remember you saying that before.
Could you explain in more detail? as it makes no sense just like before.

Are we talking CPU cashe here?
l2 cashe is core based, so each core has cashe to use.

On the threads, what im saying is out of the 4 threads the game is using 3 of them are doing almost nothing while 1 is doing allot.

W>hat is the catalyst version you use ? 15.7, 14.12 or a beta one ?