-
Notifications
You must be signed in to change notification settings - Fork 48
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
Tile loading issues #176
Comments
UPDATE: This is definitely caused by the motion prediction. Turning it off fixes the issue. Which really sucks cause otherwise it works really well |
This actually seems to be related to perspective mode for me. Turning off perspective mode fixed the issue. |
Definitely not perspective mode. If anything, turning it off made it even more noticeable |
Hey, for me the artifacts around the edges of the screen and open inventory/stats panel are acceptable. I'm talking about the "garbage" that appears at the edges of the screen when moving rapidly. (These artifacts most likely would be hard to fix as you'd need D2DX to render more cells than needed around the screen in order for the prediction to have data to work with thus preventing them) Now about the black tiles issue... I'm not able to get tiles to look as jarring as in the picture from VKatillis though. The most visible artifacts I'm able to reproduce are these : Using freshly compiled D2DX from the original repo with these settings :
|
The “garbage” you’re talking about is the same issue. |
@VKatilis can you test this version with updated external SGD2FreeRes ? I see less culling issues with it. |
@eleriaqueen It works fine with 1.09d, but MapHack for 1.09d don't recognise version of Diablo II with that glide3x.dll. With 0.99.529 MapHack works fine. |
@Vahsify weird... are you sure it's MapHack's error message you're seing ? |
@eleriaqueen Yes. Error "Unknown game version" if I click "Install/update" and nothing more. But with Bolrog's 0.99.529 (and other versions) MapHack works fine. |
@Vahsify I enabled issues tracker and added one with the problem you've described |
Just launched with this - it does seem less noticeable, but it is still there unfortunately |
"Extended the tile culling even more, to lessen the tile culling problem in D2DX with motion prediction enabled. Is not guaranteed to fully fix the tile culling problem." https://github.com/mir-diablo-ii-tools/SlashGaming-Diablo-II-Free-Resolution/releases |
You can try my build which is similar to @eleriaqueen build but with the latest SGD2FreeRes update. |
Noticed that (mostly in act II and Act V) you would have blacked out tiles near the screen edge (or as discovered recently, elements of the interface see image), no matter what the resolution is. Happens when moving towards the respective edge. Much worse in motion as those triangles flicker across the edges. Not sure whether it is motion prediction or D2 multi red causing it
The text was updated successfully, but these errors were encountered: