Looks amazing seeing it all together like that. And yeah its nice to see that mostly everyone is still around, sucks I don't have the the endless free time I did when I started because I was laid off at the time. I really, really miss that LOL... spending an entire day playing Xenoblade, working on a map or something else. Now I get home I'm usually too tired to do anything productive, but I still try to work on something when I can. I've been playing Pandora's Tower recently so that's also been eating up some of my time, decent game so far. As many times as I played through Xenoblade, I only ever had one "full" playthrough myself where I did everything imaginable. I still want to do at least one more playthrough like that eventually. I kind of been waiting for a point where I'm satisfied enough with this pack that I won't find something along the way and say "that really needs retextured", so it may be awhile.
I gave the gloves a whirl, used the metal piece from your texture with some touchups. It's mostly just a lot of gaussian blur with some air brush touch-ups and and a redrawn finger border. Texture itself isn't great, but looks good in game as always.
Loading a save state should not reload all the textures, at least in the sense it freezes up your system again. You should only experience lag with save states when "Dump Textures" is checked as it will dump any textures that are not already dumped. While working on the maps I often used save states to quickly load new textures that were already loaded. For example, SX4E01_392cc970_2.png (Eryth Sea map), I could make a quick change in GIMP, then copy the file to the Dolphin texture load folder, load the save state, and since the file was already loaded I could see the changes instantly. This was with a 5400 RPM WD Green that was loaded to the brim with junk, so the lag you are seeing with save states may stem from something else.
As for using save states with the last 32-bit version of Dolphin Ishiiruka... forget about it. Save states are not stable in this version at all. When the texmod trick was discovered, I switched to this version for awhile to dump and test new textures. Since I use the trick I mentioned above often, it wasn't long before I became extremely frustrated seeing an error message almost every time when trying to load a state. This version is also MUCH slower than the official development builds (especially since it's a 32-bit version), so you need a strong PC to get full speed.
Also, I'm really surprised you get better speed with 4.0-96 over the latest versions, especially with all the recent JIT optimizations by Fiora. I remember reading in the September progress report that Xenoblade should have seen at least like a 40% speed increase over previous Dolphin versions, which is a pretty significant number.
I gave the gloves a whirl, used the metal piece from your texture with some touchups. It's mostly just a lot of gaussian blur with some air brush touch-ups and and a redrawn finger border. Texture itself isn't great, but looks good in game as always.
Spoiler:
(12-07-2014, 10:55 PM)Nickthen Wrote: Hey, I've just got a quick query about how I can use this pack.
The only dolphin version which works well without lag on my system is the 3.0-96 dirty version, as it obviously wouldn't work with texmod I originally set it up with the version that has 10,000's of textures, this took about a minute or longer to open as I don't have any SSD's, while this wait was fine I like to use savestates and whenever I use savestates it unfortunately freezes for at least another minute which can get to be too much.
As a result of this, I switched to texmod and downloaded the final dx9 version, set that up and tried again, with this version the waiting time is fine for savestates and such but I now receive significant lag, I tweaked the settings to minimise the lag as much as possible while still allowing the game to look ok, I still receive lag during certain parts of battles where I drop from 30FPS to 20-25 which is rather annoying. This version of dolphin is also causing me issues such as crashing sometimes when I use savestates as well.
I'm not sure if you'll have a solution for my problem but I thought it would be worth asking to see what your thoughts are, let me know if you want further information.
Loading a save state should not reload all the textures, at least in the sense it freezes up your system again. You should only experience lag with save states when "Dump Textures" is checked as it will dump any textures that are not already dumped. While working on the maps I often used save states to quickly load new textures that were already loaded. For example, SX4E01_392cc970_2.png (Eryth Sea map), I could make a quick change in GIMP, then copy the file to the Dolphin texture load folder, load the save state, and since the file was already loaded I could see the changes instantly. This was with a 5400 RPM WD Green that was loaded to the brim with junk, so the lag you are seeing with save states may stem from something else.
As for using save states with the last 32-bit version of Dolphin Ishiiruka... forget about it. Save states are not stable in this version at all. When the texmod trick was discovered, I switched to this version for awhile to dump and test new textures. Since I use the trick I mentioned above often, it wasn't long before I became extremely frustrated seeing an error message almost every time when trying to load a state. This version is also MUCH slower than the official development builds (especially since it's a 32-bit version), so you need a strong PC to get full speed.
Also, I'm really surprised you get better speed with 4.0-96 over the latest versions, especially with all the recent JIT optimizations by Fiora. I remember reading in the September progress report that Xenoblade should have seen at least like a 40% speed increase over previous Dolphin versions, which is a pretty significant number.