[4.27.2] [VS2019] [VS2022] No debugging symbols for packaged configuration?

Considering the avaliable version of .27 has not worked once since release - and I have tested it on 4 different computers with wildly different builds - I wonder why you haven’t already.

It is, it may just be locked out of the build they released or something.
Normally if you install the symbols along with the engine, then the crash reporter will spit out stuff that makes sense.

When building from source you have to take care to build the correct editor version in order to have debug access. Otherwise it just closes out with a “it crashed, ok” dialog.
(And VS debug will stop running right after you open a project).

I still suggest you build from source and mess with that - it’s better in the long run.

Ps: the .27 chaos build failed to build 2 days straight due to corrupt files from GitHub desktop.
Consider that when downloading :wink: