[synthiac]

supersnail11 posted:

2010 = end of grade
2010 end - 2011 start = 7th
end of 2011 = 8th
the more you know

no it means you did that project somewhere between early 2010 and now. i'm going more towards now.

[Yogurt]

amcfaggot posted:

Wiremod, Redstone, etc.

I could maybe do it if I used magic to link blocks together.

[PieClock]

Yogurt posted:

God dammit.

I just realized that Terraria is slowly implementing all the features unique to MY game. For example, I was working on block connections for a while--connecting blocks using wires.

Too bad if I add that as a feature, it'll look like a copy of Terraria GOD DAMMIT

Not if you build your game around the concept and integrate the feature into a good portion of your game, in my opinion.

[supersnail11]

synthiac posted:

no it means you did that project somewhere between early 2010 and now. i'm going more towards now.

Early 2010.
It was the science fair at the end of the year.

[Jookia]

synthiac posted:

no it means you did that project somewhere between early 2010 and now. i'm going more towards now.

Because their grade and age totally affects our respect for him and his talent.

[Yogurt]

Jookia posted:

Because their grade and age totally affects our respect for him and his talent.

In most cases it has and does.

[supersnail11]

Jookia posted:

Because their grade and age totally affects our respect for him and his talent.

I have talent? :D

Seriously, seeing all the things that you guys program makes me think that I might not be as good as I thought I was :(

[Yogurt]

supersnail11 posted:

I have talent? :D

Seriously, seeing all the things that you guys program makes me think that I might not be as good as I thought I was :(

Nobody ever is.

[DrLuke]

supersnail11 posted:

2010 = end of grade
2010 end - 2011 start = 7th
end of 2011 = 8th
the more you know

Wow, I wasn't even that much off then

[Eric95]

garry posted:

I think skeletal looks better than pixel animation. Even in 2D.

Honestly when I see skeletal 2D animation I just think it looks cheap. Might be because I've been animating a lot of flash stuff but frame-by-frame hell yes

[garry]

The problem is that we're used to seeing smooth animations now, and pixel animations are never as smooth as skeletal.

[Electroholic]

Parser time

[Nigey Nige]

garry posted:

The problem is that we're used to seeing smooth animations now, and pixel animations are never as smooth as skeletal.

I'm not so sure about that. Depending on the aesthetic of the game, less smooth pixel animations can be a lot nicer to look at than skeletal. Comparisons, I suppose, would be LIMBO (skeletal) versus, say... Eternal Daughter (pixel).

Edit:
I guess being able to precisely control the speed of limb movement and switch it up with mad hella styled-out special maneuvres gives hand-drawn animation the edge.

[acpm]

Sorry to reask this question, as I do recall it being discussed before, but how can I create a webm clip? I'd be taking a video from Fraps and converting it, I suppose through VirtualDub with a webm extension of some sort?

[garry]

Nigey Nige posted:

I'm not so sure about that. Depending on the aesthetic of the game, less smooth pixel animations can be a lot nicer to look at than skeletal. Comparisons, I suppose, would be LIMBO (skeletal) versus, say... Eternal Daughter (pixel).

Edit:
I guess being able to precisely control the speed of limb movement and switch it up with mad hella styled-out special maneuvres gives hand-drawn animation the edge.

Well.. of course.

Edited:

amcfaggot posted:

Sorry to reask this question, as I do recall it being discussed before, but how can I create a webm clip? I'd be taking a video from Fraps and converting it, I suppose through VirtualDub with a webm extension of some sort?

Looks good: http://www.mirovideoconverter.com/

[acpm]

You know what, nevermind.

Edited:

garry posted:

Looks good: http://www.mirovideoconverter.com/

Oh thanks!

[Darwin226]

garry posted:

I'm using Chrome. Works fine here without blocking 5 animated gifs.

Yeah, my PC is more on the low end. And I've been having some hardware issues.

[Nigey Nige]

garry posted:

Well.. of course.

Edited:



Looks good: http://www.mirovideoconverter.com/

...must...argue...despite...lack...of...opponents. ..hnnngnggnf

[Electroholic]

Oh you reminded me


Added mouse following support to my desktop capture program :)

[ief014]

Nigey Nige posted:

...must...argue...despite...lack...of...opponents. ..hnnngnggnf

I just use ffmpeg command line to convert to webm. Miro uses ffmpeg, but just converts one format to another with defaulted options

[Tobba]

thisBrad posted:

Oh you reminded me

-video-
Added mouse following support to my desktop capture program :)

Holy compression rape
Makes me want to tear my eyes out

[TomGoodWoman]

im making a clock in lisp.

[Lord Ned]

ROBO_DONUT posted:

