Jan 17, 2017, 11:31 PM
Description: Every time you open the F1 menu, the game locks up for a second. Some players even experience crashes.
Since when have you experienced the bug? since it was added
Additional Information:
This is caused because the F1 menu is done in HTML, so it requires a new Awesomium process to be started. Since GMod is single core, the game locks up until the renderer has opened.
I imagine the F1 menu is not preserved when closed because most menus are created and deleted.
Theoretically, if the F1 menu is coded to be created once when the player spawns in (since it pops up anyway) this will fix this issue and crashes around it (do those still happen?). The F1 button would simply show the menu rather than opening it.
This function (theoretically, if it doesn't an issue should be opened on the GMod github or the devs told) should make it so the close button will simply hide the menu:
This will make it so the menu does not delete itself when closed.
Since when have you experienced the bug? since it was added
Additional Information:
This is caused because the F1 menu is done in HTML, so it requires a new Awesomium process to be started. Since GMod is single core, the game locks up until the renderer has opened.
I imagine the F1 menu is not preserved when closed because most menus are created and deleted.
Theoretically, if the F1 menu is coded to be created once when the player spawns in (since it pops up anyway) this will fix this issue and crashes around it (do those still happen?). The F1 button would simply show the menu rather than opening it.
This function (theoretically, if it doesn't an issue should be opened on the GMod github or the devs told) should make it so the close button will simply hide the menu:
Code:
Frame:SetDeleteOnClose(false)
This will make it so the menu does not delete itself when closed.