|
Post by frostedflakes on Jun 13, 2006 5:58:31 GMT 1
Sorry, this has probably already been covered somewhere, but I did a search for the error and came up with nothing, so. Am using LJP 1.0 pre RC3 on a Tungsten E2. Rom is installed to the appropriate directory on a 256MB SD card. When I try to launch it in LJP, though, I get the following error: MemoryMgr.c, Line:3732, NULL handle I am using UDMH and have plenty of memory available, ~15,000k according to LJP. What could be causing the error? Please help a PalmOS / LJP newbie out, would really like to get some of my favorite SNES RPGs running on my Palm.
|
|
|
|
Post by frostedflakes on Jun 13, 2006 20:21:00 GMT 1
Max chunk is 16.8MB. Will try 1.0 RC2 and see what that does. And thanks for the welcome.
|
|
|
Post by frostedflakes on Jun 14, 2006 6:52:47 GMT 1
1.0 RC2 seemed to do the trick, but it still doesn't want to run very well. I'll random errors every now and then, and when it does work, I get very low FPS (30-ish) unless I disable sound. Guess my weak ol' T|E2 can't handle SNES emulation?
|
|
|
Post by _Em on Jun 14, 2006 18:39:51 GMT 1
That's correct... you'll at least need a clocking app like WarpSpeed to increase the number of instructions it can crunch per second. Even at 520MHz, SNES audio is a little choppy on my TX. Also, Tinnus posted instructions on here somewhere for the optimal RC2 settings for SNES. I can't remember offhand what they were, but you'll want screen scaling at 1x, audio off, frameskip at around 4, and a number of special hacks turned on (like fast sprites).
|
|
|
Post by Tinnus on Jun 15, 2006 1:13:01 GMT 1
Hacks #1 and #4 are usually nearly harmless Frameskip 4 is too much IMO. Graphics on Fast, Fast Sprites ON and Transparency OFF. Audio off of course. And overclock to 180 MHz.
|
|
|
Post by frostedflakes on Jun 15, 2006 4:24:25 GMT 1
I actually messed around some with PXAClocker, but didn't have much luck. It seems like even the smallest overclocks aren't stable, as I'll get errors in LJP where I wouldn't at stock speeds. Might try another overclocking app and see if it works better, though. I'll also look around for the RC2 optimization guide. But with audio off it runs pretty well, ~60FPS average, so I'll probably end up just calling it good. Thanks for all the help everyone.
|
|
|
Post by Tinnus on Jun 16, 2006 23:18:56 GMT 1
Ah sorry you mean E2. I read E Forget the overclock to 180 thing. Just overclock as high as you can without losing stability.
|
|