raylib 6.2 lines up its image and screen drawing APIs
The C game library's new release has more than 300 changes, including a redesigned Image drawing API that mirrors the screen drawing functions, standard file return values and fixes from a security audit.
raylib 6.2 is out. Its creator, raysan5, published the release on GitHub on 15 October, almost six months after the last one. It was meant to be a small patch for a CMake build problem, but it grew into more than 300 changes: about 100 closed issues, over 500 commits, 20-plus new functions (619 in total) and more than 10 new examples.
The headline change is a redesigned Image drawing API. Most of the GPU-accelerated drawing functions now have a CPU counterpart that draws into an Image, with the same parameter order. DrawRectangle() pairs with ImageDrawRectangle(), and DrawTexturePro() with ImageDrawImagePro(), for example. Every ImageDraw function takes the target Image as its first parameter. The release notes say this could make faster 2D software rendering into an Image buffer possible later, alongside the existing rlsw software renderer.
The File API has been reworked too. Its functions now follow C conventions, returning 0 when everything worked and other values when something went wrong. Elsewhere, comments were reviewed, some parameters were renamed for clarity and some pointers were reviewed for const-correctness. raylib also went through a professional security audit by Radically Open Security, and most of the issues it reported have been fixed.
More than 100 people contributed for the first time, taking raylib past 950 contributors.
Why it matters: if you use raylib for small games or tools, this is a worthwhile update with a cleaner API. Code that checks what the file functions return may need changes, so read the changelog before you upgrade.
Source: raylib on GitHub (official post, opens in a new tab)
