Databases
StackOverflow2013
Postsdbo
PORendering problems on Chrome and Android
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORendering problems on Chrome and Android
    primarykey
    data
    text
    <p>The game I'm developing renders perfectly on the Java backend and on IE 10. However the rendering on Chrome and Android is weird. I'd assume this was because of WebGL &amp; OpenGL respectively. Here's how it looks on IE. <img src="https://i.stack.imgur.com/y7e9F.png" alt="IE"></p> <p>Here's how it looks on Chrome, and it looks exactly same on the Android backend as well. <img src="https://i.stack.imgur.com/4vty4.png" alt="Chrome"></p> <p>The background did not get rendered, and only the first and last text elements got rendered</p> <p>Are the any restrictions on texture size etc when running in Chrome and Android, anything in particular I have to take care of? All my textures have dimensions the power of 2s. I even tried creating every surface with dimensions the power of 2s, but it doesn't seem to help.</p> <p>Update: I fixed the following issue. It was due to a bug in the UI toolkit I had written, where a new surface was getting created every time a widget's text was set.</p> <p>I'm not sure if the following problem is related, but sometimes the game crashes on Android with the following exception:</p> <pre><code>03-16 14:22:29.010 E/AndroidRuntime(16253): FATAL EXCEPTION: GLThread 10 03-16 14:22:29.010 E/AndroidRuntime(16253): java.lang.StackOverflowError 03-16 14:22:29.010 E/AndroidRuntime(16253): at playn.android.AndroidPlatform.log(AndroidPlatform.java:28) 03-16 14:22:29.010 E/AndroidRuntime(16253): at playn.core.PlayN.log(PlayN.java:120) ...... ...... ...... playn.core.gl.GLContext$Pender.process(GLContext.java:242) 03-16 14:22:29.010 E/AndroidRuntime(16253): at playn.core.gl.GLContext$Pender.process(GLContext.java:242) 03-16 14:22:29.010 E/AndroidRuntime(16253): at playn.core.gl.GLContext$Pender.process(GLContext.j </code></pre> <p>This is because at <a href="http://code.google.com/p/playn/source/browse/core/src/playn/core/gl/GLContext.java" rel="nofollow noreferrer">http://code.google.com/p/playn/source/browse/core/src/playn/core/gl/GLContext.java</a>, GLContext$Pender.process() seems to be called in a never ending cycle. This doesn't happen every time, though.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBlueSilver
    1. USBlueSilver
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORendering problems on Chrome and Android
      1. USBlueSilver
      1. VTFavorite
    2. VO
      singulars
      1. PORendering problems on Chrome and Android
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORendering problems on Chrome and Android
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`java.lang.StackOverflowError` ...looks like you came to the right place for help ;)
      singulars
      1. PORendering problems on Chrome and Android
      1. USJeremy Harris
    2. COWhat is your texture size?
      singulars
      1. PORendering problems on Chrome and Android
      1. USMorrison Chang
    3. COSome 512x512, and some 1024x1024. My phone is a Samsung Galaxy R, and I'm pretty sure it's capable of those texture sizes.
      singulars
      1. PORendering problems on Chrome and Android
      1. USBlueSilver
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload