CRYENGINE 5.7 LTS Feedback Thread

#1
Hi CryENGINEERS,

This is the dedicated topic to collect your feedback regarding CRYENGINE 5.7 LTS in addition to the Launcher crash reporter and the GitHub Issue tracker. To use the Issue Tracker, please ensure your GitHub account has access to the 5.7 LTS source code and that you are logged in - to learn how to gain access to the source code, read here.
Please make sure you submit your feedback in the following format - we even made a copy/paste form for you to save you some time.

When submitting feedback for the engine build, please make sure your reply to this topic is formatted like this:

Code: Select all

Title: [TOOL] - Gist of Problem/List

[list][b]OS:[/b] Windows 10, 11 etc.
[b]Build:[/b] as shipped, or compiled from GitHub?
[b]Version Number:[/b] Exact version number: (e.g. A.B.C.D)[/list]

- Additional relevant info, summarized, see below for parts to include.
- Exact steps to reproduce the error, if you are reporting a bug.

Attachments if applicable:

DxDiag
Crash Report/Engine Log Files
Image of Error notification
Never just post the contents of a DxDiag or Crash Log File into a post! Attach it to the post as a document instead. Use the Spoiler tag to hide massive lines of text so forum pages don't get cluttered.

Image

If the engine / sandbox crashes, and the crash reporter pops up, please provide additional information about the problem as is recommended. Just let us know what you did before the crash. It helps us a lot to identify issues quicker.

For additional information, please kindly review our 'How to submit Feedback-Guide' before posting to make sure all the information we need is displayed properly and communicated well so our engineers can process it.

Thanks for helping us improve the engine! We couldn't do it without you. Have fun testing and keep those bugs coming until we get them all,

sincerely,

Please be aware this is the build feedback thread, if you want to have a discussion about the 5.7 LTS release or its features, please move your conversation to the announce thread, thanks! Please help us keep this thread tidy so our engineers can go through your bugs and issues and start investigating them sooner.

- The CRYENGINE Team

Re: CRYENGINE 5.7 LTS Feedback Thread

#3
CRYENGINE launcher Bug:

I installed the CRYENGINE launcher half month ago, then installed CRYENGINE 5.6.7. Today, I upgraded to 5.7 and deleted 5.6.7 from the launcher. But I cannot use the right-client context menu to open the .cryproject file, because the system cannot find the command to open this file using 5.7 sandbox editor. (The directory is wrong)

Later, I uninstalled the launcher and reinstalled it, also the 5.7 version. This problem is still there. It is because when uninstalling the launcher or switch the engine(1. switch manually 2. if I have two versions, delete one, the rest is the only one can open the .cryproject, right?), the registries for .cryproject (& .cryengine) don't get overwritten by the new one. I have to change all of these manually. Change something like "D:\Program Files\CRYENGINE Launcher\Engines\crytek\cryengine-56\5.6.7\Tools\CryVersionSelector\bin\cryselect\cryselect.exe" remove_plugin_gui "%1" to "D:\Program Files\CRYENGINE Launcher\Engines\crytek\cryengine-57-lts\5.7.0\Tools\CryVersionSelector\bin\cryselect\cryselect.exe" remove_plugin_gui "%1".

please fix this inconvenience. thx. :)

Re: CRYENGINE 5.7 LTS Feedback Thread

#7
4k monitor dpi problem

Working in editor on 4k monitor is uncomfortable. When windows desktop dpi is set to 100% everything is too small. When the dpi is set to 150% everything is too big. It looks the same as it was set to 200% dpi. It looks that the editor ignores dpi between 100-200%. There are blurry icons, huge UI Elements and asset browser takes almost half of the screen and can't be shrinken. Other applications work ok, including editors like Unity or Unreal. It pushes users away.

Who is online

Users browsing this forum: No registered users and 3 guests