

Wine STAGING & CSMT Builds - Engines Available
#61
Posted 21 April 2015 - 09:33 AM
engine 68c somehow works in 10.7.5 as never before. So I will stay with this compiling method. By clang!
#62
Posted 21 April 2015 - 10:56 AM
NRG90, on 20 April 2015 - 09:46 PM, said:
http://portingteam.c...e-blind-forest/
Quote
The strange thing is, what I do not understand in that bug, is that if I play the game when starting it from Windows 8.1 the game runs smoothly without the bug, but the video card is always a 9800M GTS that does not support dx11 but only dx9 ...
#63
#64
Posted 21 April 2015 - 04:27 PM
Slice, on 21 April 2015 - 02:06 PM, said:
I think the game requires features that supported by real drivers but not supported by Wine.
I think you are right: http://portingteam.c...st/#entry103453
However the game works without any crashes, but fonts are unreadable cause the "pink blocks" bug...
#65
Posted 24 April 2015 - 08:01 PM
Just trying to get a feel for the process...
#66
Posted 25 April 2015 - 10:47 AM
ovvldc, on 24 April 2015 - 08:01 PM, said:
Just trying to get a feel for the process...
I have both results. For some games it improves speed, for other reduces it.
CSMT support is not superseded by changes in Wine. There are people that are able to synchronize changes.
For now I decided to continue my investigations based on latest wine-stage 1.7.41. And I will not hurry on latest wine.
https://dl.dropboxus...7.41-76c.tar.7z
#67
Posted 25 April 2015 - 11:23 AM

I also know plain Wine doesn't have CSMT implemented yet, but Alexandre Julliard intends to have it in (it was stated as the single release criterion for Wine 1.8). I just wonder if some of that code has been merged, or if it has all been deferred until Henri Verbeet's adaptations for DX10/11 are finished.
And thanks for the engine, I downloaded it when you first posted it, though I haven't tried it yet. I will let you know if i notice anything interesting about it (good or bad).
#68
Posted 28 April 2015 - 02:32 PM
Anyway my engines much better then original.

#69
Posted 01 May 2015 - 08:15 AM
Developing engine for ATI/AMD 3D graphics
no matter if ATI or NVidia or Intel Graphics.
I will always based on Stage version but with additional patches that wine-developers rejected.
I know I am right. Let them to live with their bugs.
#70
Posted 03 May 2015 - 11:18 AM

#71
Posted 03 May 2015 - 09:48 PM

#73
Posted 17 May 2015 - 11:27 AM

#76
Posted 29 May 2015 - 08:29 PM
Slice, on 29 May 2015 - 07:57 PM, said:
1.7.44?!?
actually latest "official" staging version is the 1.7.43...
https://github.com/w.../latest-release
#77
Posted 30 May 2015 - 07:34 AM
NRG90, on 29 May 2015 - 08:29 PM, said:
actually latest "official" staging version is the 1.7.43...
https://github.com/w.../latest-release
I just apply patches wine-stage (so call upcoming release ) to the wine.
#78
Posted 30 May 2015 - 11:11 AM
Slice, on 30 May 2015 - 07:34 AM, said:
I just apply patches wine-stage (so call upcoming release ) to the wine.
Wine staging patches can change between a release and another... so please don't confuse this tread...

You could rename your release as WS9wine1.7.44-CSMT
#80
Posted 31 May 2015 - 06:44 AM
NRG90, on 30 May 2015 - 11:11 AM, said:
Wine staging patches can change between a release and another... so please don't confuse this tread...

You could rename your release as WS9wine1.7.44-CSMT
If you'll notice that the he named the engine WS9WineSherry1.7.44....pretty sure his patch set is reflective of Staging/CSMT and whatever other special brew he has going on in this build.
Kudos to you Slice, You're doing really great work
#81
Posted 31 May 2015 - 07:07 AM
Slice, on 31 May 2015 - 05:05 AM, said:
Buy.
Maybe I expressed myself too fast and wrong, but it was not my intention to offend you ... Unfortunately my English is what it is, and I help me with the online translators, sorry ...
What I meant is that the vanilla staging are one thing while finding your ideal engine an'other ... With your engines I do not know if I have to redraw every time to your libraries and though sometimes I have problems (with my nvidia card) in certain games, that's why I tried to keep things detached ...
Then, if you write "Vanilla" Stage 1.7.44, it is assumed that you've got the real vanilla staging and not the version of WineHQ with the additional CSMT patch and something else earlier, since the patches contained in the staging engines are differents and may change or be changed from one version to another ... so in this tread your engine would be little "vanilla" and very "slice" ...

