Please test this
#1
https://www.dropbox.com/s/wkqmb3rbkpq3yo...AA.7z?dl=0 for https://github.com/PCSX2/pcsx2/pull/982

PCSX2 with LargeAddressAware enabled by default(negates needing 4GB patch). They want more people to test it so please test it for me. I've already tested it for like 30 hours myself.

Just use it in place of your normal build for a bit should be good enough. It's only a couple of days old.

Thanks!
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply

Sponsored links

#2
OK, will do tonight
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#3
Any games you recommend testing it on?

Are we testing solely for stability or should we check FPS as well?

Anything we should look out for?
Reply
#4
Any game is fine.

Only looking for crashes.
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply
#5
Alright I'll throw something at it when I get home.
Reply
#6
Thanks. It's literally the most recent PCSX2 compiled with LAA so you don't have to go out of your way, just use it in place of whatever you were using before.
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply
#7
I've been using it for a few games now while testing and no crashes.

On another note: I haven't noticed any improved performance with this over the regular executable. Is there any game that really benefits from it?
Reply
#8
hm pcsx2 shouldn't be needing this.
usually it never takes up more than 2GB of ram unless there are memory leaks that blows up the memory heap due to unoptimized code

Main Rig: i7-3770k @4.5ghz | 16GB DDR3 | Nvidia GTX 980 TI | Win 10 X64
Laptop: MSI GT62VR | i7-6700HQ | 16GB DDR4 | Nvidia GTX 1060 | Win 10 X64

Reply
#9
(11-20-2015, 03:19 PM)Nexxxus Wrote: hm pcsx2 shouldn't be needing this.
usually it never takes up more than 2GB of ram unless there are memory leaks that blows up the memory heap due to unoptimized code

This is correct, however games such as the snowblind games, make thousands of small textures on the GS, but the size we specify for each texture is the "internal resolution", so even if the texture is a 10x10 texture, it gets allocated space for 1280x578 or whatever, this ramps up very very quickly.

it may be solved down the line, reducing the memory usage, but for now, it is a good temporary solution providing it doesn't cause problems.
[Image: ref-sig-anim.gif]

Reply
#10
(11-20-2015, 02:23 PM)FlatOut Wrote: I've been using it for a few games now while testing and no crashes.

On another note: I haven't noticed any improved performance with this over the regular executable. Is there any game that really benefits from it?

As ref says it's just the few games that use memory in insane ways. Snowblind games and a few others are the worst offenders.
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply




Users browsing this thread: 1 Guest(s)