Jump to content
  • Advertisement

BIZARRE Sprint 33 plus 34



Happy new year! ūüôā

The new sprint no. 34 is published today.

Let's see what we did during the last two sprints 32 and 33.

First of all, we finished texturing the first game scene, Clearwater's apartment. All furniture is modelled and textured, placed and polished.

As you can see below:


We put more effort into the park design opposite Clearwater's home. We placed benches, trees and lanterns in the park and made them all looking good.

The metro is running regularly, the little fountain is built up but what we still miss is the grass.

But we installed lamps, lights and bulbs in the houses around Clearwaters apartment, therefore his neighbors look a bit more livelier. 

Plus, we worked on Clearwater's gunplay behavior. He is now able to pull his gun when a button is pressed, he is able to shoot as long as his magazine isn't empty, he reloads when the magazine is empty and in case, he has another one. He stops shooting when all bullets are fired.

You can see an extract here in this video (#WIP):

We implemented all the gunplay behavior in C++ but also in Blueprint.

We melted various animations together, so that he can walk and aim, shoot and switch fluently.

Clearwater's gunplay is still unfinished. We still need to do a looot of things. #WIP

I wrote dream no. 12 and felt that I forgot about everything I wrote before, that's why I decided to re-read the whole book

hoping I'll like it and I can easily write dream no. 13. With dream no. 13 the writing is finished and the book is completed.

The #WORDSproductions team is currently reading the book, too, at least all released chapters I felt OK with.

The book BIZARRE Episode I is pretty thick, isn't it?

Our plans for the current sprint:

  • We have to improve Clearwater's gunplay (+ appearance)
  • We have to improve Clearwater's walking and running animation
  • We have to improve Clearwater's facial animations
  • We have to implement a shoot button and a gun status bar (UI)
  • We have to adapt the collision boxes in Clearwaters apartment
  • We have to furnish Clearwater's terrace on the first floor
  • We have to implement a stop walking button and to model a proper animation when he is touching a collision¬†
  • I have to re-read and complete the book BIZARRE Episode I
  • We have to texture the metro, and some stuff in Clearwaters-world-outside environment

It's a damn long way to our new Gameplay Video as everything is built up but nothing is 100% completed let alone perfect.

I meditate now.


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
  • Advertisement
  • What is your GameDev Story?

    In 2019 we are celebrating 20 years of GameDev.net! Share your GameDev Story with us.

    (You must login to your GameDev.net account.)

  • Blog Entries

  • Similar Content

    • By Discip13
      Hello everyone! My name is Nikita Yashukov. I'm a 3D Artist looking for projects to participate. I have been creating 3D stuff for about two years and I'am interested in teamwork experience.
      You can see my works here: https://www.artstation.com/lof
      My contacts: shvartznik@gmail.com
      Thank you.

    • By calioranged
      *** Beginner question - some terminology may not be correct ***
      I will relay my understanding of OpenGL shaders in this post in the hope that members can confirm the areas where I am correct and redress the areas where my understanding falls short.
      Firstly, here is my shader:
      #shader vertex #version 330 core layout(location = 0) in vec4 position; layout(location = 1) in vec2 tex_coord; out vec2 v_tex_coord; void main() { gl_Position = position; v_tex_coord = tex_coord; }; #shader fragment #version 330 core layout(location = 0) out vec4 colour; in vec2 v_tex_coord; uniform sampler2D u_Texture; void main() { vec4 tex_colour = texture(u_Texture,v_tex_coord); colour = tex_colour; }; First Query:
      I have been following a tutorial on shaders and have replicated the code used in the tutorial. My program renders a square, onto which a texture (image) is placed. I have bound the vertex position coordinates to the first attribute index of the vertex array, and the texture coordinates to the second attribute index of the vertex array *1*.  The program works without any issues, but there are some aspects which have me confused and I therefore seek clarification from forum members.
      The vertex shader features the below lines:
      layout(location = 0) in vec4 position; layout(location = 1) in vec2 tex_coord;  From my understanding, these lines are essentially saying: "take the layout of attribute 0 and place it in the 'position' variable" and "take the layout of attribute 1 and place in the 'tex_coord' variable". This makes sense to me since the vertex shader determines the position of each vertex on the screen. However, in the fragment shader, I am more dubious:
      layout(location = 0) out vec4 colour; If the lines in the previous snippet are saying "take the layout of attribute x and place it in the 'y' variable", then what exactly is the above line saying? Specifically, why is the layout from the position attribute (attribute 0) being used and not the texture attribute (attribute 1)? 
      Second Query:
      I understand that the input variable in the fragment shader (v_tex_coord) is supplied by the output variable from the vertex shader (which originally gathered its data from the layout of attribute 1). But how is the final colour for each pixel here actually set? In the main() function of the fragment shader, the texture() function is used. From what I have gathered this function samples the colour of each pixel in the texture.
      Once a texture has been bound to a specific slot, we can set the uniform outside of the shader with glUniform() by returning the location of the uniform variable (location of "u_Texture" in this case) and then linking it to the previously bound slot. Presumably this is the step which links together the texture image and the uniform - meaning that 'u_Texture' now has access to the texture image via the slot to which it was bound (please correct me if I am wrong here).  The next assumption is that the texture() function will sample the corresponding colour value through its parameters ('u_Texture' - which now contains the texture image (or at least has access to the slot to which the texture image is bound) and 'v_tex_coord' which contains the coordinates to which the texture should be rendered). 
      Here is the part that confuses me most:
      The outcome of the texture() function is returned to the vec4 variable 'tex_colour' which then reassigns its value to the output vec4 variable 'colour'. What was the point in this last step? 'tex_colour' already contained the result of the texture() function so why does it then need to be reassigned to 'colour'? 'colour' is not predefined by OpenGL, I can change the name to 'the_colour', 'a_colour' or 'the_ice_cream_man' and the texture image is still rendered perfectly fine. Is it the case that the variable defined as the output in the fragment shader will be used to render the colour of each pixel regardless of its name? I suppose that the reason I ask this is because the 'gl_Position' variable in the vertex shader which sets the position appears to be a variable predefined by OpenGL whereas in the fragment shader this doesn't appear to be the case with the variable which sets the colour... some clarification of this would be greatly appreciated. 
      *1* - terminology may be wrong here but essentially I have used glVertexAttribPointer() to set the below vertices position coordinates to attribute 0 and the below texture position coordinates to attribute 1. The full program consists of 16 files and it didn't want to include source code for each file because most of it is irrelevant to the questions I am asking.
      float positions[] = { // vertices // texture -0.5F,-0.5F, 0.0F,0.0F, // x and y coordinates 0.5F,-0.5F, 1.0F,0.0F, 0.5F, 0.5F, 1.0F,1.0F, -0.5F, 0.5F, 0.0F,1.0F };  
    • By Brain
      This is my level editor workflow. Levels are represented by simple integers in the right hand column under a component called LevelInfo, and meshes are placed manually on the grid. The grid is replaced at runtime with actual gridactors.
    • By Brain
      Oh dear, accidentally blown up a radioactive goop crate.

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!