Comments
- edited 11:37AMWe don't officially support Mac, but if you upload the output_log.txt file I can have a look.
In 0.6.2 we changed the way interactions are stored. They're now compressed, and upon load they're uncompressed to a temporary location and then read. I'm guessing that temporary location thing maybe doesn't work properly in wine? For the technically interested, it's System.IO.Path.GetTempFileName(); that we're using. - edited 11:37AMMaybe having a promp asking where you'd like the interactions to be saved, either the old, new, or maybe manually choose a location; this could help down the road when the possible Mac version get going.
- edited 11:37AMfrom what i've seen of Wineskin, it stores everything in the .app container itself.
while i haven't been able to get it to run quite yet i did notice that there isn't a 'Roaming' folder under {User}AppData which is where %appdata% normally maps to in windows.
if you copy a .yiff file to '.drive_cusers{your user}AppDataRoamingyiffaliciousinteractionslocal' does it show up in game?
are you getting an output_log.txt in the yiffalicious_Data folder?
and did you use the installer or the zip file to install into the wrapper? - edited January 2017@jei3 : yes I am getting a output_log.txt file in the yiffalicious_Data folder I haven't had the chance to look at it though. I used the installer, not the zip. I did try to copy a .yiff file to the local interactions file, they are not being read. The fact that I can not dl from the cloud may be an indication of the problem.
@odes: no need to waste your time. As you said it's not a supported platform, I'll play around with it a bit and see what I can come up with. - edited January 2017sorry for any confusion, i dug into this further and the paths are wrong in my post, apparently Wineskin doesn't use Win7 style paths, even if you tell it to run as if it was Win7:
but other apps that are coded to reference Environment.SpecialFolder.ApplicationData do seem to work, so i doubt the ApplicationData folder is the issue.
The System.IO.Path.GetTempFileName call on Wine in OSX however does some weird stuff and fails when i try to get a temp file:
On Windows the path looks more like this: - edited 11:37AMI'm changing System.IO.Path.GetTempFileName to a custom method for the next build so it will (hopefully) work with Wineskin.
- edited 11:37AMi can't run the game in my OSX environment (no 3d card), but if you need the method checked out i'll be happy to help.
- edited 11:37AM
- edited 11:37AMi'm curious if this fixed the issue, if it was a special path issue the change should have resolved it.
- edited 11:37AMPartially, I can now load from the cloud but loading local interactions still not possible.
i really haven't played with it much, I may find the time later in the month. - edited 11:37AMThat's odd, it should work. I'm interested in your output_log.txt file if you can share it.
- edited 11:37AMThe output_log.txt is available at:
https://drive.google.com/open?id=0B4arJ6EA3nSjQ1NnMC1tZHd2Y1U - edited December 2016this is a weird issue, i was able to get a macOS box set up to test this.
local interactions save correctly and i've validated that they are proper .yiff files, but the load interaction screen shows up blank.
i tested this in 0.6.3b for both the 32-bit installer and ZIP file, both have the issue.
0.5.4 on the other hand displays local interactions fine.
-- edit: figured it out --
the change that broke this is switching from looking for '*.yiff' to '*.yiff?'
i'm guessing it has something to do with ? being valid on macOS's filesystem
i don't see a workaround that an end user can use to get around this, it'll probably just need to be fixed in a later release. - edited 11:37AM
- edited 11:37AMthis was bugging me, so i dug into it a little more, there appears to be a bug with wine's implementation of both DirectoryInfo.GetFiles and DirectoryInfo.EnumerateFiles functions.
if you rename an interaction to .yiffx (where x is an alphanumeric character) it will show up in the local interactions browser, but this isn't a very feasible workaround.
i wrote a quick test app to query for *.yiff? using both GetFiles and EnumerateFiles and saw the same behaviour under wine on Ubuntu as well. - edited 11:37AMGuess I'll just select all directory files and filter them with linq.
- edited 11:37AMsome further testing indicates it's just the question mark (exactly zero or one) that doesn't work right. asterisk (zero or more) appears to work fine.
so '*.yiff*' works, '*.yiff?' doesn't. that would at least give you a smaller list than ALL files. - edited 11:37AMif you rename an interaction to .yiffx (where x is an alphanumeric character) it will show up in the local interactions browser, but this isn't a very feasible workaround.
Nice catch, it's not a bad workaround really. No trouble to rename a file and if I get lazy I can always write a bash script to find and rename *.yiff to *.yiff1. - edited 11:37AM
worsel said: I can always write a bash script to find and rename *.yiff to *.yiff1.
glad i could help, you'll just want to make sure you revert the file names when this is actually fixed / worked around in game. - edited 11:37AM@worsel, 0.6.4 is out now. this should fix this issue without needing to run a seperate script or rename files.
i tested it on macOS 10.12 with Wineskin 2.6.2 + WS9Wine1.9.24 - edited 11:37AM
Wineskin Manual
- Run 64bit Wine 2.6.0 on your Mac OSX system with Wineskin WS9Wine. Their was a tonne of fixes between the 2.6 and 2.21 release. Cheers, Tom January 6, 2018 at 12.
- Run 64bit Wine 2.6.0 on your Mac OSX system with Wineskin WS9Wine. Wine Reviews Wine Reviews has release information and reviews of Windows applications and games running on Linux Mac OS X and Android using Wine from WineHQ.org Q4Wine PlayOnLinux PlayOnMac WineBottler WineSkin WineTricks and Wine-Staging.
Nov 04, 2015.
Wineskin Engine 2.16
Previous Page | Back to ToC | Next Page
Wineskin 2.6.2 Download
Section 2 - Using Wineskin Winery.app
Wineskin 3.0
2.1 Updates
Wineskin 2.6 2 Download
When you first run Wineskin Winery Iffmpeg 5 5 8 – convert multimedia files between formats. , if you are connected to the internet it will prompt you if an update is available. If you update, it should automatically download and install and restart Wineskin Winery for you. If you do NOT update, there can be problems with newer engines or wrappers. If you prefer to manually update, you can go to wineskin.urgesoftware.com and download the newest version of Wineskin Winery manually and install it. |
On the main Wineskin Winery window, once its started, you’ll see an Engine list, and your current Master Wrapper.. if you have any of these installed. If there is ever an updated engine, or updated master wrapper available, you will see a notification on this page. You’ll be able to “update” the wrapper, which is your master wrapper used for creating new wrappers using the Update button right beside it. Keka 1 1 254. If you see an engine available, just click the + button by the engine list to see what engines are available, and get them.. or if you do not want one, you can set them to not prompt you about the selected engine as being new. Previous Page | Back to ToC | Next Page |