This is kind of what I was guessing, and it's reassuring to see some verification.
Most of the scene-graph driven games I've played (The Elder Scrolls III/IV and Fallout 3/NV being Netimmerse/Gamebryo-based) have never struck me as being particularly efficient at what they do. My desktop often struggles with these games when it probably would have no trouble rendering the same scene in any other engine.
Games that tend to run smoother usually use an approach that is centered around partitioning space or defining minimal bounding volumes. BSP trees, octrees, bounding volume hierarchies, etc., all of them focus on making depth-sorting, collision detection, or frustum/occlusion culling operations faster instead of worrying about how to associate meshes for minimal state switching.

I can agree with partitioning space - I was thinking using brushes (akin to Source) to build volumes (and a BSP tree) would still be quite effective in an engine full of models.

[acpm]

ROBO_DONUT posted:

This is kind of what I was guessing, and it's reassuring to see some verification.
Most of the scene-graph driven games I've played (The Elder Scrolls III/IV and Fallout 3/NV being Netimmerse/Gamebryo-based) have never struck me as being particularly efficient at what they do. My desktop often struggles with these games when it probably would have no trouble rendering the same scene in any other engine.
Games that tend to run smoother usually use an approach that is centered around partitioning space or defining minimal bounding volumes. BSP trees, octrees, bounding volume hierarchies, etc., all of them focus on making depth-sorting, collision detection, or frustum/occlusion culling operations faster instead of worrying about how to associate meshes for minimal state switching.

Lord Ned posted:

I can agree with partitioning space - I was thinking using brushes (akin to Source) to build volumes (and a BSP tree) would still be quite effective in an engine full of models.

Whoa, whoa, whoa. No. I mean, hold on. Scene-graph stuff is extremely fantastic for what it does, you can't really compare it to BSP or similar geometric compile systems, because standard BSP isn't capable of doing anything near scene-graph range work.

This is really a discussion fit for both this subforum, but also the mapping section, as I'm sure you'd hear a mouth full from them on that subject.

My point is though, you can't compare scene-graph work to BSP or similar systems in terms of efficiency, because scene-graph rendering is a runtime process of rendering and culling, whereas compiled geometric approaches give you a world rendering set and other model subsets of what to render without having the computer figure that out outside of camera positions and visibility sectors. They do two different things in two widely different approaches.

[icantread49]

Yogurt posted:

But why?

windows version won't earn me money

[Electroholic]

