DeletedUser867
Guest
Game version: 0.14.13280-255cebe-(master) (2015-04-20 11:28)
Game world: BETA 1
Browser + version: Version 42.0.2311.90 m Google Chrome is up to date.
Flash Player version: __
Adobe Flash Player - Version: 17.0.0.169
Shockwave Flash 17.0 r0
Name: Shockwave Flash
Description: Shockwave Flash 17.0 r0
Version: 17.0.0.169
Location: C:\Program Files\Google\Chrome\Application\42.0.2311.90\PepperFlash\pepflashplayer.dll
Type: PPAPI (out-of-process)
Disable
0" jstcache="22" style="vertical-align: top;">MIME types:
MIME type Description File extensions
application/x-shockwave-flash Shockwave Flash 0" class="hlisting" jstcache="30" style="border-spacing: 0px;">
.swf
application/futuresplash FutureSplash Player 0" class="hlisting" jstcache="30" style="border-spacing: 0px;">
.spl
Disable Always allowed to run
Operating System:
OS Name Microsoft Windows 8.1 Pro
Version 6.3.9600 Build 9600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name MARVL-GAMING
System Manufacturer System manufacturer
System Model System Product Name
System Type X86-based PC
System SKU To Be Filled By O.E.M.
Processor Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz, 2668 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1303, 2/26/2009
SMBIOS Version 2.5
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASUSTeK Computer INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.3.9600.17196"
User Name MarvL-Gaming\MARVL-GAMING\MarvL
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 3.00 GB
Total Physical Memory 2.99 GB
Available Physical Memory 948 MB
Total Virtual Memory 12.0 GB
Available Virtual Memory 8.74 GB
Page File Space 9.00 GB
Page File C:\pagefile.sys
Screen resolution:
AMD Radeon HD 6800 Series
1. LG M2280D, 1776 x 1000, Landscape, Extend
2. Samsung S248300, 1020 x 1080, Landscape, Extend
Account name: Katwijk
Humans or Elves: Elf
Reproducibility: I ran several trials. My methodology was to start from the home screen, and when the system stalled at 64% I waited for 10 seconds and then pressed F5. The following counts are the number of times F5 was pressed in each trial until the application completely loaded.
* Only BETA 1 running:
4,5,1,0,0,1,3,3,0,0
* Several Applications running, including FoE and WORLD 1:
0,0,0,1,0,4,3,0,3,20
These trials were run on Friday 4/24/14 at 10:30 am US Game Time
Related tests using Ctrl+F5 (ignore the cache) and loading from the initial screen provided a similar pattern.
Quest title: #NA
Current situation:
Stalling at 64% is unique to BETA 1. FoE and World 1 sail right past 64%.
Expected situation:
Load allocation should be seamless to the user.
Reproduction Steps
See above, under Reproducibility, as that's the essence of this bug.
Screenshots of the bug:
Here's a snapshot of the Resource Monitor immediately after the 20 failure trial.
Game world: BETA 1
Browser + version: Version 42.0.2311.90 m Google Chrome is up to date.
Flash Player version: __
Adobe Flash Player - Version: 17.0.0.169
Shockwave Flash 17.0 r0
Name: Shockwave Flash
Description: Shockwave Flash 17.0 r0
Version: 17.0.0.169
Location: C:\Program Files\Google\Chrome\Application\42.0.2311.90\PepperFlash\pepflashplayer.dll
Type: PPAPI (out-of-process)
Disable
0" jstcache="22" style="vertical-align: top;">MIME types:
MIME type Description File extensions
application/x-shockwave-flash Shockwave Flash 0" class="hlisting" jstcache="30" style="border-spacing: 0px;">
.swf
application/futuresplash FutureSplash Player 0" class="hlisting" jstcache="30" style="border-spacing: 0px;">
.spl
Disable Always allowed to run
Operating System:
OS Name Microsoft Windows 8.1 Pro
Version 6.3.9600 Build 9600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name MARVL-GAMING
System Manufacturer System manufacturer
System Model System Product Name
System Type X86-based PC
System SKU To Be Filled By O.E.M.
Processor Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz, 2668 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1303, 2/26/2009
SMBIOS Version 2.5
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASUSTeK Computer INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.3.9600.17196"
User Name MarvL-Gaming\MARVL-GAMING\MarvL
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 3.00 GB
Total Physical Memory 2.99 GB
Available Physical Memory 948 MB
Total Virtual Memory 12.0 GB
Available Virtual Memory 8.74 GB
Page File Space 9.00 GB
Page File C:\pagefile.sys
Screen resolution:
AMD Radeon HD 6800 Series
1. LG M2280D, 1776 x 1000, Landscape, Extend
2. Samsung S248300, 1020 x 1080, Landscape, Extend
Account name: Katwijk
Humans or Elves: Elf
Reproducibility: I ran several trials. My methodology was to start from the home screen, and when the system stalled at 64% I waited for 10 seconds and then pressed F5. The following counts are the number of times F5 was pressed in each trial until the application completely loaded.
* Only BETA 1 running:
4,5,1,0,0,1,3,3,0,0
* Several Applications running, including FoE and WORLD 1:
0,0,0,1,0,4,3,0,3,20
These trials were run on Friday 4/24/14 at 10:30 am US Game Time
Related tests using Ctrl+F5 (ignore the cache) and loading from the initial screen provided a similar pattern.
Quest title: #NA
Current situation:
Stalling at 64% is unique to BETA 1. FoE and World 1 sail right past 64%.
Expected situation:
Load allocation should be seamless to the user.
Reproduction Steps
See above, under Reproducibility, as that's the essence of this bug.
Screenshots of the bug:
Here's a snapshot of the Resource Monitor immediately after the 20 failure trial.
Last edited by a moderator: