Posted 30 May 2017 - 05:36 PM
Posted 30 May 2017 - 06:36 PM
Other than that, there is no hard need to use a newer engine all the time. Performance rarely changes dramatically over a few weeks so the big reason to try is if you can't get an application or game to work.
Posted 31 May 2017 - 05:37 PM
Sure thing, but some of my ports are so close… that passing from 2.6 to 2.9 could mean a significant progress…
Posted 16 June 2017 - 06:28 PM
I have tried a custom, 2.10-based engine with the 2.6.2 wrapper from https://www.mediafir.../rd5cxhyux7zx8/, however WineSkin was unable to open it: "The engine wine-staging-x64-2.10 is corrupted or opened incorrectly. If this error continues next time you try, reinstall the selected engine"
Posted 17 June 2017 - 06:50 AM
Posted 17 June 2017 - 06:59 AM
I've just managed to make the staging 2.9 engine work from here, both x86 and x64 http://portingteam.c...ine-repository/
If you currently feel that there is no need to update the official engines, perhaps you could mention the repository or the custom engines subforum on the WineSkin site. Maybe it' just me, but it took me quite awhile to get to this forum and to discover that there are prebuilt engines available. Just my two cents.
Posted 17 June 2017 - 08:55 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users