Stainy
Advanced Member
heheheOh! That's funny! So it's the sand that I'm stuck in and not the emulator stuck on me! Thanks for the hint.
heheheOh! That's funny! So it's the sand that I'm stuck in and not the emulator stuck on me! Thanks for the hint.
what do you mean exactly by "too much" ?I'll try this, and while I think about it, I noticed the screen sometimes move "too much", when playing Picross with the previous version.
The DS screen is even worse than the Pandora's one?Love it, I always get old complaints only right after I release something.
Sometimes games jitter the contents of the screen for a temporal anti-aliasing effect, there isn't an awful lot that can be done about it on displays that have better response times than DS's.
I'm not totally sure, but I really doubt that the shaking graphics in Picross 3D is an emulator bug rather than intentional (it happens in DeSmuME too). From a quick look on my DS Lite I couldn't see any shaking, but the graphics also looked smoother. DS does have edge anti-aliasing that neither emulator implements (couldn't tell if it was enabled here), but that wouldn't explain the textures also looking smoother. DeSmuME developer zeromus looked into it and concurs that it's deliberately done by changing the texture transform matrix:The DS screen is even worse than the Pandora's one?
notaz was experimenting with moving some of the 3D rendering to the DSP. I gave him an integer-only version with optimized Newton-Raphson divisions (DSP is super bad at normal divisions and floating point in general) and worked to move critical structures to its embedded fast SRAM. Despite this, it was still much slower than the normal NEON version (like 4x slower, also about the same speed as the C version), so it really only accelerates things a little if you have it render a small part of the screen while the CPU renders the rest. If the rendering is allowed to start really early it accelerates things a little more by having the DSP render part of the screen while the non-rendering emulation happens. But this causes big graphical problems in various games.Have you had any thought of using DSP capability for anything on DraStic?
I doubt it's not deliberate. It's not a rounding error, they're changing the texture transformation matrix which causes the sub-texel offsets of the textures to wiggle slightly. I couldn't see jitter on a DS Lite, although I only went into the tutorial. What sort of DS are you using?Picross 3D does jitter on a real DS - it's not an antialising attempt as far as I can tell, but some weird rounding error type thing I suspect.
Yes, but will I do it? Probably not.Exophase, would it be possible to have the rendered image filtered by the dsp to avoid sharp edges or upscale it nicer?
No problem, you didn't sound demanding at all. I'm just spread kind of thin with stuff to do on this. I do want to do some Pandora-specific work like USB gamepads, configurable controls, and maybe some screen stuff. Using the DSP is just not high on the list, unless notaz wants to mess around with it.Sorry I did not want to sound demanding. Thank you for your hard work on Drastic and for the free Pandora version of it .
For the Pyra version Lordus and I are interested in putting in a GLES path for shaders and positioning and stuff. Not really looking to do that sort of thing on Pandora because the overhead is too much for something that needs all the CPU time it can get, but on Pyra it should be better.You know, I would not mind paying for a PYRA DraStic version with all the bells and whistles. I bought an Android version but due to physical controls on the Pandora, I tend to use the Pandora version much more.