Most of the code updates around 162-161 revisions were related to issues involving the CD/DVD version code removal, so that probably has an impact on how resources/assets are loaded from disk, would be annoying if the game was running fine and then halfway was requesting somebody to insert CD #2 in their drive :D Regarding the code: It's not that I do not have the code, it's just that I don't know at which revision of the code that exactly build was done, and since the executable on steam is encrypted and compressed, I can't just build versions and see which ones matches.
I'm planning to have a separate thread at some point to ask more people, but before that I wanted to make sure there was no obvious big issues I missed: It's generally difficult to get people to test something multiple time, so it's important to get it right. Tldr: Are there still some mega blockers that make the game unplayable on recent machines/versions of windows, that I should look at, and if yes, how can I reproduce these issues. The reason I'm not sure about what my version does, is that I don't actually know what is in the official version (build 161 - from 2013) so the code version I started from may not completely match and have some changes that may be for the best, or the worst.
#MYST 3 PLAYONLINUX WINDOWS#
I know for example that now and then the text gets displayed in purple, that the font smoothing in windows get disabled, but I was not able to reproduce that reliably, which make debugging very difficult. If there are some other issues (I know there are), what would be cool is if I could be provided with some "foolproof" ways of reproduce them. The game is called "Longest Journey" for a reason: It's super long, and I don't really have a QA team to help, so if want any reasonable chance to not publish a broken version, I will need a few of you people go through the game (not all of it!), like loading your old save games and check that it works just fine. I'm on the issue, but there's a bunch of problems: In other news, progress on adding support for The Longest Journey to ResidualVM continues thanks to our GSoC student Liu "Douglas" Zhaosong. That's not much, but Cyan and GOG.com are planning to use ResidualVM for the Myst III digital release and we want it to be as stable as possible. It fixes a couple of Myst III bugs:įixed a rare crash when walking near the magnetic rings in Amateria.įixed unresponsive controls for the holographic projectors in J'nanin. Our previous release is already a few months old, it's time for a bug-fix release! ResidualVM 0.3.1 is available on our downloads page.
The home page tells you they have started working on support in the very first post under If he was responding to OP it doesn't matter he just ignored the mistake. You seem to be not be getting you need to use the daily build and it is fully working just needs some more testing/optimizing but even though it's still a daily build it's a much better experience than using dgvoodoo reshadeĪs for responding I only thought the Linux user had responded since it has big problems running on that with play on linux and wine and residualvm helps. The ResiddualVM team have done a great job It was a great move by funcom to do this and the best way to play the game. I just pointed out you were wrong and the information you posted was false it's not a big deal. I checked release notes and searched on the project pages. Those people are not even responding to you, they are thanking the OP.Īnyway, I did check. Ursprünglich geschrieben von fashy:Just let it go.
0 kommentar(er)
