(*) [EN/RU] Mobile devices / Мобильные устройства

vit9696

2018-04-26 14:52:06

Начиная с пятого эпизода имеется полноценная поддержка iOS 8.0 и новее, а также Android 4.1 и новее.

Для установки на iOS устройства можно воспользоваться сертификатом разработчика Apple Developer или приложеним Cydia Impactor. Для копирования файлов игры рекомендуется использовать актуальную версию iTunes.

Для установки на Android устройства воспользуйтесь FAQ ниже.

————

Starting with episode 5 we have reasonably decent iOS (8.0+) and Android (4.1+) support.

To install the app on your iOS device you could use an Apple Developer Program certificate or Cydia Impactor application. To copy game files the latest iTunes version is recommended.

To install on your Android device you may follow the FAQ below.

[+] Spoiler: Game path:
The game should be stored on any sdcard (emulated or external) in ONScripter-RU folder in the root of the sdcard.
* All the saves will be stored on the internal (emulated) sdcard due to external card being unwritable on some deivices/firmwares. For this reason you are not allowed to have ons.cfg (do not confuse with default.cfg) in the game folder if it is stored on the external sdcard.
* On some devices it is not possible to easily determine external sdcard path, and the game will fail to launch. If this happens create default.cfg file in ONScripter-RU folder on your internal (emulated) sdcard with 'root=/full/game/path' line without quotes.

Compatibility:
The game targets any armv7s, arm64, or x86 droid device on firmware 4.1 and newer, with at least 2 gigabytes of RAM and OpenGL ES 2.0 support with at least 4096 pixel texture dimension limit. However, newer os versions are generally preferred.
* Starting with droid 4.3 it is possible to use OpenGL ES 3.0 renderer on supported device models.
* Starting with droid 4.4 it is possible to use the whole screen space.
* Starting with droid 5.0 it is possible to gain from using 64-bit CPUs natively on supported device models.

Fixing visual glitches:
Some devices need render-self=no ons.cfg option to fix visual artifacts.

Fixing cropped image on wide-screen devices:
You need to update to r3569 or newer and specify manual screen offset used to shift left the game image in ons.cfg. For example, on Redmi Note 9 Pro with 2400x1080 screen it is system-offset-x=180.

Performance:
There are multiple performance issues at the moment and thus you should take good care of the configuration options described below.

Choosing renderer:
By default ONScripter-RU uses OpenGL ES 2.0 renderer and falls back to OpenGL ES 3.0 if OpenGL ES 2.0 renderer failed to initialise or if 'renderer-blacklist=GLES2' line is present in ons.cfg (!). OpenGL ES 3.0 may not be available on some devices, however, it may deliver slightly better performance.

Enabling hardware video decoding:
By default ONScripter-RU has hardware video decoding disabled on droid due to poor performance. However, you may be able to reduce power consumption by enabling it via 'hwdecoder=on' line in ons.cfg. Note that 1080p video playback is not guaranteed on any mobile devices regardless of this option.

Fallback texture loading:
When using OpenGL ES 2.0 renderer on certain devices you might be able to improve certain texture loading performance (e.g. Config menu) by using additional RAM caching. To enable this add 'texture-upload=ramcopy' to ons.cfg. Note that it may cause crashes on lower end devices having not enough memory. This setting is ignored when using OpenGL ES 3.0 renderer.

FPS limit:
You may be able to improve game performance and seriously reduce power consumption by limiting game fps to a lower value than 60 frames per second. To do so add 'force-fps=30' line to ons.cfg, where 30 is your preferred value. Note that you could additionally add 'force-vsync' line to ons.cfg to enable old-style vertical synchronisation, however it will unlikely benefit you in any way. Not setting a fps limit may result in getting rendering glitches like black stripes appearing in some scenes on some hardware.

Texture size limit:
You might get slightly better performance in some scenes by limiting the supported texture dimentsion limit to a lower value than your device supports. To do so add 'texlimit=4096' line to ons.cfg, where 4096 is a power-of-two value in pixels.

Getting log dumps:
You should install some adb drivers for your device, and then use command-line utility to obtain the necessary output. For example, on UNIX-like systems you could use:
adb logcat | grep --line-buffered -Ei 'sdl|onscripter' > /path/to/my/log.txt

