Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google      Sign In   
  • Create Account

Wine STAGING & CSMT Builds - Engines Available


  • Please log in to reply
664 replies to this topic

#601 TheTuKays

TheTuKays

    Professional Member

  • Members
  • PipPipPipPip
  • 112 posts
  • Graphics Card:ati
  • Operating System:Other OS/Not specified

Posted 26 January 2018 - 11:30 AM

View PostGurqn, on 25 January 2018 - 10:28 PM, said:

With regard to the first question, I wasn't compiling stable engines couple of months ago. That has been changed recently, that's why I just re-organized them :) Due to having a very busy schedule since the end of 2017 I can't find enough time for helping about glitches that you facing right now including what dankoB has reported. Plus, also had problems with my Hackintosh so, I'm just only able to use my laptop.

With some delay, I uploaded 3.0 stable engines to the repository. Enjoy, please :)

Note: planning to migrate everything to the MEGA

http://www.mediafire.../?md4r44g048jy9

https://mega.nz/#F!z...EbLrrzieWMbgteA
Gurqn: When i try to create a new Wrapper with the 64bit engine, i keep getting an error telling me the engine is corrupt.
The 32bit engines don't give that error.
Trying on macOS 10.12.6.

-+TheTuKays+-

#602 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 26 January 2018 - 01:52 PM

I can also attest to this when running the 64bit engines. Using Activity Monitor after launching the game I see no wine64-preloader or wineserver processes running and the wine log output is this:

/Volumes/MEDIA/Games/S.T.A.L.K.E.R. Lost Alpha.app/Contents/Frameworks/wswine.bundle/bin/S.T.A.L.K.E.R. Lost Alpha863488668Wine: line 2: /Volumes/MEDIA/Games/S.T.A.L.K.E.R. Lost Alpha.app/Contents/Frameworks/wswine.bundle/bin/S.T.A.L.K.E.R. Lost Alpha863102107Wine: No such file or directory

I'm also on 10.12.6

#603 --------

--------

    Professional Member

  • Members
  • PipPipPipPip
  • 162 posts
  • LocationIstanbul
  • Graphics Card:MSI Z97 MPOWER - GTX 980 - View Sonic VP2780-4K - 16GB Ram - macOS High Sierra
  • Operating System:Other OS/Not specified
  • I like to play:Most of games :-)
Author

Posted 07 February 2018 - 09:11 PM

3.1 devel engines have been added to the repo


https://mega.nz/#F!z...EbLrrzieWMbgteA

#604 --------

--------

    Professional Member

  • Members
  • PipPipPipPip
  • 162 posts
  • LocationIstanbul
  • Graphics Card:MSI Z97 MPOWER - GTX 980 - View Sonic VP2780-4K - 16GB Ram - macOS High Sierra
  • Operating System:Other OS/Not specified
  • I like to play:Most of games :-)
Author

Posted 07 February 2018 - 09:13 PM

View PostTheTuKays, on 26 January 2018 - 11:30 AM, said:

Gurqn: When i try to create a new Wrapper with the 64bit engine, i keep getting an error telling me the engine is corrupt. The 32bit engines don't give that error. Trying on macOS 10.12.6. -+TheTuKays+-

View PostdankoB, on 26 January 2018 - 01:52 PM, said:

I can also attest to this when running the 64bit engines. Using Activity Monitor after launching the game I see no wine64-preloader or wineserver processes running and the wine log output is this:
/Volumes/MEDIA/Games/S.T.A.L.K.E.R. Lost Alpha.app/Contents/Frameworks/wswine.bundle/bin/S.T.A.L.K.E.R. Lost Alpha863488668Wine: line 2: /Volumes/MEDIA/Games/S.T.A.L.K.E.R. Lost Alpha.app/Contents/Frameworks/wswine.bundle/bin/S.T.A.L.K.E.R. Lost Alpha863102107Wine: No such file or directory
I'm also on 10.12.6

Probably the following link will be useful?

http://portingteam.c...e/page__st__480

#605 --------

