(2016-07-15, 11:44)Trevor Sandy Wrote: Thanks Travis!

I imagine the ability to generate PoVRay renderings from the command line was not addressed in this update ?

I would like to replace the L3P module in LPub3D because is it not open source and there is no way to maintain it. If I could generate PoVRay  images from the command line using LDView, it would be possible to replace L3P.

If you care to describe an efficient approach to incorporating PoVRay image generation via the command line, I could take a look at building an LPub3D version of LDView with this capability.

Cheers,

(2016-09-14, 6:06)Michael Horvath Wrote: Is it possible to view only a sub-model of an MPD? I am trying to do this in the Model Tree list, but the only option I see is to highlight the item. Thanks.

(2016-09-14, 6:06)Michael Horvath Wrote: Is it possible to view only a sub-model of an MPD? I am trying to do this in the Model Tree list, but the only option I see is to highlight the item. Thanks.

(2016-10-23, 20:24)Michael Horvath Wrote: Will the source code compile with Visual Studio Express 2015? The 2005 version does not install on Windows 10.

(2016-10-24, 2:35)Travis Cobbs Wrote:

(2016-10-23, 20:24)Michael Horvath Wrote: Will the source code compile with Visual Studio Express 2015? The 2005 version does not install on Windows 10.

Do you mean that Visual Studio 2005 doesn't install on Windows 10, or LDView 4.2 doesn't install on Windows 10? Because my final development work was done (with Visual Studio 2005) in Windows 10, and it worked fine. Of course, Windows 10 isn't really Windows 10 any more; it's now Windows 10 with Anniversary Update, and that may as well be a whole new operating system given the huge swath of programs that Microsoft broke.

In any event, the 4.2 source tree won't build in Visual Studio 2015, but I migrated the source tree to GitHub and also updated it for Visual Studio 2015:

https://github.com/tcobbs/ldview

If you want to try to build it yourself, you are welcome to do so, and there's a decent chance that it will work, since I included pre-built VC2015 versions of the various libraries that LDView depends on in the GitHub source tree. And all my Visual Studio 2015 work was done with the free version of Visual Studio 2015.

Despite my claim that 4.2 would likely be the last release, there will in all likelihood be a 4.3 release at some point. I'm not going to make even rough estimates on when that might happen due to how bad I was with the 4.2 release.

(2016-10-24, 14:32)Michael Horvath Wrote: I meant that Visual Studio 2005 won't install on Windows 10.

I will try compiling the github stuff, though I don't really know what I'm doing.

Are the instructions in Build.txt up-to-date?

(2017-10-07, 20:17)Michael Horvath Wrote: I am trying to find in the source code where the window title bar text is set. I'm trying to keep the version I've modified separate so I don't get the two confused. I've modified several strings in 'ModelWindow.cpp', and the title text is indeed changed *after you load a model*, but not when you initially start the program. Any advice?

Also, when redistributing source code, is it customary to include the entire project directory, or only a subset? (Visual Studio)

Quote:Adds a viewing mode called "FPS Mode" that alters lateral camera movement so that it is always level with the horizon, ignoring the angle of the camera above or below it (but not ignoring the angle around the vertical axis).

(2017-10-19, 1:26)Michael Horvath Wrote: There is a bug/oversight. When FPS Mode is turned on, the camera should rotate around the universe's vertical axis no matter where the camera is pointing to. Instead, the camera is rotating around its own axis, and then auto-correcting so that its vertical axis points toward the universe's up direction. It's not a big deal, but I don't understand how I did not notice this until now.

(2017-10-20, 12:06)Michael Horvath Wrote:

(2017-10-19, 1:26)Michael Horvath Wrote: There is a bug/oversight. When FPS Mode is turned on, the camera should rotate around the universe's vertical axis no matter where the camera is pointing to. Instead, the camera is rotating around its own axis, and then auto-correcting so that its vertical axis points toward the universe's up direction. It's not a big deal, but I don't understand how I did not notice this until now.

I started a thread here.

https://gamedev.stackexchange.com/questions/149736/first-person-style-controls

As you can see, I am fumbling trying to find a solution.

(2017-10-20, 12:06)Michael Horvath Wrote:

(2017-10-19, 1:26)Michael Horvath Wrote: There is a bug/oversight. When FPS Mode is turned on, the camera should rotate around the universe's vertical axis no matter where the camera is pointing to. Instead, the camera is rotating around its own axis, and then auto-correcting so that its vertical axis points toward the universe's up direction. It's not a big deal, but I don't understand how I did not notice this until now.

I started a thread here.

https://gamedev.stackexchange.com/questions/149736/first-person-style-controls

As you can see, I am fumbling trying to find a solution.

(2017-10-21, 3:32)Travis Cobbs Wrote:

(2017-10-20, 12:06)Michael Horvath Wrote: I started a thread here.

https://gamedev.stackexchange.com/questions/149736/first-person-style-controls

As you can see, I am fumbling trying to find a solution.

I was working on a feature like this in the past, and apparently never got it working. If you set flags.keepRightSideUp to true in LDrawModelViewer, you will see what I had. Note that it sometimes twists the camera by 90 degrees briefly. I'm not sure why. It may be easier to look at what I already had and fix it than to implement it from scratch.

(2017-10-21, 5:37)Michael Horvath Wrote:

(2017-10-21, 3:32)Travis Cobbs Wrote: I was working on a feature like this in the past, and apparently never got it working. If you set flags.keepRightSideUp to true in LDrawModelViewer, you will see what I had. Note that it sometimes twists the camera by 90 degrees briefly. I'm not sure why. It may be easier to look at what I already had and fix it than to implement it from scratch.

Using flags.keepRightSideUp is not the same solution as FPS-style controls, like in a video game.

This article has a very general explanation of the solution. But I am having a hard time applying it to LDView. (I am very new to C++.)

https://gamedev.stackexchange.com/questions/136174/im-rotating-an-object-on-two-axes-so-why-does-it-keep-twisting-around-the-thir

[edit]

At the moment I am looking for a way to convert a matrix to something the camera can use. Is there documentation for the camera object?

(2017-10-21, 20:33)Travis Cobbs Wrote: There's no way to convert a matrix into something the camera can use.

(2017-10-22, 0:24)Michael Horvath Wrote:

(2017-10-21, 20:33)Travis Cobbs Wrote: There's no way to convert a matrix into something the camera can use.

Could you explain this more? I thought that "camera.rotate" takes three Euler angles as input. Am I wrong? I have written a routine for another program that can convert a matrix to Euler angles, and could adapt that to here. Will that approach not work?

(2017-10-22, 4:16)Travis Cobbs Wrote:

(2017-10-22, 0:24)Michael Horvath Wrote: Could you explain this more? I thought that "camera.rotate" takes three Euler angles as input. Am I wrong? I have written a routine for another program that can convert a matrix to Euler angles, and could adapt that to here. Will that approach not work?

LDLCamera::rotate should in fact take the Euler angles, but a transformation matrix has a lot more in it than just that. If you have a rotation-only transformation matrix, then what you're doing is probably fine.

(2017-10-22, 20:52)Michael Horvath Wrote:

(2017-10-22, 4:16)Travis Cobbs Wrote: LDLCamera::rotate should in fact take the Euler angles, but a transformation matrix has a lot more in it than just that. If you have a rotation-only transformation matrix, then what you're doing is probably fine.

Will this create the correct type of matrix?

Code:

        TCFloat identity[16] =
        {
            1.0, 0.0, 0.0, 0.0,
            0.0, 1.0, 0.0, 0.0,
            0.0, 0.0, 1.0, 0.0,
            0.0, 0.0, 0.0, 1.0
        };
        TCVector::calcRotationMatrix(cameraXRotate, cameraYRotate, identity);

(2017-10-22, 20:52)Michael Horvath Wrote: Also, I have written a matrix to euler converter in Lua for another project. Could someone explain how to convert it to C++?

(2017-10-23, 4:05)Travis Cobbs Wrote:

(2017-10-22, 20:52)Michael Horvath Wrote: Will this create the correct type of matrix?

Code:

        TCFloat identity[16] =
        {
            1.0, 0.0, 0.0, 0.0,
            0.0, 1.0, 0.0, 0.0,
            0.0, 0.0, 1.0, 0.0,
            0.0, 0.0, 0.0, 1.0
        };
        TCVector::calcRotationMatrix(cameraXRotate, cameraYRotate, identity);

