From a design perspective, I want a single stat that is easy to share with friends, and I feel that's # of skips because it's something the user is actively involved in, distance is secondary imo. But now... if I leave both, users are going to share what they think was important or best about their own run (not a single stat). But if I remove all but skips, users might feel like they either went really high or really far and there's no stat to represent that
Flappy Bird, Timber Man, and Super Hexagon all have this really simple stat I'm trying to culture
"Hahah, I made it to 10.6s in Super Hexagon!! How long did you last!?"
if someone clicks the ad while over the air and they hit that 100 MB limit and don't download it, then we're paying for clicks and not getting anything.
that aspect has been judged more important than the potential frustration of "You have the game! Now download the tutorial."
Phew, it's quite a bit of work getting something released on a phone
Just tying up loose ends, making everything look nice, adding a mute button, scaling some things but not others, remastering the audio to remove static, etc.
So yeah, I was thinking about the "Distance" stat in Skippy Fish some more last night, and I don't think it's very relatable. If I say I went "24.6m", what does that mean? So, I think I'm going to make a whole new stat: Time
"I lasted 14.6 seconds" is relatable, and everyone knows what that means
completely "basic" example of using a shader to render a tri
var vertexShaderByteCode = ShaderBytecode.CompileFromFile("MiniTri.fx", "VS", "vs_4_0", ShaderFlags.None, EffectFlags.None);
var vertexShader = new VertexShader(device, vertexShaderByteCode);
var pixelShaderByteCode = ShaderBytecode.CompileFromFile("MiniTri.fx", "PS", "ps_4_0", ShaderFlags.None, EffectFlags.None);
var pixelShader = new PixelShader(device, pixelShaderByteCode);
var layout = new InputLayout(
device,
ShaderSignature.GetInputSignature(vertexShaderByteCode),
new[]
{
so here it is
as with all demo code its usually wordy and badly "designed"
I wanted to improve the code a bit so i tried this ...
var vertexShader = new VertexShader(device, ShaderBytecode.CompileFromFile("Shaders/Coloured.fx", "VS", "vs_4_0", ShaderFlags.None, EffectFlags.None));
var pixelShader = new PixelShader(device, ShaderBytecode.CompileFromFile("Shaders/Coloured.fx", "PS", "ps_4_0", ShaderFlags.None, EffectFlags.None));
VertexPositionColour[] data = new VertexPositionColour[]
{
new VertexPositionColour { Position = new Vector4(0.0f, 0.5f, 0.5f, 1.0f), Colour = new Vector4(1.0f, 0.0f, 0.0f, 1.0f) },
new VertexPositionColour { Position = new Vector4(0.5f, -0.5f, 0.5f, 1.0f), Colour = new Vector4(0.0f, 1.…
So I got this code about rendering a shaded tri using sharpDX ...
var vertexShaderByteCode = ShaderBytecode.CompileFromFile("MiniTri.fx", "VS", "vs_4_0", ShaderFlags.None, EffectFlags.None);
var vertexShader = new VertexShader(device, vertexShaderByteCode);
var pixelShaderByteCode = ShaderByteco...
The things that can't wait are: an icon, recording the # of games, making sure it displays alright on various screen sizes, learning how to sign an APK, adding advertisements, adding analytics, and maybe also adding a way to easily share scores
heh, maybe if you last 100 seconds, I can add a Unicorn in the sky
> Apple® tools required to build iOS applications run only on the OS X operating system on Intel-based Macs. Xcode® 4.5 (the minimum required version) runs only on OS X version 10.7 (Lion) or greater, and includes the iOS 6 SDK (Software Development Kit). To submit apps to the Apple App Store℠ requires the latest versions of the Apple tools.
Just like taxes in my home province. We have decided to reduce business taxes, and abolish provincial sales taxes in Alberta. You'd kinda think that it would result in less money for the province, but it actually encourages businesses and people to move here, and therefore more money.
Hmm, I bet I can use PhoneGap Build to build for iPhones. BUT the version of "PhoneGap" that "PhoneGap Build" is using is old, so the sounds won't work
argh, I'm very tempted to ditch my in-game "edit controls" system, and just have the player(s) set up their controls before the game launches. Absolutely sick of doing my head in dealing with like 2 abstraction layers to figure out which button is what, plus requiring the player to map gamepad buttons in-game as well