--------

    Professional Member

  • Members
  • PipPipPipPip
  • 162 posts
  • LocationIstanbul
  • Graphics Card:MSI Z97 MPOWER - GTX 980 - View Sonic VP2780-4K - 16GB Ram - macOS High Sierra
  • Operating System:Other OS/Not specified
  • I like to play:Most of games :-)
Author

Posted 08 February 2018 - 12:44 PM

Post moved from: http://portingteam.c...10-ws9wine1710/

View PostNRG, on 08 February 2018 - 10:07 AM, said:

@Gurqn

Because i can use only 10.8 sdk to compile it


note: I don't think your way to compile x64 engines is correct... their internal structure are always wrong inside wswine.bundle file... did you never tried to create a working wrapper with your x64 engines and use some x64 app like 7-zip x64?!? it works?!?

It's because of wineskin's faulty implementation not because of compiling incorrectly. Compiling wine for WoW or for pure 64bit is the same for Linux/macOS etc..  I have explained that a couple of times but no one understood.

http://wineskin.urge...s_parentId=7629

Repacking and compiling from source two different thing.

I'm adhering instructions here while compiling from source, so I don't believe something is wrong at least on my side.

https://wiki.winehq.org/Building_Wine

#606 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 08 February 2018 - 02:17 PM

No, it has nothing to do with updated libs. I've had those installed since May of last year. I'm not able to even create a wrapper with any 64bit engines past WS9Wine64bit2.22. I've also only been able to create wrappers with your 32bit engines. I'm sorry to say but your 64bit engines have never worked for me to any capacity.

I've followed your tutorial to get builds working on my system again and I'm running into the exact same results you are getting. Have you tested any of these 64bit engines you are sharing on your own system? The file structures are not correct on the files I've downloaded from your repository of wineskin engines.

Posted Image

Posted Image


Along with the lib and share folders there are also files missing from the lib64 folder from our builds. Are we suppose to add files to make these work correctly?

#607 --------

--------

    Professional Member

  • Members
  • PipPipPipPip
  • 162 posts
  • LocationIstanbul
  • Graphics Card:MSI Z97 MPOWER - GTX 980 - View Sonic VP2780-4K - 16GB Ram - macOS High Sierra
  • Operating System:Other OS/Not specified
  • I like to play:Most of games :-)
Author

Posted 08 February 2018 - 03:06 PM

View PostdankoB, on 08 February 2018 - 02:17 PM, said:

No, it has nothing to do with updated libs. I've had those installed since May of last year. I'm not able to even create a wrapper with any 64bit engines past WS9Wine64bit2.22. I've also only been able to create wrappers with your 32bit engines. I'm sorry to say but your 64bit engines have never worked for me to any capacity.

I've followed your tutorial to get builds working on my system again and I'm running into the exact same results you are getting. Have you tested any of these 64bit engines you are sharing on your own system? The file structures are not correct on the files I've downloaded from your repository of wineskin engines.



Along with the lib and share folders there are also files missing from the lib64 folder from our builds. Are we suppose to add files to make these work correctly?

DankoB wow builds and 64bit builds are not the same thing. Why would you need 32bit libs alongside with 64bit libs in order to make 64bit apps works? I never compiled wow builds, that's why I shared above
link from wineskin's forum that gives you the idea about the 64bit compatibility of wrapper itself.

#608 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 08 February 2018 - 05:30 PM

Maybe I'm mistaken but in order to create a Winery Wineskin wrapper with a 64bit engine, both libraries are required to be there. Have you tested these engines you've shared? I've tried numerous and none of them have successfully been built into a wrapper.

#609 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 12 February 2018 - 08:49 AM

On InsanelyMac Slice posted WrapperUpdate6 with some more 64-bit libraries.

http://www.insanelym...ases-and-tests/


#610 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 14 February 2018 - 10:12 PM

By the looks of it, it's only liblcms.dylib and it's symlinks that were updated. Everything else seems to be the same from update 5.

#611 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 17 February 2018 - 06:02 PM

End of Wine Staging as we know it.

