Thanks for the response, Lars. I thought the same thing early on. I considered that there might be an overflow condition occurring. However, I ran the tests using only 3 significant digits with the same results. As I stated starting out, the situation occurs regardless of the value of the 2nd point. Even using integer values causes the issue. The more I look into this the more I'm thinking something got seriously broken in the vector computation routines. To me, it is acting like once there is an...
Thanks for the response, Lars. I thought the same thing early on. I considered that there might be an overflow condition occurring. However, I ran the tests using only 3 significant digits with the same results. As I stated starting out, the situation occurs regardless of the value of the 2nd point. Even using integer values causes the issue. The more I look into this the more I'm thinking something got seriously broken in the vector computation routines. To me, it is acting like once there is an...
Hi Jerome, Firstly, your English is fine, no worries there. The AUTOLEVELING property is in the Lazarus setup for CodeTyphon on my Linux (partial screencap included), however as mentioned previously, it doesn't function correctly. That property has been available as far back as CodeTyphon 6.1, and the same error exists there. It may even exist earlier than that, but 6.1 is the earliest installed version I have available on any of my machines. As far as the "lines" go, it is indeed possible to describe...
Thanks everyone for the input. The camera's up and direction properties match those of the gllines. I've also found during testing that if the camera's "autoleveling" property is set to true the camera will invert (turn upside down) instead of leveling. I am thinking something got broken at pilotlogic with the vector math. In response to the direction/up. Changing one will totally screw the other. So they are supposed to be connected in some way but from what I'm seeing, there is no documented reasoning...
Thanks everyone for the input. The camera's up and direction properties match those of the gllines. I've also found during testing that if the camera's "autoleveling" property is set to true the camera will invert (turn upside down) instead of leveling. I am thinking something got broken at pilotlogic with the vector math. I see that there was work going on to make the current SVN code Lazarus compatible, and another member had asked recently about this with no response. In response to the direction/up....
Hello, this is my first post here. I am having a devil of a time with GLLines in 3-space. Attached is a screenshot of an example. Both points are in positive space, and the 2nd point is supposed to go UP, but instead dives down into negative space. The nodes are added via Nodes.AddNode() and it does not matter whether the points are added via (.x .y .z) or as a taffinevector. As you can see from the screenshot both the UP and Direction settings are shown. The first point is correctly placed, however,...