• What are you working on? v16
    5,004 replies, posted
[QUOTE=DevBug;29322042]All of them suck, except for the first one. /trolling Can you record some gameplay when it's done?[/QUOTE] Eh? I could've sworn there was a video a few pages back. [editline]20th April 2011[/editline] [QUOTE=Helk;29257603]Game we're working on. Should be on the app store soon! [media]http://www.youtube.com/watch?v=fWy3fKX65J0[/media][/QUOTE]
If anyone is applying for Google's Computer Science Summer Institute for High School Seniors, just a reminder that the application deadline is Friday morning. And if you are seeing this for the first time, there's still time to apply online! [url]http://www.google.com/intl/en/jobs/cssi/index.html[/url] It's basically a three-week long computer science program at their headquarters in Mountainview, for high school seniors.
[QUOTE=garry;29321868]Not totally programming, but just polishing the graphics for Snabbo. Hopefully don't have to tell you which are the new ones. [img_thumb]http://dl.dropbox.com/u/3590255/Bits/IMG_0780.PNG[/img_thumb][img_thumb]http://dl.dropbox.com/u/3590255/Bits/IMG_0802.PNG[/img_thumb] [img_thumb]http://dl.dropbox.com/u/3590255/Bits/IMG_0783.PNG[/img_thumb][img_thumb]http://dl.dropbox.com/u/3590255/Bits/Shop.png[/img_thumb][/QUOTE] Why is it iOS exclusive? Unity works on Android too :raise:
[QUOTE=Robber;29322833]Why is it iOS exclusive? Unity works on Android too :raise:[/QUOTE] Where does it say its iOS exclusive?
[QUOTE=garry;29321868]Not totally programming, but just polishing the graphics for Snabbo. Hopefully don't have to tell you which are the new ones. [/QUOTE] The left ones are the new ones, right?
[QUOTE=CarlBooth;29323021]Where does it say its iOS exclusive?[/QUOTE] It doesn't say it anywhere, but it is.
I didn't MEAN to make a fractal generator... [img]http://img222.imageshack.us/img222/451/hashcodefractal.png[/img] ...but I guess that's what happens when I write crappy hash functions.
[QUOTE=Overv;29323271]It doesn't say it anywhere, but it is.[/QUOTE] God, this reminds me of a poem I'm studying for English... Nothings Changed - Tatamkhulu Afrika [code] Small round hard stones click under my heels, seeding grasses thrust bearded seeds into trouser cuffs, cans, trodden on, crunch in tall, purple-flowering, amiable weeds. District Six. No board says it is: but my feet know, and my hands, and the skin about my bones, and the soft labouring of my lungs, and the hot, white, inwards turning anger of my eyes. Brash with glass, name flaring like a flag, it squats in the grass and weeds, incipient Port Jackson trees: new, up-market, haute cuisine, guard at the gatepost, whites only inn. No sign says it is: but we know where we belong. I press my nose to the clear panes, know, before I see them, there will be crushed ice white glass, linen falls, the single rose. Down the road, working man's cafe sells bunny chows. Take it with you, eat it at a plastic table's top, wipe your fingers on your jeans, spit a little on the floor: it's in the bone. I back from the glass, boy again, leaving small mean O of small mean mouth. Hands burn for a stone, a bomb, to shiver down the glass. Nothing's changed. [/code]
[QUOTE=Loli;29324246]God, this reminds me of a poem I'm studying for English... Nothings Changed - Tatamkhulu Afrika [code] Small round hard stones click under my heels, seeding grasses thrust bearded seeds into trouser cuffs, cans, trodden on, crunch in tall, purple-flowering, amiable weeds. District Six. No board says it is: but my feet know, and my hands, and the skin about my bones, and the soft labouring of my lungs, and the hot, white, inwards turning anger of my eyes. Brash with glass, name flaring like a flag, it squats in the grass and weeds, incipient Port Jackson trees: new, up-market, haute cuisine, guard at the gatepost, whites only inn. No sign says it is: but we know where we belong. I press my nose to the clear panes, know, before I see them, there will be crushed ice white glass, linen falls, the single rose. Down the road, working man's cafe sells bunny chows. Take it with you, eat it at a plastic table's top, wipe your fingers on your jeans, spit a little on the floor: it's in the bone. I back from the glass, boy again, leaving small mean O of small mean mouth. Hands burn for a stone, a bomb, to shiver down the glass. Nothing's changed. [/code][/QUOTE] GCSE English Literature?
[QUOTE=Tangara;29314859]So here's where I've been for the last 10 days: [url]http://www.abc.net.au/news/video/2011/04/20/3196774.htm[/url] (video) I briefly appear at the end. [i]I'm the tool waving to the camera.[/i][/QUOTE] Bullshit, we all know you're the guy speaking to everyone in the green at the beginning. :v:
[QUOTE=Dotmister;29324464]GCSE English Literature?[/QUOTE] Probably, that's one I studied for GCSE English Lit too.
Some kind of pathfinding [img]http://img707.imageshack.us/img707/3972/pathfinding1.png[/img]
[QUOTE=likesoursugar;29326084]Some kind of pathfinding [img_thumb]http://img707.imageshack.us/img707/3972/pathfinding1.png[/img_thumb][/QUOTE] Some kind of pathfinding Some kind of soul Some kind of mixture Some kind of gold Some kind of majesty Some chemical load All I could think of when I read that, no idea why
Spent a bit of time today testing the new clang 2.9 release on Windows, with MSVC. I can say that clang meets all of the MSVC C extensions (they're still working on C++ support with msvc. But they'll get there soon :D). So here's a quick rundown of what clang on windows (built for and by MSVC) supports * Windows.h and any Win32 application you could throw at it * DirectX SDK (All headers :D) * clang blocks (Essentially anonymous functions) You need the BlocksRuntime for the last one, but it's piss easy to compile, if you know what to grab. I might just "fork it", and remove the need for a config.h file (Everything they handle can be done with a simple #ifdef, and cmake is barely needed beyond that) Here's a picture of the blocks in action! :D [IMG]http://i.imgur.com/R8OOT.png[/IMG] I have also built an installer, but I need to make sure it's "clean" and doesn't screw anything up. Once I've confirmed that, I'll post a link to download it here, and you all can give it a shot if you like. (Just be aware, it can be a bit of a pain, since you have to hand write all the commands... but maybe my build system can fix all that :v:)
[QUOTE=likesoursugar;29326084]Some kind of pathfinding [img_thumb]http://img707.imageshack.us/img707/3972/pathfinding1.png[/img_thumb][/QUOTE] Looks nice. How long does it take to find that path though? :o
Hey pro programmers (especially the ones who do this for a living), do you guys ever have to make really long function prologs in front of each function? And how important is format? Can format be anything as long as it looks nice? Or is there some kind of standard way to write code? I got docked a huge amount of points on my lab yesterday just because I put //===================================================== Separating my functions. Is my professor a jerk or is this the real deal?
[QUOTE=Moustach3;29318137]If you like that, go to a FIRST robotics competition. Individuality. Individuality EVERYWHERE.[/QUOTE] Collecting buttons from other teams may be common, but it is fun. And heavy, once you have about 50. I added more to my level selection screen in TopWise; now you can go through your levels.
[QUOTE=ZenX2;29328764]Collecting buttons from other teams may be common, but it is fun. And heavy, once you have about 50. I added more to my level selection screen in TopWise; now you can go through your levels.[/QUOTE] It gets annoying when the following happens: -Robot is 4 inches too wide (NOBODY FUCKING MEASURED IT EVER) -Robot is 8 pounds too heavy (NOBODY FUCKING WEIGHED IT EVER) -You're the only programmer -You have tons of code to do (In LabVIEW, too. Fucking LabVIEW...) -NOBODY IS FUCKING HELPING WITH ANYTHING, THEY'RE ALL GETTING BUTTONS
[QUOTE=Mr_Razzums;29328663]Hey pro programmers (especially the ones who do this for a living), do you guys ever have to make really long function prologs in front of each function? And how important is format? Can format be anything as long as it looks nice? Or is there some kind of standard way to write code? I got docked a huge amount of points on my lab yesterday just because I put //===================================================== Separating my functions. Is my professor a jerk or is this the real deal?[/QUOTE] Your professor is a dick, call him out on it. There aren't standards on coding, just good ideas and bad habits. As long as you can read your code then there shouldn't be a problem.
[QUOTE=Mr_Razzums;29328663]Hey pro programmers (especially the ones who do this for a living), do you guys ever have to make really long function prologs in front of each function? And how important is format? Can format be anything as long as it looks nice? Or is there some kind of standard way to write code? I got docked a huge amount of points on my lab yesterday just because I put //===================================================== Separating my functions. Is my professor a jerk or is this the real deal?[/QUOTE] I usually do that, so yeah, your professer is a jerk. I typically do things like: //===*DRAW FUNCTIONS*========
In Visual Studio I just use #region, but for anything else I'll use separators like that. I'll usually go and make them nice and large too, like [code] /*********************** * PHYSICS METHODS * ***********************/ [/code]
[QUOTE=Mr_Razzums;29328663]Hey pro programmers (especially the ones who do this for a living), do you guys ever have to make really long function prologs in front of each function? And how important is format? Can format be anything as long as it looks nice? Or is there some kind of standard way to write code? I got docked a huge amount of points on my lab yesterday just because I put //===================================================== Separating my functions. Is my professor a jerk or is this the real deal?[/QUOTE] The key idea is to be consistent. For example, when writing code for an open source project, use the style of that project throughout your code. Likewise, when writing code for your professor, use the style that your professor wants you to use. Learning to adapt to a coding style and stick to it consistently is an important skill for a programmer. In this particular case, it might have happened because some programmers are very strict with the use of comments. The idea is that code should be self-documenting and comments should be kept for instances where the code alone does not speak for itself. Yet others subscribe to more liberal use of comments. I suggest listening to your professor unless his style includes things like archaic coding conventions that are no longer recommended (one example being declaring all your variables at the top of a function). If he won't let you do the right thing, talk to him about it. But for things that are purely stylistic, like this case, you should adapt to the style he wants.
[QUOTE=jA_cOp;29329928]The key idea is to be consistent. For example, when writing code for an open source project, use the style of that project throughout your code. Likewise, when writing code for your professor, use the style that your professor wants you to use. Learning to adapt to a coding style and stick to it consistently is an important skill for a programmer. In this particular case, it might have happened because some programmers are very strict with the use of comments. The idea is that code should be self-documenting and comments should be kept for instances where the code alone does not speak for itself. Yet others subscribe to more liberal use of comments. I suggest listening to your professor unless his style includes things like archaic coding conventions that are no longer recommended (one example being declaring all your variables at the top of a function). If he won't let you do the right thing, talk to him about it. But for things that are purely stylistic, like this case, you should adapt to the style he wants.[/QUOTE] This. You're hardly ever going to have a say in what coding standards are used.
[QUOTE=Mr_Razzums;29328663]//=====================================================[/QUOTE] what the fuck is that shit
Isn't it awesome when you're trying to design some sort of system but there's some part of it that seems really challenging, then you wake up one morning a week later and suddenly you have the entire system designed in your head magically? I now have a design for a trigger/event system for a game project I'm working on. In my last project we ended up subclassing a Cause and an Effect and having a Trigger class that would check variables every game update which was not bad, but there were several issues including performance (it was for Android, so we didn't have as much power to work with), and it was really clunky because any time we added something I'd have to make a bunch of changes to our separate level editor. Now I'm planning on having every entity in the game create an enum for the methods that can be invoked from an event and also things that can fire off an event. I'll create a class that stores the enum value with a reference to the entity it will be calling, store that in a Dictionary in my main game class, and return a unique ID number, then pass that number to the entity who will be calling that output. When I'm going through a regular entity update call, I'll have the update return an int, probably 0 or -1 if no event is fired, or a stored ID number, which the game class will then use to look up in the Dictionary and fire off it's event if it's called. The entity will take in the enum value and an object array for variables, call the proper method for it. The reason for a Dictionary and not a List is because I want to be able to remove events if it's a fire once thing or for any other reason. I feel pretty awesome right now. Except that I have a ton of schoolwork, APs in 2 weeks, finals a few weeks after that. So I probably won't be able to work on this for a few weeks at least (although I probably will anyways)
[QUOTE=Robber;29322833]Why is it iOS exclusive? Unity works on Android too :raise:[/QUOTE] We'll be looking at android once it's out
[QUOTE=Chandler;29328554]Spent a bit of time today testing the new clang 2.9 release on Windows, with MSVC. I can say that clang meets all of the MSVC C extensions (they're still working on C++ support with msvc. But they'll get there soon :D). So here's a quick rundown of what clang on windows (built for and by MSVC) supports * Windows.h and any Win32 application you could throw at it * DirectX SDK (All headers :D) * clang blocks (Essentially anonymous functions) You need the BlocksRuntime for the last one, but it's piss easy to compile, if you know what to grab. I might just "fork it", and remove the need for a config.h file (Everything they handle can be done with a simple #ifdef, and cmake is barely needed beyond that) Here's a picture of the blocks in action! :D [img_thumb]http://i.imgur.com/R8OOT.png[/img_thumb] I have also built an installer, but I need to make sure it's "clean" and doesn't screw anything up. Once I've confirmed that, I'll post a link to download it here, and you all can give it a shot if you like. (Just be aware, it can be a bit of a pain, since you have to hand write all the commands... but maybe my build system can fix all that :v:)[/QUOTE] You always create the most useful stuff, well, half create it.
[QUOTE=xAustechx;29328570]Looks nice. How long does it take to find that path though? :o[/QUOTE] Another picture of 3 bots and it took 2.3 ms each to generate the path to the S symbol. Also testing my text class. [img]http://img715.imageshack.us/img715/3963/pathfinding2.png[/img]
[QUOTE=garry;29321868]Not totally programming, but just polishing the graphics for Snabbo. Hopefully don't have to tell you which are the new ones.[/QUOTE] Will I get the rest of my pay from this game? [highlight](User was permabanned for this post ("Dumb gimmick" - Overv))[/highlight]
[QUOTE=garry;29330835]We'll be looking at android once it's out[/QUOTE] Not to be negative or anything Garry, but what is the difference between this and regular bejeweled?
Sorry, you need to Log In to post a reply to this thread.