It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi!

Did anyone experience problem of codex content not showing? It was visible at first, because I've managed to get code for Penrose from it. Reinstallation did not help. I'm running Ubuntu.
Attachments:
Post edited June 09, 2020 by kretkowl
avatar
kretkowl: Hi!

Did anyone experience problem of codex content not showing? It was visible at first, because I've managed to get code for Penrose from it. Reinstallation did not help. I'm running Ubuntu.
Hey there,

Can you try this:

Launch the game with the following command line arguments:
MESA_VK_WSI_PRESENT_MODE=fifo %command% -force-vulkan

I am sure you know how but in case:
https://ubuntu.com/tutorials/command-line-for-beginners#1-overview

PS sorry for the late reply. I check the forum every day and yesterday I missed this comment!
Post edited June 11, 2020 by THEBROTHERHOOD
Thank you! It worked like a charm.
avatar
kretkowl: Thank you! It worked like a charm.
Awesome!
avatar
kretkowl: Hi!

Did anyone experience problem of codex content not showing? It was visible at first, because I've managed to get code for Penrose from it. Reinstallation did not help. I'm running Ubuntu.
avatar
THEBROTHERHOOD: Hey there,

Can you try this:

Launch the game with the following command line arguments:
MESA_VK_WSI_PRESENT_MODE=fifo %command% -force-vulkan

I am sure you know how but in case:
https://ubuntu.com/tutorials/command-line-for-beginners#1-overview

PS sorry for the late reply. I check the forum every day and yesterday I missed this comment!
Unfortunately Unity Vulkan renderer causes some issues on amdgpu (confirmed on mesa 20.3.4 RADV): https://www.youtube.com/watch?v=Gmr-9zrvWWk
So, on amdgpu, OpenGL is game-breaking (journal does not show anything) and Vulkan is immersion-breaking. It looks like that *AMD_DEBUG=nohyperz* helps a tiny bit on OpenGL, but there are still too many artefacts in the 2D overlays.

This bug report indicates that it may be Unity's engine fault (as it follows the nVidia driver implementation that defaults the depth buffer to 1.0, which may not really be following the OpenGL standard): https://gitlab.freedesktop.org/mesa/mesa/-/issues/2937. Maybe the bug can be fixed in the game code, by forcing the depth of the 2D overlays to a certain fixed level?
Post edited February 07, 2021 by zgembo
avatar
THEBROTHERHOOD: Hey there,

Can you try this:

Launch the game with the following command line arguments:
MESA_VK_WSI_PRESENT_MODE=fifo %command% -force-vulkan

I am sure you know how but in case:
https://ubuntu.com/tutorials/command-line-for-beginners#1-overview

PS sorry for the late reply. I check the forum every day and yesterday I missed this comment!
avatar
zgembo: Unfortunately Unity Vulkan renderer causes some issues on amdgpu (confirmed on mesa 20.3.4 RADV): https://www.youtube.com/watch?v=Gmr-9zrvWWk
So, on amdgpu, OpenGL is game-breaking (journal does not show anything) and Vulkan is immersion-breaking. It looks like that *AMD_DEBUG=nohyperz* helps a tiny bit on OpenGL, but there are still too many artefacts in the 2D overlays.

This bug report indicates that it may be Unity's engine fault (as it follows the nVidia driver implementation that defaults the depth buffer to 1.0, which may not really be following the OpenGL standard): https://gitlab.freedesktop.org/mesa/mesa/-/issues/2937. Maybe the bug can be fixed in the game code, by forcing the depth of the 2D overlays to a certain fixed level?
Quick update on this. GOG are pushing 1.0.5.5 which fixes this graphics glitch on these system setups. I will update this post once it is live. Nic

UPDATE:

New Build should sort out all issues, you can grab the installer now.
Post edited February 10, 2021 by THEBROTHERHOOD
Unfortunately 1.0.5.5 does not fix all the issues. It does fix missing PDA overlay on OpenGL renderer, but the PDA is missing animation layer (logo and noise-like effects). Using *AMD_DEBUG=nohyperz* results in animation layer appearing, although garbled.

The black circles are not fixed on Vulkan renderer (RADV).
Post edited February 27, 2021 by zgembo
Hi there,

same for me here, no "pencil"-elements to update my codex are showing in the world.
I'm stuck at the "Alexis Disaster Recovery".

v1.0.5.5 LINUX

MESA_VK_WSI_PRESENT_MODE=fifo ./game/desolation.x86_64 -force-vulkan

didn't help....

kind regards
avatar
matchuek: Hi there,

same for me here, no "pencil"-elements to update my codex are showing in the world.
I'm stuck at the "Alexis Disaster Recovery".

v1.0.5.5 LINUX

MESA_VK_WSI_PRESENT_MODE=fifo ./game/desolation.x86_64 -force-vulkan

didn't help....

kind regards
Are you on Ubuntu?
avatar
matchuek: Hi there,

same for me here, no "pencil"-elements to update my codex are showing in the world.
I'm stuck at the "Alexis Disaster Recovery".

v1.0.5.5 LINUX

MESA_VK_WSI_PRESENT_MODE=fifo ./game/desolation.x86_64 -force-vulkan

didn't help....

kind regards
Hi there,

i have the same problems, no codex showing as seen in walkthrough videos, also stuck at the "Alexis Disaster Recovery".
don't know how to use the "command line argument"

using Linux Mint 20.3 cinnamon

v1.0.5.5 LINUX
Same here, no "pencils" at all, additionally some, but not all "description-only" items (green cubes with text, cannot be picked up) are missing. The one at the crashed transporter is placed incorrectly (to the left of the correct location), the "camp site" description on the same screen is missing, as well as the "pencil item" to the left. Other descriptions seem to be placed correctly, if they are shown at all. According to several walkthroghs, here should be gold at the beach, rhis is also not shown, as well as the wallet item at the abbey.

"-force-vulkan" gives a misleading output here:
-8<-----------
Player data archive not found at `/usr/local/lib/games/GOG/BEAUTIFUL_DESOLATION/game/desolation_Data/data.unity3d`, using local filesystem
-8<-----------
After that the programme ends without starting the gui.
avatar
kretkowl: It was visible at first, because I've managed to get code for Penrose from it.
It was probably not visible, because the Penrose code page is added automatically, not by "picking up a pencil item".
Post edited March 18, 2023 by ChFra
A question to the programmer:

I assume that items of the same type are coded in the same way using the same functions. Obviously, they behave differently at different locations in the game nonetheless. Example: The gold at the beach and the gold nugget at the rockface are both items wirh "eye indicator", one is visible, the other isn't. If you in fact can find a difference in your code, this could be used for a bug fix, if not: in which other way are those items "different"?

I now think that I might have overlooked some "nomal (*eye*) items".
They don't seem to be affected, but the problem still remains for those "landscape descriptions": some are there, and placed at the correct locations, at least one is misplaced, others are missing (those of the "murdered" agnates, for example).

Setting "LANG=C" helps. Why?

After setting this, it seemed also to me that my companions make more comments about the environment.
In addition, the "quest markers" seem to be more reliable, I think I've seen less of those before.
Post edited April 11, 2023 by ChFra
To correct an error in my 2 previous posts:

I've already added: "I now think that I might have overlooked some "nomal (*eye*) items"."

This means that I thought, and now confirmed, that the following statements were incorrect:

"According to several walkthroghs, here should be gold at the beach, rhis is also not shown, as well as the wallet item at the abbey."

"Example: The gold at the beach and the gold nugget at the rockface are both items wirh "eye indicator", one is visible, the other isn't."

The gold nugget does exist no matter how LANG is set. I just overlooked it on my first attempt. The wallet item doesn't contain money any longer if you leave the place without taking it, and return later. This is obviously intended behaviour.

All other differences, like entirely missing description-only "items" or the misplaced one are reproducible, as well as the missing "pencil" items. I'd still like an explanation and possibly a bug fix rather than having only a workaround.