I believe it will. That function rotates around X and then rotates around Y by the given amounts. Side note: you don't have to initialize the array of floats that you pass in; that's a purely out parameter.

(2017-10-23, 4:05)Travis Cobbs Wrote:

(2017-10-22, 20:52)Michael Horvath Wrote: Also, I have written a matrix to euler converter in Lua for another project. Could someone explain how to convert it to C++?

The array of floats has indices that go from 0 to 15. I can't remember if it is horizontal first, or vertical first. If it is horizontal first, the mapping would be:

r00 = matrix[0];
r01 = matrix[1];
r02 = matrix[2];
r10 = matrix[4];
r11 = matrix[5];
r12 = matrix[6];
r20 = matrix[8];
r21 = matrix[9];
r22 = matrix[10];

(Note that the 4th column is skipped, because the rotation portion is a 3x3 matrix, but the data in LDView is a 4x4 matrix.)

If it vertical first, the mapping would be:

r00 = matrix[0];
r00 = matrix[4];
r02 = matrix[8];
r10 = matrix[1];
r11 = matrix[5];
r12 = matrix[9];
r20 = matrix[2];
r21 = matrix[6];
r22 = matrix[10];

(2017-10-23, 4:43)Michael Horvath Wrote: One more question: does the calcRotationMatrix function rotate about the camera's axes or the universe's axes? It's supposed to rotate around the camera's x axis and the universe's y axis, according to the link I provided. Or does the function already take this into account?

(2017-10-23, 4:46)Michael Horvath Wrote: Should the function that does this be a member of TCVector?

Also, could you rewrite the function? I am not familiar with C++ syntax.

(2017-10-24, 4:42)Travis Cobbs Wrote: I'm not sure it will work, but try calculating how far you need to rotate around X for Y to point straight up. Store this in deltaY. Rotate around X by that amount, then rotate around Y by the desired X rotation amount, then rotate around X by -deltaY + the desired Y rotation amount.

Note that the X and Y rotations above are inverted intentionally. If you want to turn your head left or right (X rotation amount), you rotate around the Y axis. If you want to nod your head up and down (Y rotation amount), you rotate around the X axis.

(2017-10-24, 9:17)Michael Horvath Wrote:

(2017-10-24, 4:42)Travis Cobbs Wrote: I'm not sure it will work, but try calculating how far you need to rotate around X for Y to point straight up. Store this in deltaY. Rotate around X by that amount, then rotate around Y by the desired X rotation amount, then rotate around X by -deltaY + the desired Y rotation amount.

Note that the X and Y rotations above are inverted intentionally. If you want to turn your head left or right (X rotation amount), you rotate around the Y axis. If you want to nod your head up and down (Y rotation amount), you rotate around the X axis.

How do I determine the angle between the camera's orientation and the global "up" direction if the camera angles are always local? I'm assuming that "cameraXRotate" and "cameraYRotate" are just deltas and not cumulative amounts. I haven't figured out how to print or record the angles in VS yet for debugging purposes.

(2017-10-24, 9:17)Michael Horvath Wrote: I haven't figured out how to print or record the angles in VS yet for debugging purposes.

(2017-10-25, 5:32)Travis Cobbs Wrote: When you run LDView in debug mode, it opens a console windows for stdout output. Since you're not a C++ programmer, you might want to use std::cout to output debug stuff, since lots of people don't like printf. (Don't forget to #include <iostream> before trying to use std::cout.) Example:

Code:

#include <iostream>

using namespace std;

... blah ... blah ... blah ...
cout << "cameraXRotate: " << cameraXRotate << endl;

(2017-10-27, 1:36)Michael Horvath Wrote:

(2017-10-25, 5:32)Travis Cobbs Wrote: When you run LDView in debug mode, it opens a console windows for stdout output. Since you're not a C++ programmer, you might want to use std::cout to output debug stuff, since lots of people don't like printf. (Don't forget to #include <iostream> before trying to use std::cout.) Example:

Code:

#include <iostream>

using namespace std;

... blah ... blah ... blah ...
cout << "cameraXRotate: " << cameraXRotate << endl;

Where is the output written to?

(2017-10-27, 5:46)Travis Cobbs Wrote:

(2017-10-27, 1:36)Michael Horvath Wrote: Where is the output written to?

Output goes to the console window that LDView opens when a debug build is run. I mentioned that in my post.