Quote: "There is a bug with changing Sprite U/V coordinates. If you load an image anywhere in your program it will reset all sprite u/v coordinates you have setup. This is important because if you load all of your sprite animations from a single image for speed (which is an industry standard) you then have to create sprites and manually setup which parts of the image that sprite will use (the U/V coordinates). So if you setup all these sprites, then go to load an image at some point all that stuff gets reset. It basically means using customer sprite u/v coordinates is broken and unusable in DBPro. I don't know how this was overlooked. Look at how many people used this over the years and nobody complained."
While Virtual Texture _might_ be an Industry Standard today... in 2002 - 2007., it was an uncommon practise to say the least.
Now I'd have to dig into the DBP Source to see why it resets the UV for all Sprites when you Load an Image., but it could be that DBP itself isn't actually storing said information., meaning said "bug" is with DirectX 9 itself.
This wouldn't surprise me, as keep in mind that things such-as associated Draw States are handled by the Graphics Drivers not the API.
What I mean is... are you sure the behaviour is universal to all Hardware and not just, say NVIDIA or ATI?
You will find there are a lot of behaviours in DBP that are Vendor Specific; and this is because quite a fair amount of the "Dark Engine" was just being a DirectX 9 API Wrapper., with minor streamlining to work how you'd expect for a BASIC Language.
Still even IF it's a universal behaviour, you also have to keep in mind that again at the time things were moving to pure Shader Pipelines... and well each Shader has its own State Object that is Zeroed by Default.
Don't get me wrong here, I agree it isn't working as you expect thus a bug., but it could also be DirectX 9 working "as-intended", so using these things in this way; because it wasn't a common practise then, could easily have been an oversight to not write a work around for.
If you have some Sample Code that showcases the issue; that would be useful to track down the issue.