Jump to content

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

VitorMM

Member Since 15 May 2011
Offline Last Active Jun 22 2018 04:49 PM
*****

Posts I've Made

In Topic: Wineskin Unofficial Update

09 April 2018 - 04:06 PM

 Gcenx, on 09 April 2018 - 02:01 AM, said:

Seems you have detection built in for what type of engine you try to install

Yup :)

 Gcenx, on 09 April 2018 - 02:01 AM, said:

nice, for Staging64bit engines they don't like redirection of libs or it won't create syswow64 or program files (64bit) correctly.

It will be very easy to create a condition just for that kind of engine :)

In Topic: Wineskin Unofficial Update

08 April 2018 - 09:54 PM

View PostGcenx, on 08 April 2018 - 09:23 PM, said:

Nice, what little I got done nothing really mostly just fixing some issues I noticed and adding downloads redirection and adding it into the menu

I'm going to gitclone that and take a look at the new code, I am still new to this so I might be of little help it took me a while to get my head around the original code :wacko:

In case you are clueless about that, you can just upload you code somewhere and I can check the differences between it and the original Wineskin source code ;)

That's easy to do with Terminal commands.

In Topic: Wineskin Unofficial Update

08 April 2018 - 03:42 PM

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

  • This includes the GPU detection fix by "Markus Stoll" merge request on sourceforge.

Been working on an update to make that specific part even better, with deep video card detection, more accurate and with a much wider support than the one that was been used by WineskinLauncher :)

I've reported that a long time ago, but still didn't had the chance to publish the modified Wineskin, although it's ready (however, not tested).

Me and Paul have being talking with doh about releasing a new Wineskin version. We may merge our changes to create a much more stable Wineskin :D

I will upload my modified Wineskin version to Github. In case you want to combine our changes, just submit yours in a pull request or upload your source code somewhere ;)

EDIT: Uploaded my source.
https://github.com/v...251093/wineskin

Just remembering: my source requires my framework, ObjectiveC_Extension, to be build.

In Topic: How to compile Wineskin from sourceforge?

29 December 2017 - 12:58 PM

View PostdankoB, on 29 December 2017 - 08:38 AM, said:

Is it just the Wineskin.app that you compiled? Could it be used on any Winery created wrappers? I'm interested in testing it out if you are willing to share.

Hey dankoB!

No, I guess he just recompiled the WineskinLauncher binary. There is where the problem lies.

The Wineskin.app just tells the wrapper if the Auto-detect GPU feature should be enabled or not, but is WineskinLauncher which uses that information to really detect the GPU.

In Topic: How to compile Wineskin from sourceforge?

28 December 2017 - 02:53 PM

Well, the only thing you really need is macOS and Xcode.

Git, which is part of Xcode Command Line Tools, and so can be installed by simply calling git in the terminal (if you have Xcode installed), is extremely helpful, although not really required.