OtspIII posted:

Your room placement method sounds really good, based on all the things I'm trying to make sure I worry about. The rooms seem to have a good balance of both branchyness and loopyness, and even though the screenshot you posted is pure rectangles, they do have a really nice variety of sizes and shapes. I'm obsessively hunting for other similar projects I can steal ideas from, so I'm looking forward to seeing you post more updates here in this thread.

A bunch of people posted:

PDP-1 posted:

How many regions are you planning to have to sort through? Quadtrees are most likely overkill if you'll have less than a few hundred. It's easy to waste tons of time coding up the ~*magical perfect system*~ only to find that you've added a lot of complexity for no real performance gain and it sounds to me like you might be heading down that road.

Just start with the simplest thing that works, which in this case may be to do the point-in-polygon check over all the items until you find a hit. Run the game and see what your performance looks like. If it's too slow, go up one notch in complexity and maybe wrap each region in a circle and if the click point is outside of that circle (a cheap and simple test) the region could not possibly have been clicked on and there's no reason to do the point-in-poly test. Is that fast enough? If no, then now you're in quadtree territory.

HaB posted:

Yeah it will be more like 20-30 tops, and even that's probably an over estimate.

roomforthetuna posted:

Definitely not worth doing quadtrees, probably not even worth doing pre-checks with bounding boxes, just iterate through the whole list and run point-in-poly.

Null Pointer posted:

The number of edges is what matters, not the number of regions. You're probably still right about using a linear search though.

Harvey Mantaco posted:

Yours sounds faster than mine as it seems to flow more organically.

In my defense, I just didn't turn on the other shapes for that render.
Old renders with some things turned on:

ninjeff posted:

Wow that's a pretty :smugskull:

Harvey Mantaco posted:

Hahaha the gently caress are you doing in this thread? Why aren't we working on something together? I thought you didn't code anymore.

"I like, I can't even... gently caress. Programming, I can't even like... these loving compilers, they don't even loving work. I am never going to do that poo poo."
-Mewse, 2012

mewse posted:

I'm pretty sure I told you I'm a good programmer I just hate it. I'm totally busy with boxing and work. That said, if you want to give me an account to your version control I'd love to poke around.

I'm also friends with a bunch of local game dev people if you wanted me to connect you with them.

Hanpan posted:

I -think- what I am suppose to do (from what little I can gleam from blogs and such) is attach a sensor fixture to the body of my pickup game object which hopefully will fire a collision event before anything is calculated. Can anyone confirm if this is the right way of doing things?

Hanpan posted:

Not sure if anyone here can help me. I've been playing around with libgdx and having a whale of a time. I've never really used Box2D and I'm trying to figure out how to handle "triggers" (I think they are called "sensors" in Box2D?) for when my player colliders with pickups.

I want the pickups to have bodies as I need them to collide with the environment but what I'm trying to do is make it so when the player collides with them (who is also a body), an event will fire before any collisions are calculated so the player can walk through them without a hitch.

I -think- what I am suppose to do (from what little I can gleam from blogs and such) is attach a sensor fixture to the body of my pickup game object which hopefully will fire a collision event before anything is calculated. Can anyone confirm if this is the right way of doing things?

Manslaughter posted:

I've been using FMOD for my sounds/music in pretty much every game I make for a few years now, it's fantastic.

What exactly are your goals in getting someone to use your, uh, resources? I ask because finding good sfx/music is like taking a power sander to my sensitive areas.

Pfhreak posted:

I've worked with Rupert Buttermilk before, and I highly recommend him! He did the sounds and music for our SA Gamedev contest entry. Absolutely dominated his peers.

Manslaughter posted:

I've been using FMOD for my sounds/music in pretty much every game I make for a few years now, it's fantastic.

What exactly are your goals in getting someone to use your, uh, resources? I ask because finding good sfx/music is like taking a power sander to my sensitive areas.

RoboCicero posted:

