Game looks like a broken Matrix

[Urshak84]

I started the game and the main menu looked normal. But then i started a new game and the game looked like a broken version of The Matrix.
Here are some pictures of it :

Screenshot.zip

If i can send additional data or something to help just say something. But i have to be honest i can't help debugging or something because i have no programming skills.

[Urshak84]

I have a possibly dumb question. Is it somehow possible to get an Error-Log or something out of your sourceport, something like a command ? I would really like to help to fix this issue.

[FriskTheFallenHuman]

I have a possibly dumb question. Is it somehow possible to get an Error-Log or something out of your sourceport, something like a command ? I would really like to help to fix this issue.

Windows: User/Documents/My Games/Prey06/qconsolelog.txt

[Urshak84]

Thank you very much. Here is the Log :

qconsolelog.txt

If you need a new Log or something just say something and i will look what i can do .

[FriskTheFallenHuman]

Thank you very much. Here is the Log :

qconsolelog.txt

If you need a new Log or something just say something and i will look what i can do .

uh the log does not show any sights of problem, im calling @Xanz and @m0rb here since im unable to reproduce this since i dont have a NVIDIA card.

[FriskTheFallenHuman]

just to be clear, have you use this prerelease?: https://github.com/FriskTheFallenHuman/Prey2006/releases/tag/v1.5.4_rc4

[Urshak84]

@FriskTheFallenHuman I am pretty sure i used the release u just mentioned but to be a 100% sure i re-downloaded it and created a new Log.

qconsolelog.txt

Version v1.5.4_rc1 didn't have the Matrix-Issue.

[TheMidnightHammer]

This issue can be closed.

[Urshak84]

@TheMidnightHammer i tested the latest release too and the issue still persisted. Is this issue solved in the next upcoming release, or is there something i could do on my side ?

[TheMidnightHammer]

So v1.5.4_rc1 does work and v1.5.4 does not. Can you test v1.5.4_rc2, v1.5.4_rc3 and v1.5.4_rc4? And give the results back?

[TheMidnightHammer]

Additionally, you could do a git bitsect to find the commit that broke the renderer.

[Urshak84]

Ok i couldn't find the release candidate 2 for download and i don't have it on my computer anymore. The log of the third release candidate will most likely not contain much information because i cant get past the cd-key window dispite using my original retail-key directly from the inside of the dvd-box. I have to confess that i don't know what doing an git bitsect means, sounds complicated.

rc3:

qconsolelog.txt

rc4:

qconsolelog.txt

[TheMidnightHammer]

git bitsect just finds what commits is the one that added the visual glitches.
It works like this:

1. First you need to install git, sudo apt-get install git
2. download the source with git, git clone https://github.com/FriskTheFallenHuman/Prey2006.git
3. Go in the prey folder, cd Prey2006
4. start the bitsect, git bitsect start
5. tell git that the latest git is bad git bisect bad HEAD
6. tell git that v1.5.4_rc1 is good git bisect good 1.5.4_rc1
7. build prey from source and test it for the bug, if the bug is present add git bitsect bad if its not git bitsect good

It should take a few rounds of this, when its done, please give us the commit that added the visual problem.