Hires textures with Project64

[HatCat]

It has everything to do with an issue normally patched via an increase of addressing scope, because addressing doesn't exist without size.

And yeah the runtime error is totally something else.

[Smash58]

Wow, I am having this exact same problem!

I just recently saw something about running OOT with hi-res textures and I got excited. So I obtained the emulator, rom, community texture pack, 1964video and glide64 plugin.

Just as the OP states I receive a runtime error when I try and cache the textures to memory with both plugins. If I don't cache the game stutters due to the fact that its obviously trying to load the textures off my slow HDD.

I also have Windows 7 x64, I only have 4gb ram but it still should be enough.

I have not tried the Large Address Aware. I have no idea what that is even...

I read on another forum that a OP was able to fix the issue by loading the game first, then when the game has started to then open the plugins setting and select cache textures. I tried this but it only loads some of the textures and looks really messed up!

Can someone help us with this problem? Is this a compatibility issue with Windows 7 64-bit?


PS.

After monitoring my system resources the program crashes after loading exactly 1gb into memory every time.

[squall_leonhart]

Can someone help us with this problem? Is this a compatibility issue with Windows 7 64-bit?

no.

After monitoring my system resources the program crashes after loading exactly 1gb into memory every time.

you're looking at the wrong value. and have a bad understanding of the disk cache.

[Smash58]

Originally Posted by squall_leonhart

no.



you're looking at the wrong value. and have a bad understanding of the disk cache.

You have a bad understanding of how to communicate with other human beings.

I was stating a fact. The fact is that when the textures are loading my physical memory usage rises. When that value goes from 1.6gb ( my normal operating usage ) to 2.6gb, I receive the error message. That fact is not dependent on my understanding of the disk cache.

I was giving as much information as possible to troubleshoot the issue which you obviously have no interest helping with.


Caide, I was able to solve my issue using the LAA fix (I spent a very long time looking for it). I understand that you were already asked if you used the fix correctly, but considering how closely related our issue is, it is likely that you either didn't use the patch correctly or that the one you used did not work correctly.

code.google.com/p/glidehqplusglitch64/issues/detail?id=222



good luck...

[HatCat]

A wrong patch maybe, though with the runtime errors I'm predicting squall was right about as configuration issue for him.

[squall_leonhart]

I was stating a fact. The fact is that when the textures are loading my physical memory usage rises. When that value goes from 1.6gb ( my normal operating usage ) to 2.6gb, I receive the error message. That fact is not dependent on my understanding of the disk cache.

of course, because the application suddenly requests virtual memory above 2GB and windows will not allow that where the application is not large addressing aware.

Just as the OP states I receive a runtime error when I try and cache the textures to memory with both plugins. If I don't cache the game stutters due to the fact that its obviously trying to load the textures off my slow HDD.

the game always loads the cache into memory, whether disk caching is enabled or disabled, the only thing that effects memory usage is the compression nd 16bit options, however these introduce quality degradation.

You have a bad understanding of how to communicate with other human beings.

No I just choose to limit how much i interact with idiots who haven't RTFM.

[dsx_]

the manual should just be made to cover everything then there would be no need for these forums

[HatCat]

That would be one hell of a manual, but at least alongside the testing, cheats etc. forums we can have another forum where people ask questions then we direct them to a certain page number in the manual. =D