Was trying to decode iTunes WiFi sync packets so I could make a Winamp plugin.
Fucking Apple enables SSL encryption after 18 packets :(

[Philly c]

amcfaggot posted:

Whoa, whoa, whoa. No. I mean, hold on. Scene-graph stuff is extremely fantastic for what it does, you can't really compare it to BSP or similar geometric compile systems, because standard BSP isn't capable of doing anything near scene-graph range work.

This is really a discussion fit for both this subforum, but also the mapping section, as I'm sure you'd hear a mouth full from them on that subject.

My point is though, you can't compare scene-graph work to BSP or similar systems in terms of efficiency, because scene-graph rendering is a runtime process of rendering and culling, whereas compiled geometric approaches give you a world rendering set and other model subsets of what to render without having the computer figure that out outside of camera positions and visibility sectors. They do two different things in two widely different approaches.

The point is really about scene graph traversal not actually being efficient at what it does in relation to rendering. Of course they are different, I don't really get your point.

[Lord Ned]

amcfaggot posted:

Whoa, whoa, whoa. No. I mean, hold on. Scene-graph stuff is extremely fantastic for what it does, you can't really compare it to BSP or similar geometric compile systems, because standard BSP isn't capable of doing anything near scene-graph range work.

Sorry. I wasn't trying to directly compare it. It was sort of a tangent thought you made resurface in my mind - I was thinking a reasonable way to do it if you were writing your own engine was what I suggested.

It's not something that I've done, but it's something I'd like to do at one point in life.

[acpm]

Well then let me get to the point.

My desktop often struggles with these games when it probably would have no trouble rendering the same scene in any other engine.

No, it would be worse.

[Yogurt]

icantread49 posted:

windows version won't earn me money

So? Neither will not releasing it on Windows, which really doesn't take that long.

[acpm]

icantread49 posted:

windows version won't earn me money

If you make 5 bucks off that app, I'll poop myself from disbelief

figuratively speaking

[ROBO_DONUT]

amcfaggot posted:

Whoa, whoa, whoa. No. I mean, hold on. Scene-graph stuff is extremely fantastic for what it does, you can't really compare it to BSP or similar geometric compile systems, because standard BSP isn't capable of doing anything near scene-graph range work.

This is really a discussion fit for both this subforum, but also the mapping section, as I'm sure you'd hear a mouth full from them on that subject.

My point is though, you can't compare scene-graph work to BSP or similar systems in terms of efficiency, because scene-graph rendering is a runtime process of rendering and culling, whereas compiled geometric approaches give you a world rendering set and other model subsets of what to render without having the computer figure that out outside of camera positions and visibility sectors. They do two different things in two widely different approaches.

What are you even talking about? Scene graphs, at least in the traditional sense, don't usually provide qualities that aid in the (usually most important) processes of collision detection, nearest-neighbor searches, or occlusion culling.

Ignoring BSP for a moment, I listed two other (very dynamic) schemes that can be constructed at runtime and modified whenever you need to. Octrees you should be familiar with. If you're not, I'm not going to explain them to you, they're common and simple enough that you should have no trouble at all finding information about them. Bounding volume hierarchies are a structure where items are grouped into bounding volumes (usually bounding-boxes or spheres, although any other shape will work just fine) in such a way that pairs (or three, four, etc.) of nearby objects are children of a node whose bounding geometry encompasses both, in a tree like structure with one root node which encompasses the entire scene. It makes no assumptions about scene structure (unlike even octrees, which requires you to choose some maximum dimensions for your root node) and can be built entirely at runtime using simple online construction techniques. Nodes can be inserted or removed whenever you want in O(log n) time. It works great for collision detection (including frustum culling, which is effectively a collision detection problem) and can be used to accelerate occlusion queries.

Now, getting back to BSP. BSP is a very broad term. It applies to any structure which recursively partitions space using hyperplanes (or spheres). Its use in the Id Tech and Source engines is only one of many possible applications, and you absolutely should not write it off as a "compile-time" structure.

I started out as a mapper, and I am well aware of the frustration you can encounter working with a tools that were written for an era when computers had only a small fraction of the power they have today. The choice to offload work to the level designers and map compiler was an excellent design decision at the time, but the constraints that were imposed are not an intrinsic quality of BSP trees.

[acpm]

When you show me any form of BSP structure that can do what scene-graphs are currently doing and on the scale they're doing it, then I'll be impressed.

[icantread49]

amcfaggot posted:

If you make 5 bucks off that app, I'll poop myself from disbelief

figuratively speaking

how about this, when i make 5 bucks off that app, i'll pay you to make me a less shitty icon

[ROBO_DONUT]

amcfaggot posted:

When you show me any form of BSP structure that can do what scene-graphs are currently doing and on the scale they're doing it, then I'll be impressed.

Do you understand what a BSP tree is? Outside of the bastardized Source mapping definition?
A k-D tree is a form of BSP tree.
A quad- or oct-tree is a form of BSP tree.
You can have a BSP tree using spheres instead of planes, where the volume inside is one child, while the volume outside is another. This is called a vantage-point tree, or VP-tree, and it has qualities that make it useful for finding nearest-neighbors when only a distance metric is available (think spell-check).

It's a very diverse structure, with many variants, and it's used a whole hell of a lot of places where you probably wouldn't think to look.

If you have a 'scene-graph based' renderer that scales well, it's probably also employing one of these other structures in addition to the basic scene graph.

[Jookia]

icantread49 posted:

how about this, when i make 5 bucks off that app, i'll pay you to make me a less shitty icon

I'll make you an icon if you make an Arch Linux 64bit port.

[icantread49]

Jookia posted:

I'll make you an icon if you make an Arch Linux 64bit port.

nono

amcfaggot is getting my first $5 to make a better icon

the next $50 are going to someone who knows about more than gradients and nice fonts

[slime73]

One of the problems I have with a lot of skeletal animations I see is that they can seem very jerky, because the slope (derivative) of the velocity of their bones isn't 0 when they start and stop. Using something like smoothstep instead of regular interpolation can help, although even then humans can still notice when the second derivative doesn't go to 0 at the start and end.

Another issue is that for many objects (especially ones that are alive), the movement of one part of the object can affect other parts, whereas most skeletal animation systems treats them independently.

[acpm]

icantread49 posted:

nono

amcfaggot is getting my first $5 to make a better icon

the next $50 are going to someone who knows about more than gradients and nice fonts

$50 emboss investment

[Chandler]

ROBO_DONUT posted:

Do you understand what a BSP tree is? Outside of the bastardized Source mapping definition?
A k-D tree is a form of BSP tree.
A quad- or oct-tree is a form of BSP tree.
You can have a BSP tree using spheres instead of planes, where the volume inside is one child, while the volume outside is another (this is called a vantage-point tree, or VP-tree, and it has qualities that make it useful for finding nearest-neighbors in higher dimensional spaces [think spell-check]).

It's a very diverse structure, with many variants, and it's used a whole hell of a lot of places where you probably wouldn't think to look.

If you have a 'scene-graph based' renderer that scales well, it's probably also employing one of these other structures in addition to the basic scene graph.

Just to also add on to this, the unreal engine uses BSP for rendering the CSG within the engine, and has since the first iteration of it. (All that's changed recently is they've gone from subtractive to additive CSG. Along with all those other engine improvements )