Huh. Sometimes, the code can change. Because each texture you extract can slightly differ from one that looks exactly the same, which produce different codes. And you'll need every code you get pertaining to that texture. But what textures are you working on exactly? Is it still the world map? And it's okay. I'm pretty poor when it comes to explaining things because I can be pretty dense at times.
I assume you already have the steam overlay disabled and such. Also, what version of Tonberry are you using? As for the random crashes on those moves... I've never had it happen using Defend or Lion Heart. I've had it rarely happen with Angelo Cannon, though. And I have a pretty big chance of it happening if a dang Grendel uses Breath.
But I'm not exactly sure what causes it.Yeah, I figured there might be a problem with him in the future... he is one of the few enemies that has an 'animation'. If it captured Rinoa and Tonberry, it's probably not an issue with Lunar Cry, but from FatedCourage's Character Texture mod colliding with Lunar Cry. The next version of Tonberry will have fixed these issues.
You can provide the works? Thank you very muchHi
What do you thing about this screens of battle backgrounds? please tell me which could improve
In movement is better
maybe I create a new thread to not mess this
If you're referring to character texture replacement... That's on a different thread, now. As for everyone else, I can't speak for them. We all have personal lives, so they're probably busy with that.
Tonberry is at a pretty stable state right now with all requested features implemented, no known bugs, and is running as efficiently as possible (as far as I can tell). I don't have much else to work on
Tonberry does work great. I have managed to solve almost all of the glitches on my end. Except for the codes that are literally shared. Like a Zell code being the same as a spacesuit, a few world map objects, and a special one with the Squall student uniform and the square soft logo in the beginning. You'll only see it if you reset the game at times.Tonberry is at a pretty stable state right now with all requested features implemented, no known bugs, and is running as efficiently as possible (as far as I can tell). I don't have much else to work on
The new hashing method along with selective object replacement (i.e. if it finds a match for an object but not the whole texture then it replaces the object and simply upscales the rest of the texture to 1024x1024 without changing it) is 80-90% complete but, truth be told, it doesn't seem like there's all that much modding demand for it. FatedCourage has done an excellent job wrestling with the character collisions and the other mods (read: Mcindus') work almost flawlessly. The glitches are minor at worst. Besides disappearing characters and the occasional background collision, none of the current mods will be much improved by the new hashing algorithm, and in fact Tonberry will necessarily be a bit slower.
The new hashing method would open up a lot of possibilities for new mods (e.g. animated textures), but until modders start probing in that direction (and I get a whole lot more textures to finalize the hashing coordinates) I have to say I don't feel the same urgency as I did with the current version of Tonberry.
I think the only really relevant thing for you would be blinking eyes (which is, inconveniently, one of the most troublesome parts of the new hashing algorithm). The shared codes problem would be solved off course but as you say, it doesn't appear to by that big of an issue.
Yes, please. All textures help. In a perfect world I would have every texture in the game and then I could make the algorithm optimal, perhaps even eliminating all collisions besides the few basically-impossible ones like all-black-except-for-a-few-dots, e.g. the twinkling stars.