-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
graphical issues when moving camera position during character movement #551
Comments
"Merc Lights during Movement" is known to cause a lot of trouble. This problem is known to v1.13, too. I don't think, they came up with a better solution than deactivating this option. |
I think, this is solvable -- mostly by getting rid of unnecessary surfaces for rendering. Fun experiment: |
I was considering creating another issue, but it's probably the same underlying cause so I'll post it here. After entering cheat mode (CTRL+GABBI) and enabling the display of FPS (CTRL+F), you will see traces of the text while you scroll around. This resembles what you show in the second video. It gets "fixed" by itself when I stop scrolling. Not sure of the internals, but it feels like it should be marking tiles/sections as dirty (to fully redraw them) but doesn't. I tried looking at the tile engine and though "here be dragons"... Issue #738 mentions "Replace all/most blit code with SDL function calls and load resources as SDL textures". This issue might get fixed when that is implemented. |
So, is anything left to do here, besides potential optimizations? |
I'm getting heavy graphical artefacts when I'm moving the camera, while a character is moving on the screen. It gets a lot worse, if "Merc Lights during Movement" is enabled. If it is disabled, the Mercenary is simply not visible until he has reached his destination
Attached are two videos, because it is hard to explain and it was too difficult to create it as gif. The first video shows how it is without the option enabled and the second one with it enabled.
JA2 Debug.zip
The text was updated successfully, but these errors were encountered: