Antichamber

Dead Space 2

Crysis 2

STALKER Shadow of Chernobyl

A slight workaround...

In my projects I create two constant vars one called FALSE set to 0 and another called TRUE set to 1

This means when I'm using global/local vars that technically are acting as Boolean values my code is easier to read and understand

Select a sprite you have added to your layout...

(Either from the layout directly or from Project or Object Panel)

On the "Properties" panel you have various properties you can edit such as the name its layer angle etc

One of these sections is called "Instance Variables"

Under this section you can add variables that are directly attached to the object... rather than creating local and global variables in the event sheet.

If the sprite is your player you might add a "health" value or something similar

https://www.scirra.com/manual/73/instance-variables

If you mean the block.. it really depends on the game play. If you have lots of health or perhaps a system where your health regenerates over time then the block probably wouldn't get used.

In some situations... when the player has limited health or you have ranged attackers like archers the block feature could be good for the game play.

At the moment keep it in and see where the rest of your development takes you...

Top right corner -> Click your name

Click -> My Profile

Below your picture -> Forum posts -> click the number

Click -> Start Search bottom of page

Edit: Just re-read your post and seen you've already tried that...

-> Right mouse on layout

-> Insert new object

-> scroll down - Platform Specific

-> select Scirra Arcade

:)

Tobye

One way to access layers is to setup a list of constant variables that match the index numbers of the layer...

LYR_MAINMENU = 4

LYR_HUD = 3

LYR_FOREGROUND = 2

LYR_PLAYER = 1

LYR_BACKDROP = 0

System -> Set Layer LYR_MAINMENU Visible

If I delete/add/rename/shift layers I only have to update the constant var list to match and everything still works etc...

Hope that helps

Not sure how if you've solved your problem yet...

On my Evade game I used separate LAYERS for each Menu screen, this way I could just hide/unhide the layers I needed.

Click Button "scoreboard"

-> Hide "mainmenu" Layer

-> Show "scoreboard" Layer

Click Button "scoreboard_back"

-> Hide "scoreboard" layer

-> Show "mainmenu" layer

Then any button events etc I had for the "mainmenu" I would nest inside a check visible event...

Layer "mainmenu" is visible

-> check buttons for mainmenu

-> perform updates etc

Layer "scoreboard" is visible

-> check buttons for scoreboard

-> perform updates etc

sosensible

Lighting render setups and sample rates could be a whole topic on its on own... myself personally usually between 100-500 samples depending on materials used and around 15mins max per render see guitar link...

dl.dropboxusercontent.com/u/54307246/Uploads/guitar_lrge.jpg

While I'm posting a couple more images I dug up...

<img src="https://dl.dropboxusercontent.com/u/54307246/Uploads/predator_sml.jpg" border="0" />

<img src="https://dl.dropboxusercontent.com/u/54307246/Uploads/BackpackAndMachette_sml.jpg" border="0" />

I believe the Node Web Kit, exports a compacted browser with your game so that can then play your C2 game all in one.

Also it exports various versions for mac, win etc so you can delete the ones you don't need...

HeroBiX

Cheers :) The fat destroying Adipose... very quick and fun character to make, was done for a topology study for animation ready models, hardest thing was getting good reference images.

sosensible

Has to be cycles, more intuitive and easier to proof results before final render and composition.

A few 3D models I created in Blender

<img src="https://dl.dropboxusercontent.com/u/54307246/Uploads/cruiser_guitar_sml.jpg" border="0" />

<img src="https://dl.dropboxusercontent.com/u/54307246/Uploads/samsung_camera_sml.jpg" border="0" />

<img src="https://dl.dropboxusercontent.com/u/54307246/Uploads/Adipose_sml.jpg" border="0" />