I used to have a Juke, and I'll be damned if it wasn't the hardiest phone I ever saw. It was submerged in about 5 feet of water for at least a few minutes, and all I had to do was dry it out and pop in a new battery. It was going strong for at least a year after that happened. It should still work, actually, but I don't use it now, cuz I got a Droid Incredible.

Mine is a picture of Adol Christin, also known as Adol the Red, hero of the Ys series.

A wild necropost appeared!

Please look at the date of the last post. In this case, it was in December of last year.

Due to some issues I've been having with my TI-84+ SE, and zeldaking saying that they are similiar to the issues he had before his calc went crazy, I no longer feel assured of it's stability.

As such, I don't feel comfortable using my 84+ SE for developing Nostalgia or Pokemon, in case something prevents me from backing up my progress. I will set up my 83+ to use for developing Nostalgia, but I'm not sure at what pace I can use it to develop, as last I tried to compile an app with my 83+ using Axe, it wouldn't work. Keep in mind though, that was when app compiling was a brand new feature, and I have not tried it on a more recent version.

In order to assure my 83+'s stability, I will be using Axe 0.5.3, until a stable 1.0.x build is made. Pokemon will be kept on hold, as the 83+ has issues with 4lvl grey rendering sometimes, and that I cannot use Full on an 83+, so I cannot judge timing as it would be in 15 mHz.

As soon as I get my hands on a stable 15 mHz calc, or I can assure myself of my TI-84+ SE's stability once more, progress will continue with that.

Until that time, Nostalgia will be developed on my 83+, and I will work on the Axe GUI library on my 84+ SE, as it isn't world-ending if I cannot back up and update to the GUI library.

I'm also having some issues, though not as serious as p2 or zeldaking.

I'm not sure if the culprit is Axe 1.0.2 or zStart 1.2.013, as when zStart was the only thing installed on my calc after a ROM clear and fresh OS installation, the run on RAM clear feature worked perfectly. I then proceeded to send my other apps back, though Axe was the only one I installed. I wrote a simple program, just drew a few rectangles, inverted some text, and XOR'd a sprite, compiled and ran it. No issues. Then, when I RAM cleared, zStart did not kick in, and I've had some interesting issues when I tried to uninstall and reinstall the run on RAM clear feature, such as a ERR: MEMORY when I went to the memory clear menu, or my contrast value being 104. If run on RAM clear is not installed, I have no issues.

I'm also going to post this in the zStart topic, as I don't know which app is at fault.

Quote from: FinaleTI on August 02, 2011, 07:18:00 pm

I'm thinking maybe I should write a tutorial on using 4 lvl greyscale with xLib/Celtic III/DCS7 in BASIC. Nitacku's renderer sets up the graphics well enough, but it took me a lot of time and effort to get a good looking fullscreen 4 lvl tilemapper in Hybrid BASIC.

I'm just wondering if enough people still use these libs to make writing the tutorial worth it.

I still use Celtic III, if that counts lol.

Great. If it helps even 1 person, I'm happy. I'm probably gonna cover a little more on my OS Vars Axe tutorial before I write the Hybrid BASIC one, though.

Now that I think about it, I can think of a bunch of odd things I've done with BASIC I'm tempted to make tutorials, or at least code explanations on. Things such as my homescreen scrolling tilemapper using a pic for mapdata.

Picture data is stored in consecutive bytes, like any free RAM, such as L6 or L3 in Axe. In order to access the individual pixels, you'll need to read the bits in each byte.