So I written my previous message in order to keep this tread straight and not to offend you...
If I offended you I apologize ...

However today has been released the official source of WS9wine 1.7.44 Staging
changelog...
#82
Posted 01 June 2015 - 04:02 PM
Anyone?
Gurqn?

Quote
Wine Staging Team - Sun, 31 May 2015
Today we released Wine Staging 1.7.44 with several bug fixes and switched to our new build system for our prebuilt packages. Currently most of our effort goes into fixing bugs instead of adding new features, so we also changed the format of the release notes a bit. Before we tell you more about the build system changes, here is a list of all fixed bugs / added features in this release (without any particular order).
- Add shell32 placeholder icons to match offsets with Windows, required by SuperPower 2 demo (Wine Bug #30185)
- Add stub for iphlpapi.ConvertInterfaceLuidToGuid, required by PES2015 (Wine Bug #38576)
- Add stubbed ISWbemSecurity interfaces in wbemdisp (Required by Paessler WMI Tester)
- Add support for hiding wine version information from applications (Wine Bug #38656)
- Allow to enable/disable InsertMode in wineconsole settings (Wine Bug #36704)
- Also handle '\r' as whitespace in wbemprox queries (Required by Paessler WMI Tester)
- Also output winedbg system information to the terminal, not only to dialog
- Assign a drive serial number during prefix creation/update (Wine Bug #17823)
- Do not use unixfs for devices without mountpoint (Required by 2xExplorer)
- Fix NULL pointer dereference in get_frame_by_name effecting various Web installers (Wine Bug #34982)
- Fix crash in Gothic 1/2 with builtin directmusic caused by wrong return value (Wine Bug #7425)
- Fix handling of opening a file with RootDirectory pointing to a file handle, required by Msys2 (Wine Staging Bug #299)
- Fix scaling behaviour of images and mipmap levels in IDirect3DTexture2_Load (Required by Prezzie Hunt)
- Return fake device type when systemroot is located on virtual disk (Wine Bug #36546)
- Revert upstream regression which causes broken rendering in various games (Wine Bug #38654)
- Support for ws2_32.dll.WSAPoll, required by Planetary Annihilation (Wine Bug #38601)
- Use random names when caching very long urls in wininet (Wine Staging Bug #300)
#83
Posted 01 June 2015 - 05:04 PM
It's crucial difference.
#84
Posted 01 June 2015 - 07:20 PM
NRG90, on 01 June 2015 - 04:02 PM, said:
Anyone?
Gurqn?

Im afraid but I will not be available for limited amount of time again


#85
Posted 01 June 2015 - 07:58 PM
Slice, on 01 June 2015 - 05:04 PM, said:
It's crucial difference.
no Slice, I think (imho) the differences are the new patches and bugfixes included in each new official staging release... for example the second patch of 1.7.44 STAGING for pes2015 and the online connection , in your personal 1.7.44stage did it was included?
So when I ask for official vanilla staging engine I refer to this:
http://www.wine-staging.com/news.html
Slice, No one here doubts the quality of your work and all we are grateful to you, but in this tread I thought we were talking also about the compilation of Staging versions that are released for linux... your internship versions Are also very appreciated, but without reference to patches and bug fixes I think it's better have as a reference those for linux ...
I hope I didn't offended you and I apologize if it is so ...
#86
Posted 02 June 2015 - 05:20 AM
Gurqn, on 01 June 2015 - 07:20 PM, said:


Maybe because I've never been a developer and I don't know at all xcode and company, however, I tried to compile the 1.7.44 staging but , I probably will not clear in some passages of that guide and how make precisely some things ... My situation:
1) I downloaded and installed command line tool
2) I downloaded and installed x-code 6.3.2
3) I skipped the Point 3 of the guide because the file was already amended as pictured, but forgive my bad English, what does it means:
Quote
4) I'm with Yosemite 10.10.3 and following the guidance I have downloaded and installed the 10.8 SDK in:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer5) Here perhaps I do not know if I did well...
I downloaded here: https://github.com/w...io/wine-patched
latest 1.7.44 full Staging version and the file is called:
wine-patched-master.zip
Is 'the right one?!?
I putted it on my desktop and decompressed in a folder named "wine-patched-master"
I started Wineskin Winery, Then I clicked on the "+" of "new engine(s) avviable!" then "Custom build an engine".
In the "Wine Source" box I dropped the wine-patched-master folder
Minimum os Version 10.6
Then in "Current Engine Base" I clicked on update and the "W2.5.5v1EngineBase" was installed.

After entering the Engine Name "WS9Wine1.7.44-STAGING" I clicked on "Build!"
the terminal starts and everything he does in a minute is this:
but I do not find any new engine ... where am I wrong?!?
EDIT: I was wrong in the 3d point of guidance, now it seems to compile the new engine... I'm waiting for it...
#87
Posted 02 June 2015 - 06:01 AM
NRG90, on 02 June 2015 - 05:20 AM, said:
"...(do not forget to comment gcc-4.2 and g++-4.2)"
I wouldn't worry too much about that, pretty sure it's something that would need to be patched or edited in to the source files
http://en.wikipedia....er_programming)
NRG90, on 02 June 2015 - 05:20 AM, said:
latest 1.7.44 full Staging version and the file is called:
wine-patched-master.zip
Is 'the right one?!?
Yes that is the proper patched Staging Wine source.
As for the Terminal output, I'm not really sure why it didn't paste correctly into the post but it's really difficult to read. I used command+F to search through it and found this at the very end.
no configure: error: libxml2 32-bit development files not found (or too old), XML won't be supported. This is an error since --with-xml was requested. An error occurred during Wine Configure, build halted. Cleaning up changes made for the build, if any... logout [Process Completed]
Before you build the engine look at the Wineskin Command Arguments and find --with-xml, if you put --without-xml it might compete the build but will very likely be detrimental to the engine.
#88
Posted 02 June 2015 - 06:36 AM
DankoB, on 02 June 2015 - 06:01 AM, said:
As for the Terminal output, I'm not really sure why it didn't paste correctly into the post but it's really difficult to read. I used command+F to search through it and found this at the very end.
no configure: error: libxml2 32-bit development files not found (or too old), XML won't be supported. This is an error since --with-xml was requested. An error occurred during Wine Configure, build halted. Cleaning up changes made for the build, if any... logout [Process Completed]
Before you build the engine look at the Wineskin Command Arguments and find --with-xml, if you put --without-xml it might compete the build but will very likely be detrimental to the engine.
Now I tried "--without-xml" command argument and at the end of the process it give me this:
configure: error: libxslt 32-bit development files not found, xslt won't be supported. This is an error since --with-xslt was requested. An error occurred during Wine Configure, build halted. Cleaning up changes made for the build, if any...[/s]
[s]So I can't correctly compile a 1.7.44-STAGING engine?
DankoB, on 02 June 2015 - 06:01 AM, said:
EDIT: I was wrong in the 3d point of guidance, now it seems to compile the new engine... I'm waiting for it...
#89
Posted 02 June 2015 - 08:18 AM
NRG90, on 02 June 2015 - 06:36 AM, said:
Now I tried "--without-xml" command argument and at the end of the process it give me this:
configure: error: libxslt 32-bit development files not found, xslt won't be supported. This is an error since --with-xslt was requested. An error occurred during Wine Configure, build halted. Cleaning up changes made for the build, if any...[/s]
[s]So I can't correctly compile a 1.7.44-STAGING engine?
EDIT: I was wrong in the 3d point of guidance, now it seems to compile the new engine... I'm waiting for it...
Comment means this symbol before command like a #. So when you comment like this #gcc-4.2, you are basically disabling declaration of gcc-4.2. In enginebuild file if you have un-commented gcc and g++ then you should comment gcc-4.2 and g++-4.2 respectivly for disabling.
As a last step, you should also select 10.8 as minimum OS then you are good to go. That's why we have used 10.8 SDK.
Note: By the way I am also not developer too, just a some short of geek. Also you shouldn't compile without xml, just set minimum os to 10.8 for 10.8 SDK usage.
#90
Posted 02 June 2015 - 10:04 AM
Gurqn, on 02 June 2015 - 08:18 AM, said:
As a last step, you should also select 10.8 as minimum OS then you are good to go. That's why we have used 10.8 SDK.
Note: By the way I am also not developer too, just a some short of geek. Also you shouldn't compile without xml, just set minimum os to 10.8 for 10.8 SDK usage.
thanks for the explanation, unfortunately I read your comment after I had done from filling with 10.6 as minimum OS X...

My core2duo 2,53ghz has taken 45/50 minutes

So I tried the engine and apparently new patches of this staging version works:

but when I launched my game (PES2015) has become not selectable from the menus and then I did not play ... Blocks to move the cursor ... During the long compilation I had a lot of warning ... may be because I used as minimum OS version 10.6?!?

EDIT: I recompiled it with 10.8 os x as minum os and now seems to work in game...
WS9Wine1.7.44-STAGING:
But I've a doubt, during the compiling there are many Warnings! does it's normal?!?
And another question, Command Arguments are not touched by me in the second compilation with 10.8 as minimum OS required... I hope to have made fine, right?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users