Hires textures with Project64

[Caide]

I'm running Windows 7 64 bit, and the game I'm using the hires textures for is Zelda: OoT if it matters.

The only plugin I can get these to work in is the latest rice video, but that plugin is often crashing project 64 (program not responding) and it's an auto crash if I try to alt tab or anything like that, so I've been trying other plugins.

With 1964video (r35), I can get the textures to load, but it's unstable as well.

Most of my efforts have been with Glide64 which would just give me microsoft c++ runtime errors when loading them at the start, and when trying to enable textures while in-game the program would either stop responding at some point during texture loading, or it'd get to a certain point (not the end), and just stop. I could click 'ok' at this point, but it'd just go back to the game, and the textures didn't appear to be loaded.

I attempted to fix this by making it Large Address Aware, however this didn't seem to help. Loading it at the start, it'd get pretty close to finish (3000s), but then give me the same runtime error as before. If I loaded the textures during the game, the program would stop responding at about 100 textures in. Though, after that happened a couple of times, it'd keep loading until some random point (it varied each time I tried), and then the program would stop responding as usual. This was all attempted with a bunch of different settings enabled/disabled etc. after reading through a bunch of different threads on the topic.

I've been trying to get this to work for hours, so if anyone has any suggestions, I'd love to hear it!

Also, I have both Zelda: OoT V1.0 [u] and V1.2 [u]. The differences seemed minor, but does anyone recommend using one or the other?

[Natch]

Did you try searching for your problem?

[Caide]

Yes, I did.

[Natch]

Well then, I got nothing. Just sit tight until my supervisor makes his shift.

[HatCat]

There isn't a difference with concern for compatibility between the V1.0 and V1.2 releases of the game. Some sentences were changed, Fire Temple music changed, mirror shield texture, stuff like that. Nothing that will affect your issue.

I haven't tested Large Address Aware, so I have no criteria for judging if you're using it right. If memory can't be changed to allow more textures, then loading less textures must be done. In the tab for texture enhancements for RiceVideo there is a checkbox for loading only smaller texture files, or you can just delete texture folders until not so many are installed so that LAA isn't required.

Is it the community retexture you are trying to load?

[Caide]

Originally Posted by Iconoclast

There isn't a difference with concern for compatibility between the V1.0 and V1.2 releases of the game. Some sentences were changed, Fire Temple music changed, mirror shield texture, stuff like that. Nothing that will affect your issue.

I haven't tested Large Address Aware, so I have no criteria for judging if you're using it right. If memory can't be changed to allow more textures, then loading less textures must be done. In the tab for texture enhancements for RiceVideo there is a checkbox for loading only smaller texture files, or you can just delete texture folders until not so many are installed so that LAA isn't required.

Is it the community retexture you are trying to load?

Large Address Aware is basically just Step 1: choose .exe file, Step 2: patch, so I don't think it can really be used wrong

I've considered doing that, but ideally I'd like to use them all, so for now it's a last resort. And yea, it's the community pack at n64redux.

[squall_leonhart]

how much ram do you have, and are you using x64?

[Caide]

Originally Posted by squall_leonhart

how much ram do you have, and are you using x64?

Windows 7 64 bit, yea. I have 8 gigs.

[HatCat]

Deleting textures for scenes in the game you're unlikely to visit should still help.

Also, that is one big project. You might even prefer some of the smaller ones with texture designs that aren't so damned big, but the LAA patch should still have worked anyway if you want to use the community pak, which again is big. I was satisfied with smaller ones though.