Sqiddster's Profile

- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 26 Jul, 2015
- Quote
AnD4D The function applies for only one laser, I believe it has a laser UID as a parameter. so if you want it to affect all the lasers, use a for each loop, and call the function with laser.uid inside the loop.
Putting a for each inside the function will work too, but you'll lose the ability to use it for just one laser at a time.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 25 Jul, 2015
Does anyone know the steps to get the 10.5 version working for Steam on Mac/Linux? The steps provided in this thread only seem to apply to Windows, and the app crashes when I try it on mac.

cc Aurel —

Speaking of crashing, my game seems to crash on nw preview due to the presence of the Greenworks plugin. Has anyone else experienced this?

Cheers!
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 23 Jul, 2015
- Quote
KaMiZoTo Penelope and Cosmochoria seem to be doing fine on 10.5 so I'm hoping it will be all right for me too.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 23 Jul, 2015
- Quote
I'm thrilled to announce that Airscape: The Fall of Gravity will be released August 11th!

Check out the Steam page here!

I'd like especially to thank the Scirra community for all their help and support so far. We're almost at the finish line!
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 18 Jul, 2015
- Quote
tunepunk I'm pretty sure draw calls are directly tied to how many sprites/objects are being drawn (on screen, visible). To reduce pixels per second, just... think about how many pixels are being drawn, I guess? i.e. a full screen overlay, or a layer with 'force own texture' will draw window width*window height pixels.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 17 Jul, 2015
- Quote
0plus1 correct. Memory isn't the only concern however, pixels being drawn per second is another issue, as well as number of draw calls.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 17 Jul, 2015
- Quote
0plus1 yes, that'c correct. Larger image files will mean more VRAM is used regardless of the resolution
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 17 Jul, 2015
- Quote
People who care what is used to make a game are a very very very small minority. What matters is the game.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 17 Jul, 2015
- Quote
A small layout should not boost CPU performance as collisions are based on polygons and not pixels. A small resolution will hugely boost GPU performance however due to the difference in pixel fillrate.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 16 Jul, 2015
- Quote
functions should happen immediately when they are called. there's an issue with your events.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 11 Jul, 2015
Any progress at all on getting this working with the latest NW?

10.5 has bugs of its own which are obviously not going to get fixed. The latest version is almost good, but the issue with Greenworks not working is a big one. If someone could have a look I'd be hugely grateful.
- sqiddster
- - Joined 5 Sep, 2011
  - 173 topics • 3,166 posts
- 1
- 4 Jul, 2015
- Quote
I plan on using that loader, even though I'm making a full commercial product.

It's certainly not going to 'destroy your reputation'.