Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I dunno where you find it on mac but on Windows it's named "Registry.xml" and can be found in "Documents\Endless Legend\Users" so if there is something similar on mac try searching there first
Cant find anything in the mac files with Registry in the name. Any alternative names that you think they may use for that kind of file?
Seems like it's where the game store it's files on mac according to the pinned post
https://steamcommunity.com/app/289130/discussions/0/517142253859718203/
No dice, but thanks for the help.
I found a plist file named info. its contents look like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>EndlessLegend</string>
<key>CFBundleGetInfoString</key>
<string>Unity Player version 5.3.6p1 (ef59fdfbd254). (c) 2016 Unity Technologies ApS. All rights reserved.</string>
<key>CFBundleIconFile</key>
<string>PlayerIcon.icns</string>
<key>CFBundleIdentifier</key>
<string>unity.AMPLITUDE Studios.Endless Legend</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>Endless Legend</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleShortVersionString</key>
<string>Unity Player version 5.3.6p1</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>5.3.6p1</string>
<key>NSMainNibFile</key>
<string>MainMenu</string>
<key>NSPrincipalClass</key>
<string>PlayerApplication</string>
<key>UnityBuildNumber</key>
<string>ef59fdfbd254</string>
</dict>
</plist>
Does this look similar to the registry.txt?
I won't copy everything because it's too long, but the file(at least mine) start like that:
<?xml version="1.0" encoding="utf-8"?>
<Registry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Settings>
<Steam>
<CloudRemoteStorage>True</CloudRemoteStorage>
</Steam>
<Video>
<Fullscreen>True</Fullscreen>
<Resolution>1920x1080 (60)</Resolution>
<VSyncCount>1</VSyncCount>
<RefreshRate>60</RefreshRate>
<QualityLevel>Fantastic</QualityLevel>
<TargetFrameRate>100</TargetFrameRate>
<EnableTrailers>False</EnableTrailers>
</Video>
<Audio>
On OS X Mojave (10.14.6) the game started OK with the default settings. Then I've changed the video config to full screen and a non-default resolution, and now it crashes on the start up. I do not see any way to change the settings back. I've tried re-installing the game, and also re-installing the entire Steam client in an attempt to reset the game settings, but that did not help.
There is no `Registry.xml` file (nor anything similar to it) in the ~/Library/Application Support/Steam/steamapps/common/Endless Legend/ folder. The only file i can find with `registry` in name is `registry.vdf` in ~/Library/Application Support/Steam, but that does not seem to contain anything specific to Endless Legend.
So, now I am also looking for how to reset the game settings without launching the game on OS X.
How do we set it to windowed mode if we can't even start the game?
After the game finally started, it created the registry file in `~/Library/Application Support/Endless Legend/Users/[your-steam-user-id]/Registry.xml`. The gotcha here was that when the game was crashing, the whole `~/Library/Application Support/Endless Legend` folder did not exist, so I could not find the registry file and change the video settings there.
I do not know if creating the file manually would have solved the issue. If someone else wants to try, here is the file contents: https://gist.github.com/vlukashov/c49bdbc0b23a1cd9af05fbfa0677e55d
-- Ran fine (after running installer) the first time, started in a separate window and not full-screen
-- I checked the video setting checkbox to full-screen
-- The app appeared to crash
-- My machine did something that looked like a reboot but wasn't (more on this later)
-- The app tried to start again, and crashed
-- Repeat this loop a few times
-- I finally broke out by restarting the laptop
-- Changing the screen resolution with EasyRes to a non-Retina resolution allowed Endless Legend to run OK.
In /Library/Logs/DiagnosticsReports I've got some WindowServer .crash files, so I suspect what looked like a reboot wasn't; it was the WindowServer resetting itself and trying to display the active application...which leads to the reset loop.
Some of the interesting lines from the .crash file:
MetalDevice for accelerator(0x3803): 0x7fd0e1301648 (MTLDevice: 0x7fd0b0010000)
MetalDevice for accelerator(0x4727): 0x7fd0c0518b58 (MTLDevice: 0x7fd0b0020000)
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/ATY,Xingu@0/AMDFramebufferVega10
Assertion failed: (isReady - DisplayID: 0x4281006
Surface Use Counts: 347(0) 4(0) 5(1)
FB RegID: 4294969062, On Glass SurfaceIDs: 475, Transactions: [ Active: SurfaceID: 475 ], Surface Use Counts: 23(1) 348(1) 349(1) 475(2)
), function CoreDisplay_NotReady, file /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreDisplay/CoreDisplay-110.18/CoreDisplay/Display/Display.cpp, line 2538.
...
5 com.apple.CoreDisplay 0x00007fff4ac04673 CoreDisplay_NotReady + 1045
6 com.apple.SkyLight 0x00007fff70042f6d update_display_callback(void*, double) + 631
...
I also have some SubmitDiagInfo .crash files from the same time, so the crash reports likely aren't getting submitted.
Happy to provide more info or .crash files if it's useful.