Re: Engine couldn't be found

#2
Unfortunately we the link you provided is not working for us. Please upload the raw log as an attachment and we can take a look.

Can you verify that the engine was downloaded and installed successfully by locating the physical folder on disk? By default the location should be:
C:\Program Files (x86)\Crytek\CRYENGINE Launcher\Crytek\CRYENGINE_5.6
Uniflare
CRYENGINE Technical Community Manager
Here to help the community and social channels grow and thrive.

My personal belongings;
Beginner Guides | My GitHub | Splash Plugin

Re: Engine couldn't be found

#3
Hey there!
Yes, engine Is downloaded, I even manage to launch sandbox.exe but it didn't let me create any map.

2019-09-18 14:53:20,770 DEBUG #CryEngineDB not found: ""
2019-09-18 14:53:20,800 INFO
-------------------------------------------------
CryEngine Launcher 1.10.2-2
Platform: win32 - v10.0.18362
Arch: ia32
Date: Wed Sep 18 2019 14:53:20 GMT+0200 (Rep. Płd. Afryki (czas stand.))
-------------------------------------------------
2019-09-18 14:53:20,802 DEBUG configure: starting up autoupdater
2019-09-18 14:53:20,848 DEBUG #Migrating WinRegistry to EngineDb
2019-09-18 14:53:21,691 DEBUG # nothing to migrate
2019-09-18 14:53:21,691 DEBUG #Finished Migration
2019-09-18 14:53:22,022 DEBUG #onlineStatus
2019-09-18 14:53:26,207 DEBUG checkForUpdates: Checking for updates...
2019-09-18 14:53:26,529 DEBUG getClient: obtaining the client
2019-09-18 14:53:34,899 DEBUG #CryEngineDB not found: ""
2019-09-18 14:53:34,927 INFO
-------------------------------------------------
CryEngine Launcher 1.10.2-2
Platform: win32 - v10.0.18362
Arch: ia32
Date: Wed Sep 18 2019 14:53:34 GMT+0200 (Rep. Płd. Afryki (czas stand.))
-------------------------------------------------
2019-09-18 14:53:34,929 DEBUG configure: starting up autoupdater
2019-09-18 14:53:34,982 DEBUG #Migrating WinRegistry to EngineDb
2019-09-18 14:53:35,645 DEBUG # nothing to migrate
2019-09-18 14:53:35,645 DEBUG #Finished Migration
2019-09-18 14:53:36,083 DEBUG #onlineStatus
2019-09-18 14:53:39,931 DEBUG checkForUpdates: Checking for updates...
2019-09-18 14:53:40,207 DEBUG getClient: obtaining the client
2019-09-18 14:53:45,220 DEBUG handleLogin: user logged in
2019-09-18 14:53:45,221 DEBUG $EVENT user.loggedIn
2019-09-18 14:53:45,229 DEBUG verifyLogin: session validated
2019-09-18 14:53:45,235 DEBUG handleLogin: updated common.json
2019-09-18 14:53:45,823 DEBUG getClient: obtaining the client
2019-09-18 14:53:45,823 DEBUG getClient: obtaining the client
2019-09-18 14:53:45,823 DEBUG getClient: obtaining the client
2019-09-18 14:53:45,823 DEBUG getClient: obtaining the client
2019-09-18 14:53:45,823 DEBUG getClient: obtaining the client
2019-09-18 14:53:48,414 DEBUG getClient: obtaining the client
2019-09-18 14:53:48,415 DEBUG getClient: obtaining the client
2019-09-18 14:53:48,418 DEBUG getClient: obtaining the client
2019-09-18 14:53:48,418 DEBUG getClient: obtaining the client
2019-09-18 14:53:48,419 DEBUG getClient: obtaining the client
2019-09-18 14:53:48,419 DEBUG getClient: obtaining the client
2019-09-18 14:53:48,419 DEBUG getClient: obtaining the client
2019-09-18 14:53:50,582 DEBUG #verifyingEngineRegistry 5.6
2019-09-18 14:53:50,591 DEBUG $EVENT downloadQueue.enqueued
2019-09-18 14:53:50,719 DEBUG setPluginState: new pluginState INSTALLING
2019-09-18 14:53:51,726 DEBUG setPluginState: new pluginState DOWNLOADING
2019-09-18 14:54:11,774 DEBUG setPluginState: new pluginState INSTALLING
2019-09-18 14:57:29,231 DEBUG #executeCommand:
2019-09-18 14:57:29,239 DEBUG setPluginState: new pluginState READY_TO_LAUNCH
2019-09-18 14:57:29,239 DEBUG setGameInstallationState: new gameInstallationState UP_TO_DATE
2019-09-18 14:57:29,239 DEBUG setPluginState: new pluginState REGISTERING
2019-09-18 14:57:29,819 DEBUG #stdout:
2019-09-18 14:57:29,819 DEBUG #executeCommand:
2019-09-18 14:57:30,404 DEBUG #stdout:
2019-09-18 14:57:30,419 DEBUG setPluginState: new pluginState READY_TO_LAUNCH
2019-09-18 15:01:05,994 DEBUG #verifyingEngineRegistry 5.6
2019-09-18 15:01:05,996 DEBUG $EVENT downloadQueue.enqueued
2019-09-18 15:01:06,105 DEBUG setPluginState: new pluginState INSTALLING
2019-09-18 15:01:07,712 DEBUG setPluginState: new pluginState READY_TO_LAUNCH
2019-09-18 15:01:07,712 DEBUG setPluginState: new pluginState REGISTERING
2019-09-18 15:01:07,717 DEBUG #executeCommand:
2019-09-18 15:01:08,314 DEBUG #stdout:
2019-09-18 15:01:08,327 DEBUG setPluginState: new pluginState READY_TO_LAUNCH

Re: Engine couldn't be found

#4
If you want to paste text in the post itself please use spoiler tags. you can also upload a zip or txt file directly as an attachment to the post.

The log file unfortunately does not provide any clues to your issue.

Please try these steps:
1. Go to the engine installation directory
2. Navigate to "Tools/CryVersionSelector/" and run "install.bat".
3. Navigate back to the root directory, then Right-Click on the cryengine.cryengine file and select "Register Engine"

Then try to launch Sandbox.exe from the "bin/win_x64" folder.
If you have any problems in the editor, please provide us with the editor.log file from the root directory.
Uniflare
CRYENGINE Technical Community Manager
Here to help the community and social channels grow and thrive.

My personal belongings;
Beginner Guides | My GitHub | Splash Plugin

Re: Engine couldn't be found

#5
I could not do this:
3. Navigate back to the root directory, then Right-Click on the cryengine.cryengine file and select "Register Engine"
I don't have that option there.

After running sandbox.exe I'm getting this:
Image

I don't have editor.log file in the root - I have server.log and editor.cfg
I'm attaching both in the attachment.
Attachments
CRYENGINE_5.6.7z
(4.25 KiB) Downloaded 94 times

Re: Engine couldn't be found

#7
Can you confirm that you are using an administrator account or not?

Please confirm the following contents of the registry (take note of the disclaimer at the bottom of this page).

1. Open "RegEdit.exe"
2. Navigate to the follow registry key:
Computer\HKEY_CURRENT_USER\Software\Classes\CrySelect.engine\shell\add\command
3. Post the command saved under the "Data" column in the right pane.

Disclaimer: Modifying or changing the registry of your windows machine can potentially cause irreparable damage to your windows installation and prevent certain programs or the operating system itself from working correctly. We take no responsibility for damage incurred from incorrectly modifying or changing the windows registry in any way.
Uniflare
CRYENGINE Technical Community Manager
Here to help the community and social channels grow and thrive.

My personal belongings;
Beginner Guides | My GitHub | Splash Plugin

Who is online

Users browsing this forum: No registered users and 1 guest