ID:2960723
 
Resolved
Launching the pager directly after installation caused problems with browsers in games launched from that pager instance. Closing the pager and subsequently reopening it worked around the issue.
BYOND Version:516.1651
Operating System:Windows 11 Pro 64-bit
Web Browser:Chrome 131.0.0.0
Applies to:BYOND Pager
Status: Resolved (516.1655)

This issue has been resolved.
Descriptive Problem Summary:
When you launch your pager for the first time after a 516 install, the data inside Documents\Byond\cache\WebView2 will be bugged/corrupt resulting in random issues with browsers ranging from the inability to type in input fields, events not occurring, to browser crashing when media plays/finishes.

This is greatly hampering adoption because players will try out the new version, see it is unplayable, and downgrade.

Numbered Steps to Reproduce Problem:
1. Close your pager and any byond applications
2. Delete Documents\Byond\cache\WebView2 if it exists
3. Install 516.1651_byond.exe (all default checkmarks - will launch pager after install - doesn't matter if you're already on 516.1651) https://www.byond.com/download/build/516/
4. Run my project
5. Try to type in the box (doesn't work right?)
6. Close the game & pager
7. Delete Documents\Byond\cache\WebView2
8. Start pager again
9. Run my project
10. Try to type in the box (works now right?)

Code Snippet (if applicable) to Reproduce Problem:
/world
fps = 25
icon_size = 32
view = 6

/client/New(TopicData)
..()
var/html = "<html><input type=\"text\"><br>If you can type in this box, congratulations you have a not-busted byond browser!</html>"
var/id = "browser"
src << browse(html, "window=[id]")


macro "macro"
elem
name = "North+REP"
command = ".north"
elem
name = "South+REP"
command = ".south"
elem
name = "East+REP"
command = ".east"
elem
name = "West+REP"
command = ".west"
elem
name = "Northeast+REP"
command = ".northeast"
elem
name = "Northwest+REP"
command = ".northwest"
elem
name = "Southeast+REP"
command = ".southeast"
elem
name = "Southwest+REP"
command = ".southwest"
elem
name = "Center+REP"
command = ".center"


menu "menu"
elem
name = "&Quit"
command = ".quit"
category = "&File"
saved-params = "is-checked"


window "default"
elem "default"
type = MAIN
pos = 291,0
size = 640x480
anchor1 = -1,-1
anchor2 = -1,-1
background-color = none
is-default = true
saved-params = "pos;size;is-minimized;is-maximized"
macro = "macro"
menu = "menu"
outer-size = 656x558
outer-pos = 291,0
inner-pos = 8,51
screen-size = 2560x1392
elem "browser"
type = BROWSER
pos = 0,0
size = 640x480
anchor1 = 0,0
anchor2 = 100,100
background-color = none
saved-params = ""


https://discord.com/channels/725444629172060262/ 725458744711839873/1329958419725029500

Expected Results:
A working browser after a 516 install. E.g. w/ the ability to type in input fields.

Actual Results:
A busted browser after a 516 install. E.g. w/ no ability to type in input fields.

Does the problem occur:
Every time? Or how often? Always
In other games? Yes
In other user accounts? Yes
On other computers? Yes

When does the problem NOT occur?
Unsure how this isn't more widely reported, but I have gotten others to reproduce these steps.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) Applicable to all versions of 516 as far as I can tell.

Workarounds:
Manually delete your WebView2 cache after any update/install of 516. (Pager will not delete this cache).
This is still a problem with the installer for 516.1654. Every install of 516 busts the WebView2 cache.
In response to Drathek
I can't do anything about this until I have better information on how it's happening. The installer does nothing to the cache, so the idea that the installer is somehow breaking the cache makes no sense.
Lummox JR changed status to 'Test case needed'
For clarity to others (lummox already knows) it seems the real issue is that the pager ran as admin (such as launched at the end of the installer) is what locks up the webview cache files preventing dreamseeker (not as admin) to be unable to work correctly.
Lummox JR resolved issue with message:
Launching the pager directly after installation caused problems with browsers in games launched from that pager instance. Closing the pager and subsequently reopening it worked around the issue.

Login to reply.