Not compatible with Porting-kit when using 64bit Wine about wineskin HOT 16 CLOSED

That's strange. Usually, PK doesn't work with timeouts.

Differently from Wineskin, PK "owns" the wrapper running process during its creation, so it knows when the process is killed. It has worked normally so far. Could you please tell me which engine were you using and which Custom Port options have you marked, so I can reproduce the issue?

from wineskin.

I'm not sure how it worked so that was a guess on my part, it works in stock wineskin due to a timeout before closing down the process since wineserver tends to reload.

Oh that might be it then, I have watched a 64bit wrapper during creation and wineserver closes after 32bit prefix files are added, then a new wineserver process opens then 64bit prefix files are added.

I was using WineStaging64Bit3.7 using custom setting for Skyrim wrapper. I was adding additional dotnet versions

from wineskin.

Oh that might be it then, I have watched a 64bit wrapper during creation and wineserver closes after 32bit prefix files are added, then a new wineserver process opens then 64bit prefix files are added.

I can manage to fix that. Still would need to reproduce it to test the fix thought.

I was using WineStaging64Bit3.7 using custom setting for Skyrim wrapper. I was adding additional dotnet versions

You mean you was installing the existing Skyrim port in advanced mode with that engine, or that you were installing a custom port with that engine in order to run Skyrim?

from wineskin.

I think it was Skyrim as custom, I was half asleep so I don't 100% remember

I will test it again on my end and give more information if possible, I then I can narow down if it's just 64bit related or Staging64bit

from wineskin.

@vitor251093 I did try to look into this today but PK always replaces the master wrapper now.

Is there a way to disable that so I can check if its working correctly with the current version?

from wineskin.

I can work into that. There are already some changes expecting for a new PK release. I will an option to preferences to enable the use of different versions of the master wrapper, other than the latest as specified by the Wineskin website.

from wineskin.

Alright, just released the PK update that should solve that problem. Update PK to the latest version (2.9.476) and it should be gone :)

from wineskin.

@vitor251093 I just installed the update, I checked the option but it still deleted the wrapper and gave a funny error;

from wineskin.

Is your master wrapper named in the same pattern as the Wineskin master wrapper? (eg. Wineskin-2.6.2.app)

Also, if there is more than one master wrapper, PK will consider the last one in alphabetical order, in order to find the latest one.

from wineskin.

Yes Wineskin-3.0.0.app

Is the current name for my wrapper and it’s the only one in the folder.

from wineskin.

And it's in the Wineskin wrapper folder? (~/Library/Application Support/Wineskin/Wrapper)

If so, that's weird. The image that you showed only appear if the folder does not exists or if there is no file inside the folder. There is any change that may be a hidden file in the folder? Could you check with ls -a inside it?

from wineskin.

Checked all I had inside hidden was .DS_Store

Removed it and same issue, I even using the stock wrapper name of Wineskin-2.6.2 does not work

from wineskin.

That's really strange. Could you please send me your compiled master wrapper so I can try to reproduce the issue? My e-mail is vitormm at portingkit.com

from wineskin.

Once I get back home yeah I will email you the master wrapper I’m using

from wineskin.

Done, I had to email a link due to gmail’s filter system.

from wineskin.

@vitor251093 Ok I tested again with the new version of PK and my most recent commit built, it works but will throw errors about the "WineskinMenuScripts" folder and contents being missing but other then that it built a blank wrapper.

I also tested building a wrapper using PK (Skyrim), other then the above seems to be working just fine now.

I'm leaving this open for the moment incase anything else comes to mind.

I tried to make a wrapper for "Fallout - New Vegas" and it failed to launch the installer exe after making the wrapper, but it did make the wrapper correctly and I could install the game after without issue.

from wineskin.