SolFall
February 25, 2018, 8:29am
1
As you can see below, I’ve logged in today to find just one of my portals have closed, but not the other.
Location
1 Like
vdragon
February 26, 2018, 4:25pm
2
Can you remind me what the issue was again? The portal in the first screenshot is still there, but there are no portal conduit blocks in the second.
Huh? Are all four images not showing for you? First pair shows a portal open on one end, closed on another, conduit blocks visible. Second pair gives location details.
vdragon
February 26, 2018, 5:11pm
4
Okay, I should clarify that I did visit the locations in question.
This is what I saw in Elopor:
I was able to pass through it and turned around to see the portal I just left:
Then going to the portal in Nasharil shows this:
SolFall
February 26, 2018, 5:25pm
5
OH, sorry, i broke down the conduits of the closed ones, and the open one is in front of the bugged portal. so behind the portal on Nasharil is the bugged one.
vdragon
February 27, 2018, 12:38pm
6
Thanks, I see it now.
Can you also share a game log just after you attempt to close this portal so the information should be up to date and show what the problem is?
SolFall
February 27, 2018, 2:41pm
7
Sure, no probs, i’ll post it once i get home from work… in 9 hours
SolFall
February 28, 2018, 2:04am
8
boundless_log
INFO ..\..\src\appbase\win\winentry.cpp:426 (turbulenz::WinNativeEntry::HostWndProc) WM_ERASEBKGND: erasing bg
INFO ..\..\src\browserfeatures\filecache.cpp:169 (turbulenz::FileCache::Initialize) Cache dir: C:\Users\Alex\AppData\Local\Turbulenz\boundless\static-cache\
INFO ..\..\src\appbase\standaloneplatformreaders.cpp:574 (turbulenz::StandalonePlatform::SetHttpCachePath) HttpCache: enabled (C:\Users\Alex\AppData\Local\Turbulenz\boundless\static-cache)
INFO ..\standalone\standalone.cpp:96 (turbulenz::boundless::OortApplication::ApplicationStartup) GameCodeStaticInitialize
INFO ..\..\src\graphicsdriver\d3d11\d3d11context.cpp:331 (turbulenz::graphicsdriver::D3D11Context::Initialize) GPU INFO:
INFO ..\..\src\graphicsdriver\d3d11\d3d11context.cpp:332 (turbulenz::graphicsdriver::D3D11Context::Initialize) 1 devices:
INFO ..\..\src\graphicsdriver\d3d11\d3d11context.cpp:337 (turbulenz::graphicsdriver::D3D11Context::Initialize) 0: Intel(R) HD Graphics 5500 (Driver Ver: '20.19.15.4642', Date: '3-28-2017')
INFO ..\..\src\graphicsdriver\d3d11\d3d11graphicsdriver.cpp:2772 (turbulenz::graphicsdriver::D3D11GraphicsDriver::Initialize) D3D11Info:
INFO ..\..\src\graphicsdriver\d3d11\d3d11graphicsdriver.cpp:2792 (turbulenz::graphicsdriver::D3D11GraphicsDriver::Initialize) Adapter : NVIDIA GeForce 840M
INFO ..\..\src\graphicsdriver\d3d11\d3d11graphicsdriver.cpp:2793 (turbulenz::graphicsdriver::D3D11GraphicsDriver::Initialize) VRAM : 2117992448
This file has been truncated. show original
log
both the log and boundless_log
vdragon
February 28, 2018, 11:06am
9
It’s actually just the log.txt file we needed, but thanks for providing the information regardless.
1 Like
SolFall
February 28, 2018, 2:31pm
10
OH, wasn’t sure which one so better both just in case