[GC] Star Wars Rogue Squadron III: Rebel Strike

[slarlac249]

i was using 61% underclock but i've gone up to 74%, seems after caching a bit more shaders the game is running a bit better.

ogl cache file is now 200mb.

just completed 4 missions and the speed was 80-100%


native res IR.

[slarlac249]

got the 2gb error again;



made it a point to check task manager this time and dolphin was using 2gb of ram.

then 10 of these popped up, one after another until dolphin crashed and quit.



and so on...each with different numbers.

so far it's happened on escape from bespin twice and once on attack the executor.

[Fiora]

Yes, if it fails to allocate executable memory in the right place it's a guaranteed crash (with messages like that) because the JIT wasn't built to handle it.

[slarlac249]

is it a common error?

i did a search and found threads about the same error dating back to 2011, i take it's one of those bugs that's hard to fix?

my system has plenty of ram, 16gb.

[Fiora]

JMC thinks it's caused by certain antiviruses and such that manipulate application memory in a way that makes Dolphin unable to allocate where it wants to, but I don't know any of the details myself, sorry.

[slarlac249]

i saw that mentioned in one of the threads i found. i however do not have any resident av apps loaded.

i also found this;

Quote:I've built the current master branch for x64 using visual studio 2012 on Windows 8, but unfortunately some problems remains.


To fix the locks errors the _WIN32_WINNT macro needs to be >= 0x0600 (Windows Vista or newer, see http://msdn.microsoft.com/en-us/library/windows/desktop/aa383745.aspx for values);
I've also added the include to OpenALStream.cpp (mem_fun not found) and disabled portaudio (ksguid.lib not found).

Unfortunately, "VirtualAlloc" returns a pointer with a very high address (here the "Executable memory ended up above 2GB!" error); this can be fixed using the "/LARGEADDRESSAWARE:NO" linker option, but still some pointers are >2GB and it will lead to the "BackPatch : Currently only supporting reads." errors during emulation.

Also, the current x64 vs2010 build has the LARGEADDRESSAWARE option enabled, so I don't know if it's caused by a different behavior in the Windows SDK for Windows 8 or a misconfiguration in the project.

*** UPDATE ***
The problem seems related to the address space layout randomization enabled for Windows Vista and newer.
It needs to be disabled with the "/DYNAMICBASE:NO" linker option, while LARGEADDRESSAWARE needs to be left enabled.

All working fine now

not going to pretend to understand any of that but the last bit sounds like the user found a fix?

i have manged to reproduce the error 5 times now, always when there's a couple of ties left in the flying portion of the mission the error happens. the on foot part plays perfectly with no errors, just the flying part that crashes.

[Fiora]

I thought LARGEADDRESSAWARE only applies to 32-bit builds?

[slarlac249]

is ram usage supposed to be high with this game? because it's using 1.8gb when you first boot it to the menu, then at some point it hits 2gb and that's when it crashes.

rs2 uses 640mb when it boots to the menu.


thought i'd try the latest builds instead of the hle hacky build and the memory usage is much lower, still went up to 800mb but not 1.8gb, could the hle hack be causing the high memory usage?

[slarlac249]

seems the bigger the shader cache file the higher the ram usage dolphin has on booting. deleted the cache file and now it boots at 500mb.

argh it crashed again with the 2gb error but this time it was on the foot section and dolphin was only using 612mb.


yeahhhhh, finally completed the mission with no crashes! i have a feeling the disabling idle skip tip was the cause as i tried with it back on and no crash.

[IceStrike256]

Interesting I need to invest more time in to test RS3 need just been playing 2.