Mystler wrote:Ainia wrote:Plus, I find the notable lack of interest by the shard admins in helping to solve this problem most distressing.
I find it most distressing that one person in a hundred has a problem and always expects a developer to instantly provide the correct solution.
Who says that we're not interested? I answered several times now, trying to help you, so let me make this clear:
I have absolutely NO idea why it's not working for you!
Shorah again Mystler,
Well, all I can say here is that I find your response saddening. You are interpreting my distress as a demand for immediate answers, which could not be farther from the case. it's been quite clear that nobody has answers to this, so I have been asking for information. If I'm to test this, I must start with ruling out the obvious candidates, which in this case means the August TOC updates. Put another way, my other shard installs still work fine (both Wineskin and Cider wrapper versions), which means the obvious first candidate for me to test is the TOC shard updates rather than my local computer settings.
Perhaps I am misinterpreting your responses as a whole. But overall, they have implied that these symptoms are of little to no concern because this is an isolated case and the issue simply cannot be connected with the recent TOC MOUL updates; which *is* distressing to me. Such disinterest implies a belief that a corner-case is irrelevant and that no bugs were introduced in the latest updates; which, if true, is somewhat naive. At least, that's the reality my colleagues and I live with in RL.
In terms of the git list of fixes,
this one reads as the best contender for a possible cause, since it was intended to fix a similarly-described Windows display problem. Of course, it would be helpful if I could see an example of this bug in action since I'm only assuming it looks similar to the symptoms I'm seeing, but I realize that's probably not possible. (It's described as "weird flickering" which could describe all sorts of visual behaviors.) However, the changes implemented don't provide me with much in the way of clues about what to change in the Wineskin settings to compensate and test.
In the meanwhile, I have discovered and tested a workaround. Since it involves changing and reverting game settings each time I start TOC MOUL, it's really not a fix, but at least it works. It requires a toggle to the MOUL Vertical Sync setting. I've tested this particular fix dozens of times and so am confident it is a "stable" workaround. There is a gotcha involved with it, though: if the Vertical Sync setting is left toggled on, the next TOC MOUL session will take about *1/2 hour* to load fully (get me to Relto). So it works best to toggle it on and then off again right away. The window blinds effect will be removed for the current session but will return at the start of the next session no matter which state the Vertical Sync is left in at session's end.
Also, I've observed some possible clues about root cause of the window blinds effects in that using screen casting software to capture the behavior at first caught only a strange artifact of the behavior (occasional flashes of black screen) rather than the window blinds behavior itself; and later when using screen casting software to document further testing, the act of recording the screen "cured" the bug; as soon as I stopped recording the screen, the "bug" returned. I wound up using my videocamera to record the behavior earlier today so I could have a reference for the future (or to provide to others who might be interested).
The best I can surmise from this so far is the screen casting software forces a particular setting to correct but then reverts that setting whenever the screencast is stopped.
I still have been unable to get a fresh TOC MOUL install to work and so have been focusing on working with my "old" install instead. My next steps will be to create several backup copies of my working TOC MOUL install, ensure they work, and then test some more of the Wineskin settings related to display. Sadly, all my late July-early August backups were long overwritten by the time I discovered this issue, so I won't be able to do a real compare between my older working install and this one.
At some future point, I will troubleshoot the issues with getting a new install to work. I'd been hoping that if I could get a fresh install working, I could test whether it too has this same issue. Narrowing down the possible root causes for such things is never easy...
Mystler wrote:First of all, I can only provide limited help concerning the topic (OS X and Wine) because I don't use those. Besides, re-copying the files has solved it, in general. You can try launching the repair shortcut for TOC (which is installed by the Installer), but it basically does the same thing.
Please remember that I'm doing this in my free time...
Yes, we all are doing this in our free time. I have been spending much of my free time lately testing and retesting this issue. I am hoping that if we learn more about what is happening here, it will benefit the MOUL Mac community.