Strangely enough, though I'm taking like an order of magnitude more time to build basic code, it's a ton more relaxing. Just look at this!

Kaf posted:

Can anyone recommend any books on designing/implementing match-making services? Getting into this soon at work and it's a whole new field for me.

Paniolo posted:

Harvey Mantaco posted:

Harvey Mantaco Development Cycle Revealed!:

1. Fall in love with old-school sprite based low graphics games.
2. Spend a lot of time working on game similar to step 1.
3. Read posts by people like "Paniolo" with breathtaking terrain.
4.
5. Turn on fireplace and glare into it with a blank, thousand yard stare for a couple of minutes. Sit down to code. Immediately stand up and get coffee. Sit down again, immediately stand up and go to washroom. Come back after not even going, sit down, stand up, walk to edge of room, move a book to another spot on the shelf. Sit down, look at current graphic engine. Curse.

Looks good man.

Harvey Mantaco posted:

5. Turn on fireplace and glare into it with a blank, thousand yard stare for a couple of minutes. Sit down to code. Immediately stand up and get coffee. Sit down again, immediately stand up and go to washroom. Come back after not even going, sit down, stand up, walk to edge of room, move a book to another spot on the shelf. Sit down, look at current graphic engine. Curse.

OneEightHundred posted:

Going to assume that you mean lobby type stuff.

It's not particularly complicated among network services, you pretty much just put users in a queue and when you get enough for a game you give them a lobby. Rated matchmaking uses Elo ratings and tries to group users with similar Elo, relaxing the similarity requirements if matchmaking is taking too long.

One thing to keep in mind though is that Elo is only meant for 1v1 matchups and has all sorts of weird distortions when used outside of that. 1v1 as in 1 rank vs. 1 rank, rated teams and such work fine with it as well, but it is NOT designed to handle multiple rankings vs. multiple rankings.

Multi-ranking team matchmaking is much more experimental territory at the moment, I'm of the opinion for example that individual performance metrics should be used to adjust ratings in a team game, but it's difficult to come up with a system for that which doesn't lead to counter-productive behavior.

Smurfing/tanking (deliberately crashing your rating so you can stomp inexperienced players) are also a problem you have to watch for, the only real-world solutions I've seen to that are that League of Legends appears to flag smurf accounts which looks like it stops them from getting grouped with newbies (players tend to notice they're flagged because their queue times suddenly skyrocket), and Starcraft 2 gives you one rank per copy of the game so you can't have a high-rank account and a smurf account unless you buy a second copy.

Scaevolus posted:

Microsoft's published information on their Trueskill ranking system should be quite useful, and includes formulas for calculating skill and performing matchmaking.

quote:

I'm creating a basic game for a college course and I'm having trouble with the controller script.

I have the script set to rotate a ball so you move around the level by rolling, I have the movement and rotation limited to set axis so it only moves along a 2D plane and doesn't rotate vertically to the camera view. (Z position is frozen, X and Y rotation are frozen)

I seem to be hitting a speed limit though, I can't get it to go faster than 3.5 according to the gui script I'm using to show me the speed.

Here's the GUI script and controller script.

code:

function OnGUI()
{ 
  GUI.Label(Rect(0,0,100,100), rigidbody.velocity.magnitude.ToString());
}

code:

function Update () {
if (Input.GetKey ("right")) {
rigidbody.AddRelativeTorque (Vector3.back * 200);
}
if (Input.GetKey ("left")) {
rigidbody.AddRelativeTorque (Vector3.forward * 200);
}
}

Luminaflare posted:

Does anyone know how to fix the speed/velocity limit I seem to be hitting?

roomforthetuna posted:

Perhaps adjust the drag value on the rigidbody?

Luminaflare posted:

edit: Yeah I reduced the torque a bunch, not sure why it was set to that. Torque doesn't seem to effect the speed at all though.

roomforthetuna posted:

That's pretty weird. Does the torque at least effect how long it takes to get to the top speed?