Make sure to use the uninstaller of the newer installer, and then reinstall via the old installer on the old thread: https://forums.nrvnqsr.com/showthrea...timate-EditionOriginally Posted by Mangustin
Make sure to only select the "Merge" option because the newer versions of the patches are to be manually installed from the MEGA link on the OP of this thread.
The reason why it is flagged is because it will hook and patch the game executable.
KrkrExtract uses a common chinese library "MyLib" that is also used in other executables, that may be a reason why it will get detected.
It is fine to add it to exclusion.
You may be able to use GARbro to extract the file. Be sure to select "No encryption" or "unencrypted" or the file will not be read correctly.
Thanks a lot, it worked now. I also managed to get the newer fate route translation that I was looking forward to.
I managed to extract the old (2019?) patch.xp3 with a tool called AE, which is good enough for me. Using it on the newest patch.xp3 resulted in all .ks files having weird content inside, which I think is hex? Like this "fefe 02ff fe7a 1c00 0000 0000 00b0 8300". I distinctively remember someone mentioned that the newest Ultimate Edition version had script encryption in place, guess AE couldn't handle it. After finishing the VN I'll try GARbro, thanks Alyinghood.
I am not sure if this has been reported yet, but when playing with 16:9 aspect ratio enabled, some scenes have the top of the image appearing at the bottom of the frame. See example photo.
https://imgur.com/6HXlNb4
This is at Intermission Tohsaka Rin (VI) and other scenes where the black bars appear.
Last edited by BEEFY JOE; March 20th, 2022 at 11:29 AM.
This is a known issueI am not sure if this has been reported yet, but when playing with 16:9 aspect ratio enabled, some scenes have the top of the image appearing at the bottom of the frame. See example photo.
https://imgur.com/6HXlNb4
This is at Intermission Tohsaka Rin (VI) and other scenes where the black bars appear.
Reading the scenario script, I notice some [ruby] tag has o2o=1 in it. Does anyone know what their purpose is? Sample line:
[line3]ここでは、光の速度で[ruby text=いま o2o=1]思考が過ぎる。
One to one placement
What determines the availability of the quality multiplier options? I can only pick 1.6x, and I was wondering why the others are greyed out. Is it just me, or does the patch just not support higher quality options yet?
It didn't support higher resolutions yet. The next version will offer 2.0x, 2.4x and 3.0x as well.
Sorry, I don't understand... Could you expand on your answer please? And oh, is 1 here representing a boolean value or are there other values like 2, 3, 4? Just curious.
Displays one character in ruby for one main character. Value is coerced to integer and checked
Ehh.... So for example for this line:
い will be displayed above 思 and ま will be displayed above 考, right?[line3]ここでは、光の速度で[ruby text=いま o2o=1]思考が過ぎる。
And if o2o=2, then い will be displayed above 思考 and ま will be displayed above が過, is that correct?
If o2o attribute exists and is not set to "", "0", "0.0", "false", "null", or "void", then い will be displayed above 思 and ま will be displayed above 考.
Could you have me with this? I'm trying to understand why would a ruby tag with ・・・・・・・・ would be used here, but the best I can think of is that the thinker here (Shirou) is unable to display his thought properly, hence the ・・・・・・・・, and Nasu then clarified it.
これ以上は望めないという至近距離からのつるべ打ちは、今度こそ本当に、黒い狂戦士の息の根を 止めた。
いや。[lr]それは豪快に、文句のつけようもなく、命を[ruby text=・・・・・・・・ o2o=1]弾き飛ばしていた。
Could be. Or maybe it's trying to convey that Shirou himself didn't even want to picture the graphic details of how the `blowing away of life` happend, so the dots might mean some sort of self-censoring? Like, softening the impact by not spelling it out entirely? And by this hinting to the reader the true gruesomeness of the process.
Last edited by Bohemian Waxwing; March 25th, 2022 at 07:54 AM.
The consecutive dots are for emphasis. Not unlike how we would use italics or bold in English.
それは豪快に、文句のつけようもなく、命を・弾・き・飛・ば・し・て・い。・た
This is how it would look when processed.
That's a new one. Is this a conventional Japanese thing or just a Nasu thing?
The former.
As Nanashi says, it is a common feature in Japanese writing.
Though it is a rather modern convention IIRC.
Posting Permissions
Reply With Quote
