Jacob Dixey, PPJ #1

Recording and Expanding on Game Mechanics in HackNPlan - 3 Hours
Elevator Pitch + Final One-Pager - 1 Hour
Camera Controller + Ship Controller With Peter - 6 Hours

 Samples

 CameraBasic:
void Update()
{
        Vector3 moveCamTo = ship.position - ship.forward * distanceFromShip + Vector3.up * upFromShip;
        transform.position = transform.position * springBias + moveCamTo * (1f - springBias);

        transform.LookAt(ship.position + ship.forward * lookingPointFromShip);

}

ShipControlBasic:
private void FixedUpdate()
    {
        _igniting = Input.GetMouseButton(0);
        if (invertY) { _invertYControl = -1; }
        else { _invertYControl = 1; }

        _pitch = Input.GetAxis("Vertical") * _invertYControl;
        _roll = Input.GetAxis("Horizontal");

        transform.Rotate(new Vector3(turnTorque.x * _pitch, 0, -turnTorque.z * _roll) * rotateMult * Time.fixedDeltaTime, Space.Self);

        float RotationMult = (transform.forward.y + 1)/2;
       
        rb.velocity = Mathf.Clamp(rb.velocity.magnitude, 60, 300) * transform.forward;
        //rb.velocity = new Vector3(Mathf.Clamp(rb.velocity.magnitude, 20, 200), rb.velocity.y, rb.velocity.z);

        //Mapping RotationMult to AnimationCurve
        float acceleration = (ac.Evaluate(RotationMult) * (maxAcceleration - minAcceleration)) + minAcceleration;

        rb.velocity += (transform.forward * acceleration ) * Time.fixedDeltaTime;

        if (transform.position.y <= 0)
        {
            transform.position = new Vector3(transform.position.x, 0, transform.position.z);
        }


    }

Positive: Things really came together by the end of the week, from the site, to what we were able to include in the tech demo at a basic level. There's a lot to of foundation we laid this week, and the team works together well even as most of us have just met each other.

Negative: We started both our discussion of the game and our work pretty late into the week. I'm worried we haven't had enough time to discuss the mechanics we have laid out and make changes with all the other work we had to do, but it is also somewhat on us for starting that conversation so late in the week. We'll get a head start on next week.

Upcoming: Next I plan to continue fleshing out the ship's movement system, refining it, building out all the edge cases and so on. That's going to take a while and will inevitably see change after the criticism from play-testing. I also want to build our HackNPlan project into something that can track the current design of the game efficiently, in addition to holding our tasks based on that design within sprints that we can follow easily. The last thing I want to do is partition the game out better to make sure everyone has work without stepping on each other's toes. There's inevitably going to be situations like that, but I think now that the tech demo is done, we can be less strict about what we choose to get started on.

Comments

Post a Comment

Popular posts from this blog

Image
Jacob Dixey, PPJ#3 Playtest Survey Draft  - 2 hours 2nd Scrum Presentation - 1 hour Camera Improvements - 1 hour Spinning Action - 1.5 hours COM-Buster Takeoff - 1 hour Pause Gameplay - 1 hour Bouncing - 1 hour Tweaking - 2 hours Samples Spinning and Bouncing Scrum Presentation Pause Menu Positive: The level's visual style came together really well, in addition to many of the core mechanics surrounding flying being solidified with a lot of time put into tweaking it for playtesting. Our meetings have also given us a lot of good ideas for how we can communicate the different states of the player visually, such as heating up changing a shader on the COM-Buster and its trail, and when Overheating causing a fiery effect on the screen that slightly gets in the way of your peripheral vision. Negative:  It was another week of getting things together last minute. I want us to start meeting up earlier (say, Saturday) and then using Monday (or u...
Read more

Getting Started: In the Cloud(s) Sean McFadden Summary (PPJ #01)

Image
This week was spent doing two main things, both seemingly involving clouds. The first was getting our project website setup. I don't think we need anything fancy yet, so it consists of a basic standard website hosted on an S3 instance. I added some nice features like logging and view counting just so we can monitor exposure in the future. The website is really bare bones at the moment, pretty much consisting of only a few lines of text and some empty web pages. I plan on adding some more styling and media over the coming weeks, as we don't have much in terms of presentable media at the moment. However it is important to have a good framework for a modifiable website at the moment, as it can ease the process as the game grows. If you want, you can visit the website below!  oilandcorditegame.com Additionally, I spent a big chunk of time researching and planning the implementation of our clouds system. Since the game world has a massive layer of clouds below the player, ...
Read more

Peter Eldredge PPJ #1

Image
Set up the Unity Project and GitHub, adding some of my useful Scripts - 1 Hour Group meeting about the project and tasks - 2 Hours Conceptualized and implemented a modular enemy framework - 3 Hours Helped Jake with programming the player controller (primarily the physics) - 3 Hours Final setup for the demo/build - 1 Hour Enemy Example Enemy Framework Example The behavior above was made just by tweaking some values on prefabs and scriptable objects. The idea is that this will be expanded throughout the course and we can have an easy way to create new enemies. The behavior system can also be expanded to movement patters and a health system/weak points. Here are some inspector tabs to demonstrate how the behavior was achieved. The scriptable object is the attack behavior. It controls the conditions for the attack to fire as well as the prefab which handles the attack itself. In this case, it simply instantiates the FastLaser prefab. The condition that must be met are that...
Read more