https://wine-staging...ne-staging.html

But stable and development version continue strong with CSMT integrated.

#612 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 17 February 2018 - 07:48 PM

This fork off of compholio has been updated as recent as 17 hours ago. So all hope isn't a total loss.

https://github.com/w...ng/wine-staging ...somebody else seems to be taking the reigns

**edit --- I tried to apply the patch-set from the above link to wine 3.2 and it successfully patches everything up to ntdll-Attach_Process_DLLs patch. There's a lot of stuff that was updated within the last 20 hours prior to that patch but everything below that has not been touched for months. Maybe whoever has taken over is just taking the weekend off and will continue updating the patches soon.

#613 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 17 February 2018 - 11:18 PM

Really sad news and here is note from Alexandre Jilliard

https://www.winehq.o...ary/122848.html

As I see this post Wine (us users too) really needs experimental and push forward ground like staging was.
Probably some young guns can step in with some new csmt revolution :)

But thanks Sebastian and Michael again

#614 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 03 March 2018 - 10:28 PM

Wine Staging 3.3. (unofficial staging fork)

https://dev.wine-sta...p/435/download/

- unzip, put version file inside “usr” folder, rename folder to wswine.bundle and put it into wrapper frameworks
for easy testing until someone managed to properly build Wineskin engine ;)


#615 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 20 March 2018 - 04:21 PM

Wineskin's wine-staging engine 3.4
Staging Fork b05c091935 (Mar 20)





STG 3.4 (32bit+64bit).tar.7z...


#616 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 374 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 31 March 2018 - 09:05 PM

View PostNRG, on 20 March 2018 - 04:21 PM, said:

Wineskin's wine-staging engine 3.4
Staging Fork b05c091935 (Mar 20)



I don't know if anyone noticed but the current staging branch does not make "syswow64" or "Program Files" correctly, both are empty but wine devel 3.x does so don't directly make a wrapper with staging 3.x engines.

Edit:
Not normal Program Files but Program Files (x86)

#617 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 01 April 2018 - 12:50 AM

View PostGcenx, on 31 March 2018 - 09:05 PM, said:

I don't know if anyone noticed but the current staging branch does not make "syswow64" or "Program Files" correctly, both are empty but wine devel 3.x does so don't directly make a wrapper with staging 3.x engines.

I just tried to create a new wrapper with STG 3.4 (32bit+64bit).tar.7z... and folders are rights:

Posted Image

#618 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 01 April 2018 - 01:04 AM

you need to use the second engine linked... (first one is the standard engine and it is only for 32 bit software)

Edited by NRG, 01 April 2018 - 01:09 AM.


#619 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 374 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 01 April 2018 - 01:20 AM

View PostNRG, on 01 April 2018 - 01:04 AM, said:

you need to use the second engine linked... (first one is the standard engine and it is only for 32 bit software)

I was using the correct engine even my own version still the same issue with syswow64 its empty.


Posted Image



Here is the base folder of a 3.4 Devel :>

Posted Image


And showing the syswow64 folder

Posted Image

As you can see 3.4 Devel builds the Program Files (x86) and syswow64 folders correctly and populates them, the Staging builds do no do this correctly leading to issues when using them due to missing components, even using the .pkg builds have this problem staging is not building all files for syswow64 and Program Files (x86).

This is not an issue with the engine but with Wine-Staging breaking 64bit somewhere.

Edited by Gcenx, 01 April 2018 - 01:48 AM.


#620 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 01 April 2018 - 12:00 PM

@Gcenx


maybe you are right... I will check it


note: since wine 3.0 was released, wine-staging engines aren't official more... they are staging unofficials forks... maybe they are not still perfects or complete...

if you want a x64 wineskin's engine try to use the latest official  staging 2.21 version...

#621 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 01 April 2018 - 03:03 PM

View PostIncredible Hulk, on 03 March 2018 - 10:28 PM, said:

Wine Staging 3.3. (unofficial staging fork)

https://dev.wine-sta...p/435/download/

