<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>The lab should be ready to go for the FPS and OSD stuff. If you
run into problem on you own computer with compiling the GL code,
then here are the steps I had to follow:</p>
<p>1. make sure all of your graphics card drivers are up to date</p>
<p>2. make sure that you have the most recent OpenGL libraries and
header files that your particular distribution will allow.</p>
<p>Here is the big problem -- all of these new things we are doing
with shaders hinge on the system recognizing the newer extensions
and functions (especially beyond OpenGL 4.3). The problem we had
in the labs was that everything was up do date except that the
GLEW library was ONLY recognizing functions found in OpenGL 4.3
and earlier. These were header files and libraries that are
maintained along with the distribution. That's why the lab
systems (running CentOS 7) would not run the code but my home
systems (running Rocky 8) would. Anyway, I dowloaded the source
code for GLEW and built it from scratch and installed it on each
of the systems over the old version of GLEW. Everything seems to
be working fine now. I can't wait to see what breaks when we turn
on lighting!</p>
<p>I should have code and examples and a video on how to do the OSD
display to you in the next day or so. I have tried to keep the
same philosophy as with the FPS display and made individual pieces
that you can add you code -- but I did some cool stuff with the
vertex shader this time that I think you will find useful.</p>
<p>Oh -- and the mistakes you can make on this can KILL
performance. I'll show you that too...</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-signature">-- <br>
<b>Andrew J. Pounds, Ph.D.</b><br>
<i>Professor of Chemistry and Computer Science</i><br>
<i>Director of the Computational Science Program</i><br>
<i>Mercer University, Macon, GA, 31207 (478) 301-5627 </i></div>
</body>
</html>