Touch controls are the same for iOS and Android:
— single finger tap for left click
— double finger tap for right click
— triple finger tap for middle click
— two finger swipe for scroll
— three finger swipe right is skip
— three finger swipe left is automode
— three finger swipe up is mute
— three finger swipe down is tab (skip to next chapter)

Ginand

2018-05-04 18:59:26

I keep having an "Invalid launch directory! error even though everything is seemingly in the right place. I triple checked all the folders and files. The file size is matching up. It's basically just been copy pasted from my PC folder (the .exe is working stunningly) onto the phone.
Everything is in "ONScripter-RU" which is in turn placed into the root folder, yet it seems like it doesn't even acknowledge the folders being where they're supposed to. I tried it with adding "root=ONScripter-RU" to default.cfg, but that was pretty much a wild attempt due to hitting a brick wall.
Any advice on what I can try next? Does the .apk perhaps drop a debug log somewhere?

vit9696

2018-05-04 19:24:00

Hi,

Unfortunately it is not possible for us to determine where the game is as Android does not offer any APIs in this direction. It is unfortunate, but as a result your idea about editing the default.cfg file with the root line is pretty much what one needs to do.

This line should contain not a relative (i.e. ONSCripter-RU) but actually a full path your sdcard. For example, one of our users had to add:

Code:

root=/storage/0000-0000/ONScripter-RU

I think the software like "ES File Explorer" offers you a way to obtain the full path. Another way could be trying the adb.

Also, one of the common causes of visual glitches on Android is self-rendering, so if you get them try adding "render-self=no" first

Ginand

2018-05-04 19:37:55

Thank you for the fast reply! Much obliged!
My apologies though, I meant to write down the full path but forgot after doublechecking the folder name. The actual path used was /storage/emulated/0/ONScripter-RU and I didn't have any luck with it.

vit9696

2018-05-04 19:41:15

Hmm, are you sure you added that to the correct default.cfg?
The thing is, you should not add to the ingame default.cfg (ONScripter-RU cannot find it), but actually to ONScripter-RU folder the game created itself to point the engine to the right sdcard. It should be in internal storage.

Ginand

2018-05-04 20:08:39

That's probably it. Any pointers on where the apk generates the folder(or the exact name)? I had no luck searching the data manually nor over the search function.

vit9696

2018-05-04 20:50:18

I checked out the code, and it looks like we try our best effort by looking at the following environment variables and attempting to create ONScripter-RU directory in their root: EXTERNAL_STORAGE, SECONDARY_STORAGE, EXTERNAL_SDCARD_STORAGE.
Basically this should create a directory in the root of (some) of your memory where DCIM folder (the one to store photos) is. If it does not work, you can always create ONScripter-RU folder there yourself and put there a default.cfg file with just a root=/path/to/game line.
Good luck!

Ginand

2018-05-04 22:10:18

That's interesting. It didn't generate at all for me. Subsequent uninstallations and reinstallations made no difference either. And the attempts to make one and put the config inside didn't bear fruit either. This shouldn't require a rooted device, I believe, right? I'm positive the issue is that the path isn't getting recognized. So close.
It'd be convenient to see an example of a configuration that worked, but sadly none on the dev team use android, right?

vit9696

2018-05-05 01:41:51

No, there definitely is no need to have root. Could you tell us a little more about your device? Android version, the amount of SD cards and their full paths (internal and external whatever it names them), the firmware name/build, perhaps the model name.

We got our hands on a couple of devices during Android support development, and it worked out of the box, i.e. recognised the storage paths and we did not need to specify anything like that. Problems like you face only seem to appear at our tester devices, and thus the workarounds. There was not the case where it did not function entirely, so if you have enough patience I am sure we can resolve this.

Might you have some courage to help us debug it? I know it may sound painful, but without logs there hardly is a way to understand what is going on. Could you please install adb on your PC and run adb logcat? There is a very good how to on how to install adb: https://www.xda-developers.com/install- ... cos-linux/

After you obtain the logs (adb logcat > log.txt) please upload them here (you may need to archive them or just copy-paste under a spoiler). You can filter the contents by sdl/onscripter-ru. If you think the file contains any private information, you may PM me.

Ginand

2018-05-05 11:38:03

