Addressing Rejection Feedback #2

1. Tool tip Descriptions

So basically the program was hard to use, and, I kinda agree. So I added tool tips on known attribute names to help understand which attribute/value does what.

2. Rethinking the Tutorial

In addition, the tutorial was a bit hard to understand. To address that, I simplified the tutorial and made it easier to understand what's going on. While the previous tutorial was changing a texture, that required the user to understand where the change texture button is, and then locate the texture itself, requiring some understanding of the program. This defeats the purpose of a tutorial.
My new and improved tutorial involves removing textures, a simplified process that can be done with a click of a button. This helps the user understand how removing the normal, for example, affects how lighting calculations are made..

Something I noticed reviewing feedback videos.

In addition, I noticed that ImGui windows are really small at first launch, requiring the user to adjust its size before doing anything. With this update, I bundled configured imgui.ini files for ImGui to detect and automatically scale windows to an appropriate size.

Full Changelog: v1.0.1...v1.0.2

Changes:
Fixed a minor issue related to display scaling on ImGui that may cause small interfaces on high-DPI screens, such as laptops and high-resolution displays..

Full Changelog: v1.0...v1.0.1

Vibrant Release 1.0

After a period of inactivity I finally finished this project! It's been a blast working with C++ and learning about new concepts, like std::variant and such. I think I learned alot about the standard library and am excited to use it in my later projects, although it does make debugging compile errors a nightmare....

Full Changelog: https://github.com/SoHiEarth/vibrant/commits/v1.0