Note that there are some explanatory texts on larger screens.

plurals
  1. USZiiiii
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COThanks @Lestat , that helps. I have no problem following TrivialDrive instruction on IAP but I am clueless in integrating both IAP and Libgdx. I am not sure which part is handle by Libgdx and/or android. As an example (TrivialDrive), in libgdx, where should I place the PublicKey? Do I still need to declare IabHelper mHelper, in Core or Android? How do I call the “launchPurchaseFlow(this, SKU_BUYCLICK, RC_REQUEST, mPurchaseFinishedListener, payload)”? do I call it from Core or Android? Currently I am running around like a headless chicken, any help is much appreciated.
      singulars
    2. COI/awesomegame(29728): LoadingScreen: =-800 getProgress0.0 ... I/awesomegame(29728): LoadingScreen: smallBox: in render() == null I/awesomegame(29728): LoadingScreen: loadingPercent != null I/awesomegame(29728): LoadingScreen: before calling SplashScreen =-1 getProgress1.0 I/awesomegame(29728): SplashScreen: show() I/awesomegame(29728): SplashScreen: resize() I/awesomegame(29728): game: set screen to: SplashScreen I/awesomegame(29728): AbstractScreen: pause(): SplashScreen I/awesomegame(29728): game: Pausing game I/awesomegame(29728): SplashScreen: hide()
      singulars
    3. COi re-enable all logging process, it seems that: I/awesomegame(29728): game: Creating game on Android I/awesomegame(29728): game: setScreen( new LoadingScreen(this) ) I/awesomegame(29728): LoadingScreen: assetManager.load() I/awesomegame(29728): LoadingScreen: Image smallBox I/awesomegame(29728): game: set screen to: LoadingScreen I/awesomegame(29728): game: Resizing game I/awesomegame(29728): LoadingScreen: =-800 getProgress0.0 I/awesomegame(29728): LoadingScreen: smallBox: in render() == null I/awesomegame(29728): LoadingScreen: loadingPercent != null
      singulars
 

Querying!

 
Guidance

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