By default, my Ubuntu 14.04 desktop guest running under VMware ESXi has a maximum resolution of 1360×768 when accessed with the Remote Client, which although usable is not great on my MacBook Pro:
In the guest settings for my Ubuntu guest, I have rather limited graphics settings:
I tried bumping up the memory and see if that opens up some additional settings but that didn’t change anything, although for higher resolutions it’s most likely I would need more gpu memory, but that’s not the issue with the limited settings here.
Searching for ‘ESXi linux guest maximum resolution’ I found this article:
Following on from yesterday’s post on getting started with my Blackjack Card Game Twitter bot, I’m persisting the game state per player to AWS DynamoDB. Here’s what my schema looks like so far:
Each row persisted represents a game in progress, keyed by the player’s Twitter handle. More updates to come shortly.
For my next project I’m thinking about what it would involve to build a multiplayer card game playing bot, a simple card game to get started, like Blackjack. The Twitter REST apis I’ve used so far will be reusable for this project, but the interesting parts are the interaction between a player and the bot, the game logic, and the persistence of game state (each of which I’ll discuss in future posts).
I’ve been thinking about the interaction for the gamevand think it will look something like this:
Player: @blackjackcard deal
Bot: @player bot deals you 4 Clubs and 7 Spades. Reply hit or stick
Player: @blackjackcard hit
Bot: @player bot deals you 4 Hearts. You now have 4 Clubs, 7 Spades, 4 Hearts. Reply hit or stick
Player: @blackjackcard stick
Bot: @player the bot currently has 3 Hearts, 9 Clubs, and takes a card
Bot: @player the bot takes 10 Diamonds and now has 3 Hearts, 9 Clubs, 10 Diamonds. Bust! You win!
The interesting part of the gameplay interaction is that there’s only 3 commands:
deal: start a game (get dealt your initial two cards)
hit: get dealt another card
stick: keep current hard
This makes the options that the bot needs to handle pretty simple. Next up, I’ll talk about persisting the game state to AWS DynamoDB.
It’s been a year and a half since I’ve given an update on my Space Invaders clone on Android. Admittedly I haven’t been working continuously in my spare time on this project for 18 months, in fact the last time I remember working on it was several months back. What I got stuck on was updating the animation routines so the animation would display with a constant frame rate across different Android devices, and the display of the sprites to look consistent for devices with different sized screens, resolutions and pixel densities.
If you’re a seasoned game developer this is probably nothing new to you. If you only develop for a platform with identical hardware specs (like a game console) then this is probably something you don’t have to worry (too much?) about. However with the broad range of specs for Android devices, even testing with the device emulator for different phones, it’s pretty obvious unless your code handles these differences, your game might be fast on one device but slow on another, or the sprite layout may look at intended at the resolution on one phone but be too small on another phone.
I spent a bunch of time reading game dev articles about implementing approaches for constant frame rates, and tried to incorporate what I’d learned, but still, I’ve got some weird quirks I need to iron out.
Here’s what the game looks like on an emulated Pixel:
I was initially developing and testing on the emulated Nexus devices as my baseline test target, but it runs fine, as expected on the Pixel too (it’s harder to play when pressing the buttons with the mouse!).
Now running on an emulated Pixel 2 XL, it runs fine for a while until the number of invaders gets down to where I speed up. The speed up is too fast, and then for some reason that I haven’t found yet they animation stops before the game ends but the game is still playing:
Clearly I’ve still got some work to do here, but it’s getting close.
