leycec / kiseki-linux Goto Github PK

This is a minor problem but it could be puzzling to some users.

The current link goes to the MEGA-hosted filelocker folder used for the Japanese dialogue voices linked just before, instead of this link to the actual folder of the Japanese battle voices.

Hi,

I tried using this installer today, but I could not get it to work, no matter what I did. After selecting all of the required files in the installer window and clicking the Continue button, the input fields for the GOG .bin file and the ZIP file for the japanese dialogue disappeared, whilst the input fields for the .dat and .dir file remained.

I could not get past the screen where you select the required files no matter what changes I tried making to the installer file.

I'm using Lutris 0.5.8.3 on Fedora 33.

Any help with this would be greatly appreciated.

If you need me to provide more information or doing testing then I'd be happy to provide both.

Hey there, me again! I finally had time to actually sit down and play, when I discovered to my abject horror that there wasn't any voice acting! Shocked, petrified, unable to move, I stared blankly down at my Steam Deck, then everything went black. The trauma was too much to bear.

At least seven hours later, I regained consciousness and picked myself up off the floor. After having a nutritious glass of several thousand spiders, I decided to try and investigate what could be causing this problem.

It turns out that there was an update to the game in January of 2022 that was incompatible with SoraVoice Lite. If you download the latest update for SoraVoice and overwrite everything, the voices work as they should.

Problem solved!

Hey there, having an issue with this script where it basically fails at the first juncture when it tries to symlink the bin file as it believes that one has already been made. I did try using the other TitS script (the one that doesn't include mods) first, which repeatedly failed at last step where it's supposed to launch the config tool, but I'm not sure if that would affect this at all.

Is there anything you would like me to provide to help nail this down?

I'm using lutris v0.5.12 with nvidia prime render offload(I have a laptop). Game doesn't open when I enable Virtual Desktop option, I can play without enabling that option. Wine version that I'm using is lutris-GE-Proton7-35-x86_64, OS: Fedora 37.

Other than that, guide is really nice. I installed the mods myself but game was lagging really hard. Enabling Hardware Vertex Shading fixed my issue. Thanks for the great guide and hard work!

Edit: It is an issue with prime render offload option. If you disable it, Windowed(Virtual Desktop) option will work, however you will play with integrated graphics card.

This non-issue archives images intended for external display in front-facing README.md documentation and thus does not constitute a genuine issue. While this arguably constitutes a mild misuse of Github resources, Github currently supplies no saner means of effecting this. Conventional alternatives (e.g., Github Pages) all require committing these images to this repository itself. Unacceptable.

Let's primly circumvent that, shall we? To upload GitHub-hosted images here, simply:

1. Copy the contents of the desired image to the clipboard. Do not copy the current URL of that image if any. Under Firefox, for example:
   1. Right-click the desired image.
   2. Click Copy Image.
2. Edit this issue.
3. Page down to the end of the existing Markdown for this issue.
4. Paste the current contents of the clipboard (e.g., by hitting <Ctrl-v>).

Images

@agh1467: We summon thee! Your steaming brilliance is humbly requested.

There are three additional things (in no particular order) we should do to fully support the phenomenal new Steam installer for Sky FC submitted by @agh1467 at PR #7:

1. Publish an official Lutris-hosted Steam installer. Based on past experience, I should probably be the one to do this. Lutris moderators have a tendency to ignore or delete submissions submitted by anyone else. It is what it is. That said... I should probably only do this after you've finalized any prospective changes to the Steam installer, @agh1467. A zenity-based dialog instructing the user on what to do, possibly?
2. Document Steam support in our README.rst documentation. Anyone can do this! Annnnnnnyone. 😉
3. Document Steam Deck support in our README.rst documentation. I assume Steam Deck just kinda works, but... I've assumed many things in my life. Now I live in a cabin in the Canadian wilderness. Kids, this is where assumptions get you.

Thanks so much for all the hard work, @agh1467. You amaze and you stun me! 😮