Wine development team was able to produce a new experimental release today. 1.7.17 brining many new features and as many as 89 bugfixes.
A new issue of World Wine News is also available: #367
The few most interesting features introduced in this release:
More implementations for the Task Scheduler.
C runtime made more compatible by sharing source files.
Fixes in the Mac OS X joystick support.
Various bug fixes.
To learn more about this release pleas visit this announcement.
The source code for this release is available here:
http://prdownloads.sourceforge.net/wine/wine-1.7.17.tar.bz2
http://mirrors.ibiblio.org/wine/source/1.7/wine-1.7.17.tar.bz2
To get the most recent changes, a git repository is a good starting point.
Binary packages should be available for a download as soon as the build process is finished.
Check out Page 2 for the list of fixed bugs!
A new issue of World Wine News is also available: #367
The few most interesting features introduced in this release:
To learn more about this release pleas visit this announcement.
The source code for this release is available here:
http://prdownloads.sourceforge.net/wine/wine-1.7.17.tar.bz2
http://mirrors.ibiblio.org/wine/source/1.7/wine-1.7.17.tar.bz2
To get the most recent changes, a git repository is a good starting point.
Binary packages should be available for a download as soon as the build process is finished.
Check out Page 2 for the list of fixed bugs!
Some you may have missed, popular articles from the last month:
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
13 comments
This wine fix interesting things as:
And other things
Test concluded with wine 1.7.17 with steam beta and metal gear rising revengeance works
View video on youtube.com
^_^
-Virtual memory register needed for starwars force unleashed 1
http://bugs.winehq.org/show_bug.cgi?id=21536
-Keyboard doesn't work in games launched from Steam when using virtual desktop
http://bugs.winehq.org/show_bug.cgi?id=21770
-Skyrim needs more video memory (this bug apparently ffects more on AMD users)
http://bugs.winehq.org/show_bug.cgi?id=29991
-Radeon HD6670 detected as HD3200 (this bug occurs on various AMD cards)
http://bugs.winehq.org/show_bug.cgi?id=31891
-And now recognize GTX760 (This card is detected as 8800GTX) and Geforce GTX 750
http://bugs.winehq.org/show_bug.cgi?id=3548
And other things
Test concluded with wine 1.7.17 with steam beta and metal gear rising revengeance works
View video on youtube.com
^_^
0 Likes
This wine fix interesting things as:
-Virtual memory register needed for starwars force unleashed 1And other things
http://bugs.winehq.org/show_bug.cgi?id=21536
-Keyboard doesn't work in games launched from Steam when using virtual desktop
http://bugs.winehq.org/show_bug.cgi?id=21770
-Skyrim needs more video memory (this bug apparently ffects more on AMD users)
http://bugs.winehq.org/show_bug.cgi?id=29991
-Radeon HD6670 detected as HD3200 (this bug occurs on various AMD cards)
http://bugs.winehq.org/show_bug.cgi?id=31891
-And now recognize GTX760 (This card is detected as 8800GTX) and Geforce GTX 750
http://bugs.winehq.org/show_bug.cgi?id=3548
Test concluded with wine 1.7.17 with steam beta and metal gear rising revengeance works
View video on youtube.com
^_^
You are awesome with your wine lol xD You seem to manage to make everything works so well xD How do you do it lol
0 Likes
Now while you are at it, get world of tanks to work well with the new graphics update! XD
0 Likes
You are awesome with your wine lol xD You seem to manage to make everything works so well xD How do you do it lol
Its really simple but some things are needed:
-I recommend INTEL cpu because IPC per cycle is much better than IPC per cycle on AMD and performance per core its much higher on INTEL than AMD (this is important if you use games with use 3 cores or less, CSMT is not highly multithreading normally use 2 cores, and more cores using if game become for use it), this is not mandatory but on INTEL i see better results
-I highly recommends Nvidia video card with lastest propietary drivers if you use wine, this give you more performance and compatibility on wine than AMD video cards (VLIW4-VLIW5-GCN) with/without propietary drivers (AMD opensource recently improve some compatibility but performance is lower than NVidia with propietary drivers and AMD with propietary drivers give more performance but have bugs than Nvidia with propietary drivers), INTEL video card is worst than AMD
-you must be know how to install propietary drivers
-this guides could be usefull
View video on youtube.com
View video on youtube.com
View video on youtube.com
View video on youtube.com
View video on youtube.com
And other issues can be appear depend title: add dlls, configure native dlls on wine cfg, some need NOCD/NODVD, others titles need this command __GL_ExtensionStringVersion=17700 especially on
Call of Duty 1
View video on youtube.com
Call of Duty 2 (this title need also v-sync)
View video on youtube.com
Return to Castle Wolfenstein
View video on youtube.com
Shellshock 2
View video on youtube.com
Two Worlds 1 where resolve models issues
Without __GL_ExtensionStringVersion=17700
View video on youtube.com
With __GL_ExtensionStringVersion=17700
View video on youtube.com
And could appear other issues but on middle of this situation many titles stay working
^_^
0 Likes
Er... there's a truckload of bugs fixed for Team Fortress 2 and other Valve games... ??? Those games have been ported to Linux, why did someone loose so much time making them work through Wine ?
0 Likes
You are awesome with your wine lol xD You seem to manage to make everything works so well xD How do you do it lolI've gotten a LOT more games to run with less issues when I started using playonlinux. It makes it easy to manage a wine prefix per game, so you don't accidentally break something when trying to get something new to work.
I just create a clean prefix, install the game and try to run it. When it doesn't work, check the wine output and generally you will see what's wrong quite clearly (mainly missing DLL's). When you use steam the prerequisites for the game are automatically installed most of the time.
Also check the wine appdb, the good test results often have a list of prerequisites you need to install or tweaks to improve performance.
0 Likes
Er... there's a truckload of bugs fixed for Team Fortress 2 and other Valve games... ??? Those games have been ported to Linux, why did someone loose so much time making them work through Wine ?We can only guess the reasoning behind that...
Often fixing a Wine bug for one game fixes same or similar one for another one. Also, Wine works for some platforms Steam isn't available for (unpopular Linux distribution families, FreeBSD and such).
Wish they would work more on games that are not available for Linux, though.
0 Likes
Often fixing a Wine bug for one game fixes same or similar one for another one.
This. If you know a bug exists, you fix it or it WILL cause issues futher down the line for other games.
0 Likes
You are awesome with your wine lol xD You seem to manage to make everything works so well xD How do you do it lolIts really simple but some things are needed:
-I recommend INTEL cpu because IPC per cycle is much better than IPC per cycle on AMD and performance per core its much higher on INTEL than AMD (this is important if you use games with use 3 cores or less, CSMT is not highly multithreading normally use 2 cores, and more cores using if game become for use it), this is not mandatory but on INTEL i see better results
-I highly recommends Nvidia video card with lastest propietary drivers if you use wine, this give you more performance and compatibility on wine than AMD video cards (VLIW4-VLIW5-GCN) with/without propietary drivers (AMD opensource recently improve some compatibility but performance is lower than NVidia with propietary drivers and AMD with propietary drivers give more performance but have bugs than Nvidia with propietary drivers), INTEL video card is worst than AMD
-you must be know how to install propietary drivers
And could appear other issues but on middle of this situation many titles stay working
^_^
Ah I see thank you :)
0 Likes
You are awesome with your wine lol xD You seem to manage to make everything works so well xD How do you do it lolI've gotten a LOT more games to run with less issues when I started using playonlinux. It makes it easy to manage a wine prefix per game, so you don't accidentally break something when trying to get something new to work.
I just create a clean prefix, install the game and try to run it. When it doesn't work, check the wine output and generally you will see what's wrong quite clearly (mainly missing DLL's). When you use steam the prerequisites for the game are automatically installed most of the time.
Also check the wine appdb, the good test results often have a list of prerequisites you need to install or tweaks to improve performance.
Thanks yeah Playonlinx is very useful :)
0 Likes
When someone opens bug in wine db, it gets unique id number. There are lot of bugs that has no activity for years and if someone tries the game and it works it becomes marked as fixed and will be added into new wine changelog as marked fixed even the work behind bugfix might be several versions earlier.
0 Likes
If You want wine to go faster forward,
report wine issues here
http://bugs.winehq.org/enter_bug.cgi?product=Wine
But you should have up to date wine (no crossover or playonlinux version) and debug. "wine program-name.exe >> debug.log 2>&1" creates basic debug file.
But it would be more important to test bugs with recent wines and report with debugs.
Take this list for an example
http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&limit=0&list_id=146298&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&query_format=advanced
Even reporting games back wine database would help.
Here is a link to search box your favorite games:
http://appdb.winehq.org/objectManager.php?sClass=application&sTitle=Browse%20Applications&sOrderBy=appName&bAscending=true
report wine issues here
http://bugs.winehq.org/enter_bug.cgi?product=Wine
But you should have up to date wine (no crossover or playonlinux version) and debug. "wine program-name.exe >> debug.log 2>&1" creates basic debug file.
But it would be more important to test bugs with recent wines and report with debugs.
Take this list for an example
http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&limit=0&list_id=146298&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&query_format=advanced
Even reporting games back wine database would help.
Here is a link to search box your favorite games:
http://appdb.winehq.org/objectManager.php?sClass=application&sTitle=Browse%20Applications&sOrderBy=appName&bAscending=true
0 Likes
But you should have up to date wine (no crossover or playonlinux version)You can have any wine version in playonlinux, even one you compile from source yourself (which I've had to do for a game once). When a new version is released, it's in the pol repo within a day.
0 Likes
*Translation:
If you do not get the reference, it is your fault not mine.
See more from me