Visual glitches.

Bernkastel77

2017-09-12 14:34:15

Hi vit9696.

Thanks for the fast responses.
It's done. The topic was created.

Here my GPU: http://imgur.com/a/O0Drm

Can you help me? Hahaha.

vit9696

2017-09-12 14:50:44

Hi,

I think I can. From what I can see is that you have an ASUS laptop with AMD and Intel GPUs installed. I think that due to some weird reason Intel GPU is used instead of AMD.

My first suggestion will be to try to force AMD GPU. There is a KB article on AMD website, that explains how to specify the preferred GPU for an app:
https://community.amd.com/docs/DOC-1581

I think I won't be able to explain it better, and it might be a very good idea to try it first.
Also, you probably should undo all the changes you previously made (e.g. ons.cfg changes).

Let me know if and where it fails, in this case we will think of updating the drivers. Could you also specify the exact laptop model?

Bernkastel77

2017-09-12 15:48:05

My PC is desktop, not laptop. It was built. I think it's don't have a specific model.
Also, i don't have this version of AMD Radeon settings, so I trying this with AMD CCC, i found this option (http://imgur.com/a/jSTRj) which I believe is the same.
Maybe if I put onscripter here shall this work? I'll try.

vit9696

2017-09-12 15:55:05

Ah, if it is a desktop, then it is likely that the drivers are just outdated (according to the screenshot they are from 2013).
Just install these ones: http://support.amd.com/en-us/download/d ... ows+7+-+64 and retry.

If it does not help, it might indeed be worth checking AMD CCC preferences, but I think that should not be needed.

Bernkastel77

2017-09-12 16:04:30

To be honest, when I tried solve this by my own, I tried install this "updater", but, for some reason, when the installing proceeds my screen turns entirely black (lol). So I restart my computer and nothing change.

vit9696

2017-09-12 16:16:24

In this case you will firstly have to properly uninstall the existing installation, reboot, and install again (pick 17.9.1 I guess?). Here is a relevant KB article:
http://support.amd.com/en-us/kb-article ... ivers.aspx

It is often good to avoid performing a direct upgrade and use a clean install due to clumsy situations like this.

