#crash when adjusting Lumens

48 messages · Page 1 of 1 (latest)

grim cosmos
#
[2026.01.14-03.48.47:279][523]LogViewport: Display: Viewport MouseLockMode Changed, LockOnCapture -> DoNotLock
[2026.01.14-03.48.47:279][523]LogViewport: Display: Viewport MouseCaptureMode Changed, CapturePermanently -> CaptureDuringMouseDown
[2026.01.14-03.48.47:279][523]LogViewport: Display: Player bShowMouseCursor Changed, False -> True
[2026.01.14-03.48.48:933][595]LogSlate: User[0] UsePlatformCursorForCursorUser(true)
[2026.01.14-03.48.52:196][736]LogViewport: Display: Viewport MouseLockMode Changed, DoNotLock -> LockOnCapture
[2026.01.14-03.48.52:196][736]LogViewport: Display: Viewport MouseCaptureMode Changed, CaptureDuringMouseDown -> CapturePermanently
[2026.01.14-03.48.52:196][736]LogSlate: User[0] UsePlatformCursorForCursorUser(false)
[2026.01.14-03.48.52:196][736]LogViewport: Display: Player bShowMouseCursor Changed, True -> False
[2026.01.14-03.48.55:657][879]LogViewport: Display: Viewport MouseLockMode Changed, LockOnCapture -> DoNotLock
[2026.01.14-03.48.55:657][879]LogViewport: Display: Viewport MouseCaptureMode Changed, CapturePermanently -> CaptureDuringMouseDown
[2026.01.14-03.48.55:657][879]LogViewport: Display: Player bShowMouseCursor Changed, False -> True
[2026.01.14-03.48.55:818][888]LogSlate: User[0] UsePlatformCursorForCursorUser(true)
[2026.01.14-03.49.36:580][499]LogWindows: Error: appError called: Assertion failed: ResourceIndex < State.MaxDescriptorCount [File:H:\UnrealEngines\UnrealEngine\Engine\Source\Runtime\VulkanRHI\Private\VulkanDescriptorSets.cpp] [Line: 878] 
You need to grow the resource array size for [VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER]!
#
Kernel: 6.17.9-arch1-1
MATE 1.28.0
CPU: Intel i9-10900K (20) @ 5.300GHz 
GPU: AMD ATI Radeon RX 6700/6700 XT/ 
Memory: 7997MiB / 31983MiB (18.3GB at time of crash)
#

Lumens setting stuck

#

reflection works a lot better now tho

grim cosmos
#

loading save also fixed my map apparently
those three are when i'd tried

#

when i kept ctrl+clicking and nothing was happening, apparently it was

forest sail
#

Go to Vein/Saved/Config, open or create Engine.ini, add

[ConsoleVariables]
r.Vulkan.Bindless.MaxResourceUniformTexelBufferCount=262144

Try that

grim cosmos
#

this is under the Windows Engine.ini

#

considering im on proton
that correct?

forest sail
#

I don't know what I'm looking at

grim cosmos
#

oh i couldnt find that line

#

so i need to add it into Engine.ini

#

which one

forest sail
#

Oh no put that at the bottom of Engine.ini

grim cosmos
#

copy that

#

So, under /Config I have Windows, Linux and CrashReportClient

am I adding directly into /Config/Engine.ini or am I adding a file named Engine.ini at the root of /Config ?

grim cosmos
forest sail
#

Either Windows or Linux, sorry

#

I'm not sure which one is used in your setup

#

Probably Windows through proton

grim cosmos
#

i didnt know both existed in the same install

#

was why i was wondering 🙂

#

i added it to Engine.ini
can switch back and forth

#

snappy too

#

lemme load and try now

#

ok thought it might have crashed there but it took forever to turn it off while in game
gonna turn it back on

#

i wanna say about 30s ?

#

FPS showed as about 2 then creeped back up to 40-50

forest sail
#

Same crash?

forest sail
grim cosmos
grim cosmos
#

this file shows two files

#

from the game path

#

does switching between proton and scout linux retain the files between my installs...that doesnt sound right

#

if so, could be an issue?

forest adder
#

the engine's only gonna use one of those

forest sail
#

It does but no they will use separate inis

grim cosmos
#

kk

#

ok so its normal for it to show as two files in the same game paths

#

makes sense to me

#

just confirming

#

ok ill say this one is fixed temp but ill play for a bit and share in here if i get another similar crash
ty for the quick help

#

performance looks to be about what i had before
i am alt-tabbed
fullscreen
seems fine so far