![]() ![]() But that only happens of you change those two lines. The only way to fix that is to download a patch and change more stuff and yada yada. Though the video says that it will give error messages in-game, but they aren''t real (they don''t affect anything). Additionally, the video I watched (not the forum posts) instructed me to change these lines as well (but it might not be necessary ) I''m not sure if wine installed 9 or 10, hopefully both do you know?) However the game is optimized for 10.ĥ. It is possible that only one works, try 9 first. change the following line: 0 set the 0 in the middle to 9 or 10. navigate users/Wineskin/ApplicationData/Ubisoft/Anno1404/Config and open the engine.ini file with textedit. Right click it, select show package contents.ģ. Find Anno 1404 app (most likely in your applications folder). So I watched a little video and read some forum posts and found with a possible fix, basically force DirectX9 or 10:ġ. The game is known to have these issues, it doesn''t seem that Ubi is going to anything about it (typical of them). I''ve researched this a bit and found many more users with this problem (or similar with crashing during saves) on windows machines. It turns out this is likely the game''s fault, not wine. Now, after a crash, you will be able to find it at Contents/Resources/Logs (inside the wrapper). In the advanced tab, enable it to always make logs. I''m not sure about which engine is the best, but if we find out that another one is better than the actual one, then we are also going to update the WSI fileĪbout the log file: if you show the package contents of your wrapper (you can right click its file or right click it on Porting Kit Local list), you will find the Wineskin app. So are there any other improvements that can be made? Like running in a different mode or forcing directx? Or winetricks or whatever those are called.Īlso: where can I find the log file after it crashed? If anyone finds one that performs better please let us know by posting in this thread. I tried 14.0.0, but as I said that didn''t make it any better. The current and default engine that I''ve been using is WS9WineCX13.2.0. Tried only a couple engines, both made it worse. Especially in the late game, when there is tons of stuff on the map. This is becoming a problem for me now too. So it has to do with (graphic?) memory, map size, objects on the map and graphic settings have an impact on the time before it runs out of memory. ![]() (I find it hilarious that the game actually notifies you when you have been playing for two hours) However, in the elector scenario that I''m currently playing it has not crashed a single time for me, even when playing 2 hours straight. I also toned down particles to medium, and turned off aniso completely. Funnily enough, the game still looks great and barely any different at all on medium textures. Lowering texture quality from high to medium seemed to have the biggest impact on this time increase. Then I lowered the graphics bit by bit and that seemed to increase the time before a crash to 1hr-2hrs depending on the mission. When I was playing the campaign, it crashed after half an hour at first. I usually get a stable launch in less than 2 minutes.For me, Anno 1404 also crashes after a certain amount of time. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators. DO NOT change the 3D rendering setting to "Hardware." I had to reinstall after doing that, but reinstalling did let me narrow my troubleshooting steps down to the above, which have been reliable since then. Maxing out the resolution with in-game settings caused me no problems, and is remarkably sharp on a giant 4K display. Once you're in a game, though, you're golden. Yes, I have to repeat steps 5-7 almost every time I launch the game. exe, and what value you set under SoftwareDevice doesn't matter, only that you changed it. In my experience, Safe Mode got no better results than the main. Repeat steps 5-7 until you make it into a game. I signed up for Access mainly to try out Tropico and this is pretty unacceptable. They both run for a bit and then crash out or lock up my system. Change the value for DDraw: SoftwareDevice. 1 + XP 12 September 2019 Options Grantholomaeus Novice EXACT same issues with both of those games - Tropico 5 and Burnout Paradise. If you get 3 crashes in a row, edit Tropico2.iniĦ. ![]() Hit Next and tell Windows that the settings worked.ĥ. Let it set the compatibility - it will go with WinXP SP3ģ. Right-click Tropico2.exe and choose Troubleshoot CompatibilityĢ. Since this thread is still the top result when googling T2 crashes, here's what worked for me:ġ. ![]()
0 Comments
Leave a Reply. |