A Friend From Work
11th of October, just a month away from presentation.
Here’s some updates! Kinda started on Scruffy’s new 3D model and Ryan is working hard on Programming and Ling Ern is doing her 3D food!
2D render before throwing into 3D!
Prepping for 3D render!
More next week!
Finally back from the long break. A bunch of other assignments to rush and haven’t worked on Nomadic or any programming since then. Gonna be a rough start back up.
So started slow and just changed colors and was playing with how to turn white to orange to red but didn’t really get it to work so went back to tutorials.
After understanding the import of images as textures and the structure of data memory for images in arrays, I was finally able to CREATE FLAMESSSSS!!!!
Now I kinda have an idea of just porting in the library and using hand_stabilisation.x and y to determine x and y position. Let’s see how it goes.
Ok it didn’t work. It seems like the particle system would only activate upon the seeing hand_stabilized which is weird. Possibly because I threw it into the for loop but this the x and y positions when subbed in, became 0, 0 position. I’ll possibly get Corey to help out with this.
Amazing. Corey is amazing.
I’ll just leave this here.
Cheers
So Day 4, started the day late at around 7PM with a consult with my lecturer, Corey.
Straight off the bat, Corey went on a cleaning spree. Relieving me of functions that I don’t even need, such as fingers, wrists rotation and positions. Seems like we only need a stabilized hand position for now then!
1. Create a double handed control mechanism without LEAP to test the feasibility - Possibly implementation of place holders and using mouse positions to test 2. Bring in the LEAP Motion Library and STK3. Port particle system over 4. Bring back fingers and wrists into the equation 5. Create custom gestures for different actions 6. Bug fixes(?)
Quicker than expected to be honest. Added a few more tasks into the do the list now that things are coming together. Now comes, perhaps the scariest bit: a particle system. It’s all fine and dandy on aesthetics if you’re calling it a prototype but when you start to port in.
Thanks Coding Train! After watching the video about Particle Systems, I found out I unknowingly created a particle system. Particle(my ellipse), a Particle System(my array) all clustered onto a mainframe(my leap main).
After creating a simple particle system, I thought I was ready to throw it into my main frame but boyyyyy was I wrong.
The double handed tracking was still working but I was missing the p.addParticles(); from spawning continuously. Perhaps something went wrong within the for loop. I guess I can only figure this out when I’m back from Indonesia.
Cheers.
Hey guys so it’s Day 2 and I’m meeting my lecturer later at night to discuss about the integration of LEAP.
I got an idea this morning and would like to put it up here before I forget: a Spirit Guide.
So basically, a floating Io like spirit that guides you on the controls. Perhaps a tutorial like stage before the actual game? If I’m not wrong, this would be called gameStates but how would I transit from 1 gameState to another? Guess I’ll figure it out soon.
Imported my code as a class into Grauwald’s first leap project to test out what I’m missing; it didn’t work. Or at least it didn’t work as I wanted it too. The fading disappeared, the maximum trail also disappeared. Need to figure out what just happened.
Final tests but still unsure where to go from here.
Cheers.
29/09/17 First entry for Nomadic. Excited and scared at the same time.
I got my LEAP Motion Sensor a few days back and have been playing around with it. Showed a few friends and got some feedback on the sensitivity and perhaps more methods of how I could execute it.
Pipeline (for now I guess):
1. Create a single handed control mechanism without LEAP to test the feasibility - Possibly implementation of place holders and using mouse positions to test 2. Bring in the LEAP Motion Library and STK 3. Port particle system over 4. Bug fixes(?)
Figured that I’ll start with using mouse positions on Processing as single handed use of the LEAP might be emulating the same technique as positioning on a digital display. Also, using ellipses as place holders before porting over our particles for the elements. We’ll see how it goes.
void draw(){
fill(0, 0, 0, opacity);
ellipse(mouseX, mouseY, 20, 20);
opacity--;
Did not seem to work as well as I thought. As I continued moving my mouse around, the opacity decreased instead of creating a trail of fading ellipses. I might need a timer variable(or constant) to control fade?
void draw(){
fill(255, 25);
rect(0,0,width,height);
fill(0);
ellipse(mouseX, mouseY, 20, 20);
Decided to create my background(255); in my setup(); and draw a rectangle with a constant 25 alpha(opacity) over the ellipse. It seemed to have done the trick but it leaves a a residue.
This is barely seen on my screen so I photoshopped a -200% contrast to make it a little more obvious. It seems like a leftover trail that perhaps could’ve be caused by 25 alpha.
I’ll have to find a way to solve this.
void draw(){
filter(DILATE);
fill(0, 50);
rect(0,0,width,height);
fill(255);
ellipse(mouseX, mouseY, 50, 50);
Changing it to 50 alpha seems to have solved the leftover problem(or perhaps made it really difficult for the human eyes or screen resolution to detect).
I also added a filter to make it a tad bit snappier. Was playing around with either DILATE or BLUR but it seems like there is a form of delay with BLUR which I am not very happy with, even when intensity has been dropped.
I feel this isn’t giving me enough controls and might just throw the ellipses into an array. But throwing things into an array might overcomplicate things as I’m using 3D particles and not ellipses. None-the-less, for the sake of SCIENCE, I shall try it out in arrays.
float [] x = new float [50];
float [] y = new float [50];
void setup() {
size(800, 800);
smooth();
background(0);
noStroke();
frameRate(60);
}
void draw() {
background (0,0,0);
for (int i = 0; i < 49; i++) {
x[i] = x [i+1];
y[i] = y [i+1];
fill (255);
ellipse (x[i], y[i], i, i);
}
x[49] = mouseX;
y[49] = mouseY;
}
I got really stuck on how to proceed from here and had to refer to a bunch of websites for solutions on how arrays could work. I tried implementing arrays into a Ball class but that didn’t seem to work out well as it meant I had to control multiple factors that came with a class. After stumbling across a project on openprocessing, I was heavily influenced to try out arrays on the x and y position instead. It seemed to work and I have a first prototype of what I want to implement.
A quick import of the LEAP library gave me this example that I could play with and after seeing the code, I was quite flabbergasted. I thought it would an easy job to just integrate my code and receive the x and y positions of the leap as output to replace my mouseX and Y position but I’m thoroughly wrong.
I’ll be reading up on a couple of tutorials over the next few days to ensure I understand what’s going on before even continuing. Cheers guys.
Singapore Nightfest, ended about just a month ago, featured many prominent artist from all around the globe presenting various beautiful projection mapping installations.
It kind of got me thinking of the possibilities of projection mapping. Guess I’ll try it out next semester!
I think what the Health Promotion Board is doing is very smart. What they’re doing is intergrating old people to using technology for rewards and using technology that young people love to do something healthy with their lives.
It’s a simple idea. Get people to download the app, scan QR codes, distribute walking devices to track footsteps a day, reward people.
Fundamentally, the company knew what Singaporeans enjoy, rewards(monetary of course) and made full use of it.
Something interesting that’s of local context and would be very familiar to all Singaporeans. Something so simple but beautiful.
Nothing similiar to what I’m planning to do but it’s still an inspiration.
Jake Tan 