(Don't worry, even when you remove the drivers, there will still be software driver that does not provide hardware acceleration, so you will be able to boot into Windows)

Bernkastel77

2017-09-12 23:08:13

Hi. Sorry for being late. I had to attend my college.
So now, i'm finally in home.
Well, first of all i'll make it clear: I tried what you just did say to do.
And guess what...? Didn't work.
Again, my screen became entirely black... curiously, this time the installation actually had been finished, but when I rebooted the system, before the windows start, my monitor suffered a blackout.
I searched in google and I found other people which had this trouble in the past. Apparently this is a typical AMD issue.
Buuuut, I was reading the release notes of the 17.9.1 ReLive and then I realized that is a beta version. Maybe, because of this, this fucking trouble occurs.

Now, my last try will be in the 17.7.2, the previous version.
If it doesn't work... well, we'll have to come up with another solution.

Btw, hope you're still awake. Hahahahaha.

vit9696

2017-09-12 23:28:09

Welcome back, you caught me right before heading to bed, so you should probably expect the next reply later in the morning.
I checked the forums, and it indeed seems to be a popular bug introduced in at least 17.4.x branch and still unfixed for several configurations. Goddamn AMD :/

According to https://community.amd.com/thread/217162 17.3.3 was the last one that worked for the topic starter, so I think it is worth trying: http://support.amd.com/en-us/download/d ... rev=17.3.3

If it does not, it might be worth trying a few more older versions, after all anything newer than 13.200.0 you have should be an improvement.

If you get bored in the meanwhile, after some googling I additionally discovered the following suggestions, which might actually be worth trying:
1. Try power off / Start instead of reboot
2. Check if it is only the backlight not working, and not the driver, for that attempt to create/edit the following parameters in windows registry: http://forum.radeon.ru/viewtopic.php?p=887206#p887206, actually since you have a desktop you would probably want 0s instead of 1s

vit9696

2017-09-13 08:35:21

There is something else I want to tell you. We discussed what else this could be other than GPU drivers, and… given that your friend had exactly the same issue with completely different hardware, Giza came up with a suggestion that you might have your game files corrupted. There could be various reasons for that, including:
— Failed extraction (Older versions of certain archivers could silently extract incorrectly O_o, did you use the latest version of 7-zip http://www.7-zip.org?)
— HDD fault

This hardly goes in line with:
My game has several visual glitches and errors, for example, when I try open the config in the title screen, and then I go back to menu, the screen turns entirely black.
But now that we reexamined the screenshots, all of them have missing textures and not even one corrupted/distorted image.
Could you please verify a few files, whether they open, their sizes, and maybe hashes. For example:

Code:

backgrounds/mlib_1b_bg.png, 93 392 bytes, md5 e9f080b0e1aa565ec83ad1deb0c352f8
backgrounds/mlib_1b.png, 3 748 405 bytes, md5 c5c9ce23fd4c328d54c1c8a14b399bf8
sprites/kin/1/kin_a11_defo1.png, 534 633 bytes, md5 396ee45f91174871a86dd12a0d67a081
Firstly it is worth trying to open these files, since they are all plain png images, they should open with any image viewer with no issue. Secondly, you could check the size in file properties. Then, to calculate md5 hashes you could use http://implbits.com/products/hashtab/. If you have any issue or have doubts that everything went right, you may just upload these files here.

Bernkastel77

2017-09-13 16:15:02

First of all, well, I must say that a big fucking misunderstanding occurred between me, you and AMD hahahaha.
Actually, my GPU isn't a real AMD, but a Gigabyte with AMD chipsets.
The specific model is GVR726X, and apparently there is no driver update for this version. If you access the gigabyte website, the only driver you will find will be my current one. So you're right, maybe it has nothing to do with GPU. And no, I didn't use 7zip, I used the old WinRar.

I'll check the files.

Bernkastel77

2017-09-13 16:20:26

Btw, when I install the game in my friend's pc I used the WinRar as well.

Bernkastel77

2017-09-13 16:55:51

vit9696

2017-09-13 17:14:34

The sizes look good, but do the files open fine though? The thing is old WinRAR had serious issues with our archives, so better to check MD5 hashes really.

Now that you say it, I got very confused indeed. Whatever the model is, a desktop discrete graphics card should be able to use the original AMD drivers, and the supplied ones should not really be any different. Notably I found that the latest gigabyte-supplied driver available is 14.4: https://www.gigabyte.com/Graphics-Card/ ... support-dl Might it be worth trying?

On the forums the GPU appears to be reasonably problematic, there even are recommendations to reflash its vbios @_@. Let me know how it goes, and next we will see where could we get.

Given all that strange stuff regarding the hardware, could you make a report with AIDA64 extreme or something? http://www.aida64.com/downloads
I am also interested in what your friends' hardware is. (See PM if you need a key).

Bernkastel77

2017-09-13 17:45:19

I forgot to say, but when i said "my current one" i meant the 14.4.
Actually I had updated to 14.4.
So I really think the problem isn't in the GPU.

Also my friend's GPU is a GTX 765M (he has a notebook).

Curiosly, when i was testing the game on his computer, i found the exactly same errors. Both us PC show the same errors. No exceptions.
So I think the error is due to Winrar indeed.
Should I try reinstall the game with 7zip?

Bernkastel77

2017-09-13 17:50:07

And... I can't acess the aida64 website.
"Your connection is not private"

vit9696

2017-09-13 17:52:57

Exactly the same errors sounds very worrying. If it does not hurt too much, please reinstall with 7-zip.
Let's wait for this before taking any further steps, perhaps it could be the culprit.

Bernkastel77

2017-09-13 18:15:37

Just to be sure.
Nothing was missing, right?
Need a specific order to extract the files?

https://imgur.com/a/czxPK

vit9696

2017-09-13 18:17:38

This is correct. The only exception is to always extract extra, scripts, and onscripter after everything else.

Bernkastel77

2017-09-13 19:00:36

Sorry for the delay.
Well... didn't work. \=
The errors remained.

vit9696

2017-09-13 19:09:28

Okay.

Firstly, please could you confirm that you continue to get this exact issue at this exact scene in ep1 prologue https://imgur.com/a/rPdoC over the game restarts. And it never shows Kinzo sprite/library background.
Next please ensure md5 checksums match (see this post: Visual glitches.).

If you are not fully positive about it, simply attach the files (backgrounds/mlib_1b_bg.png, backgrounds/mlib_1b.png, sprites/kin/1/kin_a11_defo1.png) to the forum. This probably will be the most definite way to conclude that there is nothing wrong with the files.

Then additionally create a report with AIDA64 and attach it here as well (there is Reports → Create report menu). You will need to create a zip/rar archive first. Use this direct link for downloading, it will work fine: http://download.aida64.com/aida64extreme592.zip

Bernkastel77

2017-09-13 20:52:25

I just attached the images.

I can't attach the report here, so I uploaded the file on mega.
> https://mega.nz/#!HhRkUZKa!PJp558SNRTdF ... _PZybwwYmc

(wtf, this report is fucking enourmous hahaha)
[+] Spoiler
kin_a11_defo1.png
kin_a11_defo1.png (522.1 KiB) Viewed 13683 times
mlib_1b_bg.png
mlib_1b_bg.png (91.2 KiB) Viewed 13683 times
mlib_1b.png
mlib_1b.png (3.57 MiB) Viewed 13683 times

Bernkastel77

2017-09-13 20:53:59

Also sorry for being late (again). I had to leave for a while.

vit9696

2017-09-13 21:03:12

Alright, the good thing is that now we can be certain that the files are not corrupted. I am currently studying the system report, and I think we are reaching the step where we will need to get some debugging info from the engine.

I made some changes that might help to give us some insight on the problem. If you are lucky, there is a slight chance the behaviour would change, if not for you, then at least for your friend. It will be nice, if you could test it later on your friend's PC as well.

Unfortunately I don't have Windows nearby, so we will have to wait for about an hour until the system builds a new engine for us.

Bernkastel77

2017-09-13 21:08:07

I see. Then i'll wait.

vit9696

2017-09-13 22:17:53

Alright, I have just sent you a PM with a new engine.

What I would like you to try is extracting the onscripter-ru_win_r2835.exe and ons.cfg file to the game directory, and running the new onscripter-ru_win_r2835.exe. Once the game launches you will see a console window with certain text output.

Please play a little, reach a couple of places where the bug happens, and then save the text printed to the console window and post it here.
In order to be able to select the text you will have to right-click the console window, and then choose Edit → Select All.

Ideally you do the same on your friend's PC if you can (sooner or later). Let me know, if anything changes.
Also, I would like you to compare very carefully whether there are any differences between:
1. Two game launches on the same PC in a row
2. Two game launches on the same PC with a reboot in between
3. Two game launches on different PCs (e.g. your and your friend's)

The thing is, even a minor difference might give us a better understanding of what is going on. For example, on all your screenshots the images were missing. And none of the textures was corrupted (i.e. displayed partially). What is most important to know is whether it is the same all the time and is it the same for your friend's PC?

Bernkastel77

2017-09-13 22:31:27

All i have to do is play? I run some dialogues but nothing has changed within the console window.

vit9696

2017-09-13 22:38:13

If it did not change, it is still a result, and if you do see a glitch, it is enough. You may stop now. All that means is that one of the issues we suspected is not happening (at least on your pc). I would still like to get the log though, since it would still have certain useful stuff in the beginning.
I would also like to get all the possible answers to my previous questions as well =)

Bernkastel77

2017-09-13 22:45:26

Sorry, i hadn't seen your question. Yes, all the time. Same about my friend's pc.
Btw, he is testing on his pc by right now, we are on skype.

Bernkastel77

2017-09-13 22:47:03

Hey! He found a issue!

Bernkastel77

2017-09-13 22:47:38

Bernkastel77

2017-09-13 22:51:37

The same errors occurs in my game.

Bernkastel77

2017-09-13 23:00:32

More and more erros https://puu.sh/xz6GA.png

Bernkastel77

2017-09-13 23:02:30

(same errors in both PCS)

vit9696

2017-09-13 23:02:51

Please note that you are running onscripter-ru_win_r2531.exe and not onscripter-ru_win_r2835.exe I sent you. Unfortunately it is not that easy. Both getram and gamepad_button warnings are harmless (and expected). And all the other messages are not errors/warnings at all, they are good debug output. If you had r2835, you would not have seen getram warning.

Either way. Please make sure that you run a correct executable now, use this ons.cfg file, and report with the log.

The good news is that at this step I am 99% confident that the issue is in the drivers. What I currently cannot understand is how your friend's PC that has a completely different GPU (i.e. NVIDIA) has the same bug. I suspect that the bug is similar but completely different in its cause. Needs to be thought about why.

Please try this config file first, and if it fails, I think I have an idea on how to install the latest drivers…
Attachments
test_onscfg_a2.zip
(617 Bytes) Downloaded 810 times

Bernkastel77

2017-09-13 23:12:48

WORKED!!!!!!

Bernkastel77

2017-09-13 23:13:34

This ons.cfg worked! The errors are gone! (lol)

Bernkastel77

2017-09-13 23:15:56

Btw, the prints are from my friend's pc. This idiot had opened 2531, but I was with 2835 for sure.

Bernkastel77

2017-09-13 23:18:24

I'm speechless. Everything is working fine now. LOL.

Bernkastel77

2017-09-13 23:20:53

It worked for my friend too.

vit9696

2017-09-13 23:22:57

Alright, but I would like to explore the problem a little deeper if possible. While this is great to hear, I added no-texture-reuse flag, and this flag causes reasonably serious performance drain. So while it usually works, often it is an overkill, and so far we only thought it is only needed on Windows.

1. Could you confirm that 2835 and a previous ons.cfg file did NOT fix the problem for your friend? (I expected r2835 to be enough for him to be honest)
2. Could you try this third ons.cfg file, whether it fixes the problem for you?
3. Could your friend try this third ons.cfg file, whether it fixes the problem for him?
Attachments
test_onscfg_a3.zip
(612 Bytes) Downloaded 881 times

Bernkastel77

2017-09-13 23:36:27

1. It seems to solve the problem for him. This donkey had not opened before, but now that he opened it all was settled. Yes, the ons.cfg 1 worked for him.
2. Yes. It works for me.
3. Work for him too.

Bernkastel77

2017-09-13 23:40:40

Now that everything has been solved, how can i get rid of this screen?
Whenever I start the game, this app comes together.
https://imgur.com/a/JsxJL

vit9696

2017-09-13 23:46:40

Nice to hear. All in all you had separate bugs, thanks to the tests we at least were able to create a builtin fix for nvidia. For AMD this is not possible, and you have to specify no-glclear manually into your ons.cfg file. We will update our Known issues page with more details in the nearest future.

To get rid of the console window just open ons.cfg with Notepad and remove "use-console" line.
And as for your friend, he could use r2835 engine and delete this ons.cfg file so that the new default file gets created. It was the engine that fixed the problem for him, not the ons.cfg file.

Bernkastel77

2017-09-13 23:55:02

"you have to specify no-glclear manually into your ons.cfg file"

What do I have to do? What I write?

vit9696

2017-09-13 23:56:22

That's what I have already done for you. If you open ons.cfg with Notepad (Right click → Open with → Choose program → Notepad), you will see that it has a line no-glclear.

Bernkastel77

2017-09-14 00:01:55

Okay. Thank you very much, bro. I'm really glad that i can enjoy Umi in its best version hehehe ^_^

vit9696

2017-09-14 00:07:35

You are welcome