* Improve cmake config file generation
This allows for finding raylib on a non-standard location (eg, not in /usr/lib{,64})
* Only have glfw as private if using internal glfw and not static
* basic pbr example
pbr implementation includes rpbr.h and few shader files header only file, which self contain everything needed for pbr rendering. Few textures and one model of the car which is under free licence which is included inside basic_pbr.c example file currently supported shader versions are 120 and 330 , version 100 has small issue which I have to resolve
* Unloading PBRMAterial
I forgot unloading PBRMaterial
* fix small issue with texOffset assigment.
value was Vector4 at first but I found out it would be unclear for and users, so I change to have two Vector2 instead, but forgot to assign offset .
* Changed size of textures and file name changed
Changed size of textures from 2048x2048 to 1024x1024 and file name changed to shaders_basic_pbr.c ,
Added the function PBRModel PBRModelLoadFromMesh(Mesh mesh);
but GenMeshPlane(2, 2.0, 3, 3) culdn't be used because it crash once GenMeshTangents() is used with that plane mesh
* Update to 5.5 version of eexample and fix to work in web
set GLSL_VERSION 100
set precision highp float;
removed in keyword
fix for loop has to use only constant
* Update shader_basic_pbr example to work on web
changed to GLSL_VERSION 100
update glsl100 shader
set float precision to highp
removed keyword in
change for loop tu use constant value gives an error
* Update shader_basic_pbr example to work on web
changed to GLSL_VERSION 100
update glsl100 shader
set float precision to highp
removed keyword in
change for loop tu use constant value gives an error
* removed rpbr.h
removed rpbr.h
* increased vertex data precision to match blender exports
* modified memory allocation to better fit higher precision data
* now accounting for newline characters during allocation
* now accounting for potentially higher vertex counts
* removed unnecessary final newline
Changed line 118 from, "// For advance camera controls, it's reecommended to compute camera movement manually", to, "// For advanced camera controls, it's recommended to compute camera movement manually".