Thank you for your patience. I was afraid of bugging you folks with this too much with this. I'm off to vacation in a few days and really hoped to get this version of Umineko up and running on mobile to help fill the long rides.
Model: Lenovo Moto G5
Android Version: 7.0
SD Card: One, but it's been formatted to serve as an extension of the internal storage. So there's only storage/emulated/0/
I currently have it set as storage/emulated/0/ONScripter-RU (only has the configuration file) and a separate directory for the game to which the .cfg leads to. Same error though.

Now, a few interesting things happened. I was getting the usual error until I started debugging. While the log dump was happening, I opened the game again so the log gets the necessary info. The error has changed, this time not starting due to a opengl resolution error. I checked the config to see if the resolution was set as too high (it wasn't), and went back to start the game and write down the error. Except this time the game actually booted up and started verifying game files.
I'm not entirely sure how android indexes file, but considering the bigger filesize, could it be possible that renaming the folder... actually took this long to take effect? Odd.

EDIT:
Interestingly enough, the game returns to being unable to start if the rendered is changed.

There is some noticeable visual tearing on some textures (like character mouths), but I can live with that.
Great work on this project!

vit9696

2018-05-05 12:22:41

What the— Well, at least it started to run now.

I think the most likely issue could be that you were editing default.cfg in Windows and used Windows Line Endings or UTF-8 Byte Order Mark. While it is supposed to handle Windows Line Endings (CRLF) now, perhaps a bug is still there. Consider downloading Notepad++ (https://notepad-plus-plus.org) or some other more functional editor and setting Unix Line Endings (LF) and UTF-8 without BOM for default.cfg.

This tearing should almost certainly be solved by adding the following line:

Code:

render-self=no

Ginand

2018-05-05 12:56:17

I've only edited the file over the phone itself, so it should have been fine (subsequent edits all worked out well too).
Thank you, that line solved the tearing and it runs nearly perfectly at the moment.
The only issue that after a while the screen turns black and a restart is necessary to continue. It's probably related to the device running out of memory, so I'll play around with some additional settings to see if it can be resolved.
Otherwise, perfect

vit9696

2018-05-05 13:12:41

That is good to hear. Unfortunately not much I can tell about black screens, but yes just 2 GB of RAM on Android could be more problematic than on iOS. We will see if we could improve the situation in the future.

Ginand

2018-05-05 20:11:38

No problem, I can live with it. The rest works marvelously.
Thanks again for your time and effort!

Rim Yroto

2019-04-23 13:07:32

Здравствуйте! Столкнулся со следующей проблемой: во всей игре присутствуют артефакты в виде пиксельных полос.
Устройство: Xiaomi Mi Mix 2S
ОС: Android 9
UPD. Помогло добавление строки render-self=no в ons.cfg

[+] Spoiler

: Если посмотреть на Кинзо; Screenshot_2019-04-23-15-48-07-097_org.umineko_project.onscripter_ru.png (1.72 MiB) Viewed 17660 times

: Или на название игры; Screenshot_2019-04-23-15-49-13-541_org.umineko_project.onscripter_ru.png (2.74 MiB) Viewed 17660 times

Dittorita

2019-06-25 23:15:57

I'm having the same issue as the above commenter, regardless of renderer or resolution. I'm using a Galaxy S9 on Android P.

vit9696

2019-06-26 07:36:27

Well, the answer is in the same post, although I guess it may be hard to read Russian for a non-native speaker

Add render-self=no line to ons.cfg, and it will work.

Dittorita

2019-06-26 16:58:03

Ha, you're right! I copied it into Google Translate, guess I missed the last line. Thanks you two.

Roak

2019-07-08 14:03:57

Are saves compatible between Android and PC? It would be cool if I could read on my phone and then copy the save onto my computer and pick up from there.

vit9696

2019-07-08 14:20:12

Yes, they are compatible.

Roak

2019-07-08 14:46:09

Sweet! I have a ten hour plane ride in a week so now I know what to spend some of that time on.

M1iraiNikki

2019-10-09 22:48:07

Может кто на русском обьяснить как фиксануть ошибку Invalid launch directory ? на андроиде

M1iraiNikki

2019-10-10 08:30:07

M1iraiNikki wrote: ↑10 Oct 2019, 01:48 Может кто на русском обьяснить как фиксануть ошибку Invalid launch directory ? на андроиде

все ,фиксанул

levalas

2019-12-15 23:44:14

Здравствуйте! Не могу запустить игру, всё скачал, установил, идёт проверка файлов и дальше нет прогресса, подскажите что делать, телефон Xiaomi Redmi 6, android 9.0, 3 gb Ram, игра стоит на внутренней памяти.

vit9696

2019-12-15 23:54:03

Добрый вечер, в некоторых случаях этот процесс небыстрый, стоит подождать до получаса.

levalas

2019-12-16 18:47:18

А что делать в случае, когда игра через некоторое время не показывает bg, а чуть позже исчезают спрайты и от них остаются только рты, а ещё через время зависает, а то и хуже вылетает?

vit9696

2019-12-17 18:14:52

Можно попробовать сначала использовать render-self=no в ons.cfg, если не поможет, поиграться с настройками кэшей. Игра требовательна к ресурсам, потому вылетать время от времени будет неизбежно.

levalas

2019-12-17 22:01:20

vit9696 wrote: ↑17 Dec 2019, 21:14 Можно попробовать сначала использовать render-self=no в ons.cfg, если не поможет, поиграться с настройками кэшей. Игра требовательна к ресурсам, потому вылетать время от времени будет неизбежно.

Спасибо! артефакты исчезли, но вылеты остались, но это терпимо

Yurimaru

2020-01-09 17:13:56

Здравствуйте. Невозможно запустить игру, застрял на верификации файлов. Все бы ничего, я бы подождал, но с течением времени просто появляется черный экран - и все.
Добавлял env[verify] none в ons.cfg тоже не помогло, как начинает верифицировать так и застревает.

Также добавил render-self=no но артефакт все еще находится на своем месте.

Я что-то не так делаю?

Благодарю за ответ.

Телефон OnePlus 7 Pro, 8GB. Android 10

вот как все выглядит.

[+] Spoiler

Упомяну что он отказывается использовать GL2.

АПД: С артефактом разобрался, его оказывается по ошибке вписал в дефолт.

vit9696

2020-01-09 18:47:15

Добрый день, для пропуска верифкации можно вписать env[verify]=none, но с этим нужно крайне осторожно. О причинах чёрного экрана ничего сказать не могу, возможно что-то с производительностью или повлияло отсутствие render-self=no при проверке.

Yurimaru

2020-01-09 19:17:55

Так в том-то и дело, что env[verify]=none не работает, игра упорно грузит верификацию. Я бы с удовольствием прошел верификацию, на компьютере все было хорошо.

Я понимаю что нужно осторожно, но я уже второй день не могу пройти верификацию, и убрать тоже не получается (

Приложение вообще падает через 10-15 минут, хотя верификация еще не закончена.

Рендерселф тоже вписан, но он работает, артефакт пропал.

Может быть другой рендеринг нужно вписать? Я не знаю уже что делать.

Вообще лучше запаковывать ресурсы в единый файл наподобие .dat имхо, так легче будет проверить все ли на месте, и передать на телефон файлы по mtp. Когда приложение вынуждено сотню тысяч отдельных файлов проверять по хэшу, юзерэкспириенс немного страдает(((

Кстати, насчет производительности, мой телефон в топах за 19 год, вряд ли он чем-то хуже других в этом плане.

Может есть идеи? Сейв файлы какие-нибудь, позволяющие мимо этого пройти.

Апд:
Так выглядит когда я переключаюсь с этого приложения на другое. Может он зависает задолго до черного экрана? Не могу понять, анимации нет.

[+] Spoiler: https://pasteboard.co/IPd2KoQ.jpg

vit9696

2020-01-09 19:32:27

env[verify]=none совершенно точно работает, проверил у себя. Возможно куда-то не туда добавлено, нужно в ons.cfg. У меня на iPad верификация проходит за пару минут, так что 10-15 вряд ли норма даже для Android.

Для поддержки единого файла нужно дорабатывать движок, сейчас это никто делать не будет. Впрочем, код открыт, можно прислать патч =)

Yurimaru

2020-01-09 19:37:12

Заработало xD
Хохма состояла в том, что я написал env[verify]=none без знака равно.
Все же проверка ресурсов не удалась, увы, надо тут тоже галочку поставить. Буду читать на свой страх риск.

В любом случае, спасибо!

vmarcelo

2020-03-10 22:02:09

Anyone had this problem too?

https://m.imgur.com/a/UfhPMKd

seth1910

2020-07-01 03:14:44

So is this can be used for 07th-mod version ? or just for umineko project ?

ShoukoMi

2020-11-24 07:47:22

распаковал игру по пути "storage/0/ONScripter-RU/umineko" . добавил в default.cfg строчку "root=/storage/0/ONScripter-RU/". но движок упорно не видит игру. что сделал не так?
redmi note 9s 10android 6ram

ShoukoMi

2020-11-24 19:04:59

Та ошибка пропала, спутся 5 переустановки. Теперь No compatible game script found

ShoukoMi

2020-11-24 19:26:32

Божьей помощью победил. Изменил игровой default.cfg на ons.cfg, и создал другой с путем игры. Теперь при заходе пишет что битые бекграунды. Попробую перекачать

lustre

2020-12-06 22:49:46

Here's hoping someone bumps across this post.

I'm getting a parsing error during the tea party for Episode 1

and have absolutely no idea how to fix it. I tried a few things, but alas - to no avail.

If anyone's got any idea how to fix it, I'd be super grateful. It's been such a comfy reread until now

Giza

2020-12-07 13:31:02

lustre wrote: ↑07 Dec 2020, 01:49 Here's hoping someone bumps across this post.

I'm getting a parsing error during the tea party for Episode 1

and have absolutely no idea how to fix it. I tried a few things, but alas - to no avail.

If anyone's got any idea how to fix it, I'd be super grateful. It's been such a comfy reread until now

I think, do not have the required voice file. Check files
90400072
90400073

luster2

2020-12-07 15:00:16

Giza wrote: ↑07 Dec 2020, 16:31 I think, do not have the required voice file. Check files
90400072
90400073

Ah, that was my first guess yesterday. But I was looking for a missing file in ./Umineko/sound/voice/13 that would start with "1" (as in: chapter 1). And I did find a few files that skipped the n+1 convention, so I tried putting an .ogg file with 1 second of silence in those "gaps", but it didn't do the trick.

What I didn't expect is that the tea parties have a prefix of their own. And sure enough:

ZArchiver must have skipped 90400073.ogg when I was unpacking the archive.

I put in a blank 90400073.ogg file and everything's A-okay now:

All I can say is: thanks for a super quick response. Back to reading and being amazed at the sheer amount of work the team put into this project. Thanks!

Had to make a new account since there's an issue with password recovery, I think. Don't be mad at me, please.

vit9696

2020-12-09 09:47:12

Had to make a new account since there's an issue with password recovery, I think. Don't be mad at me, please.

Some mail providers have mail delivery issues. Usually Microsoft is broken.

Zeatheon

2020-12-24 08:53:22

There are some weird dots on all of the sprites or any animated sprites. Tried changing the resolution and the renderers but the results are the same.

Attachments

: Screenshot_20201224-163658.jpg (52.44 KiB) Viewed 19839 times

ooa

2020-12-24 09:07:11

Zeatheon wrote: ↑24 Dec 2020, 11:53 There are some weird dots on all of the sprites or any animated sprites. Tried changing the resolution and the renderers but the results are the same.

This is generally an issue with self-rendering. Use "render-self=no" in ons.cfg.

Zeatheon

2020-12-25 05:16:58

ooa wrote: ↑24 Dec 2020, 12:07
Zeatheon wrote: ↑24 Dec 2020, 11:53 There are some weird dots on all of the sprites or any animated sprites. Tried changing the resolution and the renderers but the results are the same.
This is generally an issue with self-rendering. Use "render-self=no" in ons.cfg.

Thanks, it worked.

MakotoShinji

2021-02-12 17:38:37

Can anyone upload Umineko android downloading tutorial video on YT?

shikkakun

2021-02-17 20:59:40

Hello.
I'm trying to play on a device with Android 11 system.
Since when I tried to zip the files, the program told me the following files couldn't be transferred because they have an invalid number. I tried to open the game and the game also won't initiate because of this. I'm attaching a screenshot. Sorry if this is not a good hoster for photos. https://ibb.co/dgPQ5mz
I also tried copying the files from my computer (I also have it installed there) to my cellphone but my cellphone doesn't recognize it no matter what. I can't transfer the file or even create a dummy, because that character is not valid (this one )

Thanks in advance for your help.

ndgnuh

2021-03-04 08:13:29

How do I fix this weird offset problem on Android? I have tried every kind of window size and rendering configuration but it doesn't help. Thank you!

My phone model is Redmi Note9 Pro. I notice some other readers have this problem, too. Maybe it have something to do with 16:10 screen.

vit9696

2021-03-09 20:01:00

Apparently adding fullscreen option should fix this behaviour.

Addressed in https://github.com/umineko-project/onsc ... afcd1d907d
Updated the first post. You need to specify system-offset-x=N with suitable N value for your system.
Thanks a lot to ndgnuh for discovering this.

Kami39

2021-04-01 03:14:10

Two problems.

One, the touchscreen won't work. I'm using a Samsung s10 Lite.

Two, after using a wireless controller I could start the game but the game occupies only the top left of the screen.
http://imgur.com/a/cGITX56

Would appreciate an answer to the second problem.

vit9696

2021-04-03 11:29:08

You can try to workaround the issue by using system-offset-x/system-offset-y from the post right before yours.

chidosir

2021-04-11 11:50:47

Are there any tips to improve performance, besides what's mentioned in the first post? Playing on a Xiaomi MI A1 (SD 625, Adreno 506, 4gb ram) and while it is playable some animations seem to run at a low framerate. The text as it comes is pretty choppy most times, and the lip syncing as well. But there are other times where some of the other animations in the scene are silky smooth for some reason, even while these ones are chugging. It makes me think that maybe there's some way to improve the situation.

vit9696

2021-04-11 22:16:41

Hardly unfortunately. Playing longer should generally make it better thanks to caching, but otherwise no. The game is very hard to optimise unfortunately.

Miskuzi

2021-07-12 15:35:37

Не могу редачить ons.cfg. Когда пытаюсь добавить "render-self=no", чтобы от артефактов избавиться, игра перестает запускаться с ошибкой "Invalid launch directory". Я уже менял этот файл когда только играть начал, все было норм. Сейчас я уже на 5м эпизоде, и вот вчера зашел в игре в настройки, переключил с openчто-то там с 2 на 3 и затем обратно. Видимо это как-то повлияло на этот ons.cfg, что теперь его не то, что вручную менять нельзя, я и язык с en на ru не могу поменять, опять вылетает та же ошибка. Поэтому в итоге просто имя файла русского поставил en.file. Но вот с артефактами на спрайтах без редактирования ons.cfg не справиться...

Miskuzi

2021-07-12 16:50:03

А теперь я вообще делитнул через приложения onscripter и папку с ним (там где сейвы хранились), насколько я понял, при установке апк эта папка создавалась автоматически и там вручную создавался default.cfg с путью до игры на внешней карте. Щас устанавливаю заного апк и эта папка не появляется... А если вручную ее создать и там так же вручную default.cfg с путью, то ошибка инвалид диреетория опять...

Miskuzi

2021-07-12 17:43:38

Так ладно, пофиксил... Вся трабла оказалась в кодировках.
То есть при смене настроек уже после старта игры, он перезаписывает файл ons.cfg и ломает ему кодировку, так как это все же приложение для пк? Ну я так понял. Хотя присмене разрешения в настройках игра запускалась, а при смене GL и языка переставала.
Ну и когда вручную редачил ons.cfg, походу тож при сейве была не та кодировка, скачал специализированную прогу с указанием кодировок при сейве файла и все заработало.

vit9696

2021-07-12 19:06:01

Что-то очень странное, там нет русских букв, только латиница, потому кодировка не должна иметь значение. Файлы сохраняются с окончаниями строк Windows (CRLF), чтобы обеспечить совместимость с редакторами текста в Windows (блокнотом). Возможно имеющийся редактор как-то с ними работает некорректно. Если скините файл, возможно что-то можно будет сказать.

Лично я редактирую ons.cfg в Sublime Text. На Windows ещё есть Notepad++.

gizmo36

2021-07-29 13:36:24

Hello! I can't copy some files to my device due to unsupported characters:

Code:

sound/voice/05/31000123.ogg
sound/voice/18/11800172.ogg
sound/voice/11/42001328.ogg
sound/voice/34/31000123.ogg
sound/voice/13/40400245.ogg
sound/voice/09/11300039.ogg

Is there any solution?

Samsung A71, Android 11

chidosir

2021-08-05 18:28:11

chidosir wrote: ↑11 Apr 2021, 14:50 Are there any tips to improve performance, besides what's mentioned in the first post? Playing on a Xiaomi MI A1 (SD 625, Adreno 506, 4gb ram) and while it is playable some animations seem to run at a low framerate. The text as it comes is pretty choppy most times, and the lip syncing as well. But there are other times where some of the other animations in the scene are silky smooth for some reason, even while these ones are chugging. It makes me think that maybe there's some way to improve the situation.

just for additional info, after updating to a samsung galaxy a52 (SD 720g, adreno 618 and 6gb ram) the game now runs very smoothly at >90 fps.

if anyone here has problems with the game constantly crashing at startup I solved it by using the following ons.cfg and enabling gestures for the navigation bar (seems that there's an issue with the virtual navigation bar for some reason).

Code:

fullscreen
render-self=no
texlimit=2048
prefer-renderer=GLES3
force-fps=90
game-script=en.file
window-width=1080
scale

also for me (and probably others with >full hd resolutions) the game was shoved up in the left corner. I did see on github a release talking about a "system-offset-x/y" argument but that didn't do squat for me. what did work was going into settings, display, fullscreen apps and enabling it for this game, but not sure if this is a samsung or android wide setting. hope this helps somebody.

vit9696

2021-08-27 07:04:52

gizmo36, these files are no longer required as of https://github.com/umineko-project/umin ... be2017bb99, it was bug. Ignore them and update to the latest release: https://github.com/umineko-project/umin ... ses/latest.

otter

2021-09-16 02:05:01

Hey, so I've managed to get over several installation process issues until now and I'm currently stumped. I've already figured out I have to extract the .7z files on PC (it always errored out while extracting in android).

Phone is Samsung A51, Android 11. Updated files to r4005.
I have the game files in external SD, /0000-0000/ONScripter-RU, and I had to manually make an ONScripter-RU file in internal, /emulated/0, with a default.cfg pointing to external SD to get over the invalid directory error. Not having issues with game alignment and game file verification even gave me an "All good!" but never starts the game. It only created a savedata folder in internal (no ons.cfg, attempts to add a blank one manually to either internal/external folders brings me back to invalid directory error).

: Screenshot_20210915-181817.jpg (113.25 KiB) Viewed 19023 times

That is as far as I have gotten and no matter how long I wait it does not start. On Mac I can just close and restart and it plays the game but on android it goes back to re-verifying the files.

Here are what my internal and external folders look like, the external one possibly can't be edited by the game hence the issues? https://imgur.com/a/PaQyBBM

EDIT: here's the logcat filtered to only onscripter-ru entries, ran it while the file verification process was ongoing until past the "all good!" message, until entries slowed down. https://ghostbin.com/paste/Pf48b

Thanks in advance

vit9696

2021-09-26 20:34:04

Perform two-finger tap on the screen after completing the verification.

Haku219

2021-10-15 17:22:07

I'm having a weird issue on Android with a Snapdragon 855 device where there's severe input latency for single taps, but not for double taps or any of the swipe gestures. So it wouldn't be performance related or anything. Is this normal? Is there anything I can do about it?

I'm playing the game with the Japanese patch, but as that just changed the fonts and script, I don't think that's the cause.

Miskuzi

2021-12-28 06:48:43

При разрешении не 16:9 полетели влево кнопки.
То есть на экране вот есть кнопка, но чтобы на неё ткнуть, надо тыкать пикселей на 300 левее самой кнопки. И ещё почему-то правый край изображения обрезался (насчёт левого не знаю, справа просто меню и это заметно).

Так, почитал тему, добавляю system-offset-x=180 в ons.cfg, но после этого игра перестаёт запускаться. Просто при открытии моментально закрывается.
Хотя у меня разрешение немного другое (не 2400, а 2460). Чё-то там посчитал, пересчитал по этим "формулам" получил 210, но всё равно не работает.

Через настройки игры поставил "В окне" и 1920 ширина, заработало. Когда стояло "Авто", то не работало.