Double Bubble Demo Slot
Double bubble is the second project I worked on at Gamesys. The game is a simple slot game for mobile with the additional mechanic of a bubble line and bubble pop bonus. Rebuilt from the ground up in javascript and HTML5 it is currently the highest earning game for the company.
My contribution to the project covered the following areas:
Audio – The sounds from the game were taken from the original flash version, compressed to a 64kb bit rate to suit mobile downloads and implemented for the spin, reel stops, win levels and bubble pop bonus.
Slot development companies were quick to act and came up with a brilliant idea — demo slots. Demo slots are essentially free slots, and they enable players to play as much as they want for free. What makes them “demo” is the fact that you can make a deposit and switch to playing for real money whenever you want to. Try Bubble Double slot online for free in demo mode with no download or no registration required. Online Casinos Online casinos. Top online casinos Newly opened casinos Big brands All casinos Popular filters. Mobile-friendly casinos Bitcoin/crypto casinos Live Roulette. For those who are looking for a light and fun game, the Double Bubble slot machine is a good choice. This 5-reel game can make your inner child jump out of joy because of its color and design. A combination of hues in baby pink and blue green makes the game more pleasing in the eyes. On this page, you can access a demo version of the game for free. Double Bubble Slot Demo want to claim the online casinos welcome bonus then you will definitely have to use a debit card. Failure to do so can result in no welcome bonus being credited and then you wont be able to create a new account to get it anyway. Double Bubble Slot is a classic five-reel, 20-payline free slots game from the established UK developer Gamesys. With a simple formula that references vintage Vegas casino slots, Double Bubble will take you back to the old school! Double Bubble transports you to a.
Bubble Line – The bubble line is the meter present at the bottom of the game which reflects any bubbles currently shown on the reel-set, although the triggering of a win on this line is dealt with via https response from a server the icons on the line were implemented using Tween.js and Pixi.js.
Controls – The controls designed for the game are a standard across all Gamesys games and are injected into the DOM during the loading process, this injection was implemented via another team. My responsibility with this area was to ensure the game responded to the events sent from the controls such as mute, changing the bet lines, coin size and spin.
WinDisplay – The boxes and graphics that surround the icons of the reel-set during a win. My responsibility in this area was to draw the boxes and graphic (white background beneath the transparent icon of the reel). This was done using Pixi.js to draw the graphics in the right position. Additionally the smaller boxes that display the amount won per line were also part of this implementation.
Loading Screen – The loading screen of the game is a crucial feature, it is the entry point and the first thing the user sees when they start the game. Minus the logo and background (which is simply a canvas background set to the specific colour). The loading bar is the interesting part of this implementation.
The bar itself reflects the progress of several asset loaders running in the background via Pixi.js to load different aspects from the back end servers. These assets are determined via a bucket system and venture, the bucket system will define the boundaries of the screen and so will load the correct assets based on these reported boundaries, from the correct venture folder, in this case the venture is Virgin Games.
Additionally, the progress of the bar is forced to stop at 95%, this is to stop the user from believing the game has stalled when the bar reaches 100% and the game does not immediately start. The additional 5% reflects the game setting the assets up in the right place and waiting for the initial server handshake before showing the game, if this handshake does not get made for whatever reason an error is shown.
Bug Fixing – There were several bugs during the development process of the game. One bug that I’d like to highlight was related to memory usage within the game for iOS devices. The cache of an iPad can only support up to an OS Specific size, in our case the smallest size was 300MB. This meant that if any assets stored within the cache pushed the limit, the OS would automatically close the browser for using too much memory.
During development of the game we came across the browser crashing on an iPad 2 iOS 6. Not being sure of the cause I spent several hours tracking down the issue using instruments from Xcode to watch memory usage through the different parts of the game.
The solution to this issue lied within the drawing of the bet lines themselves. It was discovered that another developer had set the lines to cache as bitmap every time the line was shown rather than once. With 20 lines at a time and each one having the opportunity to be shown an infinite amount of times, eventually the cache limit would be hit and passed. Removing this setting to cache on draw proved an adequate solution to the issue.
Challenges:
Being the first game I have developed from start to finish using JavaScript, DoubleBubble presented many challenges, from learning another language having come from mostly a C, C++ and Java background to using several open source libraries such as Tween.js, Pixi.js, Howler.js and Node.js.
I learned not only the issues of developing for the mobile platform in terms of design, layout and problems involving rotation and screen size but also to better structure my code using the unique elements of javascript such as Closures and function callbacks.
Summary:
Since the game has been released I have moved onto other projects and my skill with JavaScript and game development in general has improved, I have learned from the mistakes made during development of the game and as a result the code written for the next games I am developing within Gamesys is shorter, more efficient and structured better to be more readable.
The game can be found here: https://m.virgingames.com/game/slot-double-bubble/demo
(NOTE: The game can only be viewed on a mobile device or with device emulation within a browser).
Images:
Double bubble is the second project I worked on at Gamesys. The game is a simple slot game for mobile with the additional mechanic of a bubble line and bubble pop bonus. Rebuilt from the ground up in javascript and HTML5 it is currently the highest earning game for the company.
My contribution to the project covered the following areas:
Audio – The sounds from the game were taken from the original flash version, compressed to a 64kb bit rate to suit mobile downloads and implemented for the spin, reel stops, win levels and bubble pop bonus.
Bubble Line – The bubble line is the meter present at the bottom of the game which reflects any bubbles currently shown on the reel-set, although the triggering of a win on this line is dealt with via https response from a server the icons on the line were implemented using Tween.js and Pixi.js.
Controls – The controls designed for the game are a standard across all Gamesys games and are injected into the DOM during the loading process, this injection was implemented via another team. My responsibility with this area was to ensure the game responded to the events sent from the controls such as mute, changing the bet lines, coin size and spin.
WinDisplay – The boxes and graphics that surround the icons of the reel-set during a win. My responsibility in this area was to draw the boxes and graphic (white background beneath the transparent icon of the reel). This was done using Pixi.js to draw the graphics in the right position. Additionally the smaller boxes that display the amount won per line were also part of this implementation.
Loading Screen – The loading screen of the game is a crucial feature, it is the entry point and the first thing the user sees when they start the game. Minus the logo and background (which is simply a canvas background set to the specific colour). The loading bar is the interesting part of this implementation.
The bar itself reflects the progress of several asset loaders running in the background via Pixi.js to load different aspects from the back end servers. These assets are determined via a bucket system and venture, the bucket system will define the boundaries of the screen and so will load the correct assets based on these reported boundaries, from the correct venture folder, in this case the venture is Virgin Games.
Additionally, the progress of the bar is forced to stop at 95%, this is to stop the user from believing the game has stalled when the bar reaches 100% and the game does not immediately start. The additional 5% reflects the game setting the assets up in the right place and waiting for the initial server handshake before showing the game, if this handshake does not get made for whatever reason an error is shown.
Bug Fixing – There were several bugs during the development process of the game. One bug that I’d like to highlight was related to memory usage within the game for iOS devices. The cache of an iPad can only support up to an OS Specific size, in our case the smallest size was 300MB. This meant that if any assets stored within the cache pushed the limit, the OS would automatically close the browser for using too much memory.
During development of the game we came across the browser crashing on an iPad 2 iOS 6. Not being sure of the cause I spent several hours tracking down the issue using instruments from Xcode to watch memory usage through the different parts of the game.
Multi Slots Demo Play
The solution to this issue lied within the drawing of the bet lines themselves. It was discovered that another developer had set the lines to cache as bitmap every time the line was shown rather than once. With 20 lines at a time and each one having the opportunity to be shown an infinite amount of times, eventually the cache limit would be hit and passed. Removing this setting to cache on draw proved an adequate solution to the issue.
Double Bubble Demo Slots
Challenges:
Being the first game I have developed from start to finish using JavaScript, DoubleBubble presented many challenges, from learning another language having come from mostly a C, C++ and Java background to using several open source libraries such as Tween.js, Pixi.js, Howler.js and Node.js.
I learned not only the issues of developing for the mobile platform in terms of design, layout and problems involving rotation and screen size but also to better structure my code using the unique elements of javascript such as Closures and function callbacks.
Summary:
Since the game has been released I have moved onto other projects and my skill with JavaScript and game development in general has improved, I have learned from the mistakes made during development of the game and as a result the code written for the next games I am developing within Gamesys is shorter, more efficient and structured better to be more readable.
The game can be found here: https://m.virgingames.com/game/slot-double-bubble/demo
(NOTE: The game can only be viewed on a mobile device or with device emulation within a browser).
Images: