ติดตั้ง Steam
เข้าสู่ระบบ
|
ภาษา
简体中文 (จีนตัวย่อ)
繁體中文 (จีนตัวเต็ม)
日本語 (ญี่ปุ่น)
한국어 (เกาหลี)
български (บัลแกเรีย)
Čeština (เช็ก)
Dansk (เดนมาร์ก)
Deutsch (เยอรมัน)
English (อังกฤษ)
Español - España (สเปน)
Español - Latinoamérica (สเปน - ลาตินอเมริกา)
Ελληνικά (กรีก)
Français (ฝรั่งเศส)
Italiano (อิตาลี)
Bahasa Indonesia (อินโดนีเซีย)
Magyar (ฮังการี)
Nederlands (ดัตช์)
Norsk (นอร์เวย์)
Polski (โปแลนด์)
Português (โปรตุเกส - โปรตุเกส)
Português - Brasil (โปรตุเกส - บราซิล)
Română (โรมาเนีย)
Русский (รัสเซีย)
Suomi (ฟินแลนด์)
Svenska (สวีเดน)
Türkçe (ตุรกี)
Tiếng Việt (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
But you can bet your *** on it, that there will be a cheat engine script for increasing that to a more proper value (usually a simple float value increasing and decreasing, also most likely a pointer, since its a static function).
Setting the FOV as +25 bonus feels like regular FOV70~75, nothing which most of the people will be satisfied with.
Got the pointer:
GhostOfTsushima.exe+19E8474
Float. Moves between 0.75 and 1.25.
Can be set to 1.60 (maximum value which works) for higher FOV.
Have fun.
Could you please share your cheat table?
There is no need for an entire table for that, since its just a very simply address addition process, as the "hardest" part of searching for the offset has been done by me already.
A cheat table would be better which i'm still working on.
Those rather require ASM coding (the "cheat table" approach), and are more likely to break with an any amount of new code being added BEFORE those offset-segments. So, there is also a chance that those won't break, if devs would consider (and can actually consider) adding new code at the end of their source executable.
Thank you so much! I spent hours trying to figure this out yesterday!
Do you know if there is a way of doing that??