Can't leave the crafting menu

itzKaeseitzKaese Posts: 2Member
edited October 2016 in Bug Reports
First things first, my OS is Windows 7 and I am playing with a keyboard and mouse.
My setup is:
AMD FX 6300 (Hexa Core Processor 3.5ghz)
Nvidia GTX 650Ti (2gb gddr5)
8gb of RAM
I have the latest game version as of now (v.0.1.4.29048).

The bug I have encounterd doesn't let me leave the inventory screen, after clicking on the gear icon of any of my items.
I am stuck in the crafting menu of whatever item I have just opened and can't even change the menu to that of a different item.
I can however still craft upgrades and items, even though that doesn't change anything.
ESC and Tab don't work and the only solution I have is to Alt+F4 to leave the game.

I have also encounterd a similar bug, where the exact same thing happens, only that I can leave the Inventory Screen, but as soon as the game unpauses, I can see my mouse pointer, hovering over the crafting menu, which immidiately pops up into the middle of the screen.
The game then begins to stutter for a few seconds before crashing and the following bug report is left behind:

Access violation - code c0000005 (first/second chance not available)

RSG_Win64_Shipping!UScrollBoxEx::IsNeeded() [i:\win64_fullrebuild\rsg\source\rsg\ui\scrollboxex.cpp:18]
RSG_Win64_Shipping!UScrollBoxEx::GetMaxScrollOffset() [i:\win64_fullrebuild\rsg\source\rsg\ui\scrollboxex.cpp:26]
RSG_Win64_Shipping!UScrollBoxEx::execGetMaxScrollOffset() [i:\win64_fullrebuild\rsg\source\rsg\ui\scrollboxex.h:15]
RSG_Win64_Shipping!UFunction::Invoke()
RSG_Win64_Shipping!UObject::CallFunction()
RSG_Win64_Shipping!UObject::ProcessContextOpcode()
RSG_Win64_Shipping!UObject::execLet()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UObject::CallFunction()
RSG_Win64_Shipping!UObject::ProcessContextOpcode()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UObject::CallFunction()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UObject::CallFunction()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UObject::CallFunction()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UFunction::Invoke()
RSG_Win64_Shipping!UObject::ProcessEvent()
RSG_Win64_Shipping!TMulticastScriptDelegate::ProcessMulticastDelegate() [c:\program files (x86)\epic games\4.12\engine\source\runtime\core\public\uobject\scriptdelegates.h:454]
RSG_Win64_Shipping!FCallDelegateHelper::CallMulticastDelegate()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UObject::CallFunction()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UObject::CallFunction()
RSG_Win64_Shipping!UObject::ProcessInternal()
RSG_Win64_Shipping!UFunction::Invoke()
RSG_Win64_Shipping!UObject::ProcessEvent()
RSG_Win64_Shipping!UUserWidget::OnKeyUp()
RSG_Win64_Shipping!UUserWidget::NativeOnKeyUp()
RSG_Win64_Shipping!SObjectWidget::OnKeyUp()
RSG_Win64_Shipping!SWindow::FArguments::operator[]()
RSG_Win64_Shipping!FEventRouter::Route >()
RSG_Win64_Shipping!FSlateApplication::ProcessKeyUpEvent()
RSG_Win64_Shipping!FSlateApplication::OnKeyUp()
RSG_Win64_Shipping!FWindowsApplication::ProcessDeferredMessage()
RSG_Win64_Shipping!FWindowsApplication::DeferMessage()
RSG_Win64_Shipping!FWindowsApplication::ProcessMessage()
RSG_Win64_Shipping!FWindowsApplication::AppWndProc()
user32
user32
RSG_Win64_Shipping!FWindowsPlatformMisc::PumpMessages()
RSG_Win64_Shipping!FEngineLoop::Tick()
RSG_Win64_Shipping!GuardedMain()
RSG_Win64_Shipping!GuardedMainWrapper()
RSG_Win64_Shipping!WinMain()
RSG_Win64_Shipping!__scrt_common_main_seh() [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253]
kernel32
ntdll

Comments

  • ROCKFISH_AndiROCKFISH_Andi Posts: 1,033Moderator
    Thanks for reporting, I think I fixed the problem for #2 on Friday. Hopefully it's related to #1, not sure, though.
  • itzKaeseitzKaese Posts: 2Member
    Small Update, for anyone experiencing the same bug, if you use the keyboard to access, just access, the crafting menu, then this bug doesn't seem to appear at all.
    I think that this bug only appears, when people like me, who have tendency to double-click the mouse, click on the little gear icon too often and too fast.
Sign In or Register to comment.