RE: LDView 4.3 Released
2018-02-01, 6:59 (This post was last modified: 2018-02-01, 7:10 by Michael Horvath.)
2018-02-01, 6:59 (This post was last modified: 2018-02-01, 7:10 by Michael Horvath.)
(2018-02-01, 6:20)Travis Cobbs Wrote:(2018-02-01, 5:24)Michael Horvath Wrote: Could you add the basics, please? I am mainly a JavaScript and Lua scripter. All this C++ stuff is confusing.
1. A new button and icon for "FPS Mode"
2. Keyboard bindings WASD (move laterally, parallel to the XZ plane) and RF (float up/down, parallel to the Y axis)
The problem is that LDView's current design makes this significantly more difficult than it seems like it should be, and changing the design to make this work in an expected way would be a lot of work. The root problem is that while LDView does have the concept of a camera (which could easily be constrained to move horizontally), rotations don't happen by moving the camera around the model; instead the model itself is rotated. So, starting from the default viewing angle, moving forward is moving the camera purely horizontally, but it looks like the camera is moving down, since there is no unrotated reference frame to see that it is the model that is rotated to give that viewing angle. The existing fly-through mode works fine because the fact that the model happens to be rotated doesn't hurt anything.
For the "FPS Mode" that you want (which I would call "Walk Mode", given the pre-existing "Fly-Through Mode"), the model itself needs to not be rotated. Otherwise it appears to not be working. This is possible, but it's a whole lot more work than it seems like it should be.
Well, I got #2 working without problems in the beta. I skipped #1 intending to fix it later, but never got around to doing it. #3 is not urgent since the existing method is "good enough" for the time being.
Here is the executable so you can see it is working:
http://www.mediafire.com/file/4dv77m2p5l...180201.zip
Use the WASD and RF keys to move around. You need to turn on both the "Fly-through" and "FPS" modes at the same time in the menu (which needs to be corrected).