- unzip, put version file inside “usr” folder, rename folder to wswine.bundle and put it into wrapper frameworks
for easy testing until someone managed to properly build Wineskin engine ;)

The WineStaging64bit3.4 files can be found here... https://dev.wine-sta...p/480/download/

Download the portable version...both 64bit and 32bit work.

edit--- ahhh...sorry, bad link...the above link is the development branch of Wine...staging branch is here... https://dev.wine-sta...p/481/download/

#622 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 01 April 2018 - 04:12 PM

View PostdankoB, on 01 April 2018 - 03:03 PM, said:

.staging branch is here... https://dev.wine-sta...p/481/download/

the issue, mentioned above by Gcenx, persists also with more recent version of 3.4 64bit branch

#623 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 374 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 01 April 2018 - 04:23 PM

View PostNRG, on 01 April 2018 - 04:12 PM, said:

the issue mentioned above by Gcenx persists also with more recent version of 3.4 64bit branch

Still the same in the new 3.5 64bit also :(

#624 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 01 April 2018 - 04:25 PM

View PostGcenx, on 01 April 2018 - 04:23 PM, said:

Still the same in the new 3.5 64bit also :(

yes

maybe since they are  unofficials staging forks, they aren't yet complete ...

however I tried to install 7-zip x64 and it works fine in the right path... while if you try to install the x86 version it will install in a wrong path

#625 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 01 April 2018 - 06:06 PM

Official builds by new Staging maintainer Aleslie Hughes can be found here:

https://repos.wine-s...es/macosx/pool/

Unfortunately with staging 3.5 Steam opens but not one of the games is working with different errors?
3.4 worked fine but I was just updating wrapper.

#626 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 01 April 2018 - 08:04 PM

View PostIncredible Hulk, on 01 April 2018 - 06:06 PM, said:

Official builds by new Staging maintainer Aleslie Hughes can be found here:

https://repos.wine-s...es/macosx/pool/

Unfortunately with staging 3.5 Steam opens but not one of the games is working with different errors?
3.4 worked fine but I was just updating wrapper.

same identical issue explained by @Gcenx in aboves posts regardin the 64bit version

#627 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 01 April 2018 - 08:25 PM

View PostNRG, on 01 April 2018 - 08:04 PM, said:

same identical issue explained by @Gcenx in aboves posts regardin the 64bit version

I couldn't start any game in Wine Staging 3.5 until I deleted DllRedirects "wined3d.dll to wined3d-csmt.dll".
I also manually changed csmt key from string "enabled" to DWORD 0x1 as in devel version.
Now all my Steam games are running in 64-bit wrapper but it needs more testing regarding performance.

Edit: some testing and maybe regressions - Crysis 2 doesn't start and COJ Gunslinger has heavy stuttering.

It seems that from v3.5 staging is using vanilla version of CSMT and that old staging version is abandoned?

#628 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 02 April 2018 - 05:19 AM

CSMT is now enabled by default since Wine 3.3 (https://www.winehq.org/announce/3.3). However, I do not know how many additional performance fixes are still in staging and how to enable them.

#629 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 374 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 06 April 2018 - 07:42 PM

View PostNRG, on 01 April 2018 - 08:04 PM, said:

same identical issue explained by @Gcenx in aboves posts regardin the 64bit version

I think the real issue is wrapper update5/6 does not contain needed staging libs I belive that is the issue with creating syswow64 files as needed, try to make a known working staging64 engine and it will have the same effect.

I would test even the old staging libs but I don't have a copy and the like is now offline




Ignore the above, I took a Staging 32+64bit engine wswine.bundle and launched Wine directly from terminal, it created the .wine directory correctly.....

Edited by Gcenx, 17 April 2018 - 05:52 PM.


#630 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 17 April 2018 - 11:44 AM

Has anyone tried the Staging 3.6 yet? https://dev.wine-sta...ross-macosx-x64

I've literally just been manually renaming and dropping the usr folder right into the wrappers. I haven't had time to do anything in the last couple weeks but it seems to be working fine for the stuff I've been putting together then.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users