Name: ビッグプロジェクト!トップダウンシティベースの自動車犯罪ゲーム #1 (BIG PROJECT! Top Down City Based Car Crime Game #1)
Uploaded: 2021-01-14T10:15:05.000Z
Duration: 1 h 3 min 52 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

Let's make a top down, city based car crying game.

This is a big project until all the newcomers to the channel welcome.

By the way, that means we'll be splitting this over several episodes, and I tried to start each episode by showing what we're aiming for.

And as you can see, we have a car here and we're driving around the city.

There's no collision detection yet, so I'm only really showing what will be getting done in this particular episode.

Now, when I do a big project, I like to use things that I've shown in previous videos on Build upon Them and show how it all comes together.

And here we can see the city is in using the three D engine, But I'm also using the pixel game engine.

All the graphics are quite simple and really just placeholders.

Whilst we developed the game, I think this is quite an important strategy just to make sure that first of all, you can get it to work on, then make it work well.

And when I say a top down city, I mean a top down city, so we'll be looking at how we're handling.

The three D graphics will be looking at things like collision detection will, of course, be adding non player units such as police cars and possibly pedestrians on.

We'll need some sort of mission based system, so there's quite a lot to get on with.

I've spent lots of a lot of time developing this city on that driving around it.

Now when we're working with a game that has a large amount of rich details such as this, it's quite important that we also developed the tools to help us develop the game.

So in this video will show some very basic city editing tools that I can show you something.

Now, using the mouse cursor, I can place it anywhere in the scene and place additional roads and you'll see that the roads automatically align themselves with the correct junctions and I could remove the roads as well.

I can also place buildings and I can place buildings of different height, grow the buildings up and I could grow them back down on there's a little bit of novel interaction.

I'm using the car to control the camera, but editing a city like this might take some time doing it tile by tile.

So I've also implemented the ability to select tiles in the scene and apply the same transformation to all the tiles simultaneously on the selection works at any zoom level.

One of the principles I tried to adopt when I'm developing a game is that the game on the game editors should try and use the same engine on The primary reason for this is that you can edit the game as necessary whilst you're playing it so you can find tune it quite easily.

I'll just show a little bit more road building that we can connect these two roads together.

As you can see right now, the game is in a very basic for the graphics look a little bit repetitive and a little bit square on that simply because they're placeholders.

Let's make it work before we make it work.

Well, we'll have to keep remembering this mantra on what is especially important before taking on any larger project is that you have a plan, so let's get started.

Clearly, this game is inspired by the classic Grand Theft Auto, Siri's, but I don't intend to clone it completely.

I'm going to be making a much more cooked down, simpler version.

So what are the features that I'm aiming for in this game?

Well, the first thing I want is a large city, and I want the ability to choose and drive cars.

You need cars to get from A to be, which implies some sort of mission based activities.

The city would be a bit boring if it was empty, So I'm going to need some traffic in there as well, so I'm gonna have to have some other carts on.

As with the classic Grand Theft Auto, the player could literally steal a car that they saw driving around.

Typically, the missions will involve with you being chased by police force.

So I think a particular game dynamic is to evade capture in games.

I personally like collecting things, so I'll probably have some pickups in there as well on because the city is quite large, we're probably going to need a few things to help us.

Might need some navigation aids, like a GPS system.

Perhaps we're doing some editing tools for the different cars.

They're probably going to have a unique properties such a speed and handling or resilience to damage if you crash them into things.

And that's quite an important thing, because if we're driving around, we're going to need some collision detection.

I don't want the missions to just be to go from random location a two random location.

It would be more fun if they tell a bit of a story.

So we want the missions to be script a ble.

And this has already got me thinking, because if we're going to have assets with variable properties on, we're going to have game play with variable properties.

Perhaps, just maybe, we want these to be modifiable, so we might want to think about using an external scripting language to handle this.

Now traffic on DDE, in some ways evading capture.

We're going to need a degree of path finding, perhaps potentially some sort of a I realistically, pickups are the easy ones in this.

It's got a lot of elements to it, and there's such typically during a big project.

I don't go into as much detail on all of the precise elements, and I might skip over some of the code that we're going to write, which means these videos tend to move it a little faster pace than my normal videos.

I'm going to start with a blank visual studio project onto this project.

I've added the oil see pixel game engine on a blank source, file the video ccc one dot cbp In this instance, the first thing I'm going to do is take the template from the head of file and paste it into the source file.

This is just a very quick and easy way to get settled.

What I will add at this point is, Please don't forget to define ol CPG application before you include the game engine.

I'll just quickly modify the template to suit our needs, and I'll remove the things that we don't need.

An unused create and on user update if you knew to pixel game engine on user create is a place that only gets called once, so you can use this to load your resources.

Andan user update is called every frame I'm going to create a pixel game engine, which is 768 pixels wide by, 480 pixels high.

So it's a widescreen application, so I'm going to reduce the pixel size because it's quite a high resolution to So I wanted to fit on my monitor.

I want to keep many aspects of the game very, very simple indeed.

So I'm going to restrict my city to really just being a two dimensional array.

Were each cell in the array represents something different.

For example, I'm going to want to know if a cell contains road or not, so we'll have a flag that indicates if it's a road.

I think it might be quite useful later on when we're dealing with navigation to know that road's a distinct.

If the cell isn't a road, then presumably it contains some sort of scenery, and for now I'm going to represent that scenery using a single interview.

For example, if the scenery interview is zero, then it's just flat, so we'll draw some grass.

If the interview is less than zero, then for now the cells simply not going to exist.

But in the future, video I'm going to want that to be water, and this gives me 1/3 option for anything that is greater than zero.

And I'm going to assume that any value greater than zero is going to be a building on that.

The value indicates how many stories that building has.

So if it's a one, then we have a single story.

If it's too and we'll have two stories, there's the 1st 1 It will be a second on top.

So in my cell structure so far that means I've got something that indicates road.

You're probably going to be a Boolean, and I've got an interview I'm going to call height.

That's enough to get us started right now.

I'm making no attempt to optimize any of this at all, but I'm going to need some geometry for my three d engine to render.

So the first mesh is just going to be a simple flat quad two triangles and I'm going to use this quad for rendering roads grass on the roofs of the buildings, basically anything that's flat when look down from above the second type of mesh I'm going to use our sort of the outer walls.

So if we're looking at this, we got a Southern direction here.

We've got a quad that makes the Southern direction, but in the same match, I'm also going to attach the other side's as well.

Br westerly direction northerly on easterly.

I'm going to keep that as one single mesh.

I'm also going to keep all of my coordinate systems in unit values.

So our quant is a one by one unit quad on our outer walls are going to be a one by one by one, not a cube, because I've not got a top or a bottom.

However, whenever I'm working with three D onions, I also want to include a cube somewhere because it's a good way of testing that you've got everything settled correctly, have created some very simple placeholder assets to, and you'll notice that these are also based on a single cell sites, particularly for the roads and grass.

The sides of the buildings here aren't, but laying out the texture in this way has revealed what kind of junctions I need.

So I got a north south East and West T Junction.

I've got horizontal and vertical road segments.

I've got a crossroads, so I've covered all of the types of road I want to have.

This does imply single constraint, though, and that is that.

Not only does this make the production of the graphic simpler, it's also going to help later on when we're dealing with the artificial intelligence and non player vehicles, because I've got a feeling things like Dead ends.

My cause is a problem because I'm using the pixel game engine.

字幕リスト動画再生

ビッグプロジェクト!トップダウンシティベースの自動車犯罪ゲーム #1 (BIG PROJECT! Top Down City Based Car Crime Game #1)

sort

access

scale

position