Help on playing

[kateku]

Hi,

I have been trying for a long time to play on Chrome. But i had no luck since it was lanch, whenever i load the game, it always stuck at 43% and then the game will keep loading and never reach the login page.

I try enable or disable on Chrome. It is not Failed to initialize graphics.

Hope there is help on how to play on Win7.

[BodMaster]

Hey Devine,

Check some of these fixes out.

http://www.spacetimestudios.com/showthread.php?40941-quot-Failed-to-initialize-graphics-quot-**FIX**

Also ensure you have the most upto date graphics driver.

[Skeletonlord]

im on windows 7 and i can play. reinstall and install chrome, and enable native client. if this is enabled hit "relauch browser" at the bottom of the page. Then click the spanner tool top right, and "about google chrome" it will update for you.

make sure you have the most up to date and newest version of chrome, as well as your graphics drivers.

link to download google chrome: https://www.google.com/chrome/?brand=ECDB&installdataindex=no-apps-no-promo

link to update graphics drivers: http://windows.microsoft.com/en-US/windows-vista/Update-a-driver-for-hardware-that-isnt-working-properly

[jupi]

Hi, I am experiencing the same problem, when I launch the game in Chrome, it stays at 43%.

I'm using Chrome 17.0.963.12 dev with nvidia-drivers 290.10 (GeForce 9500 GT) on a 64bit gentoo linux system.

I was thinking the bug would have come from my "excentric" system, but now I see that you have it on windows too, it seems it might not be.

[Futumsh]

Hi, I am experiencing the same problem, when I launch the game in Chrome, it stays at 43%.

I'm using Chrome 17.0.963.12 dev with nvidia-drivers 290.10 (GeForce 9500 GT) on a 64bit gentoo linux system.

I was thinking the bug would have come from my "excentric" system, but now I see that you have it on windows too, it seems it might not be.

Open up the javascript console and refresh, and tell us what shows up there, if anything.

[jupi]

Ok, thanks for the hint!
Now I see that :

"NativeClient: NaCl module load failed: Nexe crashed during startup"

switching to chrome-17.0.963.26 and nacl-toolchain-newlib 0_p7311 didn't help.

[Matutd]

Type in:
Chrome:flags and enable native client it should work then

[jupi]

Allready done that:

Native Client
Enable Native Client for all web applications, even those that were not installed from the Chrome Web Store.
Disable

Should work, but doesn't... still the nexe crashed
it would seem someone has the same problem with a 64 bit arch linux.

[jupi]

Re, just gave it another try, with launching chrome from the console with --enable-nacl.
Here's the console output (comments in bold)

jupiter@JuPiTeR ~ $ google-chrome --enable-nacl
[29621:29631:1699861081109:ERROR:object_proxy.cc(23 9)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files (this error is when I launch Chrome)
[29621:29634:1699864952711:ERROR:native_backend_kwa llet_x.cc(774)] Error obtaining KWallet handle (this error is when I deny access to my KDE wallet to chrome (shouldn't be needed anyway)
All the next errors are when I try to start Starlegends
[29700,1901070080:09:44:45.735435] Native Client module will be loaded at base address 0x00007f2200000000
[29700,1901070080:09:44:46.851766] Entered NaClMakeDispatchThunk
[29700,1901070080:09:44:46.851936] NaCl_page_alloc_randomized: 0x7fbd3708
[29700,1901070080:09:44:46.851947] NaCl_page_alloc_randomized: hint 0x7fbd37080000
[29700,1901070080:09:44:46.851961] NaClMakeDispatchThunk: got addr 0x7fbd37080000
[29700,1712695616:09:44:47.007914] MakeDynamicCodePageVisible: NaCl_mprotect() failed
LOG_FATAL abort exit
[29673,3161859840:10:44:47.009539] PluginReverseInterface::ReportCrash
[29673,3161859840:10:44:47.009653] PluginReverseInterface::ReportCrash: invoking CB
jupiter@JuPiTeR ~ $

Any further idea?

PS: I submitted the bug to the Google Chrome dev at http://code.google.com/p/nativeclient/issues/detail?id=2533

[jupi]

Solved by Google devs:
And from there the answer came...
on my computer, it just worked by remounting shm with exec rights:
# mount -o exec /dev/shm

(note: this weakens systemwide security)