Jump to content

b10b

Members
  • Content Count

    678
  • Joined

  • Last visited

  • Days Won

    24

b10b last won the day on June 1

b10b had the most liked content!

2 Followers

About b10b

  • Rank
    Advanced Member

Contact Methods

  • Twitter
    b10bgames

Recent Profile Visitors

8848 profile views
  1. I am wondering about your audience, who they are, where, what they spend money on, and how? At such low eCPM and no uptake on the IAP the answers might not be good news and hitting reset may be appropriate. Then pivot the positioning of the game towards a higher value audience and build the audience back up? But for sure, removing non-performing ads in the meanwhile is a very good thing.
  2. All ads are annoying, the value to obstruction ratio is negative whether someone is aware of it or not. Your players hate the ads; they don't click on them; no value is earned for the advertiser; eCPM plunges. Mathematical proof: at $0.05 eCPM you are needing to present 20,000 ads to earn a single dollar. Those ads have consumed hours and hours of players' time to display (even if dismissed immediately) to create the equivalent game content that can be developed for $1 of your creative time. This isn't just annoying, it is an irritation inflicted on others of such magnitude that it is easi
  3. Oof ... yet $2 eCPM is relatively "good". So my suggestion is to accept how it is and stop using ads - they are annoying to players and create negligible value to advertisers. Or, the benefit does not warrant the cost. By totally rejecting eCPM it may lead to discovering something new?
  4. Have you considered doing your collisions on a dataset that isn't the isometric view? For example, the isometric world is likely created with tiles (2D) from a dataset (2D map)? Why not generate a "hit map" (2D top down) at the same time the isometric tiles are parsed? Then use that exclusively for collision detection and Y displacement (for raised areas). I have a vague recollection that the original "Marble Madness" (or another old school game) used a chromakey of the isometric view for collisions and physics properties. A chromakey (where each item has a unique color, thereby r
  5. My advice would be don't worry too much about "spinning" reels or "graphics" to start off with (first project afterall). First think of columns of data ... each "reel" (x5) is an array of 64 "symbol"s. Then increment the "index" of that array per reel. The 3 symbols visible on each reel are: reel[index-1], reel[index], reel[index+1]. Next consider that -1 or +1 might take the array out of range, fix that with modulo: reel[(index-1)%reel.length], reel[index], reel[(index+1)%reel.length]. Starting a spin, stopping a spin, shuffling a spin, even animating the spin are now modifiers
  6. Yep ... think of it as "reading a page" rather than "flying a plane" then it'll make a bit more sense until it becomes automatic. Why is Y down? iirc it's to do with gravity, and how on early raster displays there are no lines, just a gradual droop of the ray with a period return of the X, and a period return of the Y as a multiple of the X period.
  7. Edit ... found it, three links in: https://www.facebook.com/fbgaminghome/developers/instant-games/approved-partner-program Btw I'm pleased to see this approach, I doubt I'd ever put "my" indie games on Facebook but it's good to see that copycats won't be able to clone my games as easily in future. It should lift quality and player experience.
  8. @serhiic is that your tool? If so thanks. One issue I found was (within styles) the drop shadow was on top of the stroke. Seems wrong to me, the drop shadow should be lowest element, underneath the stroke.
  9. https://pixijs.download/dev/docs/PIXI.Texture.html#from For the blob scenario it's a helper function to ImageResource which uses the same async methods you describe (image.src + image.onload). https://pixijs.download/v5.1.2/docs/packages_core_src_textures_resources_ImageResource.js.html So what's the alternative? Custom write a blob to pixel data parser in Javascript (to replicate the inbuilt image.src + image.onload methods). Then you have the option to run it synchronous and wait for completion by blocking the main thread. However ... Such a parser will likely
  10. I doubt there will be a holy war - neither are bad choices for making web games, but one is not a game engine so a direct comparison might be on shaky ground? From my understanding: Pixi is proven for putting things on screen in a mostly unopinionated way (library). Phaser is proven for making Phasery style games in a Phasery style way (framework). Pixi is first in class (not many alternatives for rendering 2D graphics fast to browser). Phaser has stiff competition (many alternatives for HTML5 game engines). Pixi will need developer expertise to make a technically goo
  11. Generally this. Or at least that's the starting point. There are finer points to consider: how large a buffer / margin to operate, how frequently to reconfigure the tiles, whether the larger tilemap should be chunked, whether tiles can be cached / cloned, ..., ..., ...., no end to it? Tiling is about juggling multiple subsystems at once, each having their own level of precision vs performance. Rendering on screen needs highest precision and will likely represent the largest impact on performance - so don't worry about abstract calculations that will reduce that burden. And remembe
  12. If I understand correctly the player is effectively being viewed in a predicted future - so when an unexpected interaction from the past catches up with them it is jarring because it proves the recent predictions wrong. The goal is to smooth this out to the extent it is no longer distractingly observable. This article explains some approaches better than I would manage here: https://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking The takeaway is to embrace a default 100ms lag. Compensate the Players' inputs (rewind time to when the input was most likely made) rat
  13. Interesting. Does WebVR not solve this? As HTML5 devs shouldn't we champion web over installables / app stores? Perhaps, if VR users are early adopters, minor obstacles like web delivery won't massively interfere? Cordova / PhoneGap aren't limited to 2D so, if an app is important for other reasons, these may achieve the goal for Quest?
×
×
  • Create New...