- This topic has 4 replies, 2 voices, and was last updated 9 years, 10 months ago by Brook.
-
AuthorPosts
-
-
February 5, 2015 at 11:40 am #8019BrookMember
As of the last build, I don’t get a properly minimized window when I hit Enter while in the client. Instead I get a purely non-client title window bar and no mouse cursor. Tabbing out eventually works but the window cannot be re-entered. Sometimes on launch I see the same behavior–a non-client title bar which never opens into a full-screen window. Eventually after enough re-tries it opens as expected. I’ve checked for Oort executables stuck in memory but I don’t see any.
-
February 6, 2015 at 1:52 am #8042BrookMember
Now it just doesn’t start at all.
javascriptengine_v8.cpp(581): (turbulenz::ArrayBufferAllocator::ArrayBufferAllocator) Creating 14 fast allocators
win32entry.cpp(228): (turbulenz::Win32NativeEngine::HostWndProc) erasing bg
tasks.cpp(17): (Tasks::Initialize) Initializing TBB task scheduler. 9 threads
turbulenz.cpp(115): (turbulenz::Turbulenz::StaticInitialize) Enabling ENGINELOG
winsysteminfo.cpp(405): (turbulenz::GetSystemInfo) SystemInfo:
winsysteminfo.cpp(406): (turbulenz::GetSystemInfo) cpuDescription : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
winsysteminfo.cpp(407): (turbulenz::GetSystemInfo) cpuVendor : GenuineIntel
winsysteminfo.cpp(408): (turbulenz::GetSystemInfo) numPhysicalCores : 4
winsysteminfo.cpp(409): (turbulenz::GetSystemInfo) numLogicalCores : 8
winsysteminfo.cpp(410): (turbulenz::GetSystemInfo) ramInMegabytes : 9207
winsysteminfo.cpp(411): (turbulenz::GetSystemInfo) frequencyInMHz : 2672
winsysteminfo.cpp(412): (turbulenz::GetSystemInfo) architecture : x86_64
winsysteminfo.cpp(413): (turbulenz::GetSystemInfo) osName : Windows 7 Professional
winsysteminfo.cpp(414): (turbulenz::GetSystemInfo) osVersionMajor : 6
winsysteminfo.cpp(415): (turbulenz::GetSystemInfo) osVersionMinor : 1
winsysteminfo.cpp(416): (turbulenz::GetSystemInfo) osVersionBuild : 7601
winsysteminfo.cpp(417): (turbulenz::GetSystemInfo) userLocale : en_US
standalone.cpp(160): (turbulenz::oortonline::GameCodeStaticInitialize) –> ENTERED FUNCTION
standalone.cpp(161): (turbulenz::oortonline::GameCodeStaticInitialize) GameCodeStaticInitialize
standalone.cpp(67): (turbulenz::oortonline::NativeCode::StaticInitialize) STATIC INIT (TEMPLATE): NativeCode
standalone.cpp(-1): (turbulenz::oortonline::GameCodeStaticInitialize) <– LEAVING FUNCTION
javascriptengine_v8.h(3470): (turbulenz::internal::V8TypeInitializeStatic) –> ENTERED FUNCTION
javascriptengine_v8.h(-1): (turbulenz::internal::V8TypeInitializeStatic) <– LEAVING FUNCTION
nativeplatform_steam.cpp(28): (turbulenz::NativePlatform::SteamInitialize) –> ENTERED FUNCTION
nativeplatform_steam.cpp(40): (turbulenz::NativePlatform::SteamInitialize) SteamServices::Initialize returned false: Steam initialization failed (steam_api_init)
steam.cpp(142): (turbulenz::SteamServices::Shutdown) –> ENTERED FUNCTION
steam.cpp(-1): (turbulenz::SteamServices::Shutdown) <– LEAVING FUNCTION
steam.cpp(142): (turbulenz::SteamServices::Shutdown) –> ENTERED FUNCTION
steam.cpp(-1): (turbulenz::SteamServices::Shutdown) <– LEAVING FUNCTION
nativeplatform_steam.cpp(-1): (turbulenz::NativePlatform::SteamInitialize) <– LEAVING FUNCTION
engine.cpp(390): (turbulenz::StandaloneEngine::Initialize) !! failed to initialize NativePlatform
win32entry.cpp(708): (turbulenz::Win32NativeEngine::Initialize) !! Engine Init: Steam initialization failed (steam_api_init)
win32entry.cpp(714): (turbulenz::Win32NativeEngine::~Win32NativeEngine) Destroying
engine.cpp(642): (turbulenz::StandaloneEngine::GetConfigString) !! steam not available when getting data path
engine.cpp(183): (turbulenz::StandaloneEngine::Shutdown) Exiting turbulenz
standalone.cpp(216): (turbulenz::oortonline::GameCodeShutdown) –> ENTERED FUNCTION
standalone.cpp(217): (turbulenz::oortonline::GameCodeShutdown) GameCodeShutdown
standalone.cpp(-1): (turbulenz::oortonline::GameCodeShutdown) <– LEAVING FUNCTION
engine.cpp(193): (turbulenz::StandaloneEngine::Shutdown) calling TurbulenzEngine.onunload
platform.cpp(373): (turbulenz::Platform::ShutdownAllTasks) shutting down tasks …
engine.cpp(198): (turbulenz::StandaloneEngine::Shutdown) remaining object counts
javascriptengine_v8.cpp(2388): (turbulenz::JavaScriptEngine::DumpObjectCounts) Object Counts:
javascriptengine_v8.cpp(2396): (turbulenz::JavaScriptEngine::DumpObjectCounts) DynamicTestObject – 1
javascriptengine_v8.cpp(2396): (turbulenz::JavaScriptEngine::DumpObjectCounts) ConsoleObject – 1
javascriptengine_v8.cpp(2396): (turbulenz::JavaScriptEngine::DumpObjectCounts) NativePlatform – 1
javascriptengine_v8.cpp(2396): (turbulenz::JavaScriptEngine::DumpObjectCounts) WindowObject – 1
javascriptengine_v8.cpp(2396): (turbulenz::JavaScriptEngine::DumpObjectCounts) Turbulenz – 1
javascriptengine_v8.cpp(2396): (turbulenz::JavaScriptEngine::DumpObjectCounts) DocumentObject – 1
javascriptengine_v8.cpp(2396): (turbulenz::JavaScriptEngine::DumpObjectCounts) StaticTestObject – 1
engine.cpp(202): (turbulenz::StandaloneEngine::Shutdown) Global objects removal
engine.cpp(220): (turbulenz::StandaloneEngine::Shutdown) turbulenzjsengine shutdown
nativeplatform_steam.cpp(54): (turbulenz::NativePlatform::SteamShutdown) –> ENTERED FUNCTION
nativeplatform_steam.cpp(-1): (turbulenz::NativePlatform::SteamShutdown) <– LEAVING FUNCTION
javascriptengine_v8.cpp(1051): (turbulenz::JavaScriptEngine::CollectAllWrappedObjects) Released 0 objects
javascriptengine_v8.cpp(1054): (turbulenz::JavaScriptEngine::CollectAllWrappedObjects) Giving up.
javascriptengine_v8.cpp(1266): (turbulenz::JavaScriptEngine::Shutdown) Custom shutdown …
javascriptengine_v8.cpp(1051): (turbulenz::JavaScriptEngine::CollectAllWrappedObjects) Released 1 objects
engine.cpp(223): (turbulenz::StandaloneEngine::Shutdown) turbulenz static release
engine.cpp(226): (turbulenz::StandaloneEngine::Shutdown) delete platform
engine.cpp(230): (turbulenz::StandaloneEngine::Shutdown) delete jsengine
engine.cpp(234): (turbulenz::StandaloneEngine::Shutdown) static shutdown …
standalone.cpp(168): (turbulenz::oortonline::GameCodeStaticShutdown) –> ENTERED FUNCTION
standalone.cpp(169): (turbulenz::oortonline::GameCodeStaticShutdown) GameCodeStaticShutdown
standalone.cpp(74): (turbulenz::oortonline::NativeCode::StaticRelease) STATIC SHUTDOWN (TEMPLATE): NativeCode
standalone.cpp(-1): (turbulenz::oortonline::GameCodeStaticShutdown) <– LEAVING FUNCTION
engine.cpp(252): (turbulenz::StandaloneEngine::Shutdown) Shutdown doneBased on reading that I infer an issue with Steam, but haven’t any idea how to remedy it.
-
February 6, 2015 at 9:42 am #8057michaelbKeymaster
The log shows the game failed to connect to steam. The obvious things are that steam needs to be running and up to date, as well as connected to the net. Make sure you launch the game from steam, rather than run the exe directly, and the Oort client is up to date in steam.
-
February 6, 2015 at 10:27 am #8058BrookMember
Steam is set to auto-update the game. The client EXE is dated 04FEB15, and displays version 0.1.0 in Properties|Details. The steam_api64.dll file is file version 2.30.48.16, product version 01.00.00.01, last updated locally 14JAN15.
My connection to the internet is 60Mb and running quite well (you can tell because I’m posting this message). It doesn’t appear to matter whether I have Steam running or not. The memory-resident web helpers are always running, and starting the OO client prior to this would generate Steam activity (daily news, etc.). I’ve almost always used a desktop link generated by the Steam install, which is a URL forward to steam://rungameid/324510, to launch OO; until this morning I didn’t know where the actual EXE was.
-
February 7, 2015 at 11:45 am #8073BrookMember
Problem solved–the game was running the entire time. When the window minimized the last time I used the Enter key, the client area size went to 0x0, instead of–whatever seems like a good choice for that. Following a thread of logic I thought I’d see if resizing worked, and it did. The couldn’t contact Steam API message may have been spurious because of something I clicked in the context menu opened by right-clicking the icon in the app tray.
-
-
AuthorPosts
- You must be logged in to reply to this topic.