..:: PCSX2 Forums ::..

[deleted]

already discussed
http://forums.pcsx2.net/Thread-SSE4-X-OR-AVX

(05-30-2012, 06:05 AM)tallbender Wrote: [ -> ]already discussed
http://forums.pcsx2.net/Thread-SSE4-X-OR-AVX

3 post is not what i call discussed.

@op a real benchmark would be to take the source code and implement a routine to measure the frame times precisely. and cheat or somehow setup a scene in the game where the content is constant. means a good ingame sequence. also start and end are supposed to match for both tests.

there you go. try that.

[deleted]

You need to use a FPS measurement tool that averages the numbers more, try FRAPS for that.
Then you'll want to check several scenes, that all seem to stress different parts in GSdx.
Make sure you choose scenes that go slow enough (below 100fps) and that show a high use percentage in the GS window title bar.

[deleted]

[deleted]

[deleted]

Changing plugins on the fly, as the warning dialog says, has a high chance of instability. I don't think that that can be helped.

(05-30-2012, 12:09 PM)Bositman Wrote: [ -> ]Changing plugins on the fly, as the warning dialog says, has a high chance of instability. I don't think that that can be helped.

Do you think it would be possible to write in code to PCSX2 to auto restart if the plugin was changed or would that be a big headache?