..:: PCSX2 Forums ::..

 [Bug Report] Final Fantasy Final Fantasy XII International Zodiac Job System

# PCSX2 version:

pcsx2-v1.3.1-1416-gb6f78d8-windows-x86 and all builds above up to pcsx2-v1.3.1-1480-g59dc0e8-windows-x86

pcsx2-v1.3.1-1415-g9bb990e-windows-x86 and some builds below it


# CPU options: EE/IOP defaults, VUs defaults

# Plugins used: GSdx32-AVX2 on all the builds all on software direct3d11

# Description: Massive slowdown on the "License board" on builds pcsx2-v1.3.1-1416-gb6f78d8-windows-x86 and above it up to pcsx2-v1.3.1-1480-g59dc0e8-windows-x86 (latest today) when you have all 6 playable characters, everything below these builds work fine. Attached below are the snaps of the game
pcsx2-v1.3.1-1415-g9bb990e-windows-x86


pcsx2-v1.3.1-1416-gb6f78d8-windows-x86


pcsx2-v1.3.1-1480-g59dc0e8-windows-x86

looks like the GS% takes a hit.
what are your specs ?

Your cpu is not by chance a skylake one?
This would make dr_hycodan really happy.

(11-25-2015, 03:29 PM)jesalvein Wrote: [ -> ]looks like the GS% takes a hit.
what are your specs ?

(11-25-2015, 05:01 PM)willkuer Wrote: [ -> ]Your cpu is not by chance a skylake one?
This would make dr_hycodan really happy.

yes its skylake i7

Ok. Then skylake is the winner. The switch to vs2015 seems to dramatically reduce performance on skylake cpus using mutlithreading.

This should be pushed to github.
I guess none of the devs has a skylake and therefore i guess a valid fix could be reverting to vs2013.

Can you please confirm that single threaded performance is similar (e.g. put extra rendering threads to 0) between these versions and that increasing extra rendering threads dont create benefits on newer builds?

I'd still like more testing, but yeah, it's not looking good

Possibly the kind of threading gsdx uses is already known to have problems with skylake. But if the dev's can not test their results I guess it is hard for them to fix it properly.

Has this been pushed to github yet? If not I will do it and call for more skylake testing.

no it hasn't. the problem with reverting seems to be because of VS2015 being the first VS to support C++11 core features

Well there has got to be some way around it without going back. If Microsoft's new visual studio has unavoidable issues with Intel's new chips... that won't make for a very happy PC community.

https://github.com/PCSX2/pcsx2/issues/998