Daniel Marques

Welcome to Yara, a tropical paradise frozen in time. As the dictator of Yara, Antón Castillo is intent on restoring his nation back to its former glory by any means, with his son, Diego, following in his bloody footsteps. Their oppressive rule has ignited a revolution. Play as Dani Rojas, a local Yaran, as you fight alongside a modern-day guerrilla revolution to liberate Yara! Fight against Castillo's regime in the most expansive Far Cry to date, through jungles, beaches, and Esperanza, the capital city of Yara. Employ an arsenal of resolver weapons, backpacks, and vehicles to take down Castillo's ruthless regime.

I joined the Far Cry 6 gameplay programming team during its final stages of production and continued to work on it after its launch.

My responsibilities on Far Cry 6 consisted mostly of fixing bugs and crashes and polishing features spanning the areas of gameplay ingredients, gameplay systems, game mode logic, physics, weapons and gadgets, vehicles, 3Cs (character, camera, controls), network replication, quest scripting, and more.

I learned a lot during this project simply by virtue of being exposed to a large codebase, working with very knowledgeable people, and taking every opportunity to broaden my knowledge of each gameplay system.

Experience an epic action-adventure story set in feudal Japan! Become a lethal shinobi assassin and powerful, legendary samurai as you explore a beautiful open world in a time of chaos. Switch between these two unlikely allies as you discover their common destiny. Master complementary playstyles, create your shinobi league, customize your hideout, and usher in a new era for Japan.

I worked on Assassin's Creed Shadows for the entire production phase and during post-launch.

I was responsible for the technical implementation of various new gameplay systems. Namely, the Opportunity, Scouting and Ally systems. The Opportunity system was a novel way of exploring the world, purposely built for Assassin's Creed Shadows to contribute towards realising the Shinobi fantasy. It does so by building a passive network of scouts who provide the player with information each season about locations, activities, valuables, and rumours across Japan. The system also evolved to allow the player to find quest objectives by deploying their scouts to the specified area of Japan. Since this scouting system was a departure from the previous exploration paradigm, I was also responsible for creating the Guided Mode: an alternative mode where players automatically see their quest markers, bypassing scouting and locating the objective.

The Ally system aimed to contribute towards the same vision but in a more active way: the player can call upon recruited allies to assist in battle. Each ally has their own set of skills, useful in each situation the player encounters.

On a technical level, for each system and its multiple ever-evolving features, I conceptualised the code architecture, envisioned the data setup, and implemented the code. This was accomplished by working closely with colleagues from different disciplines and teams, namely game designers, technical designers, quest designers, testers, and other programmers.

Besides code ownership of the new systems, I was responsible for others, such as the exploration system, and I contributed to online collectables, the hideout, notoriety, achievements, and more.

Throughout the project, I applied my leadership skills to elevate the team by providing meaningful insights when discussing code architecture, by fostering their knowledge of C++, memory and performance, and by promoting high standards on our codebase through code reviews and discussions.

I enjoy learning about graphics programming, so I decided to create Roar: a small amateur Vulkan Rendering Engine. The project is written in C++, leveraging the more recent language features. The engine is loosely built with an Entity-Component-System (ECS) architecture using the EnTT library. Components represent meshes, lights, transforms, cameras, and graphics resources, while model loading, render passes, uniform buffer updates, and camera movement are implemented as systems. The project features a very rudimentary Render Graph which owns the render passes, uses dynamic rendering, automatically creates and destroys attachments and texture resources, and deals with layout transitions. In terms of shading, it features a Physically-Based Rendering (PBR) pipeline with Image-Based Lighting (IBL).