Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!


1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


RobinsonUK

Member Since 12 Feb 2012
Offline Last Active Apr 30 2012 02:36 AM

Posts I've Made

In Topic: Eigen with modern OpenGL

26 April 2012 - 11:40 AM

I had no end of problems when I tried to use a SIMD aware math library in my project (slmath). First I had to allocate on a boundary and second there's a problem with containers in VC++ such that putting such aligned objects into them resulted in seg faults and all kinds of issues (I'm a heavy user of std::). In the end I decided it was too much trouble for the potential gain in speed, so I switched to glm::, which so far has been a joy to use (and program that doesn't seg fault runs much faster than one that does!). I wouldn't rule out using SIMD for very tight, focused algorithms though, and I'm waiting with anticipation for a future where compilers intelligently make use of SIMD themselves, so I don't have to.

In Topic: GLSL Shader

26 April 2012 - 10:30 AM

Are you sharing vertices between edges? If you are, you'll have problems because the normal on the outside flat surface needs to be different to the normal on the inside circular surface.

In Topic: Where is the best place to put your .lib, .dll and gl header files?

22 April 2012 - 11:28 PM

OpenGL? SFML is pretty good.

In Topic: Where is the best place to put your .lib, .dll and gl header files?

21 April 2012 - 03:38 AM

I'm using GLU to bring in all the required extensions and then doing all of the windowing stuff myself. SFML is a pretty good library to use. I think the trouble with GLUT is that it hasn't been actively maintained for a very long time.

In Topic: Where is the best place to put your .lib, .dll and gl header files?

20 April 2012 - 05:31 PM

Personal preference I guess. I have a directory called libraries within which they sit. My applications are in the originally named "applications" at the same level as the libs. I have a single solution called 3rdpartylibs, that builds all libraries together and puts the resulting libs and dlls into a directory called Built/r or Built/d. All of my applications link against Built/r or Built/d. This way I can prevent the total randomness that tends to happen when the second law of thermodynamics applies itself to your hard drive ;).

PARTNERS