Green Bar and Red/Green Lines in Cutscenes

[svet-am]

I bought this game a couple of days ago for my daughter and she is having an issue in the cutscenes where there is a green bar at the bottom of the screen and there are red/green lines throughout the video. The color is also very unsaturated (like an old time newsreel).

I thought this might be a codec issue so I installed an updated codec pack and it didn't help. The issue is *only* during the cutscenes, all of the rest of the game plays flawlessly so far.

[Trainerchris]

Автор сообщения: Pikafoop

Автор сообщения: Galwar

I just bought the game.
I have a mobile RTX 3060 and have the same problem.

I also have a machine with an integrated AMD GPU and an RTX 3060 mobile. I experienced this issue but was able to correct it by forcing the program to execute exclusively on the RTX 3060.

HOWTO:
- While the program is not running, access Windows 10 "Graphics Settings" (Start Menu -> gear icon for Settings -> System -> Display -> Graphics Settings link near the bottom of the page; I recommend just searching for "Graphics Settings" instead).
- Here you can assign a "Graphics performance preference" to this game's executable. Select "Dekstop App", press the "Browse" button, and find the executable. By default, this will be "C:\Program Files (x86)\Steam\steamapps\common\LEGO City Undercover\LEGOLCUR_DX11.exe".
- Click on "LEGO CITY UNDERCOVER" in the list of apps, press the "Options" button, select "High performance", and press the "Save" button.

Had the same issue thanks for the advice :D

[Beakerman999]

I also have a machine with an AMD GPU 6700 XT. I used the Windows 10 "Graphics Settings" below along with enabling "HDMI Link Assurance" from within the AMD Adrenalin Software, and only had this issued with the intro cutsceen. I'm on driver 22.6.1. Running good at 1440P with Vsyn off.

Gaming -> Global Display -> HDMI Link Assurance

Автор сообщения: Trainerchris

Автор сообщения: Pikafoop

HOWTO:
- While the program is not running, access Windows 10 "Graphics Settings" (Start Menu -> gear icon for Settings -> System -> Display -> Graphics Settings link near the bottom of the page; I recommend just searching for "Graphics Settings" instead).
- Here you can assign a "Graphics performance preference" to this game's executable. Select "Dekstop App", press the "Browse" button, and find the executable. By default, this will be "C:\Program Files (x86)\Steam\steamapps\common\LEGO City Undercover\LEGOLCUR_DX11.exe".
- Click on "LEGO CITY UNDERCOVER" in the list of apps, press the "Options" button, select "High performance", and press the "Save" button.

Had the same issue thanks for the advice :D

[Lagnutthelobster]

Автор сообщения: Trainerchris

Автор сообщения: Pikafoop

I also have a machine with an integrated AMD GPU and an RTX 3060 mobile. I experienced this issue but was able to correct it by forcing the program to execute exclusively on the RTX 3060.

HOWTO:
- While the program is not running, access Windows 10 "Graphics Settings" (Start Menu -> gear icon for Settings -> System -> Display -> Graphics Settings link near the bottom of the page; I recommend just searching for "Graphics Settings" instead).
- Here you can assign a "Graphics performance preference" to this game's executable. Select "Dekstop App", press the "Browse" button, and find the executable. By default, this will be "C:\Program Files (x86)\Steam\steamapps\common\LEGO City Undercover\LEGOLCUR_DX11.exe".
- Click on "LEGO CITY UNDERCOVER" in the list of apps, press the "Options" button, select "High performance", and press the "Save" button.

Had the same issue thanks for the advice :D

I tried this on Windows 11 and it didn't work

[Depression]

I just should have sticked to Nvidia...

[TimeFreeze]

Found a solution for this bug so i'm just gonna shamelessly advertise my Guide:
https://steamcommunity.com/sharedfiles/filedetails/?id=2889353226

[Marie]

Автор сообщения: TimeFreeze

Found a solution for this bug so I'm just gonna shamelessly advertise my Guide:
https://steamcommunity.com/sharedfiles/filedetails/?id=2889353226

i tried it i got a virus

[Hiroshi Mishima]

It's not a virus, I was able to download the other day and install it without any issue. Depending on your anti-virus software it's most certainly a false flag.

Incidentally, big thanks to TimeFreeze for this because I was also having that problem.

[zblazer]

Автор сообщения: TimeFreeze

Found a solution for this bug so i'm just gonna shamelessly advertise my Guide:
https://steamcommunity.com/sharedfiles/filedetails/?id=2889353226

Tried this guide with various versions of DXVK, but none of them worked. The game tries to launch but doesn't. Attempted with 2.3, 2.0, 1.3, and 1.0.

[josephgallipoli19]

Yea i tried all that and nothing happened, I even tried to convert the files to text files like it showed in the picture and I still have the glitch. And when I did it normally the game wouldn't start. I have an HP omen 15 laptop

[C.L.A.Y.]

Автор сообщения: TimeFreeze

Found a solution for this bug so i'm just gonna shamelessly advertise my Guide:
https://steamcommunity.com/sharedfiles/filedetails/?id=2889353226

Lol it's not working

[Neptune IDK]

Автор сообщения: TimeFreeze

Found a solution for this bug so i'm just gonna shamelessly advertise my Guide:
https://steamcommunity.com/sharedfiles/filedetails/?id=2889353226

This doesn't work at all

[TimeFreeze]

To everyone who says this doesnt work: Yes it does work!

I'm truly sorry but if you are incapable of following simple instructions or are trying it on a GPU which cant even do Vulkan then thats not my fault. Many users said it works and i just tested it again myself. So yeah it does work.

[[{******---Dead4Life---******}]]

Автор сообщения: TimeFreeze

Found a solution for this bug so i'm just gonna shamelessly advertise my Guide:
https://steamcommunity.com/sharedfiles/filedetails/?id=2889353226

Aaannnd thanks! Works in 2024 too!

[J4BB3R W0CK1E]

The DXVK worked a treat on my Legion Go. Thank you! ✌️

[OptimusHippo]

This issue popped up recently on Steam Deck. Forcing the game to use Proton 8.0-5 fixes it.