quick question about the saints patch

  • Thread starter Thread starter Jaitsu
  • Start date Start date
Status
Not open for further replies.
J

Jaitsu

Guest
aright, two quick questions actually, sorry if this belongs in game tweaking, its hard to tell with this

ok, so on my old laptop, i tried installing the saints patch and it turns out my computer couldn't handle the resolution, im not a computer wiz (ima computa failure TT.TT) so how do i find out if the saints patch will run with my current laptop?

also, does it work with NPC reconstruction v 0.6? (not pheonix, i don't plan on using that just yet)

if you know the answers, thanks in advance, if not, thanks anyway

PEACE
 
Answer to question 1: Don't use the saint's patch. Use Aali's driver instead, if you want high resolution graphics. It'll support any resolution you throw at it, and it's a lot less glitchy.
 
Answer to question 1: Don't use the saint's patch. Use Aali's driver instead, if you want high resolution graphics. It'll support any resolution you throw at it, and it's a lot less glitchy.
Click to expand...
i've been having trouble with Aali's driver lately, i think its what caused me to crash at the temple of ancients & it seems that battles are slightly glitchy when i use it
 
Please provide a copy of app.log and crash.dmp in the custom driver thread and I will see what I can do about that crash.
 
Please provide a copy of app.log and crash.dmp in the custom driver thread and I will see what I can do about that crash.
Click to expand...
alright, i'll do so tomorrow, not saying it "is" the driver, it just appears to be, as i was able to get passed that point in the game when i stopped using the driver
 
It's quite likely to be the driver, seeing as it has just gotten some new features that could very well mess with a lot of sequences I haven't been able to test yet.

There's also a known crash issue in the latest version on top of that. So far it has only happened in battle but who knows? Could be the same thing. Your app.log and crash.dmp should make it clear whats causing it though.
 
Last edited:
It's quite likely to be the driver, seeing as it has just gotten some new features that could very well mess with a lot of sequences I haven't been able to test yet.

There's also a known crash issue in the latest version on top of that. So far it has only happened in battle but who knows? Could be the same thing. Your app.log and crash.dmp should make it clear whats causing it though.
Click to expand...

uhh... hehe  :lol: where exactly do i get thoughs files again?
 
Status
Not open for further replies.
Back
Top