Hi everyone!
I bought Drastic way back, and I've had a great time using it across multiple devices. It's worked like a charm on each one, especially my galaxy s6.
However, I recently got an Amazon Fire 7" tablet. Games run fine on it(tested Mega Man ZX and Dragon Quest IX so far), but for some reason, the bottom screen doesn't display at all.
Attached is an image of how it looks when the game is running, where no bottom image is displayed.
And here is an image of how it looks when the game is paused, with the bottom image working normally.
Any idea how to fix this?
Bottom screen not displaying
- Kyousuke753
- Posts: 846
- Joined: Sun Apr 10, 2016 10:30 am
- Location: ???
Re: Bottom screen not displaying
Are you using the latest Drastic version r2.4.0.2a?
Beta version is 2.5.0.0 ATM which I'm posting from this screenshot and I can run this game with Multi-threaded 3D Rendering turned on with no issues and the 2nd screen shows normally.
Or simply you got a bad ROM patch...I can't provide you with that or I'll receive an instant ban resulting in the deletion of my account and a good Google search should yield good results.
Also before you run Drastic close all other apps running in the background and lastly post on the link below so the developers can look into it please
http://www.drastic-ds.com/viewtopic.php?f=7&t=461

Beta version is 2.5.0.0 ATM which I'm posting from this screenshot and I can run this game with Multi-threaded 3D Rendering turned on with no issues and the 2nd screen shows normally.
Or simply you got a bad ROM patch...I can't provide you with that or I'll receive an instant ban resulting in the deletion of my account and a good Google search should yield good results.
Also before you run Drastic close all other apps running in the background and lastly post on the link below so the developers can look into it please
http://www.drastic-ds.com/viewtopic.php?f=7&t=461


Re: Bottom screen not displaying
What filter option are you using, if any? Try using different filter modes, there was an issue where certain drivers interacted badly with some shaders causing something like this. Could